[jira] [Commented] (HBASE-4131) Make the Replication Service pluggable via a standard interface definition

["dhruba borthakur (JIRA)" <ji...@apache.org>]

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

dhruba borthakur commented on HBASE-4131:
-----------------------------------------

To keep compatibility with the currently existing Replication Service, my initial proposal is to do something like this:

{code}

public interface ReplicationService {

  /**
   * Start replication services.
   * @throws IOException
   */
  public void startReplicationService() throws IOException;

  /**
   * Stops replication service.
   */
  public void stopReplicationService();

  /**
   * Returns a WALObserver for the service. This is needed to 
   * observe log rolls and log archival events.
   */
  public WALObserver getWALObserver();

  /**
   * Carry on the list of log entries down to the sink
   * @param entries list of entries to replicate
   * @throws IOException
   */
  public void replicateLogEntries(HLog.Entry[] entries) throws IOException;
}
{code}

> Make the Replication Service pluggable via a standard interface definition
> --------------------------------------------------------------------------
>
>                 Key: HBASE-4131
>                 URL: https://issues.apache.org/jira/browse/HBASE-4131
>             Project: HBase
>          Issue Type: Improvement
>          Components: regionserver
>            Reporter: dhruba borthakur
>            Assignee: dhruba borthakur
>
> The current HBase code supports a replication service that can be used to sync data from from one hbase cluster to another. It would be nice to make it a pluggable interface so that other cross-data-center replication services can be used in conjuction with HBase.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira