Hi Jeszy,
Thanks for looking into this. I think we were configuring impalad how you
suggest, but just to be sure, please see my questions inline below:
- impalad should be configured to have a catalog and statestore
> service through its startup flags
>
This is how we've always configured
Hey Cliff,
Thanks.
In general:
- you should have a hive-site.xml pointing to the metastore URIs on
the classpath for all deamons (I'm not sure if it's strictly required
for impalad - maybe others can clear that up -, but assuming yes for
now).
- impalad should be configured to have a catalog and
The failed attempt to initialize the metastore was near the very start of
the impalad log
I0114 16:31:24.238524 11902 HiveConf.java:188] Found configuration file null
I0114 16:31:24.498625 11902 QueryEventHookManager.java:92] QueryEventHook
config:
I0114 16:31:24.498726 11902
'Unlike previous versions, in 3.3 impalad would not start unless
installed a local hive metastore db on the impalad instance, not just
the catalogd instance.' - this sounds weird and is unexpected, and
multiple metastores can easily lead to issues further down the line.
What was the end of the log
