...", user="admin", app="", savedsearch_name="", priority=default, status=skipped, reason="The maximum number of concurrent running jobs for this historical scheduledsearch on this cluster has b...
...hatOneGuyCausingProblemsForMe", app="myApp", savedsearch_name="Pull: Pull Domain IOCs from MISP", priority=default, status=skipped, reason="The maximum number of concurrent running jobs for this historical scheduledsearch o...
...avedSplunker - The maximum number of concurrentscheduledsearches has been reached (limits: historical=132, realtime=132). historical=233, realtime=0 ready-to-run scheduledsearches are pending.
host = i...
The concurrency limit is set to five based on the below log.
We are using a 4 core CPU, and according to the limits.conf, shouldn't the limit be 10 concurrentsearches(6+4*1)?
B...
...aximum number of concurrent historical scheduledsearches on this instance has been reached
The maximum number of concurrent running jobs for this historical scheduledsearch on this instance has been r...
...avedsearch_name="JBoss7 OutOfMemory Alert", priority=default, status=skipped, reason="The maximum number of concurrent historical scheduledsearches on this instance has been reached", concurr...
...t has the forwarder license.
After looking in some logs I am now seeing these errors:
02-08-2011 19:15:01.011 WARN SavedSplunker - Maximum number (1) of concurrentscheduledsearches reached. 1 r...
I was wondering... how are foreach-generated searches treated regarding the searcheslimits? I mean - normally you have your maximum number of concurrentsearchesset in your limits.conf - it can a...
...imilar issue was faced by us earlier forscheduled saved searches and we had fixed the issue by assigning the owner of saved searches as "admin", increasing concurrency limitsfor "admin" and r...
...he following errors in my splunkd.log:
WARN SavedSplunker - Maximum number
(2) of concurrentscheduledsearches
reached. 16 ready-to-run scheduledsearches pending.
Can I tune s...