accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Elser (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (ACCUMULO-1268) add client wide timeout setting
Date Sat, 04 Apr 2015 02:32:33 GMT

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

Josh Elser updated ACCUMULO-1268:
---------------------------------
    Fix Version/s:     (was: 1.7.0)
                   1.8.0

> add client wide timeout setting
> -------------------------------
>
>                 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
>             Fix For: 1.8.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.
> More generally it would be nice if the user could configure a timeout that would be honored
by all client API calls.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message