-
Notifications
You must be signed in to change notification settings - Fork 7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
odbc-bridge stuck #3825
Comments
Same problem. Begins since 18.14.17 |
@alesapin please take a look |
Looks same #3829. |
The bug fixed in #3857. As workaround you can set logger settings for odbc-bridge in server
|
v18.14.19-stable released, please update and try to disable settings. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We use external dictionary in postgres via odbc-bridge. The odbc-bridge connects to a pgbouncer proxy on postgres. both pgbouncer and postgres seem healthy but it's possible some query times out.
After a recent upgrade:
v18.14.11-stable...v18.14.17-stable
We are seeing instability in odbc-bridge. The bridge gets "stuck". Here is what I observe:
https://gist.github.com/johnskopis/c2f661dee3b1e5a79b636ca038d254f9
There is no activity on postgres socket (verified with tcpdump, strace).
After killing odbc-bridge it seems to be OK. As a workaround maybe a periodic task can check odbc-bridge health (/ping) and restart when unhealthy?
I am not too familiar with poco but looks like a coroutine bug. Maybe it gets confused and never switches back and gets stuck between read/write? I mention this because I noticed in the changeset:
The upgrade included some process lifecycle management changes for odbc-bridge
The upgrade also included a change in AIO eof detection.
Any help would be greatly appreciated.
Also, is it possible to run odbc-bridge outside of clickhouse? Maybe a workaround is to run using a scheduler and restart unhealthy odbc-bridge.
Thanks
The text was updated successfully, but these errors were encountered: