hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Todd Lipcon (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-2010) Clean up and test behavior under failed edit streams
Date Mon, 30 May 2011 05:08:47 GMT

     [ https://issues.apache.org/jira/browse/HDFS-2010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Todd Lipcon updated HDFS-2010:
------------------------------

          Component/s: name-node
          Description: 
Right now there is very little test coverage of situations where one or more of the edits
directories fails. In trunk, the behavior when all of the edits directories are dead is that
the NN prints a fatal level log message and calls Runtime.exit(-1).

I don't think this is really the behavior we want. Needs a bit of thought, but I think something
like the following would make more sense:
- any calls currently waiting on logSync should end up throwing an exception
- NN should probably enter safe mode
- ops can restore edits directories and then ask the NN to restore storage, at which point
it could edit safemode
- alternatively, ops could call ask the NN to do saveNamespace and then shut it down
    Affects Version/s: Edit log branch (HDFS-1073)
        Fix Version/s: Edit log branch (HDFS-1073)

> Clean up and test behavior under failed edit streams
> ----------------------------------------------------
>
>                 Key: HDFS-2010
>                 URL: https://issues.apache.org/jira/browse/HDFS-2010
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: name-node
>    Affects Versions: Edit log branch (HDFS-1073)
>            Reporter: Todd Lipcon
>            Assignee: Todd Lipcon
>             Fix For: Edit log branch (HDFS-1073)
>
>
> Right now there is very little test coverage of situations where one or more of the edits
directories fails. In trunk, the behavior when all of the edits directories are dead is that
the NN prints a fatal level log message and calls Runtime.exit(-1).
> I don't think this is really the behavior we want. Needs a bit of thought, but I think
something like the following would make more sense:
> - any calls currently waiting on logSync should end up throwing an exception
> - NN should probably enter safe mode
> - ops can restore edits directories and then ask the NN to restore storage, at which
point it could edit safemode
> - alternatively, ops could call ask the NN to do saveNamespace and then shut it down

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message