[ https://issues.apache.org/jira/browse/HBASE-17918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Duo Zhang updated HBASE-17918: ------------------------------ Resolution: Fixed Status: Resolved (was: Patch Available) Pushed to master and branch-2. > 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)