You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-dev@james.apache.org by "Tellier Benoit (JIRA)" <se...@james.apache.org> on 2018/01/04 08:20:00 UTC
[jira] [Closed] (JAMES-2272) Add a TaskManager
[ https://issues.apache.org/jira/browse/JAMES-2272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tellier Benoit closed JAMES-2272.
---------------------------------
> Add a TaskManager
> -----------------
>
> Key: JAMES-2272
> URL: https://issues.apache.org/jira/browse/JAMES-2272
> Project: James Server
> Issue Type: Improvement
> Components: task
> Affects Versions: master
> Reporter: Tellier Benoit
> Labels: feature
>
> As mentioned by [~matthieu-at-arkoon] in https://github.com/linagora/james-project/pull/1199 ( JAMES-2266) we have long running tasks that deserves a better support.
> We want an entity running tasks, and allowing to monitor / cancel them.
> Hence, I got a try, and proposes a Task Manager implementation. I use it in the context of Cassandra migration.
> 1. Cassandra migration schedule a task and return the corresponding ID
> 2. Webadmin task API can then be called to get execution details / await task end / cancel task
> Note that the context of task is more generic, and might apply to:
> - JAMES-2266 solving ghost mailbox bug
> - mailbox re-indexing
> - Quota re-calculation
> - Mail repository re-processing
> - etc...
> Its use should later on be extended to CLI.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org