Alerting

'Memory Usage on Splunk server

SabariRajanT
Path Finder

 

There are 3 indexer, In which CPU usage is 99.77, 99.72, 99.61 respectively.  Data is not getting indexed. any possible solution for this to resolve and troubleshoot?

 

Looking forward quick help

Labels (1)
0 Karma
1 Solution

burwell
SplunkTrust
SplunkTrust

Hmm. Have you looked at the Splunkd.log on these indexers? What else is running? Could it be there is so much searching there are no free cycles? Does /bar/log/messages offer any hints?

View solution in original post

0 Karma

burwell
SplunkTrust
SplunkTrust

Hmm. Have you looked at the Splunkd.log on these indexers? What else is running? Could it be there is so much searching there are no free cycles? Does /bar/log/messages offer any hints?

0 Karma

SabariRajanT
Path Finder

I see DatabaseDirectoryManager, BucketMover,CMSlave, IndexerIf, S2SFileReceiver under var/log/messages.

 

0 Karma

burwell
SplunkTrust
SplunkTrust

So what's your architecture? How much data are your indexers indexing each day? How many indexers do you have? Are there other indexers that are not having cpu issues?

I think a lot more info is needed here.

0 Karma

gjanders
SplunkTrust
SplunkTrust
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!

Fuel Your Journey: What’s Waiting for You at the .conf26 Acceleration Station

Navigating the show floor at .conf26 isn't just about keynotes and technical breakout sessions; it's also ...

Join the Final Session of the Data Management & Federation Bootcamp Series

Over the past three sessions of the Data Management & Federation Bootcamp Series, we've explored how to build ...

From Data to Insight: Announcing the Winners of the Splunk Dashboard Contest

Hi Splunkers, First off, thank you to everyone who participated in our very first From Data to Insight: The ...