[
https://issues.apache.org/jira/browse/HBASE-24984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17381032#comment-17381032
]
Gaurav Kanade commented on HBASE-24984:
---------------------------------------
Incidentally the original Jira HBASE-22539, was first reported on a 2.1.x
branch and then mentioned that it affects only 2.x based releases, however the
patch seems to be applied to master as well. Hence we are still checking if
something different in the buffer pool release mechanism in the master which is
causing the difference in repro.
> 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
> Assignee: Gaurav Kanade
> Priority: Critical
> Fix For: 2.5.0, 2.3.6, 3.0.0-alpha-2, 2.4.5
>
>
> 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)
