Dedicated voting-only master nodes and repository access

Christian_Dahlqvist · August 18, 2021, 8:14am

If I am deploying an Elasticsearch cluster across 2 on-premise data centres and want to place a dedicated voting-only master node in the cloud as an arbiter, would the dedicated voting-only master node still need access to and validate snapshot repositories? Would this depend on the repository type?

DavidTurner · August 18, 2021, 5:07pm

It shouldn't, but prior to 7.9.0 it did:

github.com/elastic/elasticsearch

Do not access snapshot repo on dedicated voting-only master node

elastic:master ← ywelsch:no-repo-access-on-dedicated-voting-only-node

opened 10:23AM - 12 Aug 20 UTC

ywelsch

+120 -3

Today a snapshot repository verification ensures that all master-eligible and da…ta nodes have write access to the snapshot repository (and can see each other's data) since taking a snapshot requires data nodes and the currently-elected master to write to the repository. However, a dedicated voting-only master-eligible node is not a data node and will never be the elected master so we should not require it to have write access to the repository. Closes #59649

Also there was a bug in this area fixed in 7.12.1:

github.com/elastic/elasticsearch

Fix isDedicatedVotingOnlyNode

elastic:master ← DaveCTurner:2021-04-06-fix-isDedicatedVotingOnlyNode

opened 03:59PM - 06 Apr 21 UTC

DaveCTurner

+9 -4

Today we incorrectly consider a data-containing voting-only node as a dedicated… voting-only node if it does not have the `data` role, because we check specifically for the `data` role rather than using `DiscoveryNodeRole::canContainData`. This means that such nodes don't get involved with snapshots, but they should. This commit fixes that. Closes #71352

No.

system · September 15, 2021, 5:08pm

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.