Getting Data In

Waiting for queued job to start

abdullahalhabba
Explorer

Hi Splunker;

Why the normal user when run search on search head servers getting message (Waiting for queued job to start.), why this message appear, please I need help you in that?

This message appear for normal user only not admin user.

Regards;

Tags (1)
0 Karma
1 Solution

renjith_nair
Legend

@abdullahalhabbash,

The number of concurrent searches for a user is defined by srchJobsQuota in Authorizeconf . For normal user its 3 by default and for role_admin it was around 50 (check in your authorize.conf in defaualt folder)

srchJobsQuota = <number>
* Maximum number of concurrently running historical searches a member of   this role can have.
* This excludes real-time searches, see rtSrchJobsQuota.
* Defaults to 3.

Also look at the cumulativeSrchJobsQuota

cumulativeSrchJobsQuota = <number>
* Maximum number of concurrently running historical searches in total
  across all members of this role
* Requires enable_cumulative_quota = true in limits.conf to take effect.
* If a user belongs to multiple roles, the user's searches count against 
  the role with the largest cumulative search quota. Once the quota for 
  that role is consumed, the user's searches count against the role with 
  the next largest quota, and so on.
* In search head clustering environments, this setting takes effect on a 
  per-member basis. There is no cluster-wide accounting.
---
What goes around comes around. If it helps, hit it with Karma 🙂

View solution in original post

0 Karma

abdullahalhabba
Explorer

@renjith.nair
Thank you for your reply, I will do that.
If appear the message another time I will tell you

0 Karma

renjith_nair
Legend

@abdullahalhabbash,

The number of concurrent searches for a user is defined by srchJobsQuota in Authorizeconf . For normal user its 3 by default and for role_admin it was around 50 (check in your authorize.conf in defaualt folder)

srchJobsQuota = <number>
* Maximum number of concurrently running historical searches a member of   this role can have.
* This excludes real-time searches, see rtSrchJobsQuota.
* Defaults to 3.

Also look at the cumulativeSrchJobsQuota

cumulativeSrchJobsQuota = <number>
* Maximum number of concurrently running historical searches in total
  across all members of this role
* Requires enable_cumulative_quota = true in limits.conf to take effect.
* If a user belongs to multiple roles, the user's searches count against 
  the role with the largest cumulative search quota. Once the quota for 
  that role is consumed, the user's searches count against the role with 
  the next largest quota, and so on.
* In search head clustering environments, this setting takes effect on a 
  per-member basis. There is no cluster-wide accounting.
---
What goes around comes around. If it helps, hit it with Karma 🙂
0 Karma

abdullahalhabba
Explorer

@renjith.nair
Thank you for your reply, I will do that.
If appear the message another time I will tell you

0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

May 2026 Splunk Expert Sessions: Security & Observability

Level Up Your Operations: May 2026 Splunk Expert Sessions Whether you are refining your security posture or ...

Network to App: Observability Unlocked [May & June Series]

In today’s digital landscape, your environment is no longer confined to the data center. It spans complex ...

SPL2 Deep Dives, AppDynamics Integrations, SAML Made Simple and Much More on Splunk ...

Splunk Lantern is Splunk’s customer success center that provides practical guidance from Splunk experts on key ...