Splunk Search

large delay between dispatch_time and scheduled_time in shc - SHCRepJob failed

schose
Builder

Hi forum,

we are facing large increasing delays between dispatch_time and scheduled_time in scheduler log. We see delays up to 200 seconds for searches which are scheduled every minute - resulting in not-scheduled searches.

this directly correlates to "ERROR SHCRepJob - failed to delegate job job=SHPDelegateSearchJob peer="peername", guid="466C6F6D-2779-4BFD-AE1F-64A71D0A5AC8" saved_search=system;; err="
messages we see at the SHC Captain.

Any hints? Other Single-Search-head instances do not show any issues. Using v.7.1.6

Best Regards,

Andreas

0 Karma

harsmarvania57
Ultra Champion

Hi,

Have you looked at scheduler.log on your Search Head Cluster Members ?

Below query will help you to identify why captain failed to delegate job to SHC members.

index=_internal host IN(SH1,SH2,SH3) sourcetype=scheduler status=delegated_remote_error
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 ...