Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jira@apache.org
Date: Tue, 3 Sep 2013 22:15:52 +0000 (UTC)
From: "John Vines (JIRA)" <jira@apache.org>
To: notifications@accumulo.apache.org
Message-ID: <JIRA.12647067.1368209627151.74140.1378246552325@arcas>
In-Reply-To: <JIRA.12647067.1368209627151@arcas>
References: <JIRA.12647067.1368209627151@arcas>
Subject: [jira] [Assigned] (ACCUMULO-1410) ZooSession.connect barely adheres
 to timeout
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

John Vines reassigned ACCUMULO-1410:
------------------------------------

    Assignee: John Vines
    
> ZooSession.connect barely adheres to timeout
> --------------------------------------------
>
>                 Key: ACCUMULO-1410
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-1410
>             Project: Accumulo
>          Issue Type: Bug
>          Components: client, fate
>            Reporter: John Vines
>            Assignee: John Vines
>
> ZooSession.connect, which is used by ZooKeeperInstance, takes an argument for a timeout, and utilizes it to an extent-
> {quote}
> if (System.currentTimeMillis() - startTime > 2 * timeout)
> {quote}
> However, this is only used after a check which uses hardcoded values. Currently, this is set to 10*1000ms. More specifically, it uses this value and checks every 100ms to see if it's connected. So if you have a tiny timeout, there are 2 issues:
> # Your timeout is only useful in 10 second increments, rounded up
> # You get a nice helpful error message that hides that real lengths of attempt
> I think the block of code should be changed to just try to connect for the user specified timeout length, working in the same 100ms increments. This allows more granularity in the handling of the user specified values (and I think it also simplifies the code). This will also make the timeout message more accurate.

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