Hi.
I do not understand well the SHC config,
[raft_statemachine] disabled = <boolean> * Set to true to disable the raft statemachine. * This feature requires search head clustering to be enabled. * Any consensus replication among search heads uses this feature. * Default: true replicate_search_peers = <boolean> * Add/remove search-server request is applied on all members of a search head cluster, when this value to set to true. * Requires a healthy search head cluster with a captain.
What changes in a SHC by setting "disabled = true or false"? By default is true.
"replicate_search_peers = true" works only if disabled is false.
What does setting this to true or false do to the cluster?
The disabled setting in SHC only impacts captain election and member roster management.
https://en.m.wikipedia.org/wiki/Raft_(algorithm)
Without raft algorithm your captain election will not work properly. You might get away with static captain but it's not fault tolerant so if you lose your static captain your SHC will more or less fall apart.
I neved had problems with Captain Election, both with
[raft_statemachine] disabled = true
disabled = false
🤷
It's not the only factor in captain election. So just because you have raft enabled doesn't mean that your election will work properly.
Don't understand the question 🙄🙄🙄
I have a non clustered Indexing infrastructure (8 standalone indexers).
@sainag_splunk wrote:I don't think that required.
I decide what's required 😉and i want the SHC to replicate distsearch.conf 😉😉
My question was another, leave replicate_search_peers away,
What changes in a SHC by setting "disabled = true or false"? By default is true.
The disabled setting in SHC only impacts captain election and member roster management.
@sainag_splunk wrote:The disabled setting in SHC only impacts captain election and member roster management.
Ok, so it's minimal, and has ne real impact of cluster operativity 👍
Thanks 👍