[
https://issues.apache.org/jira/browse/HADOOP-3363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12595180#action_12595180
]
Steve Loughran commented on HADOOP-3363:
----------------------------------------
I certainly expect the operation to fail, but it shouldnt be with a 'you havent
upgraded' message.
Looking at the code in analyzeStorage(), there is a check for an unformatted
filesystem later, which then returns a StorageState.NOT_FORMATTED response to
FSImage.recoverTransitionRead(), which then chooses its actions based on
filesystem state. Only it isnt getting a chance to apply its policy when not
formatted, because the exception is being thrown and forcing it off on a
different path.
> HDFS throws a InconsistentFSStateException when the name node starts up on a
> directory that isnt formatted
> ----------------------------------------------------------------------------------------------------------
>
> Key: HADOOP-3363
> URL: https://issues.apache.org/jira/browse/HADOOP-3363
> Project: Hadoop Core
> Issue Type: Bug
> Affects Versions: 0.16.3
> Environment: namenode deployed on java1.6/ubuntu8.04 in a SmartFrog
> managed JVM
> Reporter: Steve Loughran
> Priority: Trivial
>
> I deploy a namenode with directories that exist but are empty, an
> InconsistentFSStateException is thrown instead of the FS entering the
> unformatted state -the check for upgrade state fails when there is no file
> system there at all.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
