[
https://issues.apache.org/jira/browse/HDFS-7231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14183724#comment-14183724
]
Allen Wittenauer edited comment on HDFS-7231 at 10/24/14 11:29 PM:
-------------------------------------------------------------------
bq. (unable to continue)
This is the part I've also been trying to get more information on as well. :D
From what I've been told, the first few directories were converted to the new
format but not all of them. This seems to imply that the DN process was
brought down at some point in time.
bq. This as you know is a recipe for disaster
I can neither confirm nor deny this statement. ;)
bq. Before you go on to 2.4.1, if you do finalize of upgrade what happens?
It appears to work as expected. So this whole condition appears to trigger
with non-finalized systems.
was (Author: aw):
bq. (unable to continue)
This is the part I've also been trying to get more information on as well. :D
From what I've been told, the first few directories were converted to the new
format but not all of them. This seems to imply that the DN process was
brought down at some point in time.
bq. This as you know is a recipe for disaster
I can neither confirm or deny this statement. ;)
bq. Before you go on to 2.4.1, if you do finalize of upgrade what happens?
It appears to work as expected. So this whole condition appears to trigger
with non-finalized systems.
> rollingupgrade needs some guard rails
> -------------------------------------
>
> Key: HDFS-7231
> URL: https://issues.apache.org/jira/browse/HDFS-7231
> Project: Hadoop HDFS
> Issue Type: Bug
> Affects Versions: 2.6.0
> Reporter: Allen Wittenauer
> Priority: Blocker
>
> See first comment.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
