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

List:       james-dev
Subject:    [jira] [Resolved] (JAMES-3934) Allow external scheduling for RabbitMQ mailQueue browse start update
From:       René_Cordier_(Jira) <server-dev () james ! apache ! org>
Date:       2023-08-22 2:43:00
Message-ID: JIRA.13547584.1692197775000.21881.1692672180017 () Atlassian ! JIRA
[Download RAW message or body]


     [ https://issues.apache.org/jira/browse/JAMES-3934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel \
]

René Cordier resolved JAMES-3934.
---------------------------------
    Resolution: Fixed

The issue has been fixed and merged on master and backported to 3.8.x and 3.7.x

> Allow external scheduling for RabbitMQ mailQueue browse start update
> --------------------------------------------------------------------
> 
> Key: JAMES-3934
> URL: https://issues.apache.org/jira/browse/JAMES-3934
> Project: James Server
> Issue Type: Improvement
> Reporter: Benoit Tellier
> Priority: Major
> Fix For: master, 3.8.1, 3.7.5
> 
> Time Spent: 1h 40m
> Remaining Estimate: 0h
> 
> h3. Background
> In an attempt to avoid synchonization the browse start update is done \
> proabilistically. Configuring the underlying values is hard, and theprobability \
> behind this are hard to grasp. Full design : 
> - https://github.com/apache/james-project/blob/master/src/adr/0031-distributed-mail-queue.md
>                 
> - https://github.com/apache/james-project/blob/master/src/adr/0032-distributed-mail-queue-cleanup.md
>  h3. Goal
> In practice many environments supports centralized schedulers (eg: kubernees), we \
> can offload to them the periodic planning of the browse start update, thus easing \
> the overall reasonning around the RabbitMQ MailQueue. h3. How?
> Implement a webadmin endpoint to update browseStart pace. Only exposed if the \
> CassandraMailQueue view is supported. Example:
> {code:java}
> curl -XPOST /mailQueues/root?task=updateBrowseStart
> {code}
> DOD unit test with cassandra instrumentation on top of the mailQureueView.
> Don't forget to document this endpoint...
> Port it on master, 3.8.x, 3.7.x
> h3. Expected benefits
> Tasks allow better tracking on how long the browse start update takes. One can also \
> look atthe execution history through task results (success/failure) while \
> probabilistic scheduling demands careful log reviews.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
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]