Return-Path: X-Original-To: apmail-accumulo-notifications-archive@minotaur.apache.org Delivered-To: apmail-accumulo-notifications-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 3139B10104 for ; Tue, 3 Sep 2013 01:54:52 +0000 (UTC) Received: (qmail 62466 invoked by uid 500); 3 Sep 2013 01:54:52 -0000 Delivered-To: apmail-accumulo-notifications-archive@accumulo.apache.org Received: (qmail 62415 invoked by uid 500); 3 Sep 2013 01:54:52 -0000 Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: jira@apache.org Delivered-To: mailing list notifications@accumulo.apache.org Received: (qmail 62337 invoked by uid 99); 3 Sep 2013 01:54:52 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 03 Sep 2013 01:54:51 +0000 Date: Tue, 3 Sep 2013 01:54:51 +0000 (UTC) From: "Josh Elser (JIRA)" To: notifications@accumulo.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (ACCUMULO-1633) BatchWriter and variants don't assert maxMemory as a positive, non-zero value MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/ACCUMULO-1633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13756307#comment-13756307 ] Josh Elser commented on ACCUMULO-1633: -------------------------------------- Since there's some expectation on a maxMemory of zero (given [~ctubbsii]'s comment), I think changing the while loop that [~yuzhihong@gmail.com] pointed out would be the best fix. Personally, I don't know why someone would want to flush after every single Mutation, but who am I to judge :) > BatchWriter and variants don't assert maxMemory as a positive, non-zero value > ----------------------------------------------------------------------------- > > Key: ACCUMULO-1633 > URL: https://issues.apache.org/jira/browse/ACCUMULO-1633 > Project: Accumulo > Issue Type: Improvement > Components: client > Affects Versions: 1.4.3 > Reporter: Josh Elser > Labels: newbie > Fix For: 1.4.5 > > > I inadvertently provided 0l to the maxMemory argument to create a BatchWriter and my code immediately sat idle. > Once I figured out my problem, I was surprised that no validation was applied to the value. This can cause a BatchWriter to sit indefinitely as it waits trying to "free memory". It would be good to have a "reasonable" minimum (1KB?) to the BatchWriter/BatchDeleter/MultiTableBatchWriter. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira