vine: resolve uncertain temp availability issue #3694
Merged
btovar merged 1 commit intocooperative-computing-lab:masterfrom Mar 8, 2024
Merged
vine: resolve uncertain temp availability issue #3694btovar merged 1 commit intocooperative-computing-lab:masterfrom
btovar merged 1 commit intocooperative-computing-lab:masterfrom
Conversation
Contributor
Author
Member
|
This is a step in the right direction, however it may hide a root cause. When the manager stopped scheduling there were no tasks running, therefore there were no tasks running. Further, I waited for about 15min, so any transfer would have completed by then. Thus, either the replica had a pending state which will never progress to ready, or it is already ready and can't be found. Could it be that this is related to #3695 where a replica in the pending state is never removed after an invalid message? |
This file contains hidden or 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
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.
Proposed changes
Begin with a check to make sure a replica is ready to transfer when we decide the file is available
Post-change actions
Put an 'x' in the boxes that describe post-change actions that you have done.
The more 'x' ticked, the faster your changes are accepted by maintainers.
make testRun local tests prior to pushing.make formatFormat source code to comply with lint policies. Note that some lint errors can only be resolved manually (e.g., Python)make lintRun lint on source code prior to pushing.Additional comments
This section is dedicated to changes that are ambitious or complex and require substantial discussions. Feel free to start the ball rolling.