Hi, So I was wondering how to surmount a possible out-of-order replication of edits belonging to a particular region in the event the latter gets moved from one region server to another.
The memstores in the region would get flushed prior to the movement of the region from Region server RS1 to RS2, but if the replication source(s) on RS1 is(are) slow at shipping the edits, it may so happen that there are edits pending replication in the WAL of RS1, while the region is getting fresh edits to the WAL on RS2, after being made available on RS2. And since the replication sources on the two RSes are working independently, it's possible that the edits to a given region (and therefore a given rows) get processed out of order. Do you guys agree with the scenario. If so, is there any plan to fix this. It could be largely a non-issue as long as the edits are touching different rows in the region, but could be a stark one when the edits touch the same row. -thanks SB -- View this message in context: http://apache-hbase.679495.n3.nabble.com/Region-movements-and-HBase-replication-tp4052700.html Sent from the HBase Developer mailing list archive at Nabble.com.
