ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dmytro Sen (JIRA)" <j...@apache.org>
Subject [jira] [Reopened] (AMBARI-5065) Rolling restart should also handle clients on the same machine as the restarting component
Date Fri, 14 Mar 2014 14:54:44 GMT

     [ https://issues.apache.org/jira/browse/AMBARI-5065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Dmytro Sen reopened AMBARI-5065:
--------------------------------


> Rolling restart should also handle clients on the same machine as the restarting component
> ------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-5065
>                 URL: https://issues.apache.org/jira/browse/AMBARI-5065
>             Project: Ambari
>          Issue Type: Bug
>          Components: agent
>    Affects Versions: 1.5.0
>            Reporter: Dmytro Sen
>            Assignee: Dmytro Sen
>            Priority: Critical
>             Fix For: 1.5.0
>
>
> 3-host cluster, c6401 has nn, c6402 and c6403 have datanodes + hdfs clients
> 1. create host group in Hdfs
> 2. put one host in the group (say c6403) that has datanode and hdfs client
> 3. change datanode max java heap size so it only affects the datanode
> 4. you'll see a restart is needed only on c6403 as expected (correct) for datanode and
hdfs client
> 5. Issue a rolling restart and only on hosts that need configs (so just one host)
> 6. the works fine and it only restarts datanode c6403 as expected (correct)
> problem: hdfs client is not marked as restarted so i still see "1 HDFS Client" component
requiring a restart on that host.
> Need to handle clients on the machines as well as part of rolling restart.
> Solution:
> Update client tags on Master/Slave component update in-memory and in individual files.



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

Mime
View raw message