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-14248) After ambari-server upgrade 'start all' operation is triggered with 1 minute delay
Date Mon, 07 Dec 2015 20:23:11 GMT

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

Hudson commented on AMBARI-14248:
---------------------------------

ABORTED: Integrated in Ambari-trunk-Commit #3989 (See [https://builds.apache.org/job/Ambari-trunk-Commit/3989/])
AMBARI-14248. After ambari-server upgrade "start all" operation is (vbrodetskyi: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=a0d8e722c643c676f8e2b0b4dd5e1ee7a77cb56a])
* ambari-server/src/main/java/org/apache/ambari/server/state/ConfigHelper.java


> After ambari-server upgrade 'start all' operation is triggered with 1 minute delay
> ----------------------------------------------------------------------------------
>
>                 Key: AMBARI-14248
>                 URL: https://issues.apache.org/jira/browse/AMBARI-14248
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.2.0
>            Reporter: Vitaly Brodetskyi
>            Assignee: Vitaly Brodetskyi
>            Priority: Critical
>             Fix For: 2.2.0
>
>         Attachments: AMBARI-14248.patch
>
>
> Just after ambari-server upgrade from 2.0.2 to 2.2.0. Login and trigger 'Start All' BG
operation appears in 70 seconds after triggering action.



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

Mime
View raw message