You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@accumulo.apache.org by "John Vines (JIRA)" <ji...@apache.org> on 2013/04/11 22:23:16 UTC

[jira] [Created] (ACCUMULO-1268) getConnector should (have a flag to?) eventually timeout

John Vines created ACCUMULO-1268:
------------------------------------

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