Minor Description
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 operation.
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.
Attachments
Issue Links
- is related to
-
AURORA-1923 Aurora client should not automatically retry non-idempotent operations
-
- Resolved
-