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
Career Survey
First 500 qualified respondents will receive a $20 gift card! Tell us about your professional Splunk journey.
Get Updates on the Splunk Community!

Tech Talk Recap | Mastering Threat Hunting

Mastering Threat HuntingDive into the world of threat hunting, exploring the key differences between ...

Observability for AI Applications: Troubleshooting Latency

If you’re working with proprietary company data, you’re probably going to have a locally hosted LLM or many ...

Splunk AI Assistant for SPL vs. ChatGPT: Which One is Better?

In the age of AI, every tool promises to make our lives easier. From summarizing content to writing code, ...