You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Suresh Srinivas (Updated) (JIRA)" <ji...@apache.org> on 2012/03/07 21:12:58 UTC

[jira] [Updated] (HADOOP-7717) Move handling of concurrent client fail-overs to RetryInvocationHandler

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

Suresh Srinivas updated HADOOP-7717:
------------------------------------

     Target Version/s: 0.24.0, 0.23.3  (was: 0.24.0)
    Affects Version/s: 0.23.0
        Fix Version/s: 0.23.3
    
> 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.23.0, 0.24.0
>            Reporter: Aaron T. Myers
>            Assignee: Aaron T. Myers
>             Fix For: 0.24.0, 0.23.3
>
>         Attachments: HADOOP-7717.patch, 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