-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/35167/
-----------------------------------------------------------
(Updated June 6, 2015, 3:38 a.m.)
Review request for Ambari, Jonathan Hurley, Mahadev Konar, Myroslav
Papirkovskyy, and Yusaku Sako.
Changes
-------
I haven't removed the locking on already persisted entites on account of the
fact that there was an exception on updating configs and the explicitly getting
write lock alleviated it. Note: We do create configs on updaing Config Groups
if these entities do not exist, so the updates actually can create new
entities. I have address the concern for unlocking without addressing the lock
acquisition on persisted Config Group.
Bugs: AMBARI-11744
https://issues.apache.org/jira/browse/AMBARI-11744
Repository: ambari
Description
-------
This was observed while adding Ganglia to an existing cluster via Add Services
Wizard.
It hung after clicking Deploy at task 2 / 6.
Browser tools showed that it was doing a PUT and this call timed out after 3
mins.
All subsequent API calls hung. Ambari Server was not responsive at all to any
API calls after that.
Diffs (updated)
-----
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/ConfigGroupResourceProvider.java
3fcb84b
ambari-server/src/main/java/org/apache/ambari/server/state/configgroup/ConfigGroupImpl.java
9ec0370
Diff: https://reviews.apache.org/r/35167/diff/
Testing
-------
Verified manually.
Thanks,
Sid Wagle
