You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@accumulo.apache.org by "Eric Newton (JIRA)" <ji...@apache.org> on 2013/01/10 17:30:12 UTC
[jira] [Resolved] (ACCUMULO-733) add description of the BatchWriter
behavior
[ https://issues.apache.org/jira/browse/ACCUMULO-733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Eric Newton resolved ACCUMULO-733.
----------------------------------
Resolution: Fixed
added documentation with revision 1431485
> add description of the BatchWriter behavior
> -------------------------------------------
>
> Key: ACCUMULO-733
> URL: https://issues.apache.org/jira/browse/ACCUMULO-733
> Project: Accumulo
> Issue Type: Bug
> Components: docs
> Reporter: Eric Newton
> Assignee: Eric Newton
> Priority: Trivial
> Fix For: 1.5.0
>
>
> Keith Turner wrote up a nice description of the BatchWriter on the gora mailing list. I think it deserves to be in the BatchWriter documentation:
> {quote}
> When the user creates a
> BatchWriter to write to Accumulo they specify how much memory and how
> many threads it should use. As the user adds mutations to the batch
> writer it buffers them. Once the buffered mutations have used half of
> the user specified, the mutations are dumped into the background to be
> written by a thread pool. If the user specified memory completely
> fills up, then writes are held. When a user calls flush, it does not
> return until all buffered mutations are written.
> {quote}
--
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