Because both `add_member` and `grow` default to Membership status `promotable`, new members will have to catch up before they are considered cluster members. This can be overridden with either `voter` or (permanent `non_voter` statuses. The latter one is useless without additional tooling so kept undocumented. - non-voters do not affect quorum size for election purposes - `observer_cli` reports their status with lowercase 'f' - `rabbitmq-queues check_if_node_is_quorum_critical` takes voter status into account |
||
|---|---|---|
| .. | ||
| add_member_command_test.exs | ||
| check_if_node_is_mirror_sync_critical_command_test.exs | ||
| check_if_node_is_quorum_critical_command_test.exs | ||
| delete_member_command_test.exs | ||
| grow_command_test.exs | ||
| peek_command_test.exs | ||
| quorum_status_command_test.exs | ||
| reclaim_quorum_memory_command_test.exs | ||
| shrink_command_test.exs | ||
| stream_status_command_test.exs | ||