Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jira@apache.org
Date: Mon, 20 Jan 2014 17:32:19 +0000 (UTC)
From: "Sean Busbey (JIRA)" <jira@apache.org>
To: notifications@accumulo.apache.org
Message-ID: <JIRA.12689840.1390239029344.34661.1390239139540@arcas>
In-Reply-To: <JIRA.12689840.1390239029344@arcas>
References: <JIRA.12689840.1390239029344@arcas>
Subject: [jira] [Created] (ACCUMULO-2224) ZooSession should be more robust
 to transient DNS issues
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Sean Busbey created ACCUMULO-2224:
-------------------------------------

             Summary: ZooSession should be more robust to transient DNS issues
                 Key: ACCUMULO-2224
                 URL: https://issues.apache.org/jira/browse/ACCUMULO-2224
             Project: Accumulo
          Issue Type: Bug
          Components: client
    Affects Versions: 1.5.0, 1.4.4, 1.4.3, 1.4.2, 1.4.1
         Environment: 1.4.5-SNAP on CDH4 w/gremlins
            Reporter: Sean Busbey
            Assignee: Sean Busbey
             Fix For: 1.4.5, 1.5.1, 1.6.0


While injecting network faults, I found that transient DNS problems caused us to bail out of ZooSessions rather than retrying as we do for all other IO problems. We should retry these failures just as we do for Connection Refused or other networking problems.

Since the addition of ACCUMULO-131, we can be sure that we won't retry actual invalid hosts for ever. Instead, after the time out period that holds for all other problems we'll properly exit.

The warn messages logged for IOExceptions should suffice to indicate improperly specified host names.


--
This message was sent by Atlassian JIRA
(v6.1.5#6160)