[
https://issues.apache.org/jira/browse/HBASE-12672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14244524#comment-14244524
]
Lars Hofhansl edited comment on HBASE-12672 at 12/12/14 5:58 PM:
-----------------------------------------------------------------
That how it works now: The queue is the WAL. Once the edit is in the WAL it
will be made visible to reader and it will eventually be shipped to the
secondary.
Is what you mean:
# put it in the queue (but it's *not* visible to any readers)
# only once the edit is applied on the secondary we make it visible in the
primary
?
was (Author: lhofhansl):
That how it works now: The queue is the WAL. Once the edit is in the WAL it
will be made visible to reader and it will eventually be shipped to the
secondary.
Is what you mean is:
# put it in the queue (but it's *not* visible to any readers)
# only once the edit is applied on the secondary we make it visible in the
primary
?
> 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)
