[prev in list] [next in list] [prev in thread] [next in thread] 

List:       james-dev
Subject:    [jira] [Commented] (JAMES-2813) Implement a distributed task manager
From:       "Benoit Tellier (Jira)" <server-dev () james ! apache ! org>
Date:       2019-09-27 11:56:00
Message-ID: JIRA.13242118.1561711317000.65277.1569585360121 () Atlassian ! JIRA
[Download RAW message or body]


    [ https://issues.apache.org/jira/browse/JAMES-2813?page=com.atlassian.jira.plugin. \
system.issuetabpanels:comment-tabpanel&focusedCommentId=16939357#comment-16939357 ] 

Benoit Tellier commented on JAMES-2813:
---------------------------------------

https://github.com/linagora/james-project/pull/2722 is merged

https://github.com/linagora/james-project/pull/2690 JAMES-2813 MemoryWorkQueue should \
rely on reactor primitive 

The memory work queue consumed in a blocking fashion a LinkedBlockingQueue.
This operation will still be ongoing upon thread shutdown and will result in
an exception being thrown and logged by default reactor consumer, which is really \
verbose.

We should rather use the reactor primitives for cross-thread interactions.

(merged)

> 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
> 
> 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-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org


[prev in list] [next in list] [prev in thread] [next in thread]