You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
Create a domain with 3 azs (3 shard copies) and set shard routing weight to 0 for one of the azs.
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.
Make node stats api call GET /_nodes/<node_id>/stats/weighted-routing
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.
The text was updated successfully, but these errors were encountered:
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
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:
GET /_nodes/<node_id>/stats/weighted-routing
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):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: