You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "Liu Junhong (Jira)" <ji...@apache.org> on 2020/09/15 19:21:00 UTC

[jira] [Comment Edited] (HBASE-24984) WAL corruption due to early DBBs re-use when Durability.ASYNC_WAL is used with multi operation

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

Liu Junhong edited comment on HBASE-24984 at 9/15/20, 7:20 PM:
---------------------------------------------------------------

The cleanUp in ServerCall may be called more than once. So we should use AtomicInteger , and reference % 10 for call， reference  / 10 for wal.


was (Author: mopishv0):
The cleanUp in ServerCall may be called more than once. So we should use AtomicInteger , and referenc % 10 for call， reference  / 10 for wal.

> WAL corruption due to early DBBs re-use when Durability.ASYNC_WAL is used with multi operation
> ----------------------------------------------------------------------------------------------
>
>                 Key: HBASE-24984
>                 URL: https://issues.apache.org/jira/browse/HBASE-24984
>             Project: HBase
>          Issue Type: Bug
>          Components: rpc, wal
>    Affects Versions: 2.1.6
>            Reporter: Liu Junhong
>            Priority: Major
>
> After bugfix HBASE-22539, When client use BufferedMutator or multiple mutation , there will be one RpcCall and mutliple FSWALEntry .  At the time RpcCall finish and one FSWALEntry call release() , the remain FSWALEntries may trigger RuntimeException or segmentation fault .
> We should use RefCnt  instead of AtomicInteger for org.apache.hadoop.hbase.ipc.ServerCall.reference?



--
This message was sent by Atlassian Jira
(v8.3.4#803005)