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
Get Updates on the Splunk Community!

Stay Connected: Your Guide to May Tech Talks, Office Hours, and Webinars!

Take a look below to explore our upcoming Community Office Hours, Tech Talks, and Webinars this month. This ...

They're back! Join the SplunkTrust and MVP at .conf24

With our highly anticipated annual conference, .conf, comes the fez-wearers you can trust! The SplunkTrust, as ...

Enterprise Security Content Update (ESCU) | New Releases

Last month, the Splunk Threat Research Team had two releases of new security content via the Enterprise ...