[
https://issues.apache.org/jira/browse/HBASE-8772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13692886#comment-13692886
]
Jieshan Bean commented on HBASE-8772:
-------------------------------------
Aggreed with J-D. Below is some key points need to consider in my own
understanding:
1. Seperated process only for ReplicationSource? Meanwhile, ReplicationSink
could also be impacted by GC triggered by RegionServer, although
ReplicationSink is not a seperated thread currently.
2. Need to introduce a new RPC interface? RegionInterface can not be used any
more.
3. Need to track logs itself.
4. Queue-Failover is more complicated. Since RegionServer may have aborted but
Replication process still be there, and vice versa. So each replication process
should be registered in ZooKeeper, and tracked by each RegionServer.
5. Support for security.
> Separate Replication from HBase RegionServer process
> ----------------------------------------------------
>
> Key: HBASE-8772
> URL: https://issues.apache.org/jira/browse/HBASE-8772
> Project: HBase
> Issue Type: New Feature
> Components: regionserver, Replication
> Reporter: Sameer Vaishampayan
> Labels: performance
>
> Replication is a separate functionality than managing regions and should be
> able to be managed separately as a service rather than rolled into
> RegionServer. Load on RegionServer, gc etc shouldn't affect the replication
> service.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
