Monitoring Splunk

PipelineComponent CallbackRunnerThread is unusually busy

hellosplunkit
Loves-to-Learn

Hi Splunker,

I found the following abnormal problems when checking the Splunk system

 

 

04-07-2021 05:54:18.961 +0800 INFO  PipelineComponent - CallbackRunnerThread is unusually busy,  this may cause service delays: time_ms=0 new=0 null=0 total=2119 {'name':'DistributedRestCallerCallback','valid':'1','null':'0','last':'3','time_ms':'0'},{'name':'HTTPAuthManager:timeoutCallback','valid':'1','null':'0','last':'1','time_ms':'0'},{'name':'HttpInputMetrics:timerCallback','valid':'2','null':'0','last':'2113','time_ms':'0'},{'name':'IndexProcessor:ipCallback-0','valid':'1','null':'0','last':'6','time_ms':'0'},{'name':'MetricsManager:probeandreport','valid':'1','null':'0','last':'0','time_ms':'0'},{'name':'PullBasedPubSubSvr:timerCallback','valid':'1','null':'0','last':'2','time_ms':'0'},{'name':'ThreadedOutputProcessor:timerCallback','valid':'1','null':'0','last':'5','time_ms':'0'},{'name':'triggerCollection','valid':'2111','null':'0','last':'2118','time_ms':'0'}
04-07-2021 05:55:19.961 +0800 INFO  PipelineComponent - CallbackRunnerThread is unusually busy,  this may cause service delays: time_ms=0 new=0 null=0 total=2119 {'name':'DistributedRestCallerCallback','valid':'1','null':'0','last':'3','time_ms':'0'},{'name':'HTTPAuthManager:timeoutCallback','valid':'1','null':'0','last':'1','time_ms':'0'},{'name':'HttpInputMetrics:timerCallback','valid':'2','null':'0','last':'2113','time_ms':'0'},{'name':'IndexProcessor:ipCallback-0','valid':'1','null':'0','last':'6','time_ms':'0'},{'name':'MetricsManager:probeandreport','valid':'1','null':'0','last':'0','time_ms':'0'},{'name':'PullBasedPubSubSvr:timerCallback','valid':'1','null':'0','last':'2','time_ms':'0'},{'name':'ThreadedOutputProcessor:timerCallback','valid':'1','null':'0','last':'5','time_ms':'0'},{'name':'triggerCollection','valid':'2111','null':'0','last':'2118','time_ms':'0'}

 

 

I don't know what caused it.Which part should I start to find out the reason.

Labels (1)
0 Karma

burwell
SplunkTrust
SplunkTrust

Hi @hellosplunkit Did you ever figure out what caused this error?

I see it on one busy indexer.

Tags (1)
0 Karma
Get Updates on the Splunk Community!

Detecting Remote Code Executions With the Splunk Threat Research Team

WATCH NOWRemote code execution (RCE) vulnerabilities pose a significant risk to organizations. If exploited, ...

Enter the Splunk Community Dashboard Challenge for Your Chance to Win!

The Splunk Community Dashboard Challenge is underway! This is your chance to showcase your skills in creating ...

.conf24 | Session Scheduler is Live!!

.conf24 is happening June 11 - 14 in Las Vegas, and we are thrilled to announce that the conference catalog ...