You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Siddharth Wagle (JIRA)" <ji...@apache.org> on 2017/09/19 21:55:00 UTC
[jira] [Commented] (AMBARI-21917) Some services had issue coming up
after express upgrade on IOP clusters
[ https://issues.apache.org/jira/browse/AMBARI-21917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16172400#comment-16172400 ]
Siddharth Wagle commented on AMBARI-21917:
------------------------------------------
Speculative patch awaiting test results.
> Some services had issue coming up after express upgrade on IOP clusters
> -----------------------------------------------------------------------
>
> Key: AMBARI-21917
> URL: https://issues.apache.org/jira/browse/AMBARI-21917
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.5.2
> Reporter: Siddharth Wagle
> Assignee: Siddharth Wagle
> Priority: Critical
> Fix For: 2.6.0
>
> Attachments: AMBARI-21917.patch
>
>
> The RCO cache gets cleared on an upgrade to make sure new RCO is loaded. However, certain test environments have reported seeing incorrect / older RCO still in effect after Finalize and the operations failing due to this.
> The server log does indicate RCO getting cleared:
> {code}
> 24 Aug 2017 17:15:26,701 INFO [Server Action Executor Worker 1509] StackUpgradeFinishListener:92 - Clearing RCO cache
> {code}
> But the initialization statements are missing. Making a defensive patch to for re-creation of RCO.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)