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
When a QueryStream operation ends due to the context being canceled, the error is added to the trace's span event.
To Reproduce
Steps to reproduce the behavior:
Start Cortex with tracing enabled.
Run a query that the distributor sends to more than one ingester.
Expected behavior
If an ingester context is canceled during the query (which I understand is normal operation of cortex?), then the operation results in an OK span status with no attached span event.
Describe the bug
When a QueryStream operation ends due to the context being canceled, the error is added to the trace's span event.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
If an ingester context is canceled during the query (which I understand is normal operation of cortex?), then the operation results in an OK span status with no attached span event.
Environment:
Additional Context
The span in question:
cortex/pkg/ingester/ingester.go
Lines 1744 to 1745 in ab3ca0a
Similar issue from the past:
#1279
How it was fixed in WeaveWorks:
https://github.com/weaveworks/common/pull/148/files
An example of a failing trace. In this example, there were five parallel query streams, and the one that was canceled was the slowest.
And its span event:
The text was updated successfully, but these errors were encountered: