Branch: refs/heads/master
Home:
https://github.com/hawkular/hawkular-metrics
Commit: db13be980620caf67c2dd81cdc104be33085b585
https://github.com/hawkular/hawkular-metrics/commit/db13be980620caf67c2dd...
Author: John Sanda <jsanda(a)redhat.com>
Date: 2017-01-31 (Tue, 31 Jan 2017)
Changed paths:
A job-scheduler/src/main/java/org/hawkular/metrics/scheduler/impl/Lock.java
M job-scheduler/src/main/java/org/hawkular/metrics/scheduler/impl/LockManager.java
M job-scheduler/src/main/java/org/hawkular/metrics/scheduler/impl/SchedulerImpl.java
Log Message:
-----------
[HWMETRICS-570] initial support for automatic lock renewal
The idea is to prevent a job execution lock from expiring while the job is
running without placing too much extra load on Cassandra. job execution locks
will automatically renew once more than half the time to their expiration has
passed. If a lock is set to expire in one hour for example, then it will renew
in 30 minutes.
Single execution jobs locks have a hard coded timeout of 30 minutes. That value
is completely arbitrary. I did not want a value to small resulting in lots of
lock renewal queries.
Repepating job lock timeouts are based on the job interval. The timeout is 25%
more than the interval. The compression job runs every two hours, so the lock
timeout will be 2.5 hours and will renew in 75 minutes.
Commit: f2f4d0add6ef0f9751b8b5e9ce41555d75b4f8fc
https://github.com/hawkular/hawkular-metrics/commit/f2f4d0add6ef0f9751b8b...
Author: Stefan Negrea <stefannegrea(a)users.noreply.github.com>
Date: 2017-02-01 (Wed, 01 Feb 2017)
Changed paths:
A job-scheduler/src/main/java/org/hawkular/metrics/scheduler/impl/Lock.java
M job-scheduler/src/main/java/org/hawkular/metrics/scheduler/impl/LockManager.java
M job-scheduler/src/main/java/org/hawkular/metrics/scheduler/impl/SchedulerImpl.java
Log Message:
-----------
Merge pull request #747 from jsanda/hwkmetrics-570
[HWKMETRICS-570] add support for automatic job lock renewal
Compare:
https://github.com/hawkular/hawkular-metrics/compare/1914d1627a59...f2f4d...