Uploaded image for project: 'Hawkular Metrics'
  1. Hawkular Metrics
  2. HWKMETRICS-224

Triggers must have a delay

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Duplicate Issue
    • Affects Version/s: 0.6.0
    • Fix Version/s: 0.20.0
    • Component/s: Scheduler
    • Labels:
      None

      Description

      The scheduler uses time based queues in which there are separate queues for each time bucket. With the way the scheduler is designed, jobs can only be scheduled into the future. You cannot schedule a job to execute now for example. The scheduler checks for jobs to run every minutes. This means that the soonest a job can be executed is the next minute. If I create a job at 14:15 which is supposed to execute every 30 minutes, then the job should first execute at 14:30. The Trigger classes should included the necessary logic for this. Right now you have to explicitly add a delay for the trigger. This is error prone as can easily throw off or even miss executions.

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                john.sanda John Sanda
                Reporter:
                john.sanda John Sanda
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: