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

adoroszlai pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/ozone-site.git


The following commit(s) were added to refs/heads/master by this push:
     new 5c48062ea HDDS-15127. [Auto] Update configuration documentation (#420)
5c48062ea is described below

commit 5c48062eaf099f4f2eb290ba093368c9502dfe58
Author: asf-ci-deploy <[email protected]>
AuthorDate: Thu May 7 09:33:09 2026 +0200

    HDDS-15127. [Auto] Update configuration documentation (#420)
---
 docs/05-administrator-guide/02-configuration/99-appendix.md | 1 +
 1 file changed, 1 insertion(+)

diff --git a/docs/05-administrator-guide/02-configuration/99-appendix.md 
b/docs/05-administrator-guide/02-configuration/99-appendix.md
index f4fe63eee..e18ec6cb5 100644
--- a/docs/05-administrator-guide/02-configuration/99-appendix.md
+++ b/docs/05-administrator-guide/02-configuration/99-appendix.md
@@ -130,6 +130,7 @@ This page provides a comprehensive overview of the 
configuration keys available
 | `hdds.datanode.disk.check.io.test.count` | 3 | `DATANODE` | The number of IO 
tests required to determine if a disk has failed. Each disk check does one IO 
test. The volume will be failed if more than 
`hdds.datanode.disk.check.io.failures.tolerated` out of the last 
`hdds.datanode.disk.check.io.test.count` runs failed. Set to 0 to disable disk 
IO checks. |
 | `hdds.datanode.disk.check.io.test.enabled` | true | `DATANODE` | The 
configuration to enable or disable disk IO checks. |
 | `hdds.datanode.disk.check.min.gap` | 10m | `DATANODE` | The minimum gap 
between two successive checks of the same Datanode volume. Unit could be 
defined with postfix (ns,ms,s,m,h,d). |
+| `hdds.datanode.disk.check.rocksdb.check.io.test.enabled` | true | `DATANODE` 
| The configuration to enable or disable RocksDb disk IO checks. |
 | `hdds.datanode.disk.check.sliding.window.timeout` | 70m | `DATANODE` | Time 
interval after which a disk check failure result stored in the sliding window 
will expire. Do not set the window timeout period to less than or equal to the 
disk check interval period or failures can be missed across sparse checks e.g., 
every 120m interval with a 60m window rarely accumulates enough failed events 
Unit could be defined with postfix (ns,ms,s,m,h,d). |
 | `hdds.datanode.disk.check.timeout` | 10m | `DATANODE` | Maximum allowed time 
for a disk check to complete. If the check does not complete within this time 
interval then the disk is declared as failed. Unit could be defined with 
postfix (ns,ms,s,m,h,d). |
 | `hdds.datanode.disk.check.timeout.failures.tolerated` | 1 | `DATANODE` | The 
number of volume check timeouts allowed within the timeout sliding window 
before the volume is marked as failed. |


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to