I noticed that when performing a rolling upgrade of search head cluster, it does not automatically transfercaptaincy to the first upgraded member. Based from https://docs.splunk.com/D...
...aptain. So, when I try to transfer it says
Failed to proxy call to member https://8089. ERROR: Invalid FROM mgmt_uri in transfercaptaincy request err="Deserialization failed. Could not find e...
...tatus -auth admin:xxxx
/opt/splunk/bin/splunk transfer shcluster-captain -mgmt_uri https://searchhead1.xxx.com:8089 -auth admin:xxxxx
So kindly let me know whether, we need to execute the above c...
The log is repeating at sub-second intervals:
2017-10-27T20:44:53.389Z I REPL [ReplicationExecutor] Error in heartbeat request to shccaptain:8191; InvalidReplicaSetConfig Our replica set conf...
In the last patch operation on our ITSI cluster of three SHs, we had syncing issues with the SHs. What can be a good sequence of operations when applying an OS patch on the cluster's servers?
The splunkd.log file on a search head cluster member shows 450K of this type of error:
05-01-2016 18:42:15.010 -0400 WARN SHPMaster - did not schedule removal for peer='E984FB44-0D11-4B0B-ABBF-95...
Hi,
We had some search heads in a cluster, running on VMs. A couple of the VMs were deleted without properly removing the search heads from the search head cluster first. Now, Splunk is complainin...
After pushing a new shcluster bundle, the shcluster self-initiated a rolling restart. We have 15 servers in this cluster. 5 completed the restart at some point after the "splunk rolling-restart shcl...
Any recommendations on what order and how to upgrade the instances from 6.4.0 to 6.4.4. I currently have the following instances: 1 Deployment Server 1 Cluster Master (Also the license Master) 4 I...
EDIT: This is still an issue in Splunk 6.4
I'm noticing that over time, my SHC captain starts favoring one cluster node over the others for scheduled job delegation. After a cluster restart, the...