[
https://issues.apache.org/jira/browse/HBASE-13063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Enis Soztutar updated HBASE-13063:
----------------------------------
Attachment: hbase-13063-addendum.patch
I think the problem is that the flush call after the writes may not flush
because the primary region may already be flushing (saw from failed test logs
running in a loop).
This may cause a problem with the test since it expects that the last flush
will flush everything. I have fixed the problem with this addendum patch by not
requesting the flush when the seconday region replica comes up when memstore
replication is set to false (because we do not need this for correctness).
Reviews welcome.
> Allow to turn off memstore replication for region replicas
> ----------------------------------------------------------
>
> Key: HBASE-13063
> URL: https://issues.apache.org/jira/browse/HBASE-13063
> Project: HBase
> Issue Type: New Feature
> Components: regionserver, Replication
> Reporter: Matteo Bertozzi
> Assignee: Matteo Bertozzi
> Priority: Minor
> Fix For: 2.0.0, 1.1.0
>
> Attachments: HBASE-13063-v0.patch, HBASE-13063-v1-branch-1.patch,
> HBASE-13063-v1.patch, HBASE-13063-v1.patch, HBASE-13063-v2.patch,
> HBASE-13063-v2.patch, hbase-13063-addendum.patch
>
>
> HBASE-11568 allows to use replication to send wal edits from the primary to
> the replicas.
> sometimes the memstore replication is not required, so it will be nice have a
> flag to disable it.
> the result will be more or less the same to what we have in phase-1, but with
> the row-level consistency provided by the "flush" edit transfered via
> replication to refresh the hfiles.
> create 't1', 'f', {REGION_REPLICATION => 2, REGION_MEMSTORE_REPLICATION =>
> false}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
