Skip to content
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

[BUG][Weighted Shard Routing] Fail open count is not updated for only healthy copy in weighed away az #7599

Open
anshu1106 opened this issue May 17, 2023 · 0 comments
Labels
bug Something isn't working distributed framework

Comments

@anshu1106
Copy link
Contributor

Describe the bug
Fail Open stats added as part of PR does not update fail open count if there is a fail open executed due to single healthy shard copy and that copy resides in weighed away az data node.

To Reproduce
Steps to reproduce the behavior:

  1. Create a domain with 3 azs (3 shard copies) and set shard routing weight to 0 for one of the azs.
  2. Inject faults(fail all copies of a shard except the one in weighed away az) so that fail open is executed for shard search request.
  3. Make node stats api call GET /_nodes/<node_id>/stats/weighted-routing
  4. Fail open count is not updated

Expected behavior
Fail open count should increase on fail open execution.

Plugins
Please list all plugins currently enabled.

Screenshots
If applicable, add screenshots to help explain your problem.

Host/Environment (please complete the following information):

  • OS: [e.g. iOS]
  • Version [e.g. 22]

Additional context
Add any other context about the problem here.

@anshu1106 anshu1106 added bug Something isn't working untriaged labels May 17, 2023
@anshu1106 anshu1106 changed the title [BUG][Weighted Shard Routing] Fail open count is not updated for one healthy shard copy in weighed away az [BUG][Weighted Shard Routing] Fail open count is not updated for only healthy copy in weighed away az May 17, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working distributed framework
Projects
None yet
3 participants