Our Community is getting an upgrade! To get everything ready for the relaunch, we’ll be placing the site in read-only mode starting September 21st.
We really appreciate your understanding while we get things set up behind the scenes. Catch up on all the exciting details about the move here.
Need help or have questions? Drop us a line at [email protected]

Archives of Support Questions (Read Only)

This is an archived board for historical reference. Information and links may no longer be available or relevant
Announcements
This board is archived and read-only for historical reference. To ask a new question, please post a new topic on the appropriate active board.

hiveserver2 debugging

avatar
Rising Star

Hi team....Anyone aware how to get into debug mode for beeline command shell...like in hive we use hive -hiveconf hive.root.logger=Debug,console..do we have anything for beeline..the same is not working at beeling ..I don't want to restart the hiveserver ..as this is in production will impact other due to stop and start..

1 ACCEPTED SOLUTION

avatar
New Member

Hi Ammu,

beeline has a flag --verbose=[true/false] that will output more information, I use that option regularly to get back more information about stacktraces.

related: https://cwiki.apache.org/confluence/display/Hive/HiveServer2+Clients#HiveServer2Clients-BeelineComma...

View solution in original post

3 REPLIES 3

avatar
New Member

Hi Ammu,

beeline has a flag --verbose=[true/false] that will output more information, I use that option regularly to get back more information about stacktraces.

related: https://cwiki.apache.org/confluence/display/Hive/HiveServer2+Clients#HiveServer2Clients-BeelineComma...

avatar
Rising Star

thanks for the info but looks like this is not informative for issue debugging..and I got update ..we can't change logger debug mode once hiveserver2 started...this feature is available only with HDP2.3 onwards it seems..

anyway thanks for looking into this..

avatar
Contributor

Edit the /etc/hive/conf/beeline-log4j.properties you created by copying from beeline-log4j.properties.template and specify log4j.rootLogger=DEBUG, console