(ignite-3) branch main updated: IGNITE-25075 Update TX configuration documentation (#5862)

[sk...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

sk0x50 pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/ignite-3.git


The following commit(s) were added to refs/heads/main by this push:
     new 05f64d8f4d3 IGNITE-25075 Update TX configuration documentation (#5862)
05f64d8f4d3 is described below

commit 05f64d8f4d357def047fd0bc7522b9914a637feb
Author: jinxxxoid <ji...@gmail.com>
AuthorDate: Fri Jun 6 18:18:47 2025 +0400

    IGNITE-25075 Update TX configuration documentation (#5862)
---
 .../_docs/administrators-guide/config/cluster-config.adoc | 15 +++++----------
 1 file changed, 5 insertions(+), 10 deletions(-)

diff --git a/docs/_docs/administrators-guide/config/cluster-config.adoc b/docs/_docs/administrators-guide/config/cluster-config.adoc
index 679f449d336..1cab86dcc1d 100644
--- a/docs/_docs/administrators-guide/config/cluster-config.adoc
+++ b/docs/_docs/administrators-guide/config/cluster-config.adoc
@@ -268,11 +268,8 @@ bin/ignite3 cluster config show > cluster-config.txt
 {
   "ignite" : {
     "transaction" : {
-      "abandonedCheckTs" : 5000,
-      "attemptsObtainLock" : 3,
-      "implicitTransactionTimeout" : 3000,
-      "rpcTimeout" : 60000,
-      "txnResourceTtl" : 30000
+      "readOnlyTimeoutMillis" : 600000,
+      "readWriteTimeoutMillis" : 30000
     }
   }
 }
@@ -282,11 +279,9 @@ bin/ignite3 cluster config show > cluster-config.txt
 |======
 |Property|Default|Description|Changeable|Requires Restart|Acceptable Values
 
-|abandonedCheckTs|5000|The amount of time after which the transaction is considered abandoned.|Yes|Yes|0 - inf
-|attemptsObtainLock|3|The number of attempts to obtain a lock. After this number of attempts, a lock conflict exception is thrown on the transaction.| Yes | Yes | 0 - inf
-|implicitTransactionTimeout|3000|Timeout for implicit transactions. Used for key-value table APIs invoked with `null` instead of an explicit transaction instance. Must be greater than `rpcTimeout`.| Yes | Yes | 0 - inf
-|rpcTimeout|6000|Timeout for the transaction operation. Used for table API operations.| Yes | Yes | 0 - inf
-|txnResourceTtl|30000|Time to live for transaction resources (transaction states, transaction nodes, open cursors, etc.). Should be higher than the lag to spread the actual transaction information across clusters. Otherwise, some transaction operations might take more time to find out the state from the persistence storage). Must be greater than `rpcTimeout`.| Yes | Yes | 0 - inf
+|readOnlyTimeoutMillis|600000|Timeout for read-only transactions. It defines how long the transaction holds acquired resources on participating nodes. If no timeout is specified, or it is set to `0`, a default value of 10 minutes is applied. The transaction is guaranteed to remain active until the timeout expires. Once the timeout is reached, the transaction is aborted but may persist briefly beyond the timeout while corresponding resources are cleaned up. Use instead of deprecated `read [...]
+|readWriteTimeoutMillis|30000|Timeout for read-write transactions. It defines how long the transaction holds acquired resources on participating nodes. If no timeout is specified, or it is set to `0`, a default value of 30 seconds is applied. The transaction is guaranteed to remain active until the timeout expires. Once the timeout is reached, the transaction is aborted but may persist briefly beyond the timeout while corresponding resources are cleaned up. Use instead of deprecated `rea [...]
+
 |======
 
 == System Configuration