You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@iceberg.apache.org by bl...@apache.org on 2022/09/29 21:46:10 UTC
[iceberg] branch master updated: Docs: Update lock catalog properties to correct units (#5708)
This is an automated email from the ASF dual-hosted git repository.
blue pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/iceberg.git
The following commit(s) were added to refs/heads/master by this push:
new 3af21ea62a Docs: Update lock catalog properties to correct units (#5708)
3af21ea62a is described below
commit 3af21ea62afb38f70d856b930d73b2ac84cd1f2f
Author: Kunni <38...@users.noreply.github.com>
AuthorDate: Fri Sep 30 05:46:05 2022 +0800
Docs: Update lock catalog properties to correct units (#5708)
---
docs/configuration.md | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/docs/configuration.md b/docs/configuration.md
index 55b407879d..f0f0462f94 100644
--- a/docs/configuration.md
+++ b/docs/configuration.md
@@ -148,10 +148,10 @@ Here are the catalog properties related to locking. They are used by some catalo
| --------------------------------- | ------------------ | ------------------------------------------------------ |
| lock-impl | null | a custom implementation of the lock manager, the actual interface depends on the catalog used |
| lock.table | null | an auxiliary table for locking, such as in [AWS DynamoDB lock manager](../aws/#dynamodb-for-commit-locking) |
-| lock.acquire-interval-ms | 5 seconds | the interval to wait between each attempt to acquire a lock |
-| lock.acquire-timeout-ms | 3 minutes | the maximum time to try acquiring a lock |
-| lock.heartbeat-interval-ms | 3 seconds | the interval to wait between each heartbeat after acquiring a lock |
-| lock.heartbeat-timeout-ms | 15 seconds | the maximum time without a heartbeat to consider a lock expired |
+| lock.acquire-interval-ms | 5000 (5 s) | the interval to wait between each attempt to acquire a lock |
+| lock.acquire-timeout-ms | 180000 (3 min) | the maximum time to try acquiring a lock |
+| lock.heartbeat-interval-ms | 3000 (3 s) | the interval to wait between each heartbeat after acquiring a lock |
+| lock.heartbeat-timeout-ms | 15000 (15 s) | the maximum time without a heartbeat to consider a lock expired |
## Hadoop configuration