Thanks for the clarifications. Any chance you can do a "jstack" on the coordinating impalad when in that bad state? If it's stuck in the JVM we should be able to see where.
On Tue, Jan 24, 2017 at 10:51 PM, Darren Hoo <[email protected]> wrote: > Hi Alex, > > The GET_TALBES statement is due to one of our applications using C3P0 for > jdbc connection pooling. > It will test Connections by calling the getTables() method on a > Connection's associated DatabaseMetaData object. > > We only have 26 tables, and we don't use sentry. > > > > On Wed, Jan 25, 2017 at 2:11 PM, Alex Behm <[email protected]> wrote: > >> Can you elaborate on what your GET_TABLES was doing? Do you have many >> tables? Are you running Sentry and have many roles/grants? >> >> On Tue, Jan 24, 2017 at 9:15 PM, Darren Hoo <[email protected]> wrote: >> >>> forgot to include VERSION info: >>> >>> +----------------------------------------------------------- >>> --------------------------------------+ >>> >>> | version() >>> | >>> >>> +----------------------------------------------------------- >>> --------------------------------------+ >>> >>> | impalad version 2.7.0-IMPALA_KUDU-cdh5 RELEASE (build >>> 10d4ebec3c23961218e972e74e9d342ffc417af1) | >>> >>> | Built on Mon Nov 21 23:11:10 PST 2016 >>> | >>> >>> +----------------------------------------------------------- >>> --------------------------------------+ >>> >>> >>> >> >
