[
https://issues.apache.org/jira/browse/AMBARI-17020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15313331#comment-15313331
]
Swapan Shridhar commented on AMBARI-17020:
------------------------------------------
Commits:
trunk:
{code}
commit 396adbedf0915ea4f12c0063f10bc5b46582b22d
Author: Swapan Shridhar <[email protected]>
Date: Tue May 31 12:06:01 2016 -0700
AMBARI-17017. Fixing open issues for 'Hive Server Interactive' in
Kerberized environment. AMBARI-17020. Use 'llapstatus' comand after starting
llap to check its status before starting HiveServer2.
{code}
branch-2.4:
{code}
commit 8202f954c9bb3a2d9f0138ddef57fdece1b60c86
Author: Swapan Shridhar <[email protected]>
Date: Thu Jun 2 16:35:07 2016 -0700
AMBARI-17017. Fixing open issues for 'Hive Server Interactive' in
Kerberized environment. AMBARI-17020. Use 'llapstatus' comand after starting
llap to check its status before starting HiveServer2.
{code}
> Use 'llapstatus' comand after starting llap to check its status before
> starting HiveServer2
> -------------------------------------------------------------------------------------------
>
> Key: AMBARI-17020
> URL: https://issues.apache.org/jira/browse/AMBARI-17020
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.4.0
> Reporter: Swapan Shridhar
> Assignee: Swapan Shridhar
> Fix For: 2.4.0
>
>
> - Right now, after starting llap app, we wait for 30 secs before starting
> hive2/HiveServer2.
> - Need to have status check via 'llapstatus' command and start
> hive2/HiveServer2 only if llap app deployment was a success.
> eg: llapstatus command:
> {code}
> hive2/bin/hive --service llapstatus --name <llap app name>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
