This is an automated email from the ASF dual-hosted git repository. btellier pushed a commit to branch master in repository https://gitbox.apache.org/repos/asf/james-project.git
commit e13928232df7a66b9e057f76c642766a13ff122f Author: Benoit Tellier <[email protected]> AuthorDate: Sun Mar 28 16:28:17 2021 +0700 JAMES-3435 Document message.write.strong.consistency.unsafe --- docs/modules/servers/pages/distributed/configure/cassandra.adoc | 7 +++++++ src/site/xdoc/server/config-cassandra.xml | 7 +++++++ 2 files changed, 14 insertions(+) diff --git a/docs/modules/servers/pages/distributed/configure/cassandra.adoc b/docs/modules/servers/pages/distributed/configure/cassandra.adoc index 019b14b..b9810d8 100644 --- a/docs/modules/servers/pages/distributed/configure/cassandra.adoc +++ b/docs/modules/servers/pages/distributed/configure/cassandra.adoc @@ -191,4 +191,11 @@ If enabled, regular consistency level is used for read transactions for message. in stale reads as the system.paxos table will not be checked for latest updates. Better performance are expected by turning it off. Note that reads performed as part of write transactions are always performed with a strong consistency. + +| message.write.strong.consistency.unsafe +| Optional. Boolean, defaults to true. Disabling should be considered experimental and unsafe. +If enabled, Lightweight transactions will no longer be used upon messages operation (table `imapUidTable`). +As message flags updates relies so far on a read-before-write model, it exposes yourself to data races leading to +potentially update loss. Better performance are expected +by turning it off. Reads performed as part of write transaction are also performed with a relaxed consistency. |=== \ No newline at end of file diff --git a/src/site/xdoc/server/config-cassandra.xml b/src/site/xdoc/server/config-cassandra.xml index 6271984..904247f 100644 --- a/src/site/xdoc/server/config-cassandra.xml +++ b/src/site/xdoc/server/config-cassandra.xml @@ -156,6 +156,13 @@ by turning it off. Note that reads performed as part of write transactions are always performed with a strong consistency.</dd> + <dt><strong>message.write.strong.consistency.unsafe</strong></dt> + <dd>Optional. Boolean, defaults to true. Disabling should be considered experimental and unsafe. + If enabled, Lightweight transactions will no longer be used upon messages operation (table `imapUidTable`). + As message flags updates relies so far on a read-before-write model, it exposes yourself to data races leading to + potentially update loss. Better performance are expected + by turning it off. Reads performed as part of write transaction are also performed with a relaxed consistency.</dd> + <dt><strong>Allows specifying the driver default consistency level.</strong></dt> <dt><strong>cassandra.consistency_level.regular</strong></dt> <dd>Optional. Defaults to QUORUM.<br/> <a href="https://docs.datastax.com/en/cassandra-oss/3.x/cassandra/dml/dmlConfigConsistency.html";>QUORUM, LOCAL_QUORUM, or EACH_QUORUM</a>.</dd> --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
