Skip to content
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.

Sign up for GitHub

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

Jump to bottom

SQL: Spurious 'table not found' #4258

Closed
gianm opened this issue May 8, 2017 · 2 comments · Fixed by #4551
Closed

SQL: Spurious 'table not found' #4258

gianm opened this issue May 8, 2017 · 2 comments · Fixed by #4551
Milestone
0.11.0

Comments

@gianm
Copy link
Contributor

gianm commented May 8, 2017

Some users have reported Table 'xxx' not found errors that (sometimes) resolve when restarting brokers. Seems like something off with the metadata caching.

See https://groups.google.com/d/topic/druid-user/A_C9pKWzc0M/discussion for context.
@gianm gianm added this to the 0.10.1 milestone May 8, 2017
@gianm gianm modified the milestones: 0.10.2, 0.10.1 May 23, 2017
@gianm
Copy link
Contributor Author

gianm commented May 26, 2017

I got a report recently that someone got this error consistently when using non-sticky load balancing. The Avatica server doesn't share connection state between brokers so it is totally believable that something would go wrong. Although, the error message is a weird one to get in that case.

@leventov leventov modified the milestones: 0.11.0, 0.10.2 Jun 26, 2017
@gianm gianm mentioned this issue Jul 18, 2017
Merged
@fjy fjy closed this as completed in #4551 Jul 20, 2017
@richiesgr
Copy link

Hi
I'm using imply 2.4.0 version and the problem still exists
after restarting the broker the SQL server lose the metadata of the data source.
After some time it come back but not always
Is there any workaround ?
Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
0.11.0
Development

Successfully merging a pull request may close this issue.

Fixes and improvements to SQL metadata caching. gianm/druid
3 participants
@richiesgr @leventov @gianm