ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aleksandr Kovalenko (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-4932) Moving ResourceManager/JobTracker requires shutting down entire cluster
Date Wed, 12 Mar 2014 18:38:42 GMT

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

Aleksandr Kovalenko commented on AMBARI-4932:
---------------------------------------------

committed to trunk

> Moving ResourceManager/JobTracker requires shutting down entire cluster
> -----------------------------------------------------------------------
>
>                 Key: AMBARI-4932
>                 URL: https://issues.apache.org/jira/browse/AMBARI-4932
>             Project: Ambari
>          Issue Type: Bug
>          Components: client
>    Affects Versions: 1.5.0
>            Reporter: Mikhail Bayuk
>            Assignee: Mikhail Bayuk
>             Fix For: 1.5.0
>
>         Attachments: AMBARI-4932.patch
>
>
> When we move ResourceManager/JobTracker, the move wizard shuts all services down. This
unnecessarily causes cluster downtime; services that don't depend on YARN/MR shouldn't have
to go down (especially HDFS).



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message