-
Notifications
You must be signed in to change notification settings - Fork 25k
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 logging in GlobalCheckpointSyncIT #89185
Conversation
The test GlobalCheckpointSyncIT#testBackgroundGlobalCheckpointSync failed once recently due to an engine already close exception. It has not occurred again and the reasoning is unclear. This commit adds a log line to indicate exactly when it happens, which shard it is, and what the current state of the index shard is. Closes elastic#88428.
Pinging @elastic/es-distributed (Team:Distributed) |
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. Could also just add a logger.info/debug that always happens for all shard IDs/states, instead of try/catching alternatively. But I assume you'd like to log the specific shard ID/state, right @tbrooks8 ?
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.
LGTM2 but note that we're not including the AlreadyClosedException
(plus stack trace) in the log message. Not sure of the context but maybe that'd be helpful?
The exception gets thrown and ends up as the test failure. So that is why I left it out so it did not get printed twice? I mostly wanted to propagate the shard id and state if this happens again. Does this make sense? |
Yep, perfectly, just thought it worth checking. |
Yes pretty much just trying to catch in a face of an unexpected failure. |
The test GlobalCheckpointSyncIT#testBackgroundGlobalCheckpointSync
failed once recently due to an engine already close exception. It has
not occurred again and the reasoning is unclear.
This commit adds a log line to indicate exactly when it happens, which
shard it is, and what the current state of the index shard is.
Closes #88428.