Skip to content
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

fix(Snapshot): Improve snapshot handling #7841

Closed
wants to merge 1 commit into from

Conversation

manishrjain
Copy link
Contributor

@manishrjain manishrjain commented May 21, 2021

Monitor for stuck snapshots in both directions, sender and receiver. If any of them is stuck for a while, cancel snapshot transfer.


This change is Reviewable

@CLAassistant
Copy link

CLAassistant commented Apr 29, 2022

CLA assistant check
All committers have signed the CLA.

Copy link

github-actions bot commented Aug 2, 2024

This PR has been stale for 60 days and will be closed automatically in 7 days. Comment to keep it open.

@github-actions github-actions bot added the Stale label Aug 2, 2024
@github-actions github-actions bot closed this Aug 10, 2024
@harshil-goel harshil-goel reopened this Aug 11, 2024
@harshil-goel harshil-goel requested a review from a team as a code owner August 11, 2024 18:40
@github-actions github-actions bot removed the Stale label Aug 12, 2024
@@ -912,13 +912,19 @@ func (n *node) retrieveSnapshot(snap pb.Snapshot) error {
var pool *conn.Pool
addr := snap.Context.GetAddr()
glog.V(2).Infof("Snapshot.RaftContext.Addr: %q", addr)
if len(addr) > 0 {
if addr == n.MyAddr {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

won't we always steam from leader to follower? And what happens when we skip it?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

4 participants