Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jira@apache.org
Date: Mon, 7 Oct 2013 20:30:41 +0000 (UTC)
From: "Keith Turner (JIRA)" <jira@apache.org>
To: notifications@accumulo.apache.org
Message-ID: <JIRA.12672648.1381166871328.27905.1381177841945@arcas>
In-Reply-To: <JIRA.12672648.1381166871328@arcas>
References: <JIRA.12672648.1381166871328@arcas>
Subject: [jira] [Commented] (ACCUMULO-1754) support scale-up behavior in
 BatchWriter
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Keith Turner commented on ACCUMULO-1754:
----------------------------------------

This issue complements ACCUMULO-1083. 

TableServerBatchReader does something like this.  If it has more threads than tablet servers, then it start splitting things up by tablet and sending concurrent request to tablet servers.

> support scale-up behavior in BatchWriter
> ----------------------------------------
>
>                 Key: ACCUMULO-1754
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-1754
>             Project: Accumulo
>          Issue Type: Improvement
>          Components: client
>            Reporter: Adam Fuchs
>
> The o.a.a.client.impl.TabletServerBatchWriter currently limits write threads to one per server. Some people want to use Accumulo on beefy servers where sending one batch at a time is a bottleneck. We can improve the performance on small clusters of beefy nodes by splitting up write batches by tablet and server.
> This should be done in such a way that we can still batch across tablets when the cluster is large. Basically, mutations should be binned by server, then further binned by tablet up to the limit of (some factor of) threads in the BatchWriter's thread pool.


--
This message was sent by Atlassian JIRA
(v6.1#6144)