[
https://issues.apache.org/jira/browse/MAILBOX-405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17294261#comment-17294261
]
Benoit Tellier commented on MAILBOX-405:
----------------------------------------
A longer term approach would be to govern mailbox management trough event
sourcing.
This would likely need a responsibility rework as the event sourcing aggregate
would be responsible of handling business rules (create parent mailboxes,
rename or delete parent mailboxes)
> Strengthen RENAME resiliency with retries
> -----------------------------------------
>
> Key: MAILBOX-405
> URL: https://issues.apache.org/jira/browse/MAILBOX-405
> Project: James Mailbox
> Issue Type: Improvement
> Components: cassandra
> Reporter: Benoit Tellier
> Priority: Major
>
> Today one of my users did rename a folder containing ~25 folders. The RENAME
> did fail with a Cassandra level "Write timeout".
> This resulted in an half renamed folder, harming Thunderbird experience
> (subscriptions were not updated)
> We are investigating the cause of the write timeout. So far "reactor
> concurrency" do not loo like being to blame - but 16 concurrent renames is
> likely too much. I propose to decrease this parameter.
> Also, positioning a retry would help...
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
