ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dmytro Sen" <>
Subject Review Request 19185: Rolling restart should also handle clients on the same machine as the restarting component
Date Thu, 13 Mar 2014 12:23:48 GMT

This is an automatically generated e-mail. To reply, visit:

Review request for Ambari and Sid Wagle.

Bugs: AMBARI-5065

Repository: ambari


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
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.
Update client tags on Master/Slave component update in-memory and in individual files.


  ambari-agent/src/main/python/ambari_agent/ 731ac54 
  ambari-agent/src/main/python/ambari_agent/ 024c575 
  ambari-agent/src/main/python/ambari_agent/ 6f9f4db 
  ambari-agent/src/test/python/ambari_agent/ e62dd1a 
  ambari-agent/src/test/python/ambari_agent/ 96a21b9 



Ran 284 tests in 11.538s



Dmytro Sen

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message