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

Wei-Chiu Chuang updated HDDS-11014:
-----------------------------------
    Description: 
We designed a separate lastChunkInfoTable to record the last chunk of a block 
that may be rapidly updated by hsync.

That is causing a lot of problems because if a block is not longer than a full 
chunk, it would appear to be missing to other part of Ozone system, causing 
data loss.

 

We should merge the block data from lastChunkInfoTable to blockDataTable when 
the block is finalized. 

 

And also when end of block is reached.

  was:
We designed a separate lastChunkInfoTable to record the last chunk of a block 
that may be rapidly updated by hsync.

That is causing a lot of problems because if a block is not longer than a full 
chunk, it would appear to be missing to other part of Ozone system, causing 
data loss.

 

We should merge the block data from lastChunkInfoTable to blockDataTable when 
the block is finalized.


> [hsync] Block finalization should also merge last chunk to blockDataTable
> -------------------------------------------------------------------------
>
>                 Key: HDDS-11014
>                 URL: https://issues.apache.org/jira/browse/HDDS-11014
>             Project: Apache Ozone
>          Issue Type: Sub-task
>            Reporter: Wei-Chiu Chuang
>            Priority: Blocker
>
> We designed a separate lastChunkInfoTable to record the last chunk of a block 
> that may be rapidly updated by hsync.
> That is causing a lot of problems because if a block is not longer than a 
> full chunk, it would appear to be missing to other part of Ozone system, 
> causing data loss.
>  
> We should merge the block data from lastChunkInfoTable to blockDataTable when 
> the block is finalized. 
>  
> And also when end of block is reached.



--
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