hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Xuan Gong (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-1521) Mark appropriate methods of ApplicationClientProtocol, ResourceManagerAdminist, ApplicationMasterProtocol and ResourceTracker with the idempotent annotation
Date Fri, 20 Dec 2013 02:51:06 GMT

    [ https://issues.apache.org/jira/browse/YARN-1521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13853610#comment-13853610
] 

Xuan Gong commented on YARN-1521:
---------------------------------

Currently, we only do the failover on these exceptions : ConnectException, NoRouteToHostException,
UnknownHostException, StandbyException and ConnectTimeoutException. I am thinking that if
we can use the idempotent annotation.
{code}
if (e instanceof SocketException
          || (e instanceof IOException && !(e instanceof RemoteException))) {
        if (isIdempotentOrAtMostOnce) {
          return RetryAction.FAILOVER_AND_RETRY;
        } else {
          return new RetryAction(RetryAction.RetryDecision.FAIL, 0,
              "the invoked method is not idempotent, and unable to determine "
                  + "whether it was invoked");
        }
{code}


> Mark appropriate methods of ApplicationClientProtocol, ResourceManagerAdminist, ApplicationMasterProtocol
and ResourceTracker with the idempotent annotation
> ------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: YARN-1521
>                 URL: https://issues.apache.org/jira/browse/YARN-1521
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>            Reporter: Xuan Gong
>            Assignee: Xuan Gong
>
> After YARN-1028, we add the automatically failover into RMProxy. This JIRA is to identify
whether we need to add idempotent annotation and which methods can be marked as idempotent.



--
This message was sent by Atlassian JIRA
(v6.1.4#6159)

Mime
View raw message