[
https://issues.apache.org/jira/browse/AMBARI-12026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14594892#comment-14594892
]
Hudson commented on AMBARI-12026:
---------------------------------
SUCCESS: Integrated in Ambari-trunk-Commit #2956 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/2956/])
Revert "AMBARI-12026. During rolling upgrade proces, Ambari becomes
unresponsive. (mpapirkovskyy)" (mpapyrkovskyy:
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=53b4464582ea118447f1f8991269fd3caf2d2286)
*
ambari-server/src/test/java/org/apache/ambari/server/state/cluster/ClusterDeadlockTest.java
*
ambari-server/src/test/java/org/apache/ambari/server/testing/DeadlockWarningThread.java
* ambari-server/src/main/java/org/apache/ambari/server/state/ConfigImpl.java
> During rolling upgrade proces, Ambari becomes unresponsive
> ----------------------------------------------------------
>
> Key: AMBARI-12026
> URL: https://issues.apache.org/jira/browse/AMBARI-12026
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.1.0
> Reporter: Myroslav Papirkovskyy
> Assignee: Myroslav Papirkovskyy
> Priority: Blocker
> Fix For: 2.1.0
>
>
> Ambari goes into deadlock during RU.
> Reason is config update which is not expected by design.
> Config locking strategy should be revisited.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
