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

List:       james-dev
Subject:    [jira] [Created] (JAMES-2272) Add a TaskManager
From:       "Tellier Benoit (JIRA)" <server-dev () james ! apache ! org>
Date:       2017-12-27 8:05:00
Message-ID: JIRA.13127337.1514361850000.535415.1514361900051 () Atlassian ! JIRA
[Download RAW message or body]

Tellier Benoit created JAMES-2272:
-------------------------------------

             Summary: 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


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


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