accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christopher Tubbs (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-1268) getConnector should (have a flag to?) eventually timeout
Date Fri, 12 Apr 2013 16:02:16 GMT

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

Christopher Tubbs commented on ACCUMULO-1268:
---------------------------------------------

{quote}The user probably needs the ability to configure a timeout setting that will apply
to all client operations.{quote}
+1
                
> getConnector should (have a flag to?) eventually timeout
> --------------------------------------------------------
>
>                 Key: ACCUMULO-1268
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-1268
>             Project: Accumulo
>          Issue Type: Improvement
>          Components: client
>    Affects Versions: 1.4.3
>            Reporter: John Vines
>            Assignee: Billie Rinaldi
>             Fix For: 1.5.0
>
>
> Currently if Accumulo is down, getConnector will sit indefinitely. This is designed to
be tolerant in several processes which wait for Accumulo to come up into a stable state.
> However, for writing client applications, it's horrendous. It provides no ability for
the developer to provide feedback to the client. There should be some method to allow ServerClient.executeRaw()
to eventually kick out of the infinite loop it currently has. If the developer wants the code
to continue infinitely, they can either disregard the flag or wrap the getConnector() code
in a loop themselves.

--
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