Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-issues@hadoop.apache.org
Date: Tue, 4 Oct 2011 01:20:35 +0000 (UTC)
From: "Aaron T. Myers (Updated) (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Message-ID: 
 <355659659.5979.1317691235404.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1521787727.4582.1317675634324.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (HADOOP-7717) Move handling of concurrent client
 fail-overs to RetryInvocationHandler
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Aaron T. Myers updated HADOOP-7717:
-----------------------------------

    Attachment: HADOOP-7717.patch

Here's a patch which addresses the issue.
                
> Move handling of concurrent client fail-overs to RetryInvocationHandler
> -----------------------------------------------------------------------
>
>                 Key: HADOOP-7717
>                 URL: https://issues.apache.org/jira/browse/HADOOP-7717
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: ipc
>    Affects Versions: 0.24.0
>            Reporter: Aaron T. Myers
>            Assignee: Aaron T. Myers
>             Fix For: 0.24.0
>
>         Attachments: HADOOP-7717.patch
>
>
> Currently every implementation of a {{FailoverProxyProvider}} will need to perform its own synchronization to ensure that multiple concurrent failed calls to a single client proxy object don't result in multiple client fail over events. It would be better to put this logic in {{RetryInvocationHandler.invoke}}.
> This is based on feedback provided by Todd in [this comment|https://issues.apache.org/jira/browse/HDFS-1973?focusedCommentId=13119567&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13119567].

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira