You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@aurora.apache.org by "Mehrdad Nurolahzade (JIRA)" <ji...@apache.org> on 2017/04/26 17:52:04 UTC
[jira] [Commented] (AURORA-1923) Aurora client should not
automatically retry non-idempotent operations
[ https://issues.apache.org/jira/browse/AURORA-1923?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15985256#comment-15985256 ]
Mehrdad Nurolahzade commented on AURORA-1923:
---------------------------------------------
[~treadstone90] took a stab at this a while ago by making Aurora client explicitly define idempotency of operations. Only idempotent operations are automatically retried: https://reviews.apache.org/r/54957
> Aurora client should not automatically retry non-idempotent operations
> ----------------------------------------------------------------------
>
> Key: AURORA-1923
> URL: https://issues.apache.org/jira/browse/AURORA-1923
> Project: Aurora
> Issue Type: Story
> Components: Client
> Reporter: Mehrdad Nurolahzade
>
> Aurora client has a built in mechanism to automatically retry thrift API operations if the connection with scheduler times out, experiences transport exception, or encounters a transient exception on the scheduler side.
> Retrying thrift calls due to scheduler connection timeout and transient exceptions (see [AURORA-187]) is safe. However, as Aurora has no concept of idempotency, its client can retry non-idempotent operations upon encountering transport exceptions which can lead to nondeterministic situations.
> For example, if client requests go through a proxy to reach scheduler, client might consider a non-idempotent request failed and automatically retry it while the original request has been received and processed by the scheduler.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)