[
https://issues.apache.org/jira/browse/HDFS-10614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15379230#comment-15379230
]
Vinayakumar B commented on HDFS-10614:
--------------------------------------
bq. whether we can also add an extra check to make sure the reported block's GS
is greater than the stored block. In this way the logic will be the same with
setGenerationStampAndVerifyReplicas in updatePipeline.
IMO Since the block reported in the storage is not in the FINALIZED state,
irrespective of the genstamp, block should be removed from that {{storage}}.
Anyway it would be added as expected location. Once the block is complete and
reports FINALIZED state, it would be added back.
> Appended blocks can be closed even before IBRs from DataNodes
> -------------------------------------------------------------
>
> Key: HDFS-10614
> URL: https://issues.apache.org/jira/browse/HDFS-10614
> Project: Hadoop HDFS
> Issue Type: Bug
> Reporter: Vinayakumar B
> Assignee: Vinayakumar B
> Attachments: HDFS-10614.01.patch, HDFS-10614.02.patch
>
>
> Scenario:
> 1. Open the file for append()
> 2. Trigger append pipeline setup by adding some data.
> 3. Consider RECEIVING IBRs of DNs reaches NN first.
> 4. updatePipeline() rpc sent to namenode to update the pipeline.
> 5. Now, if complete() is called on the file even before closing the
> pipeline, then block will be COMPLETE, even before block is actually
> FINALIZED at DN side and file will be closed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
