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.

Sign up for GitHub

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

Jump to bottom

Recovery process is stuck with no recovered groups #1166

Closed
DifferentSC opened this issue Jul 3, 2018 · 0 comments · Fixed by #1167
Closed

Recovery process is stuck with no recovered groups #1166

DifferentSC opened this issue Jul 3, 2018 · 0 comments · Fixed by #1167
Assignees
@DifferentSC
Labels
bug

Comments

@DifferentSC
Copy link
Contributor

In RecoveryScheduler, when startRecovery() is called with no failed groups to recover, awaitUntilRecoveryFinish() is not signaled and thus any more recovery process cannot be performed.

We need to fix this problem.
@DifferentSC DifferentSC added the bug label Jul 3, 2018
@DifferentSC DifferentSC self-assigned this Jul 3, 2018
@DifferentSC DifferentSC mentioned this issue Jul 3, 2018
Merged
taegeonum pushed a commit that referenced this issue Jul 4, 2018
@DifferentSC @taegeonum
[MIST-1166] Handling recovery with no failed groups (#1167)
9c18321 
This PR closes #1166 via

* Set conditional variable when there is no failed groups in `RecoveryScheduler`.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@DifferentSC DifferentSC

Labels
bug
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

[MIST-1166] Handling recovery with no failed groups DifferentSC/mist-1
1 participant
@DifferentSC