Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-issues@hadoop.apache.org
Date: Sun, 8 Feb 2015 17:03:35 +0000 (UTC)
From: "Steve Loughran (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Message-ID: <JIRA.12673027.1381328518000.295307.1423415015497@Atlassian.JIRA>
In-Reply-To: <JIRA.12673027.1381328518000@Atlassian.JIRA>
References: <JIRA.12673027.1381328518000@Atlassian.JIRA>
 <JIRA.12673027.1381328518105@arcas>
Subject: [jira] [Updated] (HADOOP-10036) RetryInvocationHandler should
 recognise that there is no point retrying to auth failures
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Steve Loughran updated HADOOP-10036:
------------------------------------
             Priority: Major  (was: Minor)
    Affects Version/s: 2.6.0

> RetryInvocationHandler should recognise that there is no point retrying to auth failures
> ----------------------------------------------------------------------------------------
>
>                 Key: HADOOP-10036
>                 URL: https://issues.apache.org/jira/browse/HADOOP-10036
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: ipc
>    Affects Versions: 2.3.0, 2.6.0
>            Reporter: Steve Loughran
>
> The {{RetryInvocationHandler}} tries to retry connections, so as to handle transient failures. 
> However, auth failures aren't treated as special, so it spins even though the operation will not succeed with the current configuration


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)