-
Notifications
You must be signed in to change notification settings - Fork 24.9k
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
Limit RTG exceptions to retry on #105003
Limit RTG exceptions to retry on #105003
Conversation
Pinging @elastic/es-distributed (Team:Distributed) |
I think i will also open a test PR to show that realtime-(m)get on unassigned shard will/should fail, to have that behaviour documented. But merging this first, would help with the mget PRs too. Sorry the whole get/mget stateless/stateful dimension results in too many PRs. |
serverless check failure is not related and has an open issue. |
Can we add a test that fails without this? I think a test that stops the node containing the shard could do so. Fine if that is in stateless only, but did not see a PR there. |
Sorry, missed this, I could be ok with that, but then we need to validate when writing the unassigned test that it failed with the original version of this. Feels a bit backwards and I would prefer to have the failing test first if possible, but can be persuaded 🙂 |
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
It is a bit! :) I'm just trying to reduce all the pending PRs. I can open the PR first if you want. I have a local version of it. It takes me a bit to polish it. |
ok. thanks to @ywangd 's quick reviews and help, I've been unblocked differently by merging the mget PRs. This can then wait for the test PR first. |
failure was #103588 |
Oh! I didn't want to merge this actually. My bad! 🤦🏼 |
Limit RTG exceptions to retry on and do not throw in
getCurrentNodeOfPrimary
.Follow up to #104579 (comment).
Relates ES-5727