ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aravindan Vijayan" <avija...@hortonworks.com>
Subject Review Request 41284: AMBARI-14350 : AMS does not start up after cluster redeploy because of invalid ownership of its directories.
Date Fri, 11 Dec 2015 23:17:11 GMT

-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/41284/
-----------------------------------------------------------

Review request for Ambari, Dmytro Sen, Sumit Mohanty, and Sid Wagle.


Bugs: AMBARI-14350
    https://issues.apache.org/jira/browse/AMBARI-14350


Repository: ambari


Description
-------

PROBLEM
Steps:
Deployed cluster via blueprints.
Reset cluster (reset ambari-server, host cleanup).
Deployed cluster via UI.
Result: Ambari Metrics Service go down.

BUG
AMS scripts do not change the ownership of certain directories to AMS user if they exist already.

FIX
Adding an explicit chown to take ownership of the required directories (collector conf, collector
checkpoint, HBase tmp, HBase conf, HBase root)


Diffs
-----

  ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/ams.py
733fcc0 
  ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/hbase.py
92d2bc4 
  ambari-server/src/test/python/stacks/2.0.6/AMBARI_METRICS/test_metrics_collector.py e884367


Diff: https://reviews.apache.org/r/41284/diff/


Testing
-------

Manual Testing done. Ambari server and agent unit tests pass.


Thanks,

Aravindan Vijayan


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