Deployment Architecture

How can I resolve this error I get from adding a new search head to my indexer clustering environment?

daniel_splunk
Splunk Employee
Splunk Employee

After I added a new search head to my indexer cluster environment, I started getting "Error = 'Couldn't deserialize, err=Deserialization failed parsing unsigned long long"

The searchhead is unable to update the peer information. Error = 'Couldn't deserialize, err=Deserialization failed parsing unsigned long long. key=num_buckets not found in json={"cluster_label":"00000000-0000-0000-0000-000000000001","eai:acl":null,"generation_id":839,"generation_peers":
0 Karma
1 Solution

daniel_splunk
Splunk Employee
Splunk Employee

You are getting that error because Splunk has strict versioning requirements within indexer clustering.

The cluster Master Node version must be greater than or equal to the Search Head.
The Search Head version must be greater than or equal to Search Peers.
ie. CM version => SH version => peers version

View solution in original post

daniel_splunk
Splunk Employee
Splunk Employee

You are getting that error because Splunk has strict versioning requirements within indexer clustering.

The cluster Master Node version must be greater than or equal to the Search Head.
The Search Head version must be greater than or equal to Search Peers.
ie. CM version => SH version => peers version

Get Updates on the Splunk Community!

More Ways To Control Your Costs With Archived Metrics | Register for Tech Talk

Tuesday, May 14, 2024  |  11AM PT / 2PM ET Register to Attend Join us in this Tech Talk and learn how to ...

.conf24 | Personalize your .conf experience with Learning Paths!

Personalize your .conf24 Experience Learning paths allow you to level up your skill sets and dive deeper ...

Threat Hunting Unlocked: How to Uplevel Your Threat Hunting With the PEAK Framework ...

WATCH NOWAs AI starts tackling low level alerts, it's more critical than ever to uplevel your threat hunting ...