accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Elser (JIRA)" <>
Subject [jira] [Resolved] (ACCUMULO-2581) Create service in Master to assign replication work
Date Wed, 21 May 2014 05:08:38 GMT


Josh Elser resolved ACCUMULO-2581.

       Resolution: Fixed
    Fix Version/s:     (was: 1.7.0)

Two implementations, both leverage the DistributedWorkQueue. One asserts proper ordering of
WALs for a table to a peer, and the other allows for replication of WALs to a peer in any
order (could allow for data to be replayed in the wrong order depending on the table scheme).

> Create service in Master to assign replication work
> ---------------------------------------------------
>                 Key: ACCUMULO-2581
>                 URL:
>             Project: Accumulo
>          Issue Type: Sub-task
>            Reporter: Josh Elser
>            Assignee: Josh Elser
> 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
> 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).

This message was sent by Atlassian JIRA

View raw message