Unexpected 422 Unprocessable Entity Response with Partial Response Enabled

[KEIONG]

Hi Thanos Community members,

I've encountered an issue with Thanos Query when partial response is enabled.

Problem:
Despite having partial response enabled, I am receiving a 422 Unprocessable Entity response. According to the documentation and my understanding, partial response should return a 200 status code, even if some data is missing.

Deployment Details:

• My Thanos Query and sidecars are possibly deployed in different countries.
• When querying multiple endpoints, if one of the endpoints experiences network packet loss, the query response returns a 422 status code.

This behavior is quite unexpected and does not align with the anticipated partial response behavior, which should return a 200 status code.

Could anyone provide insights or suggestions on why this might be happening and how to resolve it?

Thank you!

[dosubot[bot]]

Hey @KEIONG,

I'm here to help you with any bugs, questions, or contributions you have on Thanos Query! Let's figure this out together.

The 422 Unprocessable Entity status code you're encountering is indeed unexpected when partial response is enabled. Typically, with partial response enabled, Thanos Query should return a 200 status code along with a warning if some endpoints fail.

Here are a few things you might consider checking:

1. Configuration Verification: Ensure that the partial_response setting is correctly configured to allow partial responses. It should be set to true to avoid aborting on errors.

2. Logs and Error Messages: Check the logs for any specific error messages or warnings that might provide more context on why a 422 status code is being returned.

3. Network Reliability: Since your deployment is geographically distributed, network issues might be causing unexpected behavior. Ensure that network connectivity is stable and that there are no significant packet losses affecting the communication between Thanos components.

4. Version and Compatibility: Verify that all Thanos components are running compatible versions, as mismatches might lead to unexpected behavior.

Unfortunately, specific conditions that trigger a 422 status code in Thanos Query are not documented in the available information, so further investigation into logs and configurations might be necessary.

To continue talking to Dosu, mention @dosu.