Details

    • Release Notes:
      Introduces a new, event-driven scheduling system.
    • Rank:
      1|hzzo87:

      Description

      Currently, schedulers only support cron-based triggers. That means a workflow runs every so often. The disadvantage of that are

      • wasted resources in case no data is available
      • added latency in case the data is available sooner

      It would be better if a schedule could be triggered by event notifications about:

      • state change of another program (for example, workflow finished successfully)
      • data availability (for example, a partition was added to a PFS)
      • ...

      Event-based schedules may need to be combined with time schedules, for example: "run this workflow as soon as a new partition is available, but no more than 2 times an hour"

      This needs more detailed design. WIP design here: https://wiki.cask.co/pages/viewpage.action?pageId=4363504

        Attachments

          Issue Links

          There are no Sub-Tasks for this issue.

            Activity

              People

              • Assignee:
                andreas Andreas Neumann
                Reporter:
                andreas Andreas Neumann
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: