ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-14558) HAWQSTANDBY should start after NAMENODE has been started
Date Wed, 06 Jan 2016 22:00:41 GMT

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

Hudson commented on AMBARI-14558:
---------------------------------

SUCCESS: Integrated in Ambari-trunk-Commit #4133 (See [https://builds.apache.org/job/Ambari-trunk-Commit/4133/])
AMBARI-14558: HAWQSTANDBY should start after NAMENODE has been started (jaoki: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=d5c29f9d468a252f30bb29d5f4b9b392000685a7])
* ambari-server/src/main/resources/stacks/HDP/2.3/role_command_order.json


> HAWQSTANDBY should start after NAMENODE has been started
> --------------------------------------------------------
>
>                 Key: AMBARI-14558
>                 URL: https://issues.apache.org/jira/browse/AMBARI-14558
>             Project: Ambari
>          Issue Type: Bug
>            Reporter: Matt
>            Assignee: Matt
>            Priority: Minor
>             Fix For: trunk, 2.2.1
>
>         Attachments: AMBARI-14558-branch-2-2.patch, AMBARI-14558-trunk.patch
>
>
> When all services are being started, HAWQSTANDBY fails to start, if NAMENODE hasn't been
started.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message