[ 
https://issues.apache.org/jira/browse/HDDS-15723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ivan Andika updated HDDS-15723:
-------------------------------
    Description: 
Currently, the datanode will finalize a block if it encounters PutBlock with 
eof flag set. There should only be one eof flag since PutBlock is not 
idempotent. Currently this is not caught which can cause issue like HDDS-12007 
to not be detected.

Therefore, we need to assert that once we encounter block EOF, there will not 
be any more writes on that block (e.g. BlockID <container ID, localID>). We 
should throw exception if there are some writes after EOF.

  was:
Currently, the datanode will finalize a block if it encounters PutBlock with 
eof flag set. There should only be one eof flag since PutBlock is not 
idempotent. Currently this is not caught which can cause issue like HDDS-12007 
to not be detected.

Therefore, we need to assert that once we encounter EOF, there will not be any 
more writes. We should throw exception if there are some writes after EOF.


> Assert that there is no more PutBlock after EOF is received
> -----------------------------------------------------------
>
>                 Key: HDDS-15723
>                 URL: https://issues.apache.org/jira/browse/HDDS-15723
>             Project: Apache Ozone
>          Issue Type: Task
>            Reporter: Ivan Andika
>            Assignee: Prathmesh Sapate
>            Priority: Major
>
> Currently, the datanode will finalize a block if it encounters PutBlock with 
> eof flag set. There should only be one eof flag since PutBlock is not 
> idempotent. Currently this is not caught which can cause issue like 
> HDDS-12007 to not be detected.
> Therefore, we need to assert that once we encounter block EOF, there will not 
> be any more writes on that block (e.g. BlockID <container ID, localID>). We 
> should throw exception if there are some writes after EOF.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to