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 dba016dc7 Regenerated Amoro latest docs page based on
89d27bcd67541a6d3cc3a983cd9fe09a6e9c5cfb commit
dba016dc7 is described below
commit dba016dc7baf1c3ab2469064dfa4f0fec9c516cc
Author: GitHub Actions <[email protected]>
AuthorDate: Mon Jul 6 04:47:03 2026 +0000
Regenerated Amoro latest docs page based on
89d27bcd67541a6d3cc3a983cd9fe09a6e9c5cfb commit
---
output/docs/latest/index.html | 2 +-
output/docs/latest/managing-optimizers/index.html | 18 ++++++++++++++++++
output/docs/latest/search.json | 2 +-
3 files changed, 20 insertions(+), 2 deletions(-)
diff --git a/output/docs/latest/index.html b/output/docs/latest/index.html
index 5f013fbd1..2fcf4950a 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.1">
+ <meta name="generator" content="Hugo 0.163.3">
<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 0a33232f3..176267e7b 100644
--- a/output/docs/latest/managing-optimizers/index.html
+++ b/output/docs/latest/managing-optimizers/index.html
@@ -1194,6 +1194,13 @@ contain several optimizers with the same container
implementation to facilitate
<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>
</tr>
+ <tr>
+ <td>shutdown-timeout-ms</td>
+ <td>All</td>
+ <td>No</td>
+ <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>memory</td>
<td>Local</td>
@@ -1223,6 +1230,7 @@ contain several optimizers with the same container
implementation to facilitate
<li>Set <code>flink-conf.taskmanager.memory.managed.size</code> to
<code>32mb</code> as Flink optimizer does not have any computation logic, it
does not need to occupy managed memory.</li>
<li>Set <code>flink-conf.taskmanager.memory.network.max</code> to
<code>32mb</code> as there is no need for communication between operators in
Flink Optimizer.</li>
<li>Set <code>flink-conf.taskmanager.memory.network.min</code> to
<code>32mb</code> as there is no need for communication between operators in
Flink Optimizer.</li>
+<li>When using <code>shutdown-timeout-ms</code> with a Flink Optimizer, also
raise <code>flink-conf.task.cancellation.timeout</code> (default 180000)
accordingly — the graceful drain on job cancellation is capped below
Flink’s cancellation watchdog, which otherwise fails the whole
TaskManager.</li>
</ul>
</div>
<h3 id="edit-optimizer-group">Edit optimizer group</h3>
@@ -1320,6 +1328,11 @@ If the optimizer runs normally, you will see an
optimizer with the status <code>
<td>No</td>
<td>Timeout in optimizer cache, default
10Min.</td>
</tr>
+ <tr>
+ <td>-st</td>
+ <td>No</td>
+ <td>Graceful shutdown timeout(ms) — on
job cancellation, wait this long for in-progress tasks to complete before
force-interrupting them, default 600000(ms). The effective wait is capped below
task.cancellation.timeout (default 180000).</td>
+ </tr>
</tbody>
</table>
<p>Or you can submit optimizer in your own Spark task development platform or
local Spark environment with the following configuration. The main parameters
include:</p>
@@ -1398,6 +1411,11 @@ If the optimizer runs normally, you will see an
optimizer with the status <code>
<td>No</td>
<td>Timeout in optimizer cache, default
10Min.</td>
</tr>
+ <tr>
+ <td>-st</td>
+ <td>No</td>
+ <td>Graceful shutdown timeout(ms) — on
shutdown, wait this long for in-progress tasks to complete before
force-interrupting them, default 600000(ms).</td>
+ </tr>
</tbody>
</table>
</div>
diff --git a/output/docs/latest/search.json b/output/docs/latest/search.json
index 210678dae..15b524e47 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
