[
https://issues.apache.org/jira/browse/AMBARI-19721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15839136#comment-15839136
]
Hadoop QA commented on AMBARI-19721:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12849400/AMBARI-19721.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10268//console
This message is automatically generated.
> Use 'llapstatus' command watch mode from HDP 2.6 onwards.
> ---------------------------------------------------------
>
> Key: AMBARI-19721
> URL: https://issues.apache.org/jira/browse/AMBARI-19721
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.5.0
> Reporter: Swapan Shridhar
> Assignee: Swapan Shridhar
> Fix For: 2.5.0
>
> Attachments: AMBARI-19721.patch
>
>
> - Till HDP 2.5, Ambari had used *'llapstatus'* command to query LLAP app
> status and has wrapped around the retry logic for how many times to query
> *'llapstatus'* command in order for LLAP app to reach *RUNNING_ALL* or
> *RUNNING* with 80 % containers Up.
> - With HDP 2.6, Hive has implemented a watch mode where Ambari doesnt need to
> have the retry logic in Ambari itself, and can use the *llapstatus* watch
> mode.
> Usage is as follows: (Information provided by [~prasanth_j])
> Following options are added to llap status tool
> *->* -w : Watch mode waits until all LLAP daemons are running or subset of
> the nodes are running (threshold can be specified via -r option) (Default
> wait until all nodes are running)
> *->*-r : When watch mode is enabled (-w), wait until the specified threshold
> of nodes are running (Default 1.0 which means 100% nodes are running)
> *->*-i : Amount of time in seconds to wait until subsequent status checks in
> watch mode (Default: 1sec)
> *->*-t : Exit watch mode if the desired state is not attained until the
> specified timeout (Default: 300sec)
> *Example usage:*
> {code}
> llapstatus -w -i 1 -t 300
> {code}
> The above command waits until all nodes are running with 1 second refresh
> rate and 300 second timeout (300 max attempts else fail).
> {code}
> llapstatus -w -r 0.8 -i 2 -t 150
> {code}
> The above command waits until 80% of the nodes are running with 2 second
> refresh rate and 150 second timeout (75 max attempts else fail).
> {code}
> llapstatus -w -r 0.8
> {code}
> Use without providing the -i and -t options (Defaults used).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
