aurora-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Santhosh Kumar Shanmugham (JIRA)" <>
Subject [jira] [Updated] (AURORA-1924) Aurora client should reconcile idempotent job creations
Date Fri, 09 Jun 2017 23:10:19 GMT


Santhosh Kumar Shanmugham updated AURORA-1924:
    Fix Version/s: 0.18.0

> Aurora client should reconcile idempotent job creations
> -------------------------------------------------------
>                 Key: AURORA-1924
>                 URL:
>             Project: Aurora
>          Issue Type: Story
>          Components: Client, Scheduler
>            Reporter: Mehrdad Nurolahzade
>            Assignee: Mehrdad Nurolahzade
>            Priority: Minor
>             Fix For: 0.18.0
> Aurora scheduler rejects a request to create a job if a job with the same key already
exists (see {{SchedulerThriftInterface.createJob()}}). Aurora client exits with an error once
it receives a response with {{ResponseCode.INVALID_REQUEST}} from scheduler in this case.
> However, an attempt to create a job with the exact same configuration and number of instances
is essentially idempotent. Scheduler can detect this situation, ignore it, and signal client
to treat operation as successful; client warns user about existing job but does not fail the
> This helps Aurora client and scheduler reconcile state when creating jobs in presence
of transport layer exceptions; allowing {{aurora job create}} command can then be marked as
idempotent after [AURORA-1923] is fixed.

This message was sent by Atlassian JIRA

View raw message