[
https://issues.apache.org/jira/browse/HDFS-7541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ming Ma updated HDFS-7541:
--------------------------
Attachment: HDFS-7541.patch
UpgradeDomains_design_v2.pdf
Here are the updated design document and initial draft patch. Appreciate any
input others might have on the design and the general approach.
The maintenance state support is somewhat independent of upgrade domain work.
So the latest design doesn't include maintenance state support; which will be
discussed separately. We have tested it out on a small cluster. Others are
welcome to try out the patch.
After we finalize on the design, we can break the feature into subtasks.
> Upgrade Domains in HDFS
> -----------------------
>
> Key: HDFS-7541
> URL: https://issues.apache.org/jira/browse/HDFS-7541
> Project: Hadoop HDFS
> Issue Type: Improvement
> Reporter: Ming Ma
> Attachments: HDFS-7541.patch,
> SupportforfastHDFSdatanoderollingupgrade.pdf, UpgradeDomains_design_v2.pdf
>
>
> Current HDFS DN rolling upgrade step requires sequential DN restart to
> minimize the impact on data availability and read/write operations. The side
> effect is longer upgrade duration for large clusters. This might be
> acceptable for DN JVM quick restart to update hadoop code/configuration.
> However, for OS upgrade that requires machine reboot, the overall upgrade
> duration will be too long if we continue to do sequential DN rolling restart.
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
