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 386d132e6 Regenerated Amoro latest docs page based on
d29cbf4bcfba2ee60b24c0708aa5e7a1962205b0 commit
386d132e6 is described below
commit 386d132e6a9388cda37669e08a2c088dfc8898b3
Author: GitHub Actions <[email protected]>
AuthorDate: Wed Jul 22 07:15:51 2026 +0000
Regenerated Amoro latest docs page based on
d29cbf4bcfba2ee60b24c0708aa5e7a1962205b0 commit
---
output/docs/latest/index.html | 2 +-
output/docs/latest/managing-optimizers/index.html | 67 ++++++++++++++++++++++-
output/docs/latest/search.json | 2 +-
3 files changed, 67 insertions(+), 4 deletions(-)
diff --git a/output/docs/latest/index.html b/output/docs/latest/index.html
index 2fcf4950a..3f88703e4 100644
--- a/output/docs/latest/index.html
+++ b/output/docs/latest/index.html
@@ -32,7 +32,7 @@
<!DOCTYPE html>
<html>
<head>
- <meta name="generator" content="Hugo 0.163.3">
+ <meta name="generator" content="Hugo 0.164.0">
<meta charset="utf-8">
<meta http-equiv="X-UA-Compatible" content="IE=edge">
diff --git a/output/docs/latest/managing-optimizers/index.html
b/output/docs/latest/managing-optimizers/index.html
index 176267e7b..0a98a9180 100644
--- a/output/docs/latest/managing-optimizers/index.html
+++ b/output/docs/latest/managing-optimizers/index.html
@@ -967,7 +967,7 @@ you need to add a new container configuration. with
container-impl as <code>org.
</span></span><span style="display:flex;"><span> <span
style="color:#f92672">job-uri</span>: <span
style="color:#e6db74">"local:///opt/flink/usrlib/optimizer-job.jar"</span>
<span style="color:#75715e"># Optimizer job main
jar</span>
</span></span><span style="display:flex;"><span> <span
style="color:#f92672">ams-optimizing-uri</span>: <span
style="color:#ae81ff">thrift://ams.amoro.service.local:1261
</span> <span style="color:#75715e"># AMS optimizing uri </span>
</span></span><span style="display:flex;"><span> <span
style="color:#f92672">export.FLINK_CONF_DIR</span>: <span
style="color:#ae81ff">/opt/flink/conf/
</span> <span style="color:#75715e"># Flink config dir, flink-conf.yaml should
e in this dir, contains the rest connection parameters of the session
cluster</span>
-</span></span><span style="display:flex;"><span> <span
style="color:#f92672">flink-conf.high-availability: zookeeper
# Flink high availability mode, reference</span>: <span
style="color:#ae81ff">https://nightlies.apache.org/flink/flink-docs-release-1.18/docs/deployment/config/#high-availability</span>
+</span></span><span style="display:flex;"><span> <span
style="color:#f92672">flink-conf.high-availability</span>: <span
style="color:#ae81ff">zookeeper </span>
<span style="color:#75715e"># Flink high availability mode, reference:
https://nightlies.apache.org/flink/flink-docs-release-1.18/docs/deployment/config/#high-availability</span>
</span></span><span style="display:flex;"><span> <span
style="color:#f92672">flink-conf.high-availability.zookeeper.quorum</span>:
<span style="color:#ae81ff">xxx:2181</span>
</span></span><span style="display:flex;"><span> <span
style="color:#f92672">flink-conf.high-availability.zookeeper.path.root</span>:
<span style="color:#ae81ff">/flink</span>
</span></span><span style="display:flex;"><span> <span
style="color:#f92672">flink-conf.high-availability.cluster-id</span>: <span
style="color:#ae81ff">amoro-optimizer-cluster</span>
@@ -1192,7 +1192,7 @@ contain several optimizers with the same container
implementation to facilitate
<td>All</td>
<td>No</td>
<td>0</td>
- <td>The minimum total parallelism (CPU
cores) that the optimizer group should maintain. When the total cores of
running optimizers fall below this value, <code>OptimizerGroupKeeper</code>
will automatically scale out new optimizers. Set to <code>0</code> to disable
auto-scaling. Note: The behavior of the auto-scaling mechanism is controlled by
the AMS-level configurations
<code>optimizer-group.min-parallelism-check-interval</code> and
<code>optimizer-group.max-keeping-attempts</code>.</td>
+ <td>Deprecated since 0.9.0 in favor of
<code>dynamic-allocation.min-parallelism</code>; still honored as a fallback.
The minimum total parallelism (CPU cores) that the optimizer group should
maintain. When the total cores of running optimizers fall below this value,
<code>OptimizerGroupKeeper</code> will automatically scale out new optimizers.
Set to <code>0</code> to disable auto-scaling. Note: The behavior of the
auto-scaling mechanism is controlled by the AMS-level configurations [...]
</tr>
<tr>
<td>shutdown-timeout-ms</td>
@@ -1201,6 +1201,69 @@ contain several optimizers with the same container
implementation to facilitate
<td>600000(10min)</td>
<td>Graceful shutdown timeout in
milliseconds. On shutdown the optimizer waits up to this long for in-progress
tasks to complete before force-interrupting them. For Kubernetes optimizers,
the pod’s <code>terminationGracePeriodSeconds</code> is derived from this
value plus a 30s buffer. For Flink optimizers, the effective wait is
additionally capped below <code>task.cancellation.timeout</code>.</td>
</tr>
+ <tr>
+ <td>dynamic-allocation.enabled</td>
+ <td>All</td>
+ <td>No</td>
+ <td>false</td>
+ <td>Whether to enable dynamic resource
allocation (AIP-5) for this group: the group then grows its optimizer count
automatically in response to optimizing demand, bounded by
<code>dynamic-allocation.max-parallelism</code>. Not supported on
externally-registered optimizers. Manual optimizer operations
(scale-out/release via the dashboard) are not recommended on groups with
dynamic allocation enabled.</td>
+ </tr>
+ <tr>
+
<td>dynamic-allocation.min-parallelism</td>
+ <td>All</td>
+ <td>No</td>
+ <td>0</td>
+ <td>Lower bound on the group’s
total optimizer threads under dynamic allocation. Supersedes the deprecated
flat <code>min-parallelism</code>.</td>
+ </tr>
+ <tr>
+
<td>dynamic-allocation.max-parallelism</td>
+ <td>All</td>
+ <td>Yes (when enabled)</td>
+ <td>N/A</td>
+ <td>Upper bound on the group’s
total optimizer threads under dynamic allocation; must not exceed 1024. Also
configure Kubernetes <code>ResourceQuota</code>/<code>LimitRange</code> as the
authoritative cluster-side limit.</td>
+ </tr>
+ <tr>
+
<td>dynamic-allocation.executor-parallelism</td>
+ <td>All</td>
+ <td>No</td>
+ <td>1</td>
+ <td>Threads per optimizer instance
created by dynamic allocation (the scaling unit, like Spark’s
<code>spark.executor.cores</code>). The floor and the cap must be reachable in
units of this size. For Kubernetes groups a value of 4–8 is recommended so
per-pod JVM overhead is shared across threads.</td>
+ </tr>
+ <tr>
+
<td>dynamic-allocation.scheduler-backlog-timeout</td>
+ <td>All</td>
+ <td>No</td>
+ <td>1min</td>
+ <td>How long optimizing demand must
persist before the first scale-out.</td>
+ </tr>
+ <tr>
+
<td>dynamic-allocation.sustained-backlog-timeout</td>
+ <td>All</td>
+ <td>No</td>
+ <td>30s</td>
+ <td>Interval between subsequent
scale-outs while demand persists; also the group’s scale evaluation
cadence.</td>
+ </tr>
+ <tr>
+
<td>dynamic-allocation.executor-idle-timeout</td>
+ <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>
+ </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>
+ </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>
+ </tr>
<tr>
<td>memory</td>
<td>Local</td>
diff --git a/output/docs/latest/search.json b/output/docs/latest/search.json
index 15b524e47..291646eb8 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
