Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jira@apache.org
Date: Fri, 23 May 2014 01:48:04 +0000 (UTC)
From: "Josh Elser (JIRA)" <jira@apache.org>
To: notifications@accumulo.apache.org
Message-ID: <JIRA.12716220.1400798232384.5737.1400809684217@arcas>
In-Reply-To: <JIRA.12716220.1400798232384@arcas>
References: <JIRA.12716220.1400798232384@arcas>
Subject: [jira] [Resolved] (ACCUMULO-2834) Immediately re-queue files which
 have more data to replicate
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Josh Elser resolved ACCUMULO-2834.
----------------------------------

    Resolution: Fixed

> Immediately re-queue files which have more data to replicate
> ------------------------------------------------------------
>
>                 Key: ACCUMULO-2834
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-2834
>             Project: Accumulo
>          Issue Type: Sub-task
>          Components: replication
>            Reporter: Josh Elser
>            Assignee: Josh Elser
>             Fix For: 1.7.0
>
>
> Noticed that during high ingest load, there's a bit of downtime between iterations as, after the batch size is reached, the tserver records the progress it made, and it waits for the master to re-queue the file.
> This is a bit silly as the tserver could just continue to replicate from where it left off to reduce the latency in waiting to replicate the file. The remote side will still buffer, so we shouldn't be oversaturating the remote.


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