[
https://issues.apache.org/jira/browse/JAMES-2885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rémi Kowalski updated JAMES-2885:
---------------------------------
Description:
When updating flags, the nextmodSeq is called concurrently. This PR aims to fix
this.
The concurrent update of nextModSeq is a problem, because on the cassandra
backend this method will retry until the update succeed using a lightweight
transaction
where the condition is that the current mod seq in database match the current
mod seq provide. Which will not happen this method is called concurrenty. It
will then retry until the max number of retry is exhausted.
was:When updating flags, the nextmodSeq is called concurrently. This PR aims
to fix this.
> Avoid concurrent nexModSeq during flags update
> ----------------------------------------------
>
> Key: JAMES-2885
> URL: https://issues.apache.org/jira/browse/JAMES-2885
> Project: James Server
> Issue Type: Improvement
> Affects Versions: 3.4.0
> Reporter: Rémi Kowalski
> Priority: Major
> Fix For: 3.5.0
>
>
> When updating flags, the nextmodSeq is called concurrently. This PR aims to
> fix this.
>
> The concurrent update of nextModSeq is a problem, because on the cassandra
> backend this method will retry until the update succeed using a lightweight
> transaction
> where the condition is that the current mod seq in database match the current
> mod seq provide. Which will not happen this method is called concurrenty. It
> will then retry until the max number of retry is exhausted.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
