[
https://issues.apache.org/jira/browse/JAMES-3687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17471344#comment-17471344
]
Benoit Tellier edited comment on JAMES-3687 at 1/9/22, 12:18 PM:
-----------------------------------------------------------------
https://ci-builds.apache.org/job/james/job/ApacheJames/job/PR-826/7/
Pulsar mail queue bringed in some unstable tests
{code:java}
Test Result (4 failures / +4)
org.apache.james.queue.pulsar.PulsarMailQueueTest.removeByRecipientShouldRemoveSpecificEmail
org.apache.james.queue.pulsar.PulsarMailQueueTest.removeByRecipientShouldRemoveSpecificEmailWhenMultipleRecipients{List,
MailAddress}[5]
org.apache.james.queue.pulsar.PulsarMailQueueTest.removeByRecipientShouldRemoveSpecificEmailWhenMultipleRecipients{List,
MailAddress}[6]
org.apache.james.queue.pulsar.PulsarMailQueueTest.removeShouldRemoveMailFromStoreWhenFilteredOut
{code}
Looking at the first, some email expected to be deleted were not:
{code:java}
Error Message
Expecting actual:
["name1", "name2"]
to contain exactly (and in same order):
["name1"]
but some elements were not expected:
["name2"]
{code}
Maybe because propagation of the delete filter is asynchronous? (IE the client
delete returns when enqueuing the filter but without any warranty so as when it
would be dequeued and applied). If so this isa design flaw and I hardly see how
to improve that .
Or we add a delay in the tests to relax the consistency guaranty?
was (Author: btellier):
https://ci-builds.apache.org/job/james/job/ApacheJames/job/PR-826/7/
Pulsar mail queue bringed in some unstable tests
{code:java}
Test Result (4 failures / +4)
org.apache.james.queue.pulsar.PulsarMailQueueTest.removeByRecipientShouldRemoveSpecificEmail
org.apache.james.queue.pulsar.PulsarMailQueueTest.removeByRecipientShouldRemoveSpecificEmailWhenMultipleRecipients{List,
MailAddress}[5]
org.apache.james.queue.pulsar.PulsarMailQueueTest.removeByRecipientShouldRemoveSpecificEmailWhenMultipleRecipients{List,
MailAddress}[6]
org.apache.james.queue.pulsar.PulsarMailQueueTest.removeShouldRemoveMailFromStoreWhenFilteredOut
{code}
> Implements Apache Pulsar based Mailqueue
> ----------------------------------------
>
> Key: JAMES-3687
> URL: https://issues.apache.org/jira/browse/JAMES-3687
> Project: James Server
> Issue Type: Improvement
> Components: Queue
> Reporter: Jean Helou
> Priority: Major
> Time Spent: 2h 10m
> Remaining Estimate: 0h
>
> An apache pulsar based mailqueue offers a different set of compromises over
> the existing mailqueue implementations:
> pros:
> * pulsar is a distributed queue
> * pulsar offers scheduling facilities making it easier to implement delayed
> queues
> cons:
> * being fully distributed some consistency guarantees cannot be honored for
> flush and filter since the flushing and filtering commands take time to
> propagate in the cluster
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
