[
https://issues.apache.org/jira/browse/AMBARI-16192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15269577#comment-15269577
]
Hudson commented on AMBARI-16192:
---------------------------------
FAILURE: Integrated in Ambari-trunk-Commit #4782 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/4782/])
AMBARI-16192: 'Restart All' for HAWQ should follow role_command_order (matt:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=7eeab53c715f4667afed0217721841eabadeea76])
* ambari-server/src/main/resources/stacks/HDP/2.3/role_command_order.json
> 'Restart All' for HAWQ should follow role_command_order
> -------------------------------------------------------
>
> Key: AMBARI-16192
> URL: https://issues.apache.org/jira/browse/AMBARI-16192
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-server
> Affects Versions: trunk, 2.2.2
> Reporter: Lav Jain
> Assignee: Lav Jain
> Priority: Minor
> Fix For: 2.4.0, 2.2-next
>
> Attachments: AMBARI-16192.branch22.patch, AMBARI-16192.patch
>
>
> The current implementation in Ambari, 'Restart All' service action does not
> follow role_command_order.
> For example, all HAWQSEGMENTs start before HAWQMASTER and HAWQSTANDBY starts.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
