You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@accumulo.apache.org by "Josh Elser (JIRA)" <ji...@apache.org> on 2014/04/16 17:30:23 UTC

[jira] [Assigned] (ACCUMULO-2579) Modify "live ingest" code path to create replication entries

     [ https://issues.apache.org/jira/browse/ACCUMULO-2579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Josh Elser reassigned ACCUMULO-2579:
------------------------------------

    Assignee: Josh Elser

> Modify "live ingest" code path to create replication entries
> ------------------------------------------------------------
>
>                 Key: ACCUMULO-2579
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-2579
>             Project: Accumulo
>          Issue Type: Sub-task
>            Reporter: Josh Elser
>            Assignee: Josh Elser
>             Fix For: 1.7.0
>
>
> When new writes come in to a server, we want to track the updates to the WAL, and ensure that we create entries to track that we need to replicate that data.
> Supporting replication over portions of a WAL is desirable to reduce replication latency, but this may decrease the total ingest throughput.
> Despite not wanting to persist a replication record for every update, but we might need to so we can ensure that we don't miss data that needs replication. Need to observe how things like the tserver processes BatchWriter updates -- I believe the problem is analogous.



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