[
https://issues.apache.org/jira/browse/HBASE-12672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14244681#comment-14244681
]
James Taylor commented on HBASE-12672:
--------------------------------------
bq. any activity that depends on the special table update - is bounded by the
characteristics of the WAN link not the local in-datacenter networks.
Yes, that'd be the tradeoff, so you'd only want to do it in special
circumstances for tables that need this behavior. In particular, it may be ok
for sequences because it's incremented once for a configurable batch size, so
the cost is amortized over the batch size.
> Support optionally replicating a table synchronously
> ----------------------------------------------------
>
> Key: HBASE-12672
> URL: https://issues.apache.org/jira/browse/HBASE-12672
> Project: HBase
> Issue Type: Improvement
> Reporter: James Taylor
> Priority: Minor
>
> Sometimes a table may contain state in which it's crucial to know that
> replication occurred before continuing with the update. Though this would
> mean that you'd block updates to this table if your secondary cluster was
> unavailable, that might be a tradeoff that a user would be willing to make.
> An example would be in support of SQL sequences. See this thread
> (http://s.apache.org/fTP) and PHOENIX-1422 for more discussion and context.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
