-
Notifications
You must be signed in to change notification settings - Fork 92
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
Infinite loop of logs if database no longer exists #258
Comments
Can you please provide the entire log entry? I will check if it's coming from Metabase itself or the driver. |
Hi, The last line repete thousand of times each seconds. |
Thanks, I repro'd on 0.50.6 and 0.50.8. Steps:
Click to toggle contents of logs
The stack trace shows it is triggered downstream of
The same thing happens as in step 5: an endless stream of logs. Click to toggle contents of logs
|
Describe the bug
We noticed that if the database inside a clichouse instance is renamed or deleted the Clichouse driver starts logging about 5 million lines every 5 minutes (which has saturated our Datadog quota). Here is the repeating log line:
at com.mchange.v2.resourcepool.BasicResourcePool.checkoutResource(BasicResourcePool.java:594)
Steps to reproduce
Expected behaviour
Few logs not millions !
Error log
at com.mchange.v2.resourcepool.BasicResourcePool.checkoutResource(BasicResourcePool.java:594)
Configuration
Environment
The text was updated successfully, but these errors were encountered: