accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Keith Turner (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (ACCUMULO-1268) add client wide timeout setting
Date Fri, 12 Apr 2013 16:24:18 GMT

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

Keith Turner updated ACCUMULO-1268:
-----------------------------------

      Description: 
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.

  was:
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.

    Fix Version/s:     (was: 1.5.0)
                   1.6.0
         Assignee:     (was: Billie Rinaldi)
          Summary: add client wide timeout setting  (was: getConnector should (have a flag
to?) eventually timeout)

talked w/ [~jvines@gmail.com] on irc about this ticket... we decided to make it more general
and set it for 1.6.  The ticket was focused around setting a timeout for getConnector(). 
I modified the description and summary to broaden its scope.
                
> 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.6.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 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