accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-378) Multi data center replication
Date Thu, 29 May 2014 01:02:30 GMT

    [ https://issues.apache.org/jira/browse/ACCUMULO-378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14011910#comment-14011910
] 

ASF subversion and git services commented on ACCUMULO-378:
----------------------------------------------------------

Commit 0ff0e021d3fc95794137dfeb3f6e1335b61b0a16 in accumulo's branch refs/heads/ACCUMULO-378
from [~elserj]
[ https://git-wip-us.apache.org/repos/asf?p=accumulo.git;h=0ff0e02 ]

ACCUMULO-378 Resize the threadpool used for sending data by checking the configuration periodically

Use the SimpleTimer to just schedule a check of the configuration
to see what the value is for the maximum size of the threadpool which
is used with the DistributedWorkQueue and ReplicationProcessor.


> Multi data center replication
> -----------------------------
>
>                 Key: ACCUMULO-378
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-378
>             Project: Accumulo
>          Issue Type: New Feature
>          Components: replication
>            Reporter: Sapan Shah
>            Assignee: Josh Elser
>            Priority: Minor
>             Fix For: 1.7.0
>
>
> The use case here is where people have multiple data centers and need to replicate the
data in between them.  Accumulo can model this replication after the way that HBase currently
handles the replication as detailed here (http://hbase.apache.org/replication.html).  
> There will be one master Cluster and multiple slave clusters.  Accumulo will use the
Master-Push model to replicate the statements from the master clusters WAL to the various
slaves WALs.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message