You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
8.14.1 looks good, thanks @otoolep. Related but tangential question: is there a way to pass the nonvoters parameter to the nodes API when using the .nodes command from the CLI? Nothing major, just a tiny bit more convenient from a cluster diagnostics perspective.
What version are you running?
8.14.0
Are you using Docker or Kubernetes to run your system?
K8s
Are you running a single node or a cluster?
3 voters + 1 readonly -- or at least that's what was expected, but in practice it's 4 voters.
What did you do?
Deployed 3 voter nodes with the following (where
<N>
is the node number 0, 1 or 2):Then 1 read-only node with:
All nodes deployed and started concurrently from fresh state (empty data volume). Note that the read-only node gets
-raft-non-voter=true
.Full startup logs of rqlite-0 (current leader) and rqlite-readonly-0 are attached.
rqlite-readonly-0.log
rqlite-0.log
However the nodes list shows all nodes as being voters. This was run from
rqlite-0
(current leader) andrqlite-readonly-0
agrees:What did you expect to happen?
I expected rqlite-readonly-0 to show
voter: false
in the nodes output.Please include the Status, Nodes, and Expvar output from each node (or at least the Leader!)
Nodes list included above. The following is from
rqlite-0
(current leader):The text was updated successfully, but these errors were encountered: