[
https://issues.apache.org/jira/browse/HDFS-7541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15991533#comment-15991533
]
Kihwal Lee commented on HDFS-7541:
----------------------------------
Just found out I somehow clicked the evil "Assign to me" link 6 days ago. I
didn't mean to do that.
[~mingma], fork & exec with a large NN is not desirable for us and using the
new host file format doesn't seem attractive since a lot of automation is built
around the old format. We could probably add something similar to the network
topology java plugin.
I think 2.8.1 is for immediate stabilization and fixes after 2.8.0, so 2.8.2
will be a more reasonable target.
> 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
> Assignee: Ming Ma
> Fix For: 2.9.0, 3.0.0-alpha1
>
> Attachments: HDFS-7541-2.patch, HDFS-7541.patch,
> SupportforfastHDFSdatanoderollingupgrade.pdf, UpgradeDomains_design_v2.pdf,
> UpgradeDomains_Design_v3.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.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
