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 go-carob log seems to handle the query in a breeze, but carbonapi log reports failure with runtime of 30 seconds even if timeout is set to much higher.
IDK what limits it to 30 secs, some lower-level network stack? The error message is not really informative here (a suggestion to improve?).
Simplified query (if applicable)
Query is noted in multiple lines in logs.
Backend metric retention and aggregation schemas
Will provide if that relevant.
Backend response (if possible)
Single backend in our system. The log of the backend go-carbon is copied above.
Additional context
Our node executes both go-carbon and carbonapi. We have a dev node which reproduces the issue even though it has much less load than the prod because carbonapi almost doesn't receive any queries.
The text was updated successfully, but these errors were encountered:
Describe the bug
go-carob
log seems to handle the query in a breeze, butcarbonapi
log reports failure with runtime of 30 seconds even if timeout is set to much higher.IDK what limits it to 30 secs, some lower-level network stack? The error message is not really informative here (a suggestion to improve?).
CarbonAPI Version
0.16.0~1
Logs
jq'ed
go-carbon
log entry of the request:The jq'ed entries of the request which are grepped by UUID:
CarbonAPI Configuration:
Simplified query (if applicable)
Query is noted in multiple lines in logs.
Backend metric retention and aggregation schemas
Will provide if that relevant.
Backend response (if possible)
Single backend in our system. The log of the backend
go-carbon
is copied above.Additional context
Our node executes both
go-carbon
andcarbonapi
. We have a dev node which reproduces the issue even though it has much less load than the prod becausecarbonapi
almost doesn't receive any queries.The text was updated successfully, but these errors were encountered: