ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-21412) Cluster Effective Version Can Be Cached Incorrectly During an Upgrade
Date Tue, 11 Jul 2017 17:22:01 GMT

    [ https://issues.apache.org/jira/browse/AMBARI-21412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16082578#comment-16082578
] 

Hudson commented on AMBARI-21412:
---------------------------------

FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #1667 (See [https://builds.apache.org/job/Ambari-branch-2.5/1667/])
AMBARI-21412 - Cluster Effective Version Can Be Cached Incorrectly (jhurley: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=fa585fb4f9b96e5c5edd5b5cba887f1c7e8425ca])
* (edit) ambari-server/src/main/java/org/apache/ambari/server/serveraction/upgrades/UpdateDesiredStackAction.java
* (edit) ambari-server/src/main/java/org/apache/ambari/server/state/cluster/ClusterImpl.java


> Cluster Effective Version Can Be Cached Incorrectly During an Upgrade
> ---------------------------------------------------------------------
>
>                 Key: AMBARI-21412
>                 URL: https://issues.apache.org/jira/browse/AMBARI-21412
>             Project: Ambari
>          Issue Type: Bug
>    Affects Versions: 2.5.2
>            Reporter: Jonathan Hurley
>            Assignee: Jonathan Hurley
>            Priority: Blocker
>             Fix For: 2.5.2
>
>         Attachments: AMBARI-21412.patch
>
>
> When performing an upgrade, the cluster effective version can be cached incorrectly with
the old version after the {{UpdateDesiredStackAction}} invalidates the cache. The cache should
check to see if the {{UpdateDesiredStackAction}} is in progress and choose not to cache the
value at this time.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message