> From: Jason Rutherglen <[email protected]> > Andrew, thanks for the information. On the surface it looks like > HBASE-2357 would be using the same mechanism for streaming the WAL > (except the master slave failover) as HBASE-1295, however HBASE-2357 > seems to imply that's not the case?
It could be done that way, but 2357 has a broader focus right? -- not master-slave only (though that certainly is an option) but also master-master maintaining the same write/read ordering as achievable with single-region-location deployment. Not that such ordering is necessarily required, but the notion is to consider a three way trade off: 1) Strong consistency over other concerns with single region location deployment 2) Higher availability with consistency over write latency with read replicas and a ZAB- or Paxos-serialized write path 3) Highest availability with lowest latency over other concerns with read replicas updated best effort from the write path - Andy
