https://discuss.elastic.co/t/kubernetes-watch-connection-never-close-when-inputreload-create-runner-failed/180112
run filebeat in kubernetes cluster ad set input reload true,when reload start runner failed but the kubernetes processor have already started a watch, after ten seconds reload will try start runner again failed, at last it will keep a lot of connection with kube-apiserver, in my case, the number of connections create by filebeat have been more than 10000, and lead to kube-apiserver cost 10G memory.