From a3224f0245cd7ce0972f57a83ca1218d77f4e2ec Mon Sep 17 00:00:00 2001 From: Ginger Collison Date: Tue, 9 Feb 2021 16:50:24 -0600 Subject: [PATCH] updates based on RI updates to README 020921 --- jetstream/clustering/administration.md | 16 ++++++++++++++-- 1 file changed, 14 insertions(+), 2 deletions(-) diff --git a/jetstream/clustering/administration.md b/jetstream/clustering/administration.md index 941ee69..92efe7f 100644 --- a/jetstream/clustering/administration.md +++ b/jetstream/clustering/administration.md @@ -32,9 +32,9 @@ The `current` indicates that followers are up to date and have all the messages, The replica count cannot be edited once configured. -## Forcing leader election +## Forcing Stream and Consumer leader election -Every RAFT group has a leader that's elected by the group when needed. Generally there is no reason to interfere with this process but you might want to trigger a leader change at a convenient time. Leader elections will represent short interruptions to the stream so if you know you will work on a node later it might be worth moving leadership away from it ahead of time. +Every RAFT group has a leader that's elected by the group when needed. Generally there is no reason to interfere with this process, but you might want to trigger a leader change at a convenient time. Leader elections will represent short interruptions to the stream so if you know you will work on a node later it might be worth moving leadership away from it ahead of time. Moving leadership away from a node does not remove it from the cluster and does not prevent it from becoming a leader again, this is merely a triggered leader election. @@ -53,6 +53,18 @@ Cluster Information: Replica: n3-c1, current, seen 0.12s ago ``` +The same is true for consumers, `nats consumer cluster step-down ORDERS NEW`. + +#### Forcing Meta Group leader election + +Similar to Streams and Consumers above the Meta Group allows leader stand down. The Meta Group is cluster wide and spans all accounts, therefore to manage the meta group you have to use a `SYSTEM` user. + +```nohighlight +$ nats server raft step-down --user system +17:44:24 Current leader: n2-c2 +17:44:24 New leader: n1-c2 +``` + ## Evicting a peer Generally when shutting down NATS, including using Lame Duck Mode, the cluster will notice this and continue to function. A 5 node cluster can withstand 2 nodes being down.