Details
-
Improvement
-
Resolution: Unresolved
-
Major
-
6.6.0, 7.6.0, 7.0.0, 7.1.0, 7.2.0
-
0
Description
In recent bugs, we are seeing some indexer calls to ns_server fail with `503 Service Unavailable` error code. This is happening due to ns_server undergoing node rename but can also happen due to other reasons (eg security change?). It is better to add a retry on this error code rather than fail the respective action.
This improvement is to add retries to ns_server API calls on `503` error code.
Attachments
Issue Links
- relates to
-
MB-60668 [Upgrade][Index] : Observing panic: HTTP error 503 Service Unavailable getting "http://127.0.0.1:8091/pools": "Temporary error occurred. Please try again later."
- Open
-
MB-60498 [Query] : Observing FATAL logs in query.log - [Fatal] MetakvGet: Failed to fetch /indexing/ddl/commandToken/delete/5848318864860926916 from metakv: ns_server _metakv returned: 503 Service Unavailable
- Open