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

github-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 96fe82faf2 Automated deployment: 
907f87fe77ffbf58c67d51f12e6f627950945ba7
96fe82faf2 is described below

commit 96fe82faf2999b0892088660f7ac78d8daad6088
Author: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
AuthorDate: Wed Nov 1 01:12:49 2023 +0000

    Automated deployment: 907f87fe77ffbf58c67d51f12e6f627950945ba7
---
 data/blog/zh-cn.json                                   |  12 ++++++++++++
 fetch/blog/zh-cn.json                                  |  14 ++++++++++++++
 img/2023-10-25/1.png                                   | Bin 0 -> 684499 bytes
 img/2023-10-25/2.png                                   | Bin 0 -> 416605 bytes
 img/2023-10-31/1.png                                   | Bin 0 -> 153829 bytes
 img/2023-10-31/2.png                                   | Bin 0 -> 274185 bytes
 img/2023-10-31/3.png                                   | Bin 0 -> 158072 bytes
 img/2023-10-31/4.png                                   | Bin 0 -> 45878 bytes
 img/2023-10-31/5.png                                   | Bin 0 -> 15754 bytes
 img/2023-10-31/6.png                                   | Bin 0 -> 158797 bytes
 ...rating_from_Airflow_to_Apache_DolphinScheduler.json |   8 ++++++++
 ...nite_loop_of_Master_service_without_restarting.json |   8 ++++++++
 python/2.0.5/.buildinfo                                |   2 +-
 python/2.0.6/.buildinfo                                |   2 +-
 python/2.0.7/.buildinfo                                |   2 +-
 python/3.0.0/.buildinfo                                |   2 +-
 python/3.0.1/.buildinfo                                |   2 +-
 python/3.1.0/.buildinfo                                |   2 +-
 python/4.0.0/.buildinfo                                |   2 +-
 python/4.0.1/.buildinfo                                |   2 +-
 python/4.0.2/.buildinfo                                |   2 +-
 python/4.0.3/.buildinfo                                |   2 +-
 python/4.0.4/.buildinfo                                |   2 +-
 python/main/.buildinfo                                 |   2 +-
 24 files changed, 54 insertions(+), 12 deletions(-)

diff --git a/data/blog/zh-cn.json b/data/blog/zh-cn.json
index c88d30ed6c..f9a5af91b9 100644
--- a/data/blog/zh-cn.json
+++ b/data/blog/zh-cn.json
@@ -71,6 +71,12 @@
     "title": "Apache DolphinScheduler 获评 2021 年度「最受欢迎项目」",
     "time": "2022-1-7"
   },
+  {
+    "name": 
"Big_Data_Scheduling_Best_Practices_Migrating_from_Airflow_to_Apache_DolphinScheduler",
+    "content": "title: 大数据调度最佳实践 |  从Airflow迁移到Apache 
DolphinScheduler\nkeywords: Apache DolphinScheduler, 迁移, Airflow\ndescription: 
有部分用户原来是使用 Airflow 作为调度系统的,但是由于 Airflow 
只能通过代码来定义工作流,并且没有对资源、项目的粒度划分,导致在部分需要较强权限控制的场景下不能很好的贴合客户需求,所以部分用户需要将调度系统从 
Airflow 迁移到 Apache Dolphinscheduler。\n\n迁移背景\n有部分用户原来是使用 Airflow 作为调度系统的,但是由于 
Airflow 
只能通过代码来定义工作流,并且没有对资源、项目的粒度划分,导致在部分需要较强权限控制的场景下不能很好的贴合客户需求,所以部分用户需要将调度系统从 
Airflow 迁移到 Apache Dolphinscheduler。\n\n秉承着解决用户实际需求的角度出发,Whaleops 研发了 Air2phin 
迁移工具,协助用 [...]
+    "title": "大数据调度最佳实践 |  从Airflow迁移到Apache DolphinScheduler",
+    "time": "2023-10-25"
+  },
   {
     "name": "Board_of_Directors_Report",
     "content": "Apache DolphinScheduler 董事会报告:社区健康运行,Commit 增长 123%\n\n\n\n\n自 
2021 年 3 月 17 日从 Apache 孵化器毕业以来,Apache DolphinScheduler 
不知不觉已经和社区一起经过了十个月的成长。在社区的共同参与下,Apache DolphinScheduler 
在数次版本迭代后,蜕变为一个经过数百家企业生产环境检验的成熟调度系统产品。\n\n\n在将近一年的时间里,Apache DolphinScheduler 
有了哪些进步?今天我们将通过这篇 Apache 报告,一起回顾这段时间发生在 Apache DolphinScheduler 
及其社区中的变化。\n\n基本数据:\n成立: 2021 年 03 月 17 日(十个月前)\nChair: 代立冬\n下次报告日期: 2022 年 1 月 
19 日(星期三)\n社区健康评分( Chi ): 7.55(健康)\n项目组成:\n\n目前该项目中有 39 个 committer 和 16 个 PMC 
成员。\ [...]
@@ -173,6 +179,12 @@
     "title": "Apache DolphinScheduler 如何解决传智教育数仓调度痛点?",
     "time": "2023-9-5"
   },
