On Wed, Jan 15, 2014 at 11:17 AM, Stack <st...@duboce.net> wrote: > A few of us chatting offline -- Jimmy, Jon, Elliott, and I -- were > wondering if you couldn't solve this read replicas in a more hbase 'native' > way* by just bringing up three tables -- a main table and then two snapshot > clones with the clones refreshed on a period (via snapshot or via > in-cluster replication) -- and then a shim on top of an HBase client would > read from the main table until failure and then from a snapshot until the > main came back. Reads from snapshot tables could be marked 'stale'. You'd > have to modify the balancer so the tables -- or at least their regions -- > were physically distinct... you might be able just have the three tables > each in a different namespace. >
I like the idea of building on what we have today without introducing a lot of new code and/or making existing code twisty. -- Best regards, - Andy Problems worthy of attack prove their worth by hitting back. - Piet Hein (via Tom White)
