Date: 2019-10-02
Accepted (lazy consensus)
In order to have a distributed version of James we need to have an homogeneous way to deal with Task.
Currently, every James nodes of a cluster have their own instance of TaskManager and they have no knowledge of others, making it impossible to orchestrate task execution at the cluster level. Tasks are scheduled and ran on the same node they are scheduled.
We are also unable to list or access to the details of all the Tasks of a cluster.
Create a distribution-aware implementation of TaskManager.
TaskManager part dealing with the coordination (Task management and view) and the Task execution (located in TaskManagerWorker)TaskManager will rely on RabbitMQ to coordinate and the event system to synchronize states