[
https://issues.apache.org/jira/browse/YARN-1521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13948457#comment-13948457
]
Bikas Saha commented on YARN-1521:
----------------------------------
OK. So we are requiring the moveAppAcrossQueues API to be idempotent? How can
that be done without ignoring an illegal move of an app from a queue in which
the app does not exist? Is that correct behavior?
Any response to the second comment above about returning a new
SubmitApplicationResponse instead of the original response for the original
request. What if there are member values in SubmitApplicationResponse (there
aren't any right now).
> Mark appropriate protocol methods with the idempotent annotation or
> AtMostOnce 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
> Priority: Blocker
> Fix For: 2.4.0
>
> Attachments: YARN-1521.0.patch, YARN-1521.1.patch, YARN-1521.2.patch,
> YARN-1521.3.patch
>
>
> 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.2#6252)
