[jira] [Comment Edited] (HBASE-27464) In memory compaction 'COMPACT' may cause data corruption when adding cells large than maxAlloc(default 256k) size

["chenglei (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/HBASE-27464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17633212#comment-17633212 ] 

chenglei edited comment on HBASE-27464 at 11/13/22 4:51 AM:
------------------------------------------------------------

[~zhengzhuobinzzb], yes, it is indeed a bug , although fixing it seems somewhat simple , but I think we should better make an UT to reproduce your problem described.


was (Author: comnetwork):
[~zhengzhuobinzzb], it is indeed a bug , although fixing it seems somewhat simple , but I think we should better make an UT to reproduce your problem described.

> In memory compaction 'COMPACT' may cause data corruption when adding cells large than maxAlloc(default 256k) size
> -----------------------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-27464
>                 URL: https://issues.apache.org/jira/browse/HBASE-27464
>             Project: HBase
>          Issue Type: Bug
>          Components: in-memory-compaction
>            Reporter: zhuobin zheng
>            Priority: Critical
>         Attachments: image-2022-11-04-15-46-21-645.png
>
>
> When init 'CellChunkImmutableSegment' for 'COMPACT' action, we not force copy to current MSLab. 
> When cell size bigger than maxAlloc, cell will stay in previous chunk which will recycle after segment replace, and we may read wrong data when these chunk reused by others.
> !image-2022-11-04-15-46-21-645.png!
>  
> Timeline:
>  # add a cell 'A' bigger than 256K
>  # cell 'A' will copy to a chunk 'A' when first compact
>  # cell 'A' will retain in chunk 'A' when second compact
>  # chunk 'A' recycled after segment swap and close



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