Deployment Architecture

Failed to Register with Cluster Master

venkateshparank
Path Finder

WARN CMSlave - Failed to register with cluster master reason: failed method=POST path=/services/cluster/master/peers/?output_mode=json master=clustermaster.domain.com:8089 rv=0 gotConnectionError=0 gotUnexpectedStatusCode=1 actual_response_code=500 expected_response_code=2xx status_line="Internal Server Error" socket_error="No error" remote_error=Cannot add peer=<IP> mgmtport=8089 (reason: bucket already added as clustered, peer attempted to add again as standalone. guid=F4204358-8FF9-4DD2-A09B-A0B51735559B bid= catch_all~747~F4204358-8FF9-4DD2-A09B-A0B51735559B). [ event=addPeer status=retrying 

Labels (2)
0 Karma

richgalloway
SplunkTrust
SplunkTrust
Thank you for sharing. Do you have a question?
---
If this reply helps you, an upvote would be appreciated.
0 Karma

venkateshparank
Path Finder

How to fix that error.

0 Karma

richgalloway
SplunkTrust
SplunkTrust
It's not an error, it's just a warning.
Are you seeing this message often? How often?
Did you do anything on the indexer cluster prior to the message appearing?
---
If this reply helps you, an upvote would be appreciated.
0 Karma

venkateshparank
Path Finder

Peer node is not adding to Cluster.

When we check the logs in Indexer, we saw above warn.

0 Karma

richgalloway
SplunkTrust
SplunkTrust
The message indicates the new indexer has a bucket that already exists on another indexer. That shouldn't happen. Do you know the history of the new indexer?
---
If this reply helps you, an upvote would be appreciated.
0 Karma
Did you miss .conf21 Virtual?

Good news! The event's keynotes and many of its breakout sessions are now available online, and still totally FREE!