Monitoring Splunk

Splunk reports wrong cpu count

vanvan
Path Finder

Hi,

We are running Splunk on RedHat 7.x VMs and originally the VMs had 2 cpus with 2 cores each. In DMC and in REST service "| rest splunk_server=local /services/server/info" the output is that we have 4 cores in total. Recently we've upgraded the VMs to have 4 cpus and we were expecting to see that we'll have 8 cores available in total. But it doesn't seem so.

Any ideas why? We have restarted Splunkd and the whole VM. The outputs of linux commands in SSH like "lscpu" or "cat /proc/cpuinfo" show that there are 4 cpu's installed in the VM, but Splunkd still doesn't notice them...

Euphrates
Engager

I am experiencing identical problem. Haven't been able to find answer online nor get in contact with Splunk support. Splunk isn't noticing my extra cores after I upgraded instance. Now I'm having performance issues like hot buckets rolling prematurely and the speed of concurrent searches is suffering.

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!

Announcing Modern Navigation: A New Era of Splunk User Experience

We are excited to introduce the Modern Navigation feature in the Splunk Platform, available to both cloud and ...

Kubernetes Alerts That Work Out of the Box with AutoDetect detectors in Splunk ...

A deployment rolls out slowly, one pod sits not ready for a few minutes, and whoever is on call gets an alert ...

Observability at Your Fingertips Directly From Splunk Platform—for Free

At .conf, we announced our roadmap to bring observability foundations to Splunk Platform. Bringing metrics and ...