Details
-
Sub-task
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
Description
We likely want the Master to handle the coordination of reading the records of what data needs to be replicated to the slave(s). We do not have the Master to perform the actual replication, but to delegate out the tasks to the tservers in the master cluster, and simple track the progress, success and failure of each "replication act". This will allow for a much more scalable implementation.
This service should be able to grow and shrink as replication requests increase/decrease (but yet retain configurable upper and lower bounds). It likely requires its own Thrift service to manage the variety of responses that might come from an attempt to replicate data (failure, success, partial success, etc).
This service would be the only process that removes replication entries from the persisted store (table).