[
https://issues.apache.org/jira/browse/HDFS-5443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jing Zhao updated HDFS-5443:
----------------------------
Priority: Major (was: Blocker)
Fix Version/s: (was: 2.4.0)
2.3.0
I've merged this to branch-2.3.
> Delete 0-sized block when deleting an under-construction file that is
> included in snapshot
> ------------------------------------------------------------------------------------------
>
> Key: HDFS-5443
> URL: https://issues.apache.org/jira/browse/HDFS-5443
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: snapshots
> Affects Versions: 3.0.0, 2.2.0
> Reporter: Uma Maheswara Rao G
> Assignee: Jing Zhao
> Fix For: 2.3.0
>
> Attachments: 5443-test.patch, HDFS-5443.000.patch
>
>
> Namenode can stuck in safemode on restart if it crashes just after addblock
> logsync and after taking snapshot for such file. This issue is reported by
> Prakash and Sathish.
> On looking into the issue following things are happening.
> .
> 1) Client added block at NN and just did logsync
> So, NN has block ID persisted.
> 2)Before returning addblock response to client take a snapshot for root or
> parent directories for that file
> 3) Delete parent directory for that file
> 4) Now crash the NN with out responding success to client for that addBlock
> call
> Now on restart of the Namenode, it will stuck in safemode.
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
