hadoop-hdfs-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Uma Maheswara Rao G (JIRA)" <j...@apache.org>
Subject [jira] [Created] (HDFS-5474) Deletesnapshot can make Namenode in safemode on NN restarts.
Date Thu, 07 Nov 2013 06:33:17 GMT
Uma Maheswara Rao G created HDFS-5474:
-----------------------------------------

             Summary: Deletesnapshot can make Namenode in safemode on NN restarts.
                 Key: HDFS-5474
                 URL: https://issues.apache.org/jira/browse/HDFS-5474
             Project: Hadoop HDFS
          Issue Type: Bug
          Components: snapshots
            Reporter: Uma Maheswara Rao G
            Assignee: sathish


When we deletesnapshot, we are deleting the blocks associated to that snapshot and after that
we do logsync to editlog about deleteSnapshot.
There can be a chance that blocks removed from blocks map but before log sync if there is
BR ,  NN may finds that block does not exist in blocks map and may invalidate that block.
As part HB, invalidation info also can go. After this steps if Namenode shutdown before actually
do logsync,  On restart it will still consider that snapshot Inodes and expect blocks to report
from DN.

Simple solution is, we should simply move down that blocks removal after logsync only. Similar
to delete op.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message