-
Notifications
You must be signed in to change notification settings - Fork 810
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
Add timeout for waiting on compactor to become ACTIVE in the ring. #4262
Conversation
Signed-off-by: Albert <[email protected]>
Signed-off-by: Albert <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for working on this! Given this PR tries to address #3914, I think a timeout is just fine. You can test a deadline on the context passed to ring.WaitInstanceState
and that should be enough.
Signed-off-by: Albert <[email protected]>
Signed-off-by: Albert <[email protected]>
Signed-off-by: Albert <[email protected]>
Signed-off-by: Albert <[email protected]>
Signed-off-by: Albert <[email protected]>
Signed-off-by: Albert <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the PR! It's broadly ok, but a couple of style points.
It looks to me like the tests you've added test similar code, rather than the code you added. If I'm right, could you test the actual code?
What is the user experience if the timeout is hit? Do they see anything in the logs to let them know what happened?
Signed-off-by: Albert <[email protected]>
Signed-off-by: Albert <[email protected]>
I added tests to actually test the starting of the compactor. I also added some logging as to make it clear to why the compactor failed to start. |
Sorry but we have begun the process of cutting a new release; please rebase from |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good job and thanks for addressing my feedback. Way easier than the initial version. I left few last comments 🙏
Signed-off-by: Albert <[email protected]>
Signed-off-by: Albert <[email protected]>
Signed-off-by: Albert <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM (modulo a nit)
Signed-off-by: Albert <[email protected]>
Would I be able to get a second review on this PR and get the workflow triggered again? @bboreham |
Signed-off-by: Albert <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Signed-off-by: Marco Pracucci <[email protected]>
…ortexproject#4262) * add MaxRetries to WaitInstanceState Signed-off-by: Albert <[email protected]> * update CHANGELOG.md Signed-off-by: Albert <[email protected]> * Add timeout for waiting on compactor to become ACTIVE in the ring. Signed-off-by: Albert <[email protected]> * add MaxRetries variable back to WaitInstanceState Signed-off-by: Albert <[email protected]> * Fix linting issues Signed-off-by: Albert <[email protected]> * Remove duplicate entry from changelog Signed-off-by: Albert <[email protected]> * Address PR comments and set timeout to be configurable Signed-off-by: Albert <[email protected]> * Address PR comments and fix tests Signed-off-by: Albert <[email protected]> * Update unit tests Signed-off-by: Albert <[email protected]> * Update changelog and fix linting Signed-off-by: Albert <[email protected]> * Fixed CHANGELOG entry order Signed-off-by: Marco Pracucci <[email protected]> Co-authored-by: Albert <[email protected]> Co-authored-by: Marco Pracucci <[email protected]> Signed-off-by: Alvin Lin <[email protected]>
Signed-off-by: Albert [email protected]
What this PR does:
Addresses #3914
Which issue(s) this PR fixes:
Fixes #3914
Checklist
CHANGELOG.md
updated - the order of entries should be[CHANGE]
,[FEATURE]
,[ENHANCEMENT]
,[BUGFIX]