[
https://issues.apache.org/jira/browse/HBASE-17918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16273468#comment-16273468
]
Hudson commented on HBASE-17918:
--------------------------------
FAILURE: Integrated in Jenkins build HBase-Trunk_matrix #4145 (See
[https://builds.apache.org/job/HBase-Trunk_matrix/4145/])
HBASE-17918 document serial replication (zhangduo: rev
6a6409a30aa634875467683203de0e21e0491986)
* (edit) src/main/asciidoc/_chapters/ops_mgt.adoc
> document serial replication
> ---------------------------
>
> Key: HBASE-17918
> URL: https://issues.apache.org/jira/browse/HBASE-17918
> Project: HBase
> Issue Type: Task
> Components: documentation, Replication
> Affects Versions: 2.0.0, 3.0.0
> Reporter: Sean Busbey
> Assignee: Yi Mei
> Priority: Critical
> Fix For: 3.0.0, 2.0.0-beta-1
>
> Attachments: HBASE-17918.v1.patch, HBASE-17918.v2.patch,
> HBASE-17918.v3.patch
>
>
> It looks like HBASE-9465 addresses one of the major flaws in our existing
> replication (namely that order of delivery is not assured). All I see in the
> reference guide is a note on {{hbase.serial.replication.waitingMs}}. Instead
> we should cover this in the replication section, especially given that we
> call out the order of delivery limitation.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
