Closed jinyangli34 closed 4 years ago
I remember in early DruidSQL versions the SQL metadata could get de-synced. I think this was fixed in 0.14 (cant find the PR). SQL has been declared non-experimantal in 0.15.0 so it would be really helpful of you could upgrade and see if there is still an issue in 0.16.0.
We've got the same problem. The solution has been the same too - restarted the broker.
@ridox What version are you running on?
This issue has been marked as stale due to 280 days of inactivity. It will be closed in 4 weeks if no further activity occurs. If this issue is still relevant, please simply write any comment. Even if closed, you can still revive the issue at any time or discuss it on the dev@druid.apache.org list. Thank you for your contributions.
This issue has been closed due to lack of activity. If you think that is incorrect, or the issue requires additional review, you can revive the issue at any time.
having the same issue, pretty much breaking down entire consumption, for us restarting service doesn't help
basically, it's loss of metadata issue and loss of functionality, since the query stopped working after this feature, only restoring ingestion metadata help, no restarts, version latest, 0.21.1
Facing the same issue. Does any one know the reason behind this and possible solution ?
Please provide a detailed title (e.g. "Broker crashes when using TopN query with Bound filter" instead of just "Broker crashes").
Affected Version
0.13
Description
https://groups.google.com/forum/#!searchin/druid-user/not$20found$20in$20any$20table%7Csort:date/druid-user/yKZ4XzOTZMY/XjqdmauYBwAJ
Hit the following error with SQL query. The problem disappeared after restarting broker service. The same issue happened again after a few days. Any help is appreciated.