This is an automated email from the ASF dual-hosted git repository.
github-actions[bot] pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/amoro.git
The following commit(s) were added to refs/heads/asf-site by this push:
new 7739a7462 Regenerated Amoro latest docs page based on
287f4586b2357097e472de2e4868c8f59b8cc412 commit
7739a7462 is described below
commit 7739a746280e24a9ec9fcff74a61a05a183090ba
Author: GitHub Actions <[email protected]>
AuthorDate: Tue Aug 11 11:11:27 2026 +0000
Regenerated Amoro latest docs page based on
287f4586b2357097e472de2e4868c8f59b8cc412 commit
---
output/docs/latest/managing-optimizers/index.html | 6 +++---
output/docs/latest/search.json | 2 +-
2 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/output/docs/latest/managing-optimizers/index.html
b/output/docs/latest/managing-optimizers/index.html
index 0a98a9180..d02c34f00 100644
--- a/output/docs/latest/managing-optimizers/index.html
+++ b/output/docs/latest/managing-optimizers/index.html
@@ -1248,21 +1248,21 @@ contain several optimizers with the same container
implementation to facilitate
<td>All</td>
<td>No</td>
<td>5min</td>
- <td>Idle duration before an optimizer
becomes a scale-down candidate (minimum 30s). Scale-down lands in a later
release.</td>
+ <td>Idle duration before an optimizer
becomes a scale-down candidate (minimum 30s). Must be at least twice
<code>dynamic-allocation.sustained-backlog-timeout</code>, since idle time is
observed once per scale evaluation round. At most one optimizer is scaled down
per round, and only while the group has no scale-up demand.</td>
</tr>
<tr>
<td>dynamic-allocation.scale-down-cooldown</td>
<td>All</td>
<td>No</td>
<td>1min</td>
- <td>Minimum interval between scale-down
removals. Scale-down lands in a later release.</td>
+ <td>Minimum interval between scale-down
removals.</td>
</tr>
<tr>
<td>dynamic-allocation.drain-timeout</td>
<td>All</td>
<td>No</td>
<td>15min</td>
- <td>Force-removal safety net for a
draining optimizer during scale-down. Scale-down lands in a later release.</td>
+ <td>Force-removal safety net for a
draining optimizer. A scaled-down optimizer is drained gracefully: it stops
receiving new tasks and is removed once its in-flight tasks finish. If draining
takes longer than this timeout, the optimizer is removed anyway and its
remaining tasks are re-executed on other optimizers.</td>
</tr>
<tr>
<td>memory</td>
diff --git a/output/docs/latest/search.json b/output/docs/latest/search.json
index 291646eb8..771adfc1e 100644
--- a/output/docs/latest/search.json
+++ b/output/docs/latest/search.json
@@ -1 +1 @@
-[{"categories":null,"content":"Amoro Docs This directory contains the
documentation content of Amoro.\nThe documentation is written in Markdown
format. The images referenced in the documentation are saved in the images
folder. Style Proper nouns should start with a capital letter, like
Hadoop、Hive、Iceberg、Amoro
","description":"","title":"","uri":"https://amoro.apache.org/docs/latest/readme/"},{"categories":null,"content":";
AMS Configuration Amoro Management Service Configuration The con [...]
\ No newline at end of file
+[{"categories":null,"content":"Amoro Docs This directory contains the
documentation content of Amoro.\nThe documentation is written in Markdown
format. The images referenced in the documentation are saved in the images
folder. Style Proper nouns should start with a capital letter, like
Hadoop、Hive、Iceberg、Amoro
","description":"","title":"","uri":"https://amoro.apache.org/docs/latest/readme/"},{"categories":null,"content":";
AMS Configuration Amoro Management Service Configuration The con [...]
\ No newline at end of file
