[
https://issues.apache.org/jira/browse/HDFS-5535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13912245#comment-13912245
]
stack commented on HDFS-5535:
-----------------------------
[~kihwal]
bq. I will be more than happy to further improve the DN restart latency, if it
becomes major hurdle for HBase.
Is there anything that can be done about the following? DN is rolling
restarted under a RegionServer. It takes > timeout for the DN to come back.
DN gets added to deadnode list in DFSInputStream (right?) because we failed the
read and had to go to a remote replica instead. Hereafter all reads take
longer because they are no longer local (unless we restart regionserver).
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)
