Hi,
We have a search head cluster with 3 search heads -
We are seeing the following message and a decent skip ratio on DMC.
priority=default, status=skipped, reason="The maximum number of concurrent running jobs for this historical scheduled search on this cluster has been reached", concurrency_category="historical_scheduled", concurrency_context="saved-search_cluster-wide", concurrency_limit=1
This might be the way it is designed to run searches - only in one search head at a given time. If it turns out to be a bug, please mention how we can fix this.
regards
Pramodh
... View more