-
Notifications
You must be signed in to change notification settings - Fork 11
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
New computations is starving in init stage #1637
Comments
A workaround is to force mills to override the Computation order and pick up init Computations by changing the creation time. Use the spanner sql query against all Duchies:
The To revert the modification of CreationTime:
|
renjiezh
added a commit
that referenced
this issue
Jul 15, 2024
SanjayVas
pushed a commit
that referenced
this issue
Jul 16, 2024
Resolved by #1673 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
While duchy mills are busy on computing, new computations will stuck in init stage until all old computations are complete. This prevent EDPs from fulfilling requisitions of new computations.
Steps to reproduce
Component(s) affected
Duchy, EDP
Version
v0.5.5
Environment
halo-cmm-qa
Additional context
According to experiments, new computations only stuck at aggregator but not at worker 1.
The text was updated successfully, but these errors were encountered: