We had an incident that the fsimage at secondary NameNode was truncated but got uploaded to the primary NameNode. The primary NameNode simply rolled the image without checking its integrity, therefore causing the fsimage to corrupt. The primary NameNode should check the new image's integrity before rolling fsimage.
|Status||Patch Available [ 10002 ]||Resolved [ 5 ]|
|Fix Version/s||0.23.0 [ 12315571 ]|
|Fix Version/s||0.22.0 [ 12314241 ]|
|Resolution||Fixed [ 1 ]|
|Status||Open [ 1 ]||Patch Available [ 10002 ]|