[jira] Updated: (HADOOP-1597) Distributed upgrade status reporting and post upgrade features.

["Konstantin Shvachko (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/HADOOP-1597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Konstantin Shvachko updated HADOOP-1597:
----------------------------------------

    Attachment: DistUpgradeStatus.patch

> Distributed upgrade status reporting and post upgrade features.
> ---------------------------------------------------------------
>
>                 Key: HADOOP-1597
>                 URL: https://issues.apache.org/jira/browse/HADOOP-1597
>             Project: Hadoop
>          Issue Type: New Feature
>          Components: dfs
>    Affects Versions: 0.14.0
>            Reporter: Konstantin Shvachko
>            Assignee: Konstantin Shvachko
>            Priority: Blocker
>             Fix For: 0.14.0
>
>         Attachments: DistUpgradeStatus.patch
>
>
> This patch introduces 2 additional features to the distributed upgrade framework,
> which turned out to be useful for the crc upgrade HADOOP-1134.
> 1. I introduce a DFSAdmin command
> -upgradeProgress status | details | force
> which retrieves current upgrade status, or its detailed status, or forces the upgrade to proceed if it is stuck.
> 2. If a data-node misses an upgrade it can still join the cluster if the respective upgrade object implements
> postUpgradeAction() method.
> The framework provides a default implementation of the features.
> For (1) any upgrade object returns by default a generic UpgradeStatusReport class, which contains
> only the version and the current status of the upgrade.
> An attempt to force the upgrade will have no effect except that the name-node will log "forceProceed() is not defined"
> For (2) the default implementation leads to a data-node shutdown, which is consistent with the former behavior.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.