hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Harsh J (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-3522) If NN is in safemode, it should throw SafeModeException when getBlockLocations has zero locations
Date Tue, 12 Jun 2012 16:18:43 GMT

    [ https://issues.apache.org/jira/browse/HDFS-3522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13293729#comment-13293729
] 

Harsh J commented on HDFS-3522:
-------------------------------

I don't get it. Doesn't this disable reads in safemode completely?

We've here only thought of safemode being toggled upon NN startup but there's a case of NN
entering safemode manually by an admin and in this scenario reads *can* and *should* work
fully. Please explain why we wish to cripple this scenario/feature too, we've had customers
rely on it in past.

By definition of safemode, its always been to prevent edits (any edits to namespace) not reads
(which do NOT touch namespace). This breaks the whole concept around that, going by the release
note "getBlockLocations(), and hence open() for read, will now throw SafeModeException if
the NameNode is still in safe mode and there are no replicas reported yet for one of the blocks
in the file.".

If am grossly wrong, let me know. This may have also started failing the test {{TestFileLengthOnClusterRestart}}.
                
> If NN is in safemode, it should throw SafeModeException when getBlockLocations has zero
locations
> -------------------------------------------------------------------------------------------------
>
>                 Key: HDFS-3522
>                 URL: https://issues.apache.org/jira/browse/HDFS-3522
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: name-node
>    Affects Versions: 3.0.0
>            Reporter: Brandon Li
>            Assignee: Brandon Li
>             Fix For: 2.0.1-alpha
>
>         Attachments: HDFS-3522.patch
>
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message