[jira] [Created] (HBASE-11765) ReplicationSink should merge the Put/Delete of the same row into one Action even if they are from different hlog entry.

["Tianying Chang (JIRA)" <ji...@apache.org>]

Tianying Chang created HBASE-11765:
--------------------------------------

             Summary: ReplicationSink should merge the Put/Delete of the same row into one Action even if they are from different hlog entry.
                 Key: HBASE-11765
                 URL: https://issues.apache.org/jira/browse/HBASE-11765
             Project: HBase
          Issue Type: Improvement
          Components: Performance, Replication
    Affects Versions: 0.94.7
            Reporter: Tianying Chang
            Assignee: Tianying Chang
             Fix For: 0.94.7


The current replicationSink code make sure it will only create one Put/Delete action of the kv of same row if it is from same hlog entry. However, when the same row of Put/Delete exist in different hlog entry, multiple Put/Delete action will be created, this will cause synchronization cost during the multi batch operation. 

In one of our application traffic pattern which has delete for same row twice for many rows, we saw doMiniBatchMutation() is invoked many times due to the row lock for the same row. ReplicationSink side is super slow, and replication queue build up. 

We should put the put/delete for the same row into one Put/Delete action even if they are from different hlog entry. 



--
This message was sent by Atlassian JIRA
(v6.2#6252)