You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@aurora.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2017/05/02 17:04: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=15993286#comment-15993286 ]
Hudson commented on AURORA-1923:
--------------------------------
SUCCESS: Integrated in Jenkins build Aurora #1764 (See [https://builds.apache.org/job/Aurora/1764/])
AURORA-1923 Aurora client should not automatically retry non-idempotent (mnurolahzade: rev f1e25375def5a047da97d8bdfb47a3a9101568f6)
* (edit) src/test/python/apache/aurora/client/cli/test_task.py
* (edit) src/test/python/apache/aurora/api_util.py
* (edit) src/test/python/apache/aurora/client/cli/test_status.py
* (edit) src/main/python/apache/aurora/client/api/__init__.py
* (edit) src/test/python/apache/aurora/admin/test_maintenance.py
* (edit) src/test/python/apache/aurora/client/api/test_scheduler_client.py
* (edit) src/main/python/apache/aurora/client/api/scheduler_client.py
* (edit) src/test/python/apache/aurora/client/api/test_api.py
* (edit) src/main/python/apache/aurora/client/cli/__init__.py
> 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
> Assignee: 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)