logstash ,it published on a server alone
there are eight worker processes hogging the cpu:
%cup command
100.2 [main] > worker0
100.2 [main] > worker2
100.2 [main] > worker5
99.9 [main] > worker1
99.9 [main] > worker3
99.9 [main] > worker4
99.9 [main] > worker6
99.9 [main] > worker7
Logstah:insertToolong queue and the pipeline is blocked,temporary refusing new connection
the kopf of elasticsearch :
load average: 0.0
cpu% : 2.0
heap useage % : 44.0