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

Multiple job scheduler nodes should be able to execute same time slice concurrently

    XMLWordPrintable

    Details

    • Type: Enhancement
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: 0.18.0
    • Fix Version/s: 0.19.0
    • Component/s: Scheduler
    • Labels:
      None

      Description

      When the job scheduler starts its work for a time slice, one of things it does before executing any jobs is to acquire a time slice lock. The current code for obtaining the lock only allows for one scheduler node to hold the lock. Multiple nodes should be able to acquire the lock. There are a couple changes needed.

      First, we need to change the CQL used for acquiring the lock to:

      UPDATE locks USING TTL 300 SET VALUE = 'executing'
      WHERE name = 'time-slice[10:50]' IF IN [NULL, 'executing'];
      

      Secondly, it is also possible that the lock value is set to scheduling. This should be considered temporary, and the job scheduler should attempt to acquire the lock after a short delay.

      Lastly, automated tests are needed for these scenarios.

        Gliffy Diagrams

          Attachments

            Issue Links

              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: