-
Notifications
You must be signed in to change notification settings - Fork 215
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cluster not able to reach quorum with single master. #100
Comments
Upvoting this - essentially adding support in the operator for discovery.type: single-node which is already supported in opensearch. |
Possible workaround for you that I got working with a single node cluser was to add: nodePools:
- component: masters
additionalConfig:
discovery.seed_hosts: <cluster-name>-masters-0
cluster.initial_master_nodes: <cluster-name>-masters-0
replicas: 1 I'm not sure if you will have to add that to each component group or not. |
Fixed |
When I adding the additional config the security update does not run successfully: `OpenSearch Security not initialized.************************************************************************** Security Admin v7 |
When creating a single master cluster the, get an error as
master not discovered or elected yet
Cluster.yaml
Log:
master not discovered or elected yet, an election requires a node with id [zs52XaaoT0mHtvYMg3N_Aw], have discovered [{os-logs-master-0}{T08PHfy_TgOcFmrxp8t-Xg}{G4DypmTBQn63VlsqqgI7fw}{os-logs-master-0}{192.168.20.231:9300}{m}{shard_indexing_pressure_enabled=true}] which is not a quorum; discovery will continue using [192.168.39.238:9300, 192.168.50.75:9300] from hosts providers and [{os-logs-bootstrap-0}{zs52XaaoT0mHtvYMg3N_Aw}{0NSI6IQXSEqq-0WJv0bICQ}{os-logs-bootstrap-0}{192.168.4.104:9300}{m}{shard_indexing_pressure_enabled=true}, {os-logs-master-0}{T08PHfy_TgOcFmrxp8t-Xg}{G4DypmTBQn63VlsqqgI7fw}{os-logs-master-0}{192.168.20.231:9300}{m}{shard_indexing_pressure_enabled=true}] from last-known cluster state; node term 1, last-accepted version 29 in term 1
Cause:
It's because the operator spin up a cluster with effectively 2 master nodes, then remove the initial master which causes quorum problems.
Possible solution to fix:
Before removing the operator has to make sure that the bootstrap node should not be part of the voting configuration.
The text was updated successfully, but these errors were encountered: