go.mod: bump etcd/raft to pick up probing improvements #60581
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
This change is |
|
Looks like you might need to run |
tbg
force-pushed
the
bump-raft-probing
branch
from
81c6fda
to
97a1ccf
Compare
nvanbenschoten
approved these changes
Feb 16, 2021
This picks up this PR: etcd-io/etcd#11964 There were no other code changes affecting raft. Release note (bug fix): fixed a deficiency in the replication layer that could result in ranges becoming unavailable for prolonged periods of time (hours) when a write burst occurred under system overload. While unavailable, the range status page for the affected range would show a last index much larger than the committed index and no movement in these indexes on a quorum of the replicas. Note that this should be distinguished from the case in which enough replicas are offline to constitute a loss of quorum, where the replication layer can not make progress due to the loss of quorum itself.
tbg
force-pushed
the
bump-raft-probing
branch
from
97a1ccf
to
a7880d3
Compare
|
bors r=nvanbenschoten |
|
Build failed (retrying...): |
|
Build failed (retrying...): |
|
Build succeeded: |
This was referenced Feb 16, 2021
tbg
added a commit
to tbg/cockroach
that referenced
this pull request
Mar 25, 2021
This picks up the fix in cockroachdb#60581. Since this is the first time on this branch to pick up a version of raft that post-dates its move to a Go module, there is a large diff, very similar to cockroachdb#56233. Release note (bug fix): fixed a deficiency in the replication layer that could result in ranges becoming unavailable for prolonged periods of time (hours) when a write burst occurred under system overload. While unavailable, the range status page for the affected range would show a last index much larger than the committed index and no movement in these indexes on a quorum of the replicas. Note that this should be distinguished from the case in which enough replicas are offline to constitute a loss of quorum, where the replication layer can not make progress due to the loss of quorum itself. /cc @cockroachdb/release
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This picks up this PR:
etcd-io/etcd#11964
There were no other code changes affecting raft.
Release note (bug fix): fixed a deficiency in the replication layer
that could result in ranges becoming unavailable for prolonged periods
of time (hours) when a write burst occurred under system overload.
While unavailable, the range status page for the affected range would
show a last index much larger than the committed index and no movement
in these indexes on a quorum of the replicas. Note that this should
be distinguished from the case in which enough replicas are offline
to constitute a loss of quorum, where the replication layer can not
make progress due to the loss of quorum itself.