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/dolphinscheduler-website.git


The following commit(s) were added to refs/heads/asf-site by this push:
     new cdcb424370 Automated deployment: 
3c1ca9301a648e2aa9ed11e718d630d098c7f6fc
cdcb424370 is described below

commit cdcb424370a1f96471f68edb9eaed253c06970f4
Author: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
AuthorDate: Sun May 24 06:18:31 2026 +0000

    Automated deployment: 3c1ca9301a648e2aa9ed11e718d630d098c7f6fc
---
 data/faq/en-us.json      | 12 ++++++------
 fetch/faq/en-us/dev.json | 12 ++++++------
 2 files changed, 12 insertions(+), 12 deletions(-)

diff --git a/data/faq/en-us.json b/data/faq/en-us.json
index 2530108f32..936cb61abb 100644
--- a/data/faq/en-us.json
+++ b/data/faq/en-us.json
@@ -122,7 +122,7 @@
   {
     "version": "dev",
     "q": "<h2>Q:Worker Task will generate a child process through sudo -u 
tenant sh xxx.command, will kill when kill</h2>",
-    "a": "\n<p>A: We will add the kill task in 1.0.4 and kill all the various 
child processes generated by the task.</p>\n<hr>\n"
+    "a": "\n<p>A: We will add the kill task in 1.0.4 and kill all the various 
child processes generated by the task.</p>\n<hr>\n"
   },
   {
     "version": "dev",
@@ -172,7 +172,7 @@
   {
     "version": "dev",
     "q": "<h2>Q : Always fail when a task instance submit multiple yarn 
application</h2>",
-    "a": "\n<p align=\"center\">\n   <img 
src=\"https://user-images.githubusercontent.com/16174111/81312485-476e9380-90b9-11ea-9aad-ed009db899b1.png\";
 width=\"60%\" />\n </p>\nA: This bug have fix in dev and in Requirement/TODO 
list.\n<hr>\n"
+    "a": "\n<p align=\"center\">\n   <img 
src=\"https://user-images.githubusercontent.com/16174111/81312485-476e9380-90b9-11ea-9aad-ed009db899b1.png\";
 width=\"60%\" />\n </p>\nA: This bug has been fixed in dev and is in the 
Requirement/TODO list.\n<hr>\n"
   },
   {
     "version": "dev",
@@ -267,22 +267,22 @@
   {
     "version": "dev",
     "q": "<h2>Q:Deploy for multiple YARN clusters</h2>",
-    "a": "\n<p>A:By deploying different worker in different yarn clusters,the 
steps are as follows(eg: AWS EMR):</p>\n<ol>\n<li>\n<p>Deploying the worker 
server on the master node of the EMR cluster</p>\n</li>\n<li>\n<p>Changing 
<code>yarn.application.status.address</code> to current emr's yarn url in the 
<code>conf/common.properties</code></p>\n</li>\n<li>\n<p>Execute command 
<code>bin/dolphinscheduler-daemon.sh start worker-server</code> to start 
worker-server</p>\n</li>\n</ol>\n<hr>\n"
+    "a": "\n<p>A: By deploying different worker in different yarn clusters, 
the steps are as follows(eg: AWS EMR):</p>\n<ol>\n<li>\n<p>Deploying the worker 
server on the master node of the EMR cluster</p>\n</li>\n<li>\n<p>Changing 
<code>yarn.application.status.address</code> to current emr's yarn url in the 
<code>conf/common.properties</code></p>\n</li>\n<li>\n<p>Execute command 
<code>bin/dolphinscheduler-daemon.sh start worker-server</code> to start 
worker-server</p>\n</li>\n</ol>\n<hr>\n"
   },
   {
     "version": "dev",
     "q": "<h2>Q:Update process definition error: Duplicate key 
TaskDefinition</h2>",
-    "a": "\n<p>A:Before DS 2.0.4 (after 2.0.0-alpha), there may be a problem 
of duplicate keys TaskDefinition due to version switching, which may cause the 
update workflow to fail; you can refer to the following SQL to delete duplicate 
data, taking MySQL as an example: (Note: Before operating, be sure to back up 
the original data, the SQL from pr<a 
href=\"https://github.com/apache/dolphinscheduler/pull/8408\";>#8408</a>)</p>\n<pre><code
 class=\"language-SQL\"><span class=\"hljs-keyword\"> [...]
+    "a": "\n<p>A: Before DS 2.0.4 (after 2.0.0-alpha), there may be a problem 
of duplicate keys TaskDefinition due to version switching, which may cause the 
update workflow to fail; you can refer to the following SQL to delete duplicate 
data, taking MySQL as an example: (Note: Before operating, be sure to back up 
the original data, the SQL from pr<a 
href=\"https://github.com/apache/dolphinscheduler/pull/8408\";>#8408</a>)</p>\n<pre><code
 class=\"language-SQL\"><span class=\"hljs-keyword\" [...]
   },
   {
     "version": "dev",
     "q": "<h2>Q:Upgrade from 2.0.1 to 2.0.5 using PostgreSQL database 
failed</h2>",
-    "a": "\n<p>A:The repair can be completed by executing the following SQL in 
the database:</p>\n<pre><code class=\"language-SQL\"><span 
class=\"hljs-keyword\">update</span> t_ds_version <span 
class=\"hljs-keyword\">set</span> version<span 
class=\"hljs-operator\">=</span><span 
class=\"hljs-string\">&#x27;2.0.1&#x27;</span>;\n</code></pre>\n<hr>\n"
+    "a": "\n<p>A: The repair can be completed by executing the following SQL 
in the database:</p>\n<pre><code class=\"language-SQL\"><span 
class=\"hljs-keyword\">update</span> t_ds_version <span 
class=\"hljs-keyword\">set</span> version<span 
class=\"hljs-operator\">=</span><span 
class=\"hljs-string\">&#x27;2.0.1&#x27;</span>;\n</code></pre>\n<hr>\n"
   },
   {
     "version": "dev",
     "q": "<h2>Q:Can not find python-gateway-server in distribute package</h2>",
-    "a": "\n<p>A:After version 3.0.0-alpha, Python gateway server integrate 
into API server, and Python gateway service will start when you\nstart API 
server. If you want disabled when Python gateway service you could change API 
server configuration in path\n<code>api-server/conf/application.yaml</code> and 
change attribute <code>python-gateway.enabled : false</code>.</p>\n<hr>\n"
+    "a": "\n<p>A: After version 3.0.0-alpha, Python gateway server integrate 
into API server, and Python gateway service will start when you\nstart API 
server. If you want disabled when Python gateway service you could change API 
server configuration in path\n<code>api-server/conf/application.yaml</code> and 
change attribute <code>python-gateway.enabled : false</code>.</p>\n<hr>\n"
   },
   {
     "version": "dev",
diff --git a/fetch/faq/en-us/dev.json b/fetch/faq/en-us/dev.json
index aee5b29731..354b94da90 100644
--- a/fetch/faq/en-us/dev.json
+++ b/fetch/faq/en-us/dev.json
@@ -97,7 +97,7 @@
   },
   {
     "q": "<h2>Q:Worker Task will generate a child process through sudo -u 
tenant sh xxx.command, will kill when kill</h2>",
-    "a": "\n<p>A: We will add the kill task in 1.0.4 and kill all the various 
child processes generated by the task.</p>\n<hr>\n"
+    "a": "\n<p>A: We will add the kill task in 1.0.4 and kill all the various 
child processes generated by the task.</p>\n<hr>\n"
   },
   {
     "q": "<h2>Q : How to use the queue in DolphinScheduler, what does the user 
queue and tenant queue mean?</h2>",
@@ -137,7 +137,7 @@
   },
   {
     "q": "<h2>Q : Always fail when a task instance submit multiple yarn 
application</h2>",
-    "a": "\n<p align=\"center\">\n   <img 
src=\"https://user-images.githubusercontent.com/16174111/81312485-476e9380-90b9-11ea-9aad-ed009db899b1.png\";
 width=\"60%\" />\n </p>\nA: This bug have fix in dev and in Requirement/TODO 
list.\n<hr>\n"
+    "a": "\n<p align=\"center\">\n   <img 
src=\"https://user-images.githubusercontent.com/16174111/81312485-476e9380-90b9-11ea-9aad-ed009db899b1.png\";
 width=\"60%\" />\n </p>\nA: This bug has been fixed in dev and is in the 
Requirement/TODO list.\n<hr>\n"
   },
   {
     "q": "<h2>Q : Master server and worker server stop abnormally after run 
for a few days</h2>",
@@ -213,19 +213,19 @@
   },
   {
     "q": "<h2>Q:Deploy for multiple YARN clusters</h2>",
-    "a": "\n<p>A:By deploying different worker in different yarn clusters,the 
steps are as follows(eg: AWS EMR):</p>\n<ol>\n<li>\n<p>Deploying the worker 
server on the master node of the EMR cluster</p>\n</li>\n<li>\n<p>Changing 
<code>yarn.application.status.address</code> to current emr's yarn url in the 
<code>conf/common.properties</code></p>\n</li>\n<li>\n<p>Execute command 
<code>bin/dolphinscheduler-daemon.sh start worker-server</code> to start 
worker-server</p>\n</li>\n</ol>\n<hr>\n"
+    "a": "\n<p>A: By deploying different worker in different yarn clusters, 
the steps are as follows(eg: AWS EMR):</p>\n<ol>\n<li>\n<p>Deploying the worker 
server on the master node of the EMR cluster</p>\n</li>\n<li>\n<p>Changing 
<code>yarn.application.status.address</code> to current emr's yarn url in the 
<code>conf/common.properties</code></p>\n</li>\n<li>\n<p>Execute command 
<code>bin/dolphinscheduler-daemon.sh start worker-server</code> to start 
worker-server</p>\n</li>\n</ol>\n<hr>\n"
   },
   {
     "q": "<h2>Q:Update process definition error: Duplicate key 
TaskDefinition</h2>",
-    "a": "\n<p>A:Before DS 2.0.4 (after 2.0.0-alpha), there may be a problem 
of duplicate keys TaskDefinition due to version switching, which may cause the 
update workflow to fail; you can refer to the following SQL to delete duplicate 
data, taking MySQL as an example: (Note: Before operating, be sure to back up 
the original data, the SQL from pr<a 
href=\"https://github.com/apache/dolphinscheduler/pull/8408\";>#8408</a>)</p>\n<pre><code
 class=\"language-SQL\"><span class=\"hljs-keyword\"> [...]
+    "a": "\n<p>A: Before DS 2.0.4 (after 2.0.0-alpha), there may be a problem 
of duplicate keys TaskDefinition due to version switching, which may cause the 
update workflow to fail; you can refer to the following SQL to delete duplicate 
data, taking MySQL as an example: (Note: Before operating, be sure to back up 
the original data, the SQL from pr<a 
href=\"https://github.com/apache/dolphinscheduler/pull/8408\";>#8408</a>)</p>\n<pre><code
 class=\"language-SQL\"><span class=\"hljs-keyword\" [...]
   },
   {
     "q": "<h2>Q:Upgrade from 2.0.1 to 2.0.5 using PostgreSQL database 
failed</h2>",
-    "a": "\n<p>A:The repair can be completed by executing the following SQL in 
the database:</p>\n<pre><code class=\"language-SQL\"><span 
class=\"hljs-keyword\">update</span> t_ds_version <span 
class=\"hljs-keyword\">set</span> version<span 
class=\"hljs-operator\">=</span><span 
class=\"hljs-string\">&#x27;2.0.1&#x27;</span>;\n</code></pre>\n<hr>\n"
+    "a": "\n<p>A: The repair can be completed by executing the following SQL 
in the database:</p>\n<pre><code class=\"language-SQL\"><span 
class=\"hljs-keyword\">update</span> t_ds_version <span 
class=\"hljs-keyword\">set</span> version<span 
class=\"hljs-operator\">=</span><span 
class=\"hljs-string\">&#x27;2.0.1&#x27;</span>;\n</code></pre>\n<hr>\n"
   },
   {
     "q": "<h2>Q:Can not find python-gateway-server in distribute package</h2>",
-    "a": "\n<p>A:After version 3.0.0-alpha, Python gateway server integrate 
into API server, and Python gateway service will start when you\nstart API 
server. If you want disabled when Python gateway service you could change API 
server configuration in path\n<code>api-server/conf/application.yaml</code> and 
change attribute <code>python-gateway.enabled : false</code>.</p>\n<hr>\n"
+    "a": "\n<p>A: After version 3.0.0-alpha, Python gateway server integrate 
into API server, and Python gateway service will start when you\nstart API 
server. If you want disabled when Python gateway service you could change API 
server configuration in path\n<code>api-server/conf/application.yaml</code> and 
change attribute <code>python-gateway.enabled : false</code>.</p>\n<hr>\n"
   },
   {
     "q": "<h2>Q: Why is the schedule status of a workflow definition set to 
&quot;Offline&quot; after importing an online workflow definition?</h2>",

Reply via email to