[
https://issues.apache.org/jira/browse/JAMES-2813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16952805#comment-16952805
]
Raphael Ouazana commented on JAMES-2813:
----------------------------------------
For more details on our design choices, I attached the architectural decisions
we took to design a distributed task manager. The first one for example explain
our choice to replace the previous in memory task manager by a distributed task
manager for our distributed James product:
{{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 `Task`s of a cluster.}}
> Implement a distributed task manager
> ------------------------------------
>
> Key: JAMES-2813
> URL: https://issues.apache.org/jira/browse/JAMES-2813
> Project: James Server
> Issue Type: Task
> Reporter: Matthieu Baechler
> Priority: Major
> Attachments: 0002-make-taskmanager-distributed.md,
> 0003-distributed-workqueue.md, 0004-distributed-tasks-listing.md,
> 0005-distributed-task-termination-ackowledgement.md,
> 0006-task-serialization.md, 0007-distributed-task-cancellation.md,
> 0008-distributed-task-await.md
>
>
> Following JAMES-2272, we now would like to handle tasks at a cluster level.
> For that, we intend to use a combination of Event Sourcing for keeping track
> of Tasks submitted and RabbitMQ for dispatching the tasks in the cluster.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
