hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Konstantin Shvachko (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HDFS-1508) Ability to do savenamespace without being in safemode
Date Wed, 08 Dec 2010 02:47:03 GMT

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

Konstantin Shvachko commented on HDFS-1508:
-------------------------------------------

Dhruba, I don't think our discussion is productive here. My logic is simple. There are 2 ways
to move on with this: 
- either you need to address the validity of proposed changes by analyzing multiple failure
scenarios,
- or you should face operational issues to solve the problem with existing features.

If you are arguing that operational approach doesn't work for you, then you have to address
the validity concerns, which you don't. 
Would you rather risk loosing the last image while testing it on a live cluster running on
a spare tire?

I agree with Sanjay that 1073 will simplify the analysis.

> Ability to do savenamespace without being in safemode
> -----------------------------------------------------
>
>                 Key: HDFS-1508
>                 URL: https://issues.apache.org/jira/browse/HDFS-1508
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: name-node
>            Reporter: dhruba borthakur
>            Assignee: dhruba borthakur
>         Attachments: savenamespaceWithoutSafemode.txt, savenamespaceWithoutSafemode2.txt,
savenamespaceWithoutSafemode3.txt, savenamespaceWithoutSafemode4.txt
>
>
> In the current code, the administrator can run savenamespace only after putting the namenode
in safemode. This means that applications that are writing to HDFS encounters errors because
the NN is in safemode. We would like to allow saveNamespace even when the namenode is not
in safemode.
> The savenamespace command already acquires the FSNamesystem writelock. There is no need
to require that the namenode is in safemode too.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message