-
Notifications
You must be signed in to change notification settings - Fork 379
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
If WaitForMastership fails log_signer sits around doing nothing #1150
Comments
Hi Roland, thanks for filing this. I am working right now on factoring out the election runner, and also noticed this issue. I have a work-in-progress PR that largely interferes with this code. Would you like to review that? |
Ah cool, I'll take a look, thanks! |
Did #1144 fix your issue? |
No, that was a refactoring, and it ended up postponed. |
This is effectively fixed now. Election code has migrated to util/election (types |
No, actually the problem seems to be still there: trillian/log/operation_manager.go Line 242 in 85d73fd
|
If the call to
WaitForMastership
fails inelectionRunner.Run
it returns from the function and sits around doing nothing for that log (i.e.masterFor
calls will always return empty and nothing can be done). This can be triggered by recoverable intermittent etcd issues.The
return
should either be replaced withcontinue
(perhaps with a backoff?) when hitting errors fromWaitforMastership
or theelectionRunner
should be removed froml.electionRunner[logID]
when it exits so a new election goroutine can be created the next timemasterFor
is called. I'd probably go for the first of the two options.The text was updated successfully, but these errors were encountered: