Not registering deadline when the current label failed #718
Labels
bug
Something isn't working
Comments
enescakir
added a commit
that referenced
this issue
Oct 17, 2023
We have a known issue #718. If the label that we register deadline fails, we can't persist the deadline information to the strand's stack. When there is no space left, an exception is raised, preventing the vm strand from saving the deadline. We don't receive pages due to slow provisioning if the delay is caused by capacity issues. I moved the deadline registration to a different label until we find an elegant solution for issue #718.
enescakir
added a commit
that referenced
this issue
Oct 17, 2023
We have a known issue #718. If the label that we register deadline fails, we can't persist the deadline information to the strand's stack. When there is no space left, an exception is raised, preventing the vm strand from saving the deadline. We don't receive pages due to slow provisioning if the delay is caused by capacity issues. I moved the deadline registration to a different label until we find an elegant solution for issue #718.
enescakir
added a commit
that referenced
this issue
Oct 18, 2023
We have a known issue #718. If the label that we register deadline fails, we can't persist the deadline information to the strand's stack. When there is no space left, an exception is raised, preventing the vm strand from saving the deadline. We don't receive pages due to slow provisioning if the delay is caused by capacity issues. I moved the deadline registration to a different label until we find an elegant solution for issue #718.
enescakir
added a commit
that referenced
this issue
Oct 19, 2023
We have a known issue #718. If the label that we register deadline fails, we can't persist the deadline information to the strand's stack. If destroy or start_after_host_reboot fails for some reasons, we will not get a page.
enescakir
added a commit
that referenced
this issue
Oct 19, 2023
We have a known issue #718. If the label that we register deadline fails, we can't persist the deadline information to the strand's stack. If destroy or start_after_host_reboot fails for some reasons, we will not get a page.
enescakir
added a commit
that referenced
this issue
Oct 21, 2023
We have a known issue #718. If the label that we register deadline fails, we can't persist the deadline information to the strand's stack. If destroy or start_after_host_reboot fails for some reasons, we will not get a page.
enescakir
added a commit
that referenced
this issue
Oct 21, 2023
We have a known issue #718. If the label that we register deadline fails, we can't persist the deadline information to the strand's stack. If destroy or start_after_host_reboot fails for some reasons, we will not get a page.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When the label that we register deadline fails, we don't persist deadline because we run strand in a
DB.transaction. So it's not committing strand's stack.The text was updated successfully, but these errors were encountered: