ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-19721) Use 'llapstatus' command watch mode from HDP 2.6 onwards.
Date Thu, 26 Jan 2017 04:37:26 GMT

    [ https://issues.apache.org/jira/browse/AMBARI-19721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15839169#comment-15839169
] 

Hudson commented on AMBARI-19721:
---------------------------------

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6554 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6554/])
AMBARI-19721. Use llapstatus command watch mode from HDP 2.6 onwards (smohanty: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=35d27739976ccce1c1211def122b3dc7f404662d])
* (edit) ambari-server/src/test/python/stacks/2.5/HIVE/test_hive_server_int.py
* (edit) ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/scripts/hive_server_interactive.py
* (edit) ambari-server/src/main/resources/stacks/HDP/2.6/services/HIVE/configuration/hive-interactive-env.xml


> 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)

Mime
View raw message