Failure Policy: Adds FailurePolicy API field to Job #48
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Adds a new `List` API to the cron service. This API returns the list of current committed active jobs that have a name matching the given prefix. An empty prefix will return all jobs. ```go List(ctx context.Context, prefix string) (*ListResponse, error) ``` A new `ListResponse` proto message has been added which contains a list of named Jobs. As part of this change to clean up the codebase, the cron API definition has been moved into `api/api.go`. A new `queue` runnable has been created which is responsible for managing the underlying job queue based on events from the informer. A new `internal/api` package is responsible for implementing the server CRUD APIs. Uses dapr/kit concurrency/map from dapr/kit#104 Signed-off-by: joshvanl <[email protected]>
Signed-off-by: joshvanl <[email protected]>
Signed-off-by: joshvanl <[email protected]>
Signed-off-by: joshvanl <[email protected]>
Signed-off-by: joshvanl <[email protected]>
Separates internal "stored" API into `/internal/api/stored`, and keep consumable "api" API in `/api` package. Names the proto files into appropriate package names and changes the `proto` dir structure accordingly. Branch based off diagridio#41 and diagridio#43 Signed-off-by: joshvanl <[email protected]>
Based of dapr/proposals#66 Adds a `FailurePolicy` option to the `Job` API to allow re-triggering job which are marked as failed by the caller. Adds two types of policy; `Drop` and `Constant`. `Drop` has no retry policy, `Constant` will constantly retry the job trigger for a configurable delay, up to a configurable maximum number of retries (which could be infinite). Note that the failure policy retry cadence has no effect on the actual Job schedule, meaning if a job was to be retired and eventually succeeded, the Job would continue to trigger at the origin configured schedule. By default, all Jobs will have a `Constant` policy with a delay of 1s. Signed-off-by: joshvanl <[email protected]>
|
Superseded by #52 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Based of dapr/proposals#66
Adds a
FailurePolicyoption to theJobAPI to allow re-triggeringjob which are marked as failed by the caller. Adds two types of policy;
DropandConstant.Drophas no retry policy,Constantwillconstantly retry the job trigger for a configurable delay, up to a
configurable maximum number of retries (which could be infinite).
Note that the failure policy retry cadence has no effect on the actual
Job schedule, meaning if a job was to be retired and eventually
succeeded, the Job would continue to trigger at the origin configured
schedule.
By default, all Jobs will have a
Constantpolicy with a delay of 1s and 3 max retries.