You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Vinod Kumar Vavilapalli (JIRA)" <ji...@apache.org> on 2015/09/03 21:11:46 UTC
[jira] [Updated] (HDFS-7894) Rolling upgrade readiness is not
updated in jmx until query command is issued.
[ https://issues.apache.org/jira/browse/HDFS-7894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vinod Kumar Vavilapalli updated HDFS-7894:
------------------------------------------
Fix Version/s: 2.6.1
[~sjlee0] backported this to 2.6.1, the patch applied cleanly.
I just pushed the commit to 2.6.1 after running compilation.
> Rolling upgrade readiness is not updated in jmx until query command is issued.
> ------------------------------------------------------------------------------
>
> Key: HDFS-7894
> URL: https://issues.apache.org/jira/browse/HDFS-7894
> Project: Hadoop HDFS
> Issue Type: Bug
> Reporter: Kihwal Lee
> Assignee: Brahma Reddy Battula
> Priority: Critical
> Labels: 2.6.1-candidate
> Fix For: 2.6.1, 2.7.1
>
> Attachments: HDFS-7894-002.patch, HDFS-7894-003.patch, HDFS-7894.patch
>
>
> When a hdfs rolling upgrade is started and a rollback image is created/uploaded, the active NN does not update its {{rollingUpgradeInfo}} until it receives a query command via RPC. This results in inconsistent info being showing up in the web UI and its jmx page.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)