- User Stories Documented
- User Stories Reviewed
- Design Reviewed
- APIs reviewed
- Release priorities assigned
- Test cases reviewed
- Blog post
The current scheduler can set triggers based on time and data partitions. We wish to add a new trigger based on program statuses.
- Triggers: Pipelines should be started based on the program status of another pipeline.
- Constraints: Existing scheduling constraints should work with this new program status trigger.
- As a user, I would like to be able to start a ML workflow after an ingestion workflow has succeeded.
- As a user, I would like to be able to start an error handling workflow when an analytics workflow has failed.
- As a user, I would like to be able to start a compaction workflow if and only if a workflow has finished, with a time window constraint for the compaction workflow.
- As a user, I would like to be able to start workflow B if and only if workflow A successfully completed and dataset C has new partitions. (Stretch)
- As a user, I would like to be able to start workflow B if and only if workflow A successfully completed and dataset C has 100 MB of new data (Stretch)
- As a user, I would like to start workflow B if workflow A resulted in a lot of errors. (Stretch)
- Since schedulers can only schedule workflows, this trigger will also only be triggered for workflows. If this changes in the future, this design can adapt to account for this.
- We will only allow programs to be triggered with any combination of the following program statuses: ProgramStatus.COMPLETED, ProgramStatus.FAILED, and ProgramStatus.KILLED.
- All combinations of existing constraints are possible.
- Implementing Program Status Based Scheduling is a two step process:
1. We need to determine when the program status has changed.
2. Based on the program status change, the scheduler must schedule the program.
Both of these steps will be covered below.
1. Determining a Program State Change:
- Whenever a program status changes, we can send program status based notifications to the Transactional Messaging System (TMS).
- These messages can be emitted to topic
- The approach here will be to send a notification whenever the program status changes are persisted.
- Since DefaultStore is a central place where all program runners update their status, we can send a notification to TMS from the DefaultStore when it persists the program status.
- What happens if a YARN container crashes?
- Response: We already monitor running programs and mark the status as failed when it crashes.
2. Scheduling Based on the Program Status Change:
The scheduler will subscribe to the program status notifications with topic
- Based on the notification received, it will add a new job to the job queue.
- The existing scheduler implementation will handle data persistence and starting the job when all of its constraints have been satisfied, so the rest of the scheduler implementation remains unchanged and will work with the proposed changes.
TMS Message Design:
For a Program Status message, the notification will contain:
- programId: <the program id>
- programStatus: <the program status>
- programRunId: <the specific run id of a program>
New Programmatic APIs
New Java APIs introduced (both user facing and internal)
External Methods (in ScheduleBuilder)
Deprecated Programmatic APIs
There are none.
New REST APIs
|Path||Method||Description||Request Body||Response Code||Response|
To add a schedule for a program to an application
The body is entirely the same as the existing API endpoint already documented, but the trigger specified in the body is different.
200 - On success
404 - When application is not available
409 - Schedule with the same name already exists
500 - Any internal errors
Deprecated REST API
- There are no API routes to be deprecated.
CLI Impact or Changes
add program schedule <schedule-name> for <program-type> <program> [version <version>] [description "optional"] after program <program-name> type <program-type> status <program-status> [or <program-status>] [namespace <program-namespace>] [application <program-application>] [version <program-application-version>] [concurrency <concurrency>] [properties "optional map of properties"]
+-> PUT /v3/namespaces/default/apps/<app-id>/versions/<app-version>/schedules/<schedule-id>
update program schedule <schedule-name> for <program-type> <program> [version <version>] [description "optional"] after program <program-name> type <program-type> status <program-status> [or <program-status>] [namespace <program-namespace>] [application <program-application>] [version <program-application-version>] [concurrency <concurrency>] [properties "optional map of properties"]
+-> POST /v3/namespaces/default/apps/<app-id>/versions/<app-version>/schedules/<schedule-id>/update
- The namespace, application, and applicationVersion for the triggering program can all be optional in the CLI because they will inherit from the program that is being scheduled if they are not included.
UI Impact or Changes
- Add ProgramSchedule options to the "Schedule" panel, along with a dropdown for pipeline selection and a dropdown for program status selection
Edit: Statuses in screenshot should be a checkbox, allowing you to select multiple statuses.
- There is no notification security currently.
- Can a program A be triggered by a program B if the user running program A does not have read access to program B?
- If we allow cross namespace triggers, how will we make this secure?
Impact on Infrastructure Outages
- Since this change does not change the existing Scheduler architecture, the outage impact is the same as what we have today.
|Test ID||Test Description||Expected Results|
|1||Configure a schedule to run every 5 minutes and always complete successfully. Configure a second schedule to run if the first schedule has succeeded.||Both schedules run and finish successfully.|
|2||Configure a schedule to fail. Configure a second schedule to run only if the first schedule has succeeded.||The first schedule should run. The second schedule should not run.|
|3||Configure a schedule to run for 10 seconds before it completes. Configure a second schedule to run only if the first schedule has succeeded. 500 milliseconds before the first schedule completes, delete the second schedule.||The first schedule should run and finish successfully.|
|4||Configure a schedule to run once and start at 9:50 PM. This schedule should finish in less than 10 minutes. Configure a second schedule to run only between 10:00 PM and 11:00 PM when the first schedule has been completed successfully.||The first schedule should run and finish before 10:00 PM. The second schedule should not run|
- Is there a use case for configuring a schedule to start program B when program A has "Started"?
- Resolved: No there is not a use case.
- Should we have a user-accessible class to encapsulate a program, rather than passing in namespace, application, applicationVersion, programType, and programName to encapsulate a program?
Name topic in TMS for ProgramSchedulerStatuses
- At central location for all programs for all ProgramSchedulerStatuses
Send program status notifications through TMS
- API Specification
- Parse new ProgramStateTrigger from a request
- Add new thread to subscribe to ProgramStateNotifications from TMS and create schedule with new trigger
- Add to ProgramScheduleStore and ensure atomicity of events
- Ensure event keys are still unique for Program State Triggers
- Need long running test to test series of pipelines starting from statuses of each other
- Plus other integration tests
- Fetch all programs for user to choose from in a pipeline
- Design multiple tabs to pick between different triggers
- Add examples for how to build the trigger
Implementing program status based scheduling to schedule other workflows is a fundamental feature in this release, but the refactoring of the store to subscribe to the TMS notifications to know when to persist the program status changes, rather than making HTTP requests, may be a change for a later time.