accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Adam Fuchs (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-706) Batch Writer needs timeout
Date Mon, 26 Nov 2012 17:52:58 GMT

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

Adam Fuchs commented on ACCUMULO-706:
-------------------------------------

This example sets the maxLatency to 2 minutes, but the code committed against this ticket
sets the maxLatency to long.MAX_VALUE. I think we should have a default maxLatency of closer
to 1 second or 1 minute. Otherwise people are going to have writers that sit around in long
running processes and have data in their un-flushed buffers forever (I've seen this a couple
of times), which is a source of confusion. 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?
                
> Batch Writer needs timeout
> --------------------------
>
>                 Key: ACCUMULO-706
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-706
>             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: http://www.atlassian.com/software/jira

Mime
View raw message