[ https://issues.apache.org/jira/browse/HBASE-11367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14134572#comment-14134572 ]
Enis Soztutar commented on HBASE-11367: --------------------------------------- [~ram_krish] any luck so far? Do you want to create a separate backport issue? I remembered that I have a patch for this that applies on top of 0.98.4, which is backported from the final master patch. Do you want me to attach it? > Pluggable replication endpoint > ------------------------------ > > Key: HBASE-11367 > URL: https://issues.apache.org/jira/browse/HBASE-11367 > Project: HBase > Issue Type: Sub-task > Reporter: Enis Soztutar > Assignee: Enis Soztutar > Priority: Blocker > Fix For: 0.99.0, 2.0.0 > > Attachments: 0001-11367.patch, hbase-11367_v1.patch, > hbase-11367_v2.patch, hbase-11367_v3.patch, hbase-11367_v4.patch, > hbase-11367_v4.patch, hbase-11367_v5.patch > > > We need a pluggable endpoint for replication for more flexibility. See parent > jira for more context. > ReplicationSource tails the logs for each peer. This jira introduces > ReplicationEndpoint which is customizable per peer. ReplicationEndpoint is > run in the same RS process and instantiated per replication peer per region > server. Implementations of this interface handle the actual shipping of WAL > edits to the remote cluster. -- This message was sent by Atlassian JIRA (v6.3.4#6332)