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

Job scheduler should be able to reacquire job lock after server restart

    XMLWordPrintable

    Details

      Description

      When the scheduler acquires a job lock, the expiration of the lock is currently hard coded for one hour (HWKMETRICS-570 has been opened to address this). Suppose the compression job starts up and then the server is shutdown a few seconds after the job starts. When the server starts back up, it will not be able to resume executing the compression job until that lock expires. This is due to what is used for lock values. The lock name is the job id. Qualifying the lock value with the hostname will allow the job scheduler to immediately reacquire the lock and resume executing the job after restart.

        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: