Andrew Purtell wrote:
There's no reason that all the live HRS cannot use ZK to
negotiate among themselves who should also assume the master
role, since the master role will also go on a diet. After ZK
integration, is there a need for separate processes for the
master and region server functions?
Yesterday profiling the master, its doing next to nothing but waiting
for something to do (heavy upload on small cluster) -- and this is
before a bunch of its functionality is redone over in ZK.
In fact the master role might be distributed among the HRS
via ZK. About the only need for a master would be to manage
region assignments upon splits and HRS failures. Why not put
up locks (or appropriate synchronization primitives) for
every region and have the HRS figure out among themselves
who should carry new or unassigned regions?
I like this idea of yours Andrew. Make an issue?
St.Ack
