All Apps and Add-ons

Splunk App for VMware: "ERROR [HydraWorkerNode] Incorrect number of heads" - Any idea what could cause this?

Plotkowski
Path Finder

I am trying to set up the Splunk App for VMware
I installed the DCN from the .ova, installed the VMware app on my indexer/search head.

Credentials are correct, green ticks everywhere.
But when I run the scheduler, I get error messages from the hydraworker:

ERROR [ta_vmware_collection_scheduler://puff] [HydraWorkerNode] Incorrect number of heads=3 on node=https://XXX:8089, actual_heads=2, trying to bring number up to correct value

The value for actual_heads is sometimes different (0, 1, or 2)
No matter what value I set at "worker processes" for the DCN, I always get these errors and no data is coming in at all.

Do you have any idea what could cause this problem? Is number of heads the number of CPU cores allocated to the virtual machine DCN?

0 Karma

kserra_splunk
Splunk Employee
Splunk Employee

The number of worker process should be set to , # of cpu cores - 1

0 Karma

trapti_splunk
Splunk Employee
Splunk Employee

Is your Data Collection Node added as DCN from multiple schedulers? Or is it acting as DCN for multiple apps?

0 Karma

Plotkowski
Path Finder

Only 1 DCN, 1 scheduler and only VMWare app.

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!

Automated Threat Analysis: Available in ES Premier

Automated Threat Analysis: Centralize and Accelerate Phishing Investigations in Splunk Enterprise ...

What’s New in Splunk AI: Volume 02

Welcome to the second edition of “What’s New in Splunk AI” where we look at the latest and greatest updates, ...

Best Practices: Splunk auto adjust pipeline queue

When you enable autoAdjustQueue in Splunk, maxSize should be understood as the queue size Splunk starts with ...