[Hawkular-commits] [hawkular/hawkular-metrics] 13edce: [HWKMETRICS-168] big refactoring to get concurrenc...

[John Sanda]

  Branch: refs/heads/task-scheduler
  Home:   https://github.com/hawkular/hawkular-metrics
  Commit: 13edcedaaec4de356f82eadc1e3b609a649accd0
      https://github.com/hawkular/hawkular-metrics/commit/13edcedaaec4de356f82eadc1e3b609a649accd0
  Author: John Sanda <jsanda at redhat.com>
  Date:   2015-07-23 (Thu, 23 Jul 2015)

  Changed paths:
    M pom.xml
    M schema-manager/src/main/resources/schema.cql
    M task-queue/src/main/java/org/hawkular/metrics/tasks/api/RepeatingTrigger.java
    M task-queue/src/main/java/org/hawkular/metrics/tasks/api/TaskScheduler.java
    M task-queue/src/main/java/org/hawkular/metrics/tasks/api/Trigger.java
    M task-queue/src/main/java/org/hawkular/metrics/tasks/impl/Lease.java
    M task-queue/src/main/java/org/hawkular/metrics/tasks/impl/Queries.java
    M task-queue/src/main/java/org/hawkular/metrics/tasks/impl/Task2Impl.java
    M task-queue/src/main/java/org/hawkular/metrics/tasks/impl/TaskSchedulerImpl.java
    M task-queue/src/test/java/org/hawkular/metrics/tasks/BaseTest.java
    M task-queue/src/test/java/org/hawkular/metrics/tasks/impl/TaskSchedulerImplTest.java
    M task-queue/src/test/java/org/hawkular/metrics/tasks/impl/TaskSubscriber.java
    M task-queue/src/test/resources/log4j.xml

  Log Message:
  -----------
  [HWKMETRICS-168] big refactoring to get concurrency right.

The scheduler deals with 4 different thread pools - one for emitting ticks, one
for processing leases, one for executing tasks, and the C* driver's I/O
threads. Making sure things execute on the right thread pool turned out to be
a challenge when chaning various Rx operators together. It is not obvious like
when you explicitly submit some task to a thread pool.