accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Keith Turner (JIRA)" <>
Subject [jira] [Commented] (ACCUMULO-706) Batch Writer needs timeout
Date Mon, 26 Nov 2012 18:26:58 GMT


Keith Turner commented on ACCUMULO-706:

bq.  Is there a counter-argument for making the default MAX_VALUE? Is there a performance
problem with keeping it in the 1-100 second range?

No, not that I can think of.  Not sure why I did that.  Maybe to make it consistent with setTimeout().
  I think 1 second would be too low, 1 or 2 minutes would be probably be an ok default.  
Seems like one second would cause small batches to be sent, which would be slower.  I suppose
if writing small batches were slower, then larger batches would build up.  But it may oscillate.
  Seems like that could possibly cause unnecessary thrashing.  Anyway, I think 2 minutes would
be good.   There was not a default previously, the user always had to specify something.

If changed, would also need to update javadocs 
> Batch Writer needs timeout
> --------------------------
>                 Key: ACCUMULO-706
>                 URL:
>             Project: Accumulo
>          Issue Type: New Feature
>          Components: client
>            Reporter: Keith Turner
>            Assignee: Keith Turner
>             Fix For: 1.5.0
> The BatchWriter needs a user configurable timeout.  The current behavior when a tablet
or tablet server can not be successfully written to is that it will hang indefinitely retrying.
 The timeout could default to max long to preserve current behavior.  

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:

View raw message