[
https://issues.apache.org/jira/browse/HDFS-5535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13912575#comment-13912575
]
stack commented on HDFS-5535:
-----------------------------
[~kihwal]
bq. ....we may be able to (asynchronously?) probe and remove it from deadNodes.
I believe that is what our mighty [~cmccabe] is suggesting too in his comment
above (i.e. HDFS-4246 added something like this on the write path and then
there is apparently an issue to do similar at read time). Chatting w/ Colin
too, it sound like SSR, if it fails a local read, it will then retry the local
read again after some number of minutes have elapsed. This could be enough to
get reads over the DN restart blip. Thanks.
> Umbrella jira for improved HDFS rolling upgrades
> ------------------------------------------------
>
> Key: HDFS-5535
> URL: https://issues.apache.org/jira/browse/HDFS-5535
> Project: Hadoop HDFS
> Issue Type: New Feature
> Components: datanode, ha, hdfs-client, namenode
> Affects Versions: 3.0.0, 2.2.0
> Reporter: Nathan Roberts
> Attachments: HDFSRollingUpgradesHighLevelDesign.pdf,
> h5535_20140219.patch, h5535_20140220-1554.patch, h5535_20140220b.patch,
> h5535_20140221-2031.patch, h5535_20140224-1931.patch,
> h5535_20140225-1225.patch
>
>
> In order to roll a new HDFS release through a large cluster quickly and
> safely, a few enhancements are needed in HDFS. An initial High level design
> document will be attached to this jira, and sub-jiras will itemize the
> individual tasks.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
