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

Only DU/DD accepted by the restarted node should be cancelled #8534

Open
Lyndon-Li opened this issue Dec 19, 2024 · 3 comments
Open

Only DU/DD accepted by the restarted node should be cancelled #8534

Lyndon-Li opened this issue Dec 19, 2024 · 3 comments

Comments

@Lyndon-Li
Copy link
Contributor

At present, when a node-agent pod restarts, all DU/DD in Accepted phase are cancelled.
We may be able to enhance this as we have recorded the accepted node in DUCR/DDCR as of #8498

@dharanui
Copy link

dharanui commented Dec 23, 2024

Also @Lyndon-Li , can you confirm if any new node-agent pod comes up(not restart) due to a new node creation during the time of backup, will it still cancel? Asking this because we had cancellation of datauploads and no restart was observed, except new node-agent creation.

@SCLogo
Copy link

SCLogo commented Dec 23, 2024

We saw the same. We use spit instances. In log I see only new nodes and no agent restarts

@Lyndon-Li
Copy link
Contributor Author

can you confirm if any new node-agent pod comes up(not restart) due to a new node creation during the time of backup, will it still cancel?

I think so, the checks happen during node-agent starts.

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

No branches or pull requests

3 participants