Affects Version/s: 1.2.0, 3.0.0
Fix Version/s: None
In one test case, NameNode allocated a block and then was killed before the client got the addBlock response.
After NameNode restarted, the block which was never created was considered as a missing block and FSCK would report the file is corrupted.
The problem seems to be that, NameNode can't differentiate between a never-created block and a block which is really missing.
|Assignee||Brandon Li [ brandonli ]|
|Status||Open [ 1 ]||Resolved [ 5 ]|
|Resolution||Duplicate [ 3 ]|