+  {
+    "name": 
"How_does_Apache_Dolphinscheduler_solve_the_infinite_loop_of_Master_service_without_restarting",
+    "content": "title: Apache Dolphinscheduler如何不重启解决Master服务死循环\nkeywords: 
Apache DolphinScheduler, 死循环, Master\ndescription: 
相信不少使用过3.0的用户都遇到过Master服务中存在一些工作流一直不停的死循环的问题,本人到现在也没找到触发的原因,但是通过与同事的摸索,暂时找到了一个可以借助Arthas解决死循环的方法。\n\n个人建议\nApache
 
Dolphinscheduler作为一个开源的调度平台,目前已经更新到了3.X版本,4.0版本也已经呼之欲出。3.0版本作为尝鲜版本,新添加了许多的功能,同时也存在非常多的隐患,本人使用3.0版本作为生产调度也踩了很多坑,到现在依然存在很多难以解决的问题,所以建议小伙伴们尽量使用2.x版本,相对稳定一些。\n\n近期在跟社区的沟通中,**最新3.2.0版本,该问题已经得到解决!**感兴趣可以了解最新版本。\n\n\n下面主要记录的是
 一个3.0比较难搞的问题,相信不少使用过3.0的用户都遇到过Mas [...]
+    "title": "Apache Dolphinscheduler如何不重启解决Master服务死循环",
+    "time": "2023-10-31"
+  },
   {
     "name": 
"How_does_the_national_dairy_giant_Yili_open_up_a_path_for_enterprise_digital_transformation_based_on_Apache_DolphinScheduler",
     "content": "title: 国民乳业巨头伊利如何基于 DolphinScheduler 开辟企业数字化转型“蹊径”?\nkeywords: 
Apache DolphinScheduler, 伊利, 数字化转型\ndescription: 
在数据驱动转型的过程中,会存在海量的数据集成任务,整体集成架构的合理性、调度的稳定性会严重影响数据流转的效率,也会制约数据的价值挖掘,伊利基于 Apache 
DolphinScheduler 
构建了统一的调度服务与数据集成体系,加速数据流转,助力企业数字化转型。\n\n\n精彩回顾\n近期,国民乳业巨头伊利集团在社区线上 Meetup 
上带来了《伊利集团基于 DolphinScheduler 
的探索与实践》。\n伊利集团数字化中心统筹推进全集团的数字化转型工作,姜涛及其团队在数字化中心负责大数据技术能力的建设以及相关的业务支持工作。在数据驱动转型的过程中,会存在海量的数据集成任务,整体集成架构的合理性、调度的�
 ��定性会严重影响数据流转的效率,也会制约数据的价值挖掘,伊利基于 Apache DolphinScheduler [...]
diff --git a/fetch/blog/zh-cn.json b/fetch/blog/zh-cn.json
index 11399ef5b2..9141f8fa79 100644
--- a/fetch/blog/zh-cn.json
+++ b/fetch/blog/zh-cn.json
@@ -58,6 +58,20 @@
     "type": "tech",
     "label": "技术详解",
     "children": [
+      {
+        "name": 
"How_does_Apache_Dolphinscheduler_solve_the_infinite_loop_of_Master_service_without_restarting",
+        "title": "Apache Dolphinscheduler如何不重启解决Master服务死循环",
+        "author": "Niko Zemg",
+        "dateStr": "2023-10-31",
+        "desc": 
"相信不少使用过3.0的用户都遇到过Master服务中存在一些工作流一直不停的死循环的问题,本人到现在也没找到触发的原因,但是通过与同事的摸索,暂时找到了一个可以借助Arthas解决死循环的方法......"
+      },
+      {
+        "name": 
"Big_Data_Scheduling_Best_Practices_Migrating_from_Airflow_to_Apache_DolphinScheduler",
+        "title": "大数据调度最佳实践 |  从Airflow迁移到Apache DolphinScheduler",
+        "author": "Niko Zemg",
+        "dateStr": "2023-10-25",
+        "desc": "有部分用户原来是使用 Airflow 作为调度系统的,但是由于 Airflow 
只能通过代码来定义工作流,并且没有对资源、项目的粒度划分,导致在部分需要较强权限控制的场景下不能很好的贴合客户需求,所以部分用户需要将调度系统从 
Airflow 迁移到 Apache Dolphinscheduler。......"
+      },
       {
         "name": "K8s_Cisco_Hangzhou",
         "title": "全面拥抱 K8s,ApacheDolphinScheduler 应用与支持 K8s 任务的探索",
diff --git a/img/2023-10-25/1.png b/img/2023-10-25/1.png
new file mode 100644
index 0000000000..c537f35d79
Binary files /dev/null and b/img/2023-10-25/1.png differ
diff --git a/img/2023-10-25/2.png b/img/2023-10-25/2.png
new file mode 100644
index 0000000000..8894c0c86f
Binary files /dev/null and b/img/2023-10-25/2.png differ
diff --git a/img/2023-10-31/1.png b/img/2023-10-31/1.png
new file mode 100644
index 0000000000..2ecf1bcabc
Binary files /dev/null and b/img/2023-10-31/1.png differ
diff --git a/img/2023-10-31/2.png b/img/2023-10-31/2.png
new file mode 100644
index 0000000000..aa011aed1a
Binary files /dev/null and b/img/2023-10-31/2.png differ
diff --git a/img/2023-10-31/3.png b/img/2023-10-31/3.png
new file mode 100644
index 0000000000..13306060f5
Binary files /dev/null and b/img/2023-10-31/3.png differ
diff --git a/img/2023-10-31/4.png b/img/2023-10-31/4.png
new file mode 100644
index 0000000000..703329e354
Binary files /dev/null and b/img/2023-10-31/4.png differ
diff --git a/img/2023-10-31/5.png b/img/2023-10-31/5.png
new file mode 100644
index 0000000000..878980d381
Binary files /dev/null and b/img/2023-10-31/5.png differ
diff --git a/img/2023-10-31/6.png b/img/2023-10-31/6.png
new file mode 100644
index 0000000000..fa36ba28d4
Binary files /dev/null and b/img/2023-10-31/6.png differ
diff --git 
a/pages/blog/zh-cn/Big_Data_Scheduling_Best_Practices_Migrating_from_Airflow_to_Apache_DolphinScheduler.json
 
b/pages/blog/zh-cn/Big_Data_Scheduling_Best_Practices_Migrating_from_Airflow_to_Apache_DolphinScheduler.json
new file mode 100644
index 0000000000..f46cfe15a4
--- /dev/null
+++ 
b/pages/blog/zh-cn/Big_Data_Scheduling_Best_Practices_Migrating_from_Airflow_to_Apache_DolphinScheduler.json
@@ -0,0 +1,8 @@
+{
+  "__html": "<pre><code class=\"language-yaml\"><span 
class=\"hljs-attr\">title:</span> <span class=\"hljs-string\">大数据调度最佳实践</span> 
<span class=\"hljs-string\">|</span>  <span 
class=\"hljs-string\">从Airflow迁移到Apache</span> <span 
class=\"hljs-string\">DolphinScheduler</span>\n<span 
class=\"hljs-attr\">keywords:</span> <span class=\"hljs-string\">Apache</span> 
<span class=\"hljs-string\">DolphinScheduler,</span> <span 
class=\"hljs-string\">迁移,</span> <span class=\"hljs-string\">Airflow</s [...]
+  "time": "2023-10-25",
+  "author": "Niko Zemg",
+  "title": "大数据调度最佳实践 |  从Airflow迁移到Apache DolphinScheduler",
+  "type": "tech",
+  "label": "技术详解"
+}
\ No newline at end of file
diff --git 
a/pages/blog/zh-cn/How_does_Apache_Dolphinscheduler_solve_the_infinite_loop_of_Master_service_without_restarting.json
 
b/pages/blog/zh-cn/How_does_Apache_Dolphinscheduler_solve_the_infinite_loop_of_Master_service_without_restarting.json
new file mode 100644
index 0000000000..fb86f32d4e
--- /dev/null
+++ 
b/pages/blog/zh-cn/How_does_Apache_Dolphinscheduler_solve_the_infinite_loop_of_Master_service_without_restarting.json
@@ -0,0 +1,8 @@
+{
+  "__html": "<pre><code class=\"language-yaml\"><span 
class=\"hljs-attr\">title:</span> <span class=\"hljs-string\">Apache</span> 
<span class=\"hljs-string\">Dolphinscheduler如何不重启解决Master服务死循环</span>\n<span 
class=\"hljs-attr\">keywords:</span> <span class=\"hljs-string\">Apache</span> 
<span class=\"hljs-string\">DolphinScheduler,</span> <span 
class=\"hljs-string\">死循环,</span> <span 
class=\"hljs-string\">Master</span>\n<span 
class=\"hljs-attr\">description:</span> <span class=\"hljs-strin [...]
+  "time": "2023-10-31",
+  "author": "Niko Zemg",
+  "title": "Apache Dolphinscheduler如何不重启解决Master服务死循环",
+  "type": "tech",
+  "label": "技术详解"
+}
\ No newline at end of file
diff --git a/python/2.0.5/.buildinfo b/python/2.0.5/.buildinfo
index 2f812ef41f..7186ed9fd5 100644
--- a/python/2.0.5/.buildinfo
+++ b/python/2.0.5/.buildinfo
@@ -1,4 +1,4 @@
 # Sphinx build info version 1
 # This file hashes the configuration used when building these files. When it 
is not found, a full rebuild will be done.
-config: c2bf2715d5f47aea6f59c3c1c00ac658
+config: 3f1b04846aa44de2f8394086499d794b
 tags: 645f666f9bcd5a90fca523b33c5a78b7
diff --git a/python/2.0.6/.buildinfo b/python/2.0.6/.buildinfo
index 46cfcafc41..54fbd2ba1d 100644
--- a/python/2.0.6/.buildinfo
+++ b/python/2.0.6/.buildinfo
@@ -1,4 +1,4 @@
 # Sphinx build info version 1
 # This file hashes the configuration used when building these files. When it 
is not found, a full rebuild will be done.
-config: 240a0b1e5d2a67b54e5198314ed8e83a
+config: c342a749cf7cdbdd5f4588deeec283d4
 tags: 645f666f9bcd5a90fca523b33c5a78b7
diff --git a/python/2.0.7/.buildinfo b/python/2.0.7/.buildinfo
index 07bcbc0172..72dfac03f1 100644
--- a/python/2.0.7/.buildinfo
+++ b/python/2.0.7/.buildinfo
@@ -1,4 +1,4 @@
 # Sphinx build info version 1
 # This file hashes the configuration used when building these files. When it 
is not found, a full rebuild will be done.
-config: 6e9fe12c799cb2f6310761a1628f5e92
+config: e337b0c96c39b2f0a36e0b40e02ab728
 tags: 645f666f9bcd5a90fca523b33c5a78b7
diff --git a/python/3.0.0/.buildinfo b/python/3.0.0/.buildinfo
index f47917e50c..94a3309776 100644
--- a/python/3.0.0/.buildinfo
+++ b/python/3.0.0/.buildinfo
@@ -1,4 +1,4 @@
 # Sphinx build info version 1
 # This file hashes the configuration used when building these files. When it 
is not found, a full rebuild will be done.
-config: 28bca37da5a3291e89009b1d8e91b74a
+config: f12f4abf1008524cf0df60b5dfc4d82a
 tags: 645f666f9bcd5a90fca523b33c5a78b7
diff --git a/python/3.0.1/.buildinfo b/python/3.0.1/.buildinfo
index 35a1056da8..b190a4712d 100644
--- a/python/3.0.1/.buildinfo
+++ b/python/3.0.1/.buildinfo
@@ -1,4 +1,4 @@
 # Sphinx build info version 1
 # This file hashes the configuration used when building these files. When it 
is not found, a full rebuild will be done.
-config: 7e87e05b52a100d0b794e9bba2f6008a
+config: 321a34feb468242f666fd5d32fa06088
 tags: 645f666f9bcd5a90fca523b33c5a78b7
diff --git a/python/3.1.0/.buildinfo b/python/3.1.0/.buildinfo
index 01d2dfc69a..9b36d08c62 100644
--- a/python/3.1.0/.buildinfo
+++ b/python/3.1.0/.buildinfo
@@ -1,4 +1,4 @@
 # Sphinx build info version 1
 # This file hashes the configuration used when building these files. When it 
is not found, a full rebuild will be done.
-config: f0109e215f24e61d887b26434b5c63b5
+config: 2536ffe8128c424907aed8d83566ab7d
 tags: 645f666f9bcd5a90fca523b33c5a78b7
diff --git a/python/4.0.0/.buildinfo b/python/4.0.0/.buildinfo
index 869df0e009..393c77d94a 100644
--- a/python/4.0.0/.buildinfo
+++ b/python/4.0.0/.buildinfo
@@ -1,4 +1,4 @@
 # Sphinx build info version 1
 # This file hashes the configuration used when building these files. When it 
is not found, a full rebuild will be done.
-config: 8c219e0af9d924111f2293b08539765d
+config: 5046bdc4d76f4a5551611c588c63f210
 tags: 645f666f9bcd5a90fca523b33c5a78b7
diff --git a/python/4.0.1/.buildinfo b/python/4.0.1/.buildinfo
index 94a7e674d5..2b92406d65 100644
--- a/python/4.0.1/.buildinfo
+++ b/python/4.0.1/.buildinfo
@@ -1,4 +1,4 @@
 # Sphinx build info version 1
 # This file hashes the configuration used when building these files. When it 
is not found, a full rebuild will be done.
-config: da2dd7286af0a64d02819898d82b2f0f
+config: 0374ecc529643b7d0640a9bd42483eb1
 tags: 645f666f9bcd5a90fca523b33c5a78b7
diff --git a/python/4.0.2/.buildinfo b/python/4.0.2/.buildinfo
index 75d0dfb7f9..88c0736fda 100644
--- a/python/4.0.2/.buildinfo
+++ b/python/4.0.2/.buildinfo
@@ -1,4 +1,4 @@
 # Sphinx build info version 1
 # This file hashes the configuration used when building these files. When it 
is not found, a full rebuild will be done.
-config: fec592ec38207c34293e1d9499627e22
+config: 0f72a7381b8c054fd51d4856441a0a59
 tags: 645f666f9bcd5a90fca523b33c5a78b7
diff --git a/python/4.0.3/.buildinfo b/python/4.0.3/.buildinfo
index e6d03e07a1..5857399440 100644
--- a/python/4.0.3/.buildinfo
+++ b/python/4.0.3/.buildinfo
@@ -1,4 +1,4 @@
 # Sphinx build info version 1
 # This file hashes the configuration used when building these files. When it 
is not found, a full rebuild will be done.
-config: 40321023124c464c80d512e21ed92327
+config: cdb79da490e7b37f78c56dfa511af727
 tags: 645f666f9bcd5a90fca523b33c5a78b7
diff --git a/python/4.0.4/.buildinfo b/python/4.0.4/.buildinfo
index 4b7f9101bb..319765f0d6 100644
--- a/python/4.0.4/.buildinfo
+++ b/python/4.0.4/.buildinfo
@@ -1,4 +1,4 @@
 # Sphinx build info version 1
 # This file hashes the configuration used when building these files. When it 
is not found, a full rebuild will be done.
-config: 195fae70a774578f6baaebfc19e58c9c
+config: 5b77dec5e7253eaf87d14f1fda99a944
 tags: 645f666f9bcd5a90fca523b33c5a78b7
diff --git a/python/main/.buildinfo b/python/main/.buildinfo
index 02aae924db..a84b54a36f 100644
--- a/python/main/.buildinfo
+++ b/python/main/.buildinfo
@@ -1,4 +1,4 @@
 # Sphinx build info version 1
 # This file hashes the configuration used when building these files. When it 
is not found, a full rebuild will be done.
-config: d0d3bb3c89ffbc1343f4849bc1d893e6
+config: 0d87c22403d4f4f3940eb77c20c71a9e
 tags: 645f666f9bcd5a90fca523b33c5a78b7

Reply via email to