-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
Set replication metric to 0 when losing leadership #20665
Set replication metric to 0 when losing leadership #20665
Conversation
This pull request has been automatically flagged for inactivity because it has not been acted upon in the last 60 days. It will be closed if no new activity occurs in the next 30 days. Please feel free to re-open to resurrect the change if you feel this has happened by mistake. Thank you for your contributions. |
9e3747e
to
b9ef886
Compare
Hi there. There's one other place that needs a similar change to fixup the rest of the replicators (like for config entries). For historical reasons there are two versions of the replicators, the ACL ones and the common plumbing for the rest. You fixed the former in this PR so far and the other is in this area: https://github.com/hashicorp/consul/blob/main/agent/consul/replication.go#L156 You can see the pairing of status/index normally being set down here https://github.com/hashicorp/consul/blob/main/agent/consul/leader.go#L797 so you'll just have to repeat the fix in this one place and it should be good. |
Hi @rboyer, I made the change you suggested. |
This pull request has been automatically flagged for inactivity because it has not been acted upon in the last 60 days. It will be closed if no new activity occurs in the next 30 days. Please feel free to re-open to resurrect the change if you feel this has happened by mistake. Thank you for your contributions. |
d98299b
to
b6f60eb
Compare
b6f60eb
to
74a6463
Compare
📣 Hi @jorgemarey! a backport is missing for this PR [20665] for versions [1.15,1.17,1.18] please perform the backport manually and add the following snippet to your backport PR description:
|
4 similar comments
📣 Hi @jorgemarey! a backport is missing for this PR [20665] for versions [1.15,1.17,1.18] please perform the backport manually and add the following snippet to your backport PR description:
|
📣 Hi @jorgemarey! a backport is missing for this PR [20665] for versions [1.15,1.17,1.18] please perform the backport manually and add the following snippet to your backport PR description:
|
📣 Hi @jorgemarey! a backport is missing for this PR [20665] for versions [1.15,1.17,1.18] please perform the backport manually and add the following snippet to your backport PR description:
|
📣 Hi @jorgemarey! a backport is missing for this PR [20665] for versions [1.15,1.17,1.18] please perform the backport manually and add the following snippet to your backport PR description:
|
* Set replication metric to 0 when losing leadership * Fix replication metrics on replication.go also --------- Co-authored-by: sarahalsmiller <[email protected]>
Fixes #11377 (comment)
When the leader changes the replication metrics on the old leader (now follower) keeps reporting 1. This PR fixes that issue.