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
executeWithRetry is not work
the reason is req.Body can only be readed once.
when req.Body is readed by one clickhouse and clickhouse shutdown, executeWithRetry to another clickhouse will lead to 400 bad request, since req.Body will be empty
To Reproduce
Steps to reproduce the behavior.
set 2 backend clickhouse-server
set config retry_number > 0
send request to chproxy
shutdown one clickhouse
request will failed
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Environment information
Information about OS, chproxy and Clickhouse versions on which issue occures.
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
Hello @jiachinzhao, can you tell us if the issue is present for both POST and GET requests? From your description it sounds that retry mechanism does not work while chproxy used with POST
since the PR fixing the issue was merged, I'm closing this issue.
We will try to release a new version of chproxy next week.
Feel free to reopen the issue is the fix is not enough
Describe the bug
executeWithRetry is not work
the reason is req.Body can only be readed once.
when req.Body is readed by one clickhouse and clickhouse shutdown, executeWithRetry to another clickhouse will lead to 400 bad request, since req.Body will be empty
To Reproduce
Steps to reproduce the behavior.
set 2 backend clickhouse-server
set config retry_number > 0
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Environment information
Information about OS, chproxy and Clickhouse versions on which issue occures.
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: