[
https://issues.apache.org/jira/browse/ACCUMULO-1268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Vines updated ACCUMULO-1268:
---------------------------------
Fix Version/s: (was: 1.6.0)
1.7.0
I would love to see this in 1.6, but I don't see that happening, unless someone
is currently working on it.
> 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.7.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.1#6144)
