stack wrote:
Andrew Purtell wrote:
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?
Thinking more on the above, HRS failures are currently done by the
single-node master in a single thread when what we really need is a
distributed processing of the failure splitting commit logs (as per BT
paper) so failures are cleaned up promptly.
Base point is that after ZK integration, Master can be shrunk even
further. Rather than running actual split, instead its role shrinks to
that of orchestrator.
St.Ack
