[
https://issues.apache.org/jira/browse/HBASE-17918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16435082#comment-16435082
]
Hudson commented on HBASE-17918:
--------------------------------
Results for branch HBASE-19064
[build #94 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/HBASE-19064/94/]:
(x) *{color:red}-1 overall{color}*
----
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://builds.apache.org/job/HBase%20Nightly/job/HBASE-19064/94//General_Nightly_Build_Report/]
(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://builds.apache.org/job/HBase%20Nightly/job/HBASE-19064/94//JDK8_Nightly_Build_Report_(Hadoop2)/]
(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://builds.apache.org/job/HBase%20Nightly/job/HBASE-19064/94//JDK8_Nightly_Build_Report_(Hadoop3)/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
> document serial replication
> ---------------------------
>
> Key: HBASE-17918
> URL: https://issues.apache.org/jira/browse/HBASE-17918
> Project: HBase
> Issue Type: Task
> Components: documentation, Replication
> Reporter: Sean Busbey
> Assignee: Yi Mei
> Priority: Critical
> Fix For: 3.0.0, 2.1.0
>
> Attachments: HBASE-17918-v4.patch, 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
(v7.6.3#76005)
