From 419b52038df01f1776449fedf7a7533c0aa0ff99 Mon Sep 17 00:00:00 2001 From: josh-wong Date: Thu, 7 Sep 2023 15:32:40 +0900 Subject: [PATCH 1/2] Delete file Delete `configurations-for-consensus-commit.md` because it's contents have been added to `configurations.md`. --- .../configurations-for-consensus-commit.md | 34 ------------------- .../configurations-for-consensus-commit.md | 34 ------------------- .../configurations-for-consensus-commit.md | 34 ------------------- 3 files changed, 102 deletions(-) delete mode 100644 docs/3.10/configurations-for-consensus-commit.md delete mode 100644 docs/3.9/configurations-for-consensus-commit.md delete mode 100644 docs/latest/configurations-for-consensus-commit.md diff --git a/docs/3.10/configurations-for-consensus-commit.md b/docs/3.10/configurations-for-consensus-commit.md deleted file mode 100644 index 6e6434c5..00000000 --- a/docs/3.10/configurations-for-consensus-commit.md +++ /dev/null @@ -1,34 +0,0 @@ -# Configurations for Consensus Commit - -Consensus Commit transaction manager is the default transaction manager type in ScalarDB. -If you don't specify the `scalar.db.transaction_manager` property, or you specify `consensus-commit` for the property as follows, the Consensus Commit transaction manager is used. - -```properties -scalar.db.transaction_manager=consensus-commit -``` - -The following sections describes the configurations for Consensus Commit. - -## Basic configurations - -The basic configurations for Consensus Commit are as follows: - -| name | description | default | -|--------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------| -| scalar.db.consensus_commit.isolation_level | Isolation level used for ConsensusCommit. Either `SNAPSHOT` or `SERIALIZABLE` can be specified. | SNAPSHOT | -| scalar.db.consensus_commit.serializable_strategy | Serializable strategy used for ConsensusCommit transaction manager. Either `EXTRA_READ` or `EXTRA_WRITE` can be specified. If `SNAPSHOT` is specified in the property `scalar.db.consensus_commit.isolation_level`, this is ignored. | EXTRA_READ | -| scalar.db.consensus_commit.coordinator.namespace | Namespace name of coordinator tables. | coordinator | - -## Performance related configurations - -The Performance related configurations for Consensus Commit are as follows: - -| name | description | default | -|---------------------------------------------------------|--------------------------------------------------------------------------------|-------------------------------------------------------------------| -| scalar.db.consensus_commit.parallel_executor_count | The number of the executors (threads) for the parallel execution. | 128 | -| scalar.db.consensus_commit.parallel_preparation.enabled | Whether or not the preparation phase is executed in parallel. | true | -| scalar.db.consensus_commit.parallel_validation.enabled | Whether or not the validation phase (in `EXTRA_READ`) is executed in parallel. | The value of `scalar.db.consensus_commit.parallel_commit.enabled` | -| scalar.db.consensus_commit.parallel_commit.enabled | Whether or not the commit phase is executed in parallel. | true | -| scalar.db.consensus_commit.parallel_rollback.enabled | Whether or not the rollback phase is executed in parallel. | The value of `scalar.db.consensus_commit.parallel_commit.enabled` | -| scalar.db.consensus_commit.async_commit.enabled | Whether or not the commit phase is executed asynchronously. | false | -| scalar.db.consensus_commit.async_rollback.enabled | Whether or not the rollback phase is executed asynchronously. | The value of `scalar.db.consensus_commit.async_commit.enabled` | diff --git a/docs/3.9/configurations-for-consensus-commit.md b/docs/3.9/configurations-for-consensus-commit.md deleted file mode 100644 index 6e6434c5..00000000 --- a/docs/3.9/configurations-for-consensus-commit.md +++ /dev/null @@ -1,34 +0,0 @@ -# Configurations for Consensus Commit - -Consensus Commit transaction manager is the default transaction manager type in ScalarDB. -If you don't specify the `scalar.db.transaction_manager` property, or you specify `consensus-commit` for the property as follows, the Consensus Commit transaction manager is used. - -```properties -scalar.db.transaction_manager=consensus-commit -``` - -The following sections describes the configurations for Consensus Commit. - -## Basic configurations - -The basic configurations for Consensus Commit are as follows: - -| name | description | default | -|--------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------| -| scalar.db.consensus_commit.isolation_level | Isolation level used for ConsensusCommit. Either `SNAPSHOT` or `SERIALIZABLE` can be specified. | SNAPSHOT | -| scalar.db.consensus_commit.serializable_strategy | Serializable strategy used for ConsensusCommit transaction manager. Either `EXTRA_READ` or `EXTRA_WRITE` can be specified. If `SNAPSHOT` is specified in the property `scalar.db.consensus_commit.isolation_level`, this is ignored. | EXTRA_READ | -| scalar.db.consensus_commit.coordinator.namespace | Namespace name of coordinator tables. | coordinator | - -## Performance related configurations - -The Performance related configurations for Consensus Commit are as follows: - -| name | description | default | -|---------------------------------------------------------|--------------------------------------------------------------------------------|-------------------------------------------------------------------| -| scalar.db.consensus_commit.parallel_executor_count | The number of the executors (threads) for the parallel execution. | 128 | -| scalar.db.consensus_commit.parallel_preparation.enabled | Whether or not the preparation phase is executed in parallel. | true | -| scalar.db.consensus_commit.parallel_validation.enabled | Whether or not the validation phase (in `EXTRA_READ`) is executed in parallel. | The value of `scalar.db.consensus_commit.parallel_commit.enabled` | -| scalar.db.consensus_commit.parallel_commit.enabled | Whether or not the commit phase is executed in parallel. | true | -| scalar.db.consensus_commit.parallel_rollback.enabled | Whether or not the rollback phase is executed in parallel. | The value of `scalar.db.consensus_commit.parallel_commit.enabled` | -| scalar.db.consensus_commit.async_commit.enabled | Whether or not the commit phase is executed asynchronously. | false | -| scalar.db.consensus_commit.async_rollback.enabled | Whether or not the rollback phase is executed asynchronously. | The value of `scalar.db.consensus_commit.async_commit.enabled` | diff --git a/docs/latest/configurations-for-consensus-commit.md b/docs/latest/configurations-for-consensus-commit.md deleted file mode 100644 index 6e6434c5..00000000 --- a/docs/latest/configurations-for-consensus-commit.md +++ /dev/null @@ -1,34 +0,0 @@ -# Configurations for Consensus Commit - -Consensus Commit transaction manager is the default transaction manager type in ScalarDB. -If you don't specify the `scalar.db.transaction_manager` property, or you specify `consensus-commit` for the property as follows, the Consensus Commit transaction manager is used. - -```properties -scalar.db.transaction_manager=consensus-commit -``` - -The following sections describes the configurations for Consensus Commit. - -## Basic configurations - -The basic configurations for Consensus Commit are as follows: - -| name | description | default | -|--------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------| -| scalar.db.consensus_commit.isolation_level | Isolation level used for ConsensusCommit. Either `SNAPSHOT` or `SERIALIZABLE` can be specified. | SNAPSHOT | -| scalar.db.consensus_commit.serializable_strategy | Serializable strategy used for ConsensusCommit transaction manager. Either `EXTRA_READ` or `EXTRA_WRITE` can be specified. If `SNAPSHOT` is specified in the property `scalar.db.consensus_commit.isolation_level`, this is ignored. | EXTRA_READ | -| scalar.db.consensus_commit.coordinator.namespace | Namespace name of coordinator tables. | coordinator | - -## Performance related configurations - -The Performance related configurations for Consensus Commit are as follows: - -| name | description | default | -|---------------------------------------------------------|--------------------------------------------------------------------------------|-------------------------------------------------------------------| -| scalar.db.consensus_commit.parallel_executor_count | The number of the executors (threads) for the parallel execution. | 128 | -| scalar.db.consensus_commit.parallel_preparation.enabled | Whether or not the preparation phase is executed in parallel. | true | -| scalar.db.consensus_commit.parallel_validation.enabled | Whether or not the validation phase (in `EXTRA_READ`) is executed in parallel. | The value of `scalar.db.consensus_commit.parallel_commit.enabled` | -| scalar.db.consensus_commit.parallel_commit.enabled | Whether or not the commit phase is executed in parallel. | true | -| scalar.db.consensus_commit.parallel_rollback.enabled | Whether or not the rollback phase is executed in parallel. | The value of `scalar.db.consensus_commit.parallel_commit.enabled` | -| scalar.db.consensus_commit.async_commit.enabled | Whether or not the commit phase is executed asynchronously. | false | -| scalar.db.consensus_commit.async_rollback.enabled | Whether or not the rollback phase is executed asynchronously. | The value of `scalar.db.consensus_commit.async_commit.enabled` | From 7203ddf37eed753bbb34f54d7c13fcc2a7404b3c Mon Sep 17 00:00:00 2001 From: josh-wong Date: Thu, 7 Sep 2023 15:32:56 +0900 Subject: [PATCH 2/2] Remove doc from list Remove `configurations-for-consensus-commit.md` because it's contents have been added to `configurations.md`. --- docs/3.10/development-configurations.md | 5 ++--- docs/3.9/development-configurations.md | 5 ++--- docs/latest/development-configurations.md | 5 ++--- 3 files changed, 6 insertions(+), 9 deletions(-) diff --git a/docs/3.10/development-configurations.md b/docs/3.10/development-configurations.md index 4121f4dc..de2efb38 100644 --- a/docs/3.10/development-configurations.md +++ b/docs/3.10/development-configurations.md @@ -3,8 +3,7 @@ The following is a list of configuration guides for ScalarDB: - [Configure ScalarDB](configurations.md) -- [Configure ScalarDB Cluster](scalardb-cluster/scalardb-cluster-configurations.md) -- [Configure ScalarDB SQL](scalardb-sql/configurations.md) -- [Configure Consensus Commit](configurations-for-consensus-commit.md) - [Configure Multi-Storage Transactions](multi-storage-transactions.md) - [Configure Two-Phase Commit Transactions](two-phase-commit-transactions.md) +- [Configure ScalarDB Cluster](scalardb-cluster/scalardb-cluster-configurations.md) +- [Configure ScalarDB SQL](scalardb-sql/configurations.md) diff --git a/docs/3.9/development-configurations.md b/docs/3.9/development-configurations.md index 4121f4dc..de2efb38 100644 --- a/docs/3.9/development-configurations.md +++ b/docs/3.9/development-configurations.md @@ -3,8 +3,7 @@ The following is a list of configuration guides for ScalarDB: - [Configure ScalarDB](configurations.md) -- [Configure ScalarDB Cluster](scalardb-cluster/scalardb-cluster-configurations.md) -- [Configure ScalarDB SQL](scalardb-sql/configurations.md) -- [Configure Consensus Commit](configurations-for-consensus-commit.md) - [Configure Multi-Storage Transactions](multi-storage-transactions.md) - [Configure Two-Phase Commit Transactions](two-phase-commit-transactions.md) +- [Configure ScalarDB Cluster](scalardb-cluster/scalardb-cluster-configurations.md) +- [Configure ScalarDB SQL](scalardb-sql/configurations.md) diff --git a/docs/latest/development-configurations.md b/docs/latest/development-configurations.md index 4121f4dc..de2efb38 100644 --- a/docs/latest/development-configurations.md +++ b/docs/latest/development-configurations.md @@ -3,8 +3,7 @@ The following is a list of configuration guides for ScalarDB: - [Configure ScalarDB](configurations.md) -- [Configure ScalarDB Cluster](scalardb-cluster/scalardb-cluster-configurations.md) -- [Configure ScalarDB SQL](scalardb-sql/configurations.md) -- [Configure Consensus Commit](configurations-for-consensus-commit.md) - [Configure Multi-Storage Transactions](multi-storage-transactions.md) - [Configure Two-Phase Commit Transactions](two-phase-commit-transactions.md) +- [Configure ScalarDB Cluster](scalardb-cluster/scalardb-cluster-configurations.md) +- [Configure ScalarDB SQL](scalardb-sql/configurations.md)