[jira] [Resolved] (AMBARI-17020) Use 'llapstatus' comand after starting llap to check its status before starting HiveServer2
[ https://issues.apache.org/jira/browse/AMBARI-17020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya resolved AMBARI-17020. Resolution: Duplicate > 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 > {code} -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AMBARI-17020) Use 'llapstatus' comand after starting llap to check its status before starting HiveServer2
[ https://issues.apache.org/jira/browse/AMBARI-17020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar resolved AMBARI-17020. -- Resolution: Fixed > 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 > {code} -- This message was sent by Atlassian JIRA (v6.3.4#6332)