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 "Benoit Tellier (Jira)" <se...@james.apache.org> on 2020/08/25 08:55:00 UTC

[jira] [Created] (JAMES-3364) DeletedMessageVault: deleting many messages dead-locks

Benoit Tellier created JAMES-3364:
-------------------------------------

             Summary: DeletedMessageVault: deleting many messages dead-locks
                 Key: JAMES-3364
                 URL: https://issues.apache.org/jira/browse/JAMES-3364
             Project: James Server
          Issue Type: Improvement
          Components: mailbox
    Affects Versions: 3.6.0
            Reporter: Benoit Tellier


== Symptoms

When deleting ~1000 messages at once with the deletedMessage vault enabled, the deletion dead-locks and never completes.

== Fix

The deleted message vault goup bys deleted entries when retrieving the username associated with a mailbox (performance purposes) then groups the mailboxIds together for a given  messageId.

These too groupBys steps proved to be failing.

Getting read of the second groupbys eventually solve the dead lock issues.

Drawback: if a message is referenced in several mailboxes at once, we expect it to be inserted several time in the (indempotent) deleted message vault, leading to a performance penalty. However this is a rare unexpected corner case, and it looks like premature optimization.



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