Monitoring Splunk

Delete busy jobs in the cli

chris
Motivator

Hi

We recently had the situation, where the web interface was responding slowly and we had a high load on the system caused by splunk processes.

The following message was in splunkd.log:

WARN  DispatchCommand - The system is approaching the maximum number of historical searches that can be run concurrently. current=55 maximum=68  

We think this could be because the searches running concurrently cause the high load.

Is there a way to use the CLI to display how resource intensive jobs/searches are that are currently running and is there a way to kill/cancel/delete resource intensive jobs?

Thanks

Chris

0 Karma
1 Solution

Dark_Ichigo
Builder

To search for the Current jobs:

ps -ef | grep "splunkd search"

http://www.splunk.com/base/Documentation/latest/Admin/ManagejobsintheOS

To terminate, just kill the proccess ID

View solution in original post

Dark_Ichigo
Builder

To search for the Current jobs:

ps -ef | grep "splunkd search"

http://www.splunk.com/base/Documentation/latest/Admin/ManagejobsintheOS

To terminate, just kill the proccess ID

Dark_Ichigo
Builder

No worries 🙂

0 Karma

chris
Motivator

Thanks, it's: ps -ef | grep "splunkd search" can you change that in the response and I'll accept it.

0 Karma
Career Survey
First 500 qualified respondents will receive a $20 gift card! Tell us about your professional Splunk journey.

Can’t make it to .conf25? Join us online!

Get Updates on the Splunk Community!

Splunkbase Unveils New App Listing Management Public Preview

Splunkbase Unveils New App Listing Management Public PreviewWe're thrilled to announce the public preview of ...

Leveraging Automated Threat Analysis Across the Splunk Ecosystem

Are you leveraging automation to its fullest potential in your threat detection strategy?Our upcoming Security ...

Can’t Make It to Boston? Stream .conf25 and Learn with Haya Husain

Boston may be buzzing this September with Splunk University and .conf25, but you don’t have to pack a bag to ...