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 2013/08/26 17:03:51 UTC

[jira] [Updated] (ACCUMULO-1633) BatchWriter and variants don't assert maxMemory as a positive, non-zero value

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

Josh Elser updated ACCUMULO-1633:
---------------------------------

    Fix Version/s:     (was: 1.4.4)
                   1.4.5
    
> 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