[
https://issues.apache.org/jira/browse/HBASE-13367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14390520#comment-14390520
]
Liu Shaohui commented on HBASE-13367:
-------------------------------------
[~esteban]
{quote}
how the transitions from this new state will happen? when the delta between the
source and the sink is 0?
{quote}
Yes. We need a external tool to check all edits have been replicated to the
sink cluster.
{quote}
or do we need an operator to perform the transition?
{quote}
Yes, we may introduce an new attribute in HTD.
{quote}
wouldn't be easier just re-use the READONLY attribute from HTD?
{quote}
This new state is used for tables in backup cluster. But the read only table
will reject the write operations from replication.
So we may need to introduce a new attribute.
> Add a replication label to mutations from replication
> -----------------------------------------------------
>
> Key: HBASE-13367
> URL: https://issues.apache.org/jira/browse/HBASE-13367
> Project: HBase
> Issue Type: Improvement
> Reporter: Liu Shaohui
> Assignee: Liu Shaohui
>
> In some scenarios, the regions need to distinguish the mutations from client
> for actual users or from replication of peer cluster.
> - Lower the priority of mutations from replication to improve the latency of
> requests from actuals users
> - Set table in replicated state to keep data consistent. In this state, the
> table will reject mutations from users, but accept mutations from replication
> and read requests from users.
> So we need to add a replication label to mutations from replication.
> Suggestions and discussions are welcomed. Thanks
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
