[
https://issues.apache.org/jira/browse/HBASE-8772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13689951#comment-13689951
]
Andrew Purtell edited comment on HBASE-8772 at 6/21/13 1:58 AM:
----------------------------------------------------------------
So we should set up and manage separate replicator processes? HBase is already
considered to have too many moving parts. How do we deal with that?
On the other hand, maybe a small refactoring would give us a Main somewhere
where it could be an option if you want to take it on. But this would not be a
default. Would that work?
was (Author: apurtell):
So we should set up and manage separate replicator processes? HBase is
already considered to have too many moving parts? How do we deal with that?
> 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
