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/03/12 10:40:00 UTC

[jira] [Commented] (JAMES-3111) Cassandra timeouts at ConsistencyLevel ALL

    [ https://issues.apache.org/jira/browse/JAMES-3111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17057796#comment-17057796 ] 

Benoit Tellier commented on JAMES-3111:
---------------------------------------

https://github.com/linagora/james-project/pull/3193 proposesthis

> Cassandra timeouts at ConsistencyLevel ALL
> ------------------------------------------
>
>                 Key: JAMES-3111
>                 URL: https://issues.apache.org/jira/browse/JAMES-3111
>             Project: James Server
>          Issue Type: New Feature
>          Components: cassandra
>            Reporter: Benoit Tellier
>            Priority: Major
>
> We encounter some Cassandra timeouts with consistency level ALL in production.
> We should understand why we use a Consistency level All in the first place.
> We can leverage a RetryStrategy to log those request.
> Also we can retry those operation at a lower consistency level.



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