You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@seata.apache.org by ji...@apache.org on 2024/12/13 16:32:51 UTC
(incubator-seata-website) branch asf-site updated: Automated deployment: Fri Dec 13 16:32:35 UTC 2024 8c4a31524d098ac18a7b67da86212a75ce08c853
This is an automated email from the ASF dual-hosted git repository.
jimin pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/incubator-seata-website.git
The following commit(s) were added to refs/heads/asf-site by this push:
new 1bbb000ca5d Automated deployment: Fri Dec 13 16:32:35 UTC 2024 8c4a31524d098ac18a7b67da86212a75ce08c853
1bbb000ca5d is described below
commit 1bbb000ca5db6efb129c7cffaadd7477aac8f564
Author: funky-eyes <fu...@users.noreply.github.com>
AuthorDate: Fri Dec 13 16:32:36 2024 +0000
Automated deployment: Fri Dec 13 16:32:35 UTC 2024 8c4a31524d098ac18a7b67da86212a75ce08c853
---
...2024121301-4613ead894d7510e65d88296eb86e297.png | Bin 0 -> 365111 bytes
...2024121302-39625f525d6da1bbc7ad4509c94718eb.png | Bin 0 -> 318738 bytes
...2024121303-bad6bb1db830335d72e2037ea7dbf4de.png | Bin 0 -> 419640 bytes
...2024121304-fcc9119043d66143a841d2008ef136f5.png | Bin 0 -> 413464 bytes
...2024121305-327ecb450c5fd7f7fc636165421972b2.png | Bin 0 -> 358454 bytes
...024121306-5568d956a86d67c43e4d76837dd5c8b8.jpeg | Bin 0 -> 92986 bytes
assets/js/11ce4159.9318726b.js | 1 +
assets/js/1dc3c500.ea283c57.js | 1 +
assets/js/2d6322e8.0f290bfd.js | 1 +
assets/js/44ac4dbb.8a588fe0.js | 1 +
assets/js/52099127.5f140573.js | 1 +
assets/js/5c941569.831d6e25.js | 1 +
assets/js/7d9726a8.2f524a19.js | 1 +
assets/js/814f3328.42bfeb1c.js | 1 +
assets/js/8eb4e46b.acb9610d.js | 1 +
assets/js/8f32d218.e50ccc03.js | 1 +
assets/js/92999a1c.3f3d9d67.js | 1 +
assets/js/b2b675dd.8bb91942.js | 1 +
assets/js/b2f554cd.9ea9c4f0.js | 1 +
assets/js/d1400855.24cc561c.js | 1 +
assets/js/ef915a9a.5686e2ca.js | 1 +
assets/js/main.aeea7339.js | 2 +
assets/js/main.aeea7339.js.LICENSE.txt | 64 +
assets/js/runtime~main.762ed5c0.js | 1 +
blog/archive/index.html | 6 +-
blog/atom.xml | 179 +--
.../index.html | 6 +-
blog/explore-seata-journey/index.html | 6 +-
blog/how-to-support-spring-cloud/index.html | 6 +-
blog/how-to-write-unit-tests/index.html | 6 +-
blog/index.html | 114 +-
.../index.html | 6 +-
blog/integrate-seata-with-spring-cloud/index.html | 6 +-
blog/iscas2023/index.html | 6 +-
blog/manual-transaction-mode/index.html | 6 +-
blog/page/2/index.html | 179 +--
blog/page/3/index.html | 164 ++-
blog/page/4/index.html | 142 +--
blog/page/5/index.html | 242 ++--
blog/page/6/index.html | 247 ++--
blog/page/7/index.html | 98 +-
.../index.html | 6 +-
blog/rss.xml | 173 +--
blog/seata-1.5.2/index.html | 6 +-
blog/seata-1.6.0/index.html | 6 +-
blog/seata-analysis-UUID-generator/index.html | 6 +-
blog/seata-analysis-config-modular/index.html | 6 +-
blog/seata-analysis-core-modular/index.html | 8 +-
blog/seata-analysis-dubbo-transmit-xid/index.html | 6 +-
blog/seata-analysis-go-server/index.html | 6 +-
blog/seata-analysis-java-client/index.html | 6 +-
blog/seata-analysis-java-server/index.html | 6 +-
blog/seata-analysis-simple/index.html | 6 +-
blog/seata-analysis-tcc-modular/index.html | 6 +-
blog/seata-at-demo-in-mac/index.html | 6 +-
blog/seata-at-lock/index.html | 6 +-
blog/seata-at-mode-design/index.html | 6 +-
blog/seata-at-mode-start-rm-tm/index.html | 6 +-
blog/seata-at-mode-start/index.html | 6 +-
blog/seata-at-tcc-saga/index.html | 6 +-
blog/seata-client-start-analysis-01/index.html | 6 +-
blog/seata-client-start-analysis-02/index.html | 6 +-
.../index.html | 6 +-
blog/seata-config-center/index.html | 6 +-
blog/seata-config-manager/index.html | 6 +-
blog/seata-connect-data-and-application/index.html | 6 +-
blog/seata-datasource-proxy/index.html | 6 +-
blog/seata-dsproxy-deadlock/index.html | 6 +-
.../index.html | 6 +-
blog/seata-feature-undo-log-compress/index.html | 6 +-
blog/seata-go-1.2.0/index.html | 6 +-
blog/seata-golang-communication-mode/index.html | 6 +-
blog/seata-grpc-client/index.html | 76 ++
blog/seata-ha-practice/index.html | 6 +-
blog/seata-meetup-hangzhou/index.html | 6 +-
blog/seata-mybatisplus-analysis/index.html | 6 +-
blog/seata-nacos-analysis/index.html | 6 +-
blog/seata-nacos-docker/index.html | 6 +-
blog/seata-namingserver/index.html | 8 +-
blog/seata-observable-practice/index.html | 6 +-
blog/seata-quick-start/index.html | 6 +-
blog/seata-raft-config-center/index.html | 8 +-
blog/seata-raft-detailed-explanation/index.html | 6 +-
blog/seata-rpc-multi-protocol01/index.html | 6 +-
blog/seata-rpc-multi-protocol02/index.html | 6 +-
blog/seata-rpc-refactor/index.html | 6 +-
blog/seata-snowflake-explain/index.html | 6 +-
blog/seata-sourcecode-client-bootstrap/index.html | 6 +-
blog/seata-sourcecode-server-bootstrap/index.html | 6 +-
blog/seata-spring-boot-aop-aspectj/index.html | 6 +-
blog/seata-tcc-fence/index.html | 6 +-
blog/seata-tcc/index.html | 6 +-
blog/seata-xa-introduce/index.html | 6 +-
blog/springboot-dubbo-mybatisplus-seata/index.html | 6 +-
blog/tags/index.html | 6 +-
blog/tags/seata/index.html | 6 +-
.../index.html | 6 +-
blog/tcc-mode-design-principle/index.html | 6 +-
build/404.html | 4 +-
...2024121301-4613ead894d7510e65d88296eb86e297.png | Bin 0 -> 365111 bytes
...2024121302-39625f525d6da1bbc7ad4509c94718eb.png | Bin 0 -> 318738 bytes
...2024121303-bad6bb1db830335d72e2037ea7dbf4de.png | Bin 0 -> 419640 bytes
...2024121304-fcc9119043d66143a841d2008ef136f5.png | Bin 0 -> 413464 bytes
...2024121305-327ecb450c5fd7f7fc636165421972b2.png | Bin 0 -> 358454 bytes
...024121306-5568d956a86d67c43e4d76837dd5c8b8.jpeg | Bin 0 -> 92986 bytes
build/assets/js/11ce4159.9318726b.js | 1 +
build/assets/js/1dc3c500.ea283c57.js | 1 +
build/assets/js/2d6322e8.0f290bfd.js | 1 +
build/assets/js/44ac4dbb.8a588fe0.js | 1 +
build/assets/js/52099127.5f140573.js | 1 +
build/assets/js/5c941569.831d6e25.js | 1 +
build/assets/js/7d9726a8.2f524a19.js | 1 +
build/assets/js/814f3328.42bfeb1c.js | 1 +
build/assets/js/8eb4e46b.acb9610d.js | 1 +
build/assets/js/8f32d218.e50ccc03.js | 1 +
build/assets/js/92999a1c.3f3d9d67.js | 1 +
build/assets/js/b2b675dd.8bb91942.js | 1 +
build/assets/js/b2f554cd.9ea9c4f0.js | 1 +
build/assets/js/d1400855.24cc561c.js | 1 +
build/assets/js/ef915a9a.5686e2ca.js | 1 +
build/assets/js/main.aeea7339.js | 2 +
build/assets/js/main.aeea7339.js.LICENSE.txt | 64 +
build/assets/js/runtime~main.762ed5c0.js | 1 +
build/blog/archive/index.html | 6 +-
build/blog/atom.xml | 179 +--
.../index.html | 6 +-
build/blog/explore-seata-journey/index.html | 6 +-
build/blog/how-to-support-spring-cloud/index.html | 6 +-
build/blog/how-to-write-unit-tests/index.html | 6 +-
build/blog/index.html | 114 +-
.../index.html | 6 +-
.../integrate-seata-with-spring-cloud/index.html | 6 +-
build/blog/iscas2023/index.html | 6 +-
build/blog/manual-transaction-mode/index.html | 6 +-
build/blog/page/2/index.html | 179 +--
build/blog/page/3/index.html | 164 ++-
build/blog/page/4/index.html | 142 +--
build/blog/page/5/index.html | 242 ++--
build/blog/page/6/index.html | 247 ++--
build/blog/page/7/index.html | 98 +-
.../index.html | 6 +-
build/blog/rss.xml | 173 +--
build/blog/seata-1.5.2/index.html | 6 +-
build/blog/seata-1.6.0/index.html | 6 +-
.../blog/seata-analysis-UUID-generator/index.html | 6 +-
.../blog/seata-analysis-config-modular/index.html | 6 +-
build/blog/seata-analysis-core-modular/index.html | 8 +-
.../seata-analysis-dubbo-transmit-xid/index.html | 6 +-
build/blog/seata-analysis-go-server/index.html | 6 +-
build/blog/seata-analysis-java-client/index.html | 6 +-
build/blog/seata-analysis-java-server/index.html | 6 +-
build/blog/seata-analysis-simple/index.html | 6 +-
build/blog/seata-analysis-tcc-modular/index.html | 6 +-
build/blog/seata-at-demo-in-mac/index.html | 6 +-
build/blog/seata-at-lock/index.html | 6 +-
build/blog/seata-at-mode-design/index.html | 6 +-
build/blog/seata-at-mode-start-rm-tm/index.html | 6 +-
build/blog/seata-at-mode-start/index.html | 6 +-
build/blog/seata-at-tcc-saga/index.html | 6 +-
.../blog/seata-client-start-analysis-01/index.html | 6 +-
.../blog/seata-client-start-analysis-02/index.html | 6 +-
.../index.html | 6 +-
build/blog/seata-config-center/index.html | 6 +-
build/blog/seata-config-manager/index.html | 6 +-
.../seata-connect-data-and-application/index.html | 6 +-
build/blog/seata-datasource-proxy/index.html | 6 +-
build/blog/seata-dsproxy-deadlock/index.html | 6 +-
.../index.html | 6 +-
.../seata-feature-undo-log-compress/index.html | 6 +-
build/blog/seata-go-1.2.0/index.html | 6 +-
.../seata-golang-communication-mode/index.html | 6 +-
build/blog/seata-grpc-client/index.html | 76 ++
build/blog/seata-ha-practice/index.html | 6 +-
build/blog/seata-meetup-hangzhou/index.html | 6 +-
build/blog/seata-mybatisplus-analysis/index.html | 6 +-
build/blog/seata-nacos-analysis/index.html | 6 +-
build/blog/seata-nacos-docker/index.html | 6 +-
build/blog/seata-namingserver/index.html | 8 +-
build/blog/seata-observable-practice/index.html | 6 +-
build/blog/seata-quick-start/index.html | 6 +-
build/blog/seata-raft-config-center/index.html | 8 +-
.../seata-raft-detailed-explanation/index.html | 6 +-
build/blog/seata-rpc-multi-protocol01/index.html | 6 +-
build/blog/seata-rpc-multi-protocol02/index.html | 6 +-
build/blog/seata-rpc-refactor/index.html | 6 +-
build/blog/seata-snowflake-explain/index.html | 6 +-
.../seata-sourcecode-client-bootstrap/index.html | 6 +-
.../seata-sourcecode-server-bootstrap/index.html | 6 +-
.../blog/seata-spring-boot-aop-aspectj/index.html | 6 +-
build/blog/seata-tcc-fence/index.html | 6 +-
build/blog/seata-tcc/index.html | 6 +-
build/blog/seata-xa-introduce/index.html | 6 +-
.../springboot-dubbo-mybatisplus-seata/index.html | 6 +-
build/blog/tags/index.html | 6 +-
build/blog/tags/seata/index.html | 6 +-
.../index.html | 6 +-
build/blog/tcc-mode-design-principle/index.html | 6 +-
build/community/contactItem/index.html | 4 +-
build/community/contributorItem/index.html | 4 +-
build/community/eventCard/index.html | 4 +-
build/community/index.html | 4 +-
.../docs/dev/domain/overviewDomainModel/index.html | 4 +-
build/docs/dev/domain/rm/index.html | 4 +-
build/docs/dev/domain/tc/index.html | 4 +-
build/docs/dev/domain/tm/index.html | 4 +-
build/docs/dev/mode/at-mode/index.html | 4 +-
build/docs/dev/mode/saga-mode/index.html | 4 +-
build/docs/dev/mode/tcc-mode/index.html | 4 +-
build/docs/dev/mode/xa-mode/index.html | 4 +-
build/docs/dev/seata-mertics/index.html | 4 +-
.../label-an-issue-guide_dev/index.html | 4 +-
.../committer-guide/website-guide_dev/index.html | 4 +-
.../top-contributer_dev/index.html | 4 +-
.../new-contributor-guide_dev/index.html | 4 +-
.../reporting-security-issues_dev/index.html | 4 +-
.../test-coverage-guide_dev/index.html | 4 +-
build/docs/developers/guide_dev/index.html | 4 +-
.../ppmc-guide/release-guide_dev/index.html | 4 +-
.../next/dev/domain/overviewDomainModel/index.html | 4 +-
build/docs/next/dev/domain/rm/index.html | 4 +-
build/docs/next/dev/domain/tc/index.html | 4 +-
build/docs/next/dev/domain/tm/index.html | 4 +-
build/docs/next/dev/mode/at-mode/index.html | 4 +-
build/docs/next/dev/mode/saga-mode/index.html | 4 +-
build/docs/next/dev/mode/tcc-mode/index.html | 4 +-
build/docs/next/dev/mode/xa-mode/index.html | 4 +-
build/docs/next/dev/seata-mertics/index.html | 4 +-
.../label-an-issue-guide_dev/index.html | 4 +-
.../committer-guide/website-guide_dev/index.html | 4 +-
.../top-contributer_dev/index.html | 4 +-
.../new-contributor-guide_dev/index.html | 4 +-
.../reporting-security-issues_dev/index.html | 4 +-
.../test-coverage-guide_dev/index.html | 4 +-
build/docs/next/developers/guide_dev/index.html | 4 +-
.../ppmc-guide/release-guide_dev/index.html | 4 +-
build/docs/next/ops/config-center/index.html | 4 +-
.../docs/next/ops/deploy-by-docker-142/index.html | 4 +-
.../ops/deploy-by-docker-compose-142/index.html | 4 +-
.../next/ops/deploy-by-docker-compose/index.html | 4 +-
build/docs/next/ops/deploy-by-docker/index.html | 4 +-
build/docs/next/ops/deploy-by-helm/index.html | 4 +-
.../docs/next/ops/deploy-by-kubernetes/index.html | 4 +-
.../docs/next/ops/deploy-guide-beginner/index.html | 4 +-
build/docs/next/ops/deploy-ha/index.html | 4 +-
build/docs/next/ops/deploy-server-raft/index.html | 4 +-
build/docs/next/ops/deploy-server/index.html | 4 +-
.../ops/multi-configuration-isolation/index.html | 4 +-
build/docs/next/ops/upgrade/index.html | 4 +-
build/docs/next/overview/faq/index.html | 4 +-
build/docs/next/overview/history/index.html | 4 +-
build/docs/next/overview/terminology/index.html | 4 +-
build/docs/next/overview/what-is-seata/index.html | 4 +-
build/docs/next/release-notes/index.html | 4 +-
build/docs/next/user/api/index.html | 4 +-
build/docs/next/user/apm/prometheus/index.html | 4 +-
build/docs/next/user/apm/skywalking/index.html | 4 +-
.../appendix/global-transaction-status/index.html | 4 +-
build/docs/next/user/appendix/isolation/index.html | 4 +-
.../docs/next/user/configuration/apollo/index.html | 4 +-
.../docs/next/user/configuration/consul/index.html | 4 +-
.../docs/next/user/configuration/etcd3/index.html | 4 +-
build/docs/next/user/configuration/index.html | 4 +-
.../docs/next/user/configuration/nacos/index.html | 4 +-
.../next/user/configuration/zookeeper/index.html | 4 +-
build/docs/next/user/configurations/index.html | 4 +-
build/docs/next/user/configurations090/index.html | 4 +-
build/docs/next/user/configurations100/index.html | 4 +-
build/docs/next/user/datasource/index.html | 4 +-
build/docs/next/user/microservice/index.html | 4 +-
build/docs/next/user/mode/at/index.html | 4 +-
build/docs/next/user/mode/saga/index.html | 4 +-
build/docs/next/user/mode/tcc/index.html | 4 +-
build/docs/next/user/mode/xa/index.html | 4 +-
build/docs/next/user/ormframework/index.html | 4 +-
build/docs/next/user/performance/index.html | 4 +-
build/docs/next/user/quickstart/index.html | 4 +-
build/docs/next/user/registry/consul/index.html | 4 +-
build/docs/next/user/registry/etcd3/index.html | 4 +-
build/docs/next/user/registry/eureka/index.html | 4 +-
build/docs/next/user/registry/index.html | 4 +-
build/docs/next/user/registry/nacos/index.html | 4 +-
.../next/user/registry/namingserver/index.html | 4 +-
build/docs/next/user/registry/zookeeper/index.html | 4 +-
build/docs/next/user/spring/index.html | 4 +-
build/docs/next/user/sqlreference/dml/index.html | 4 +-
.../next/user/sqlreference/function/index.html | 4 +-
.../user/sqlreference/sql-decoration/index.html | 4 +-
.../user/sqlreference/sql-restrictions/index.html | 4 +-
.../txgroup/transaction-group-and-ha/index.html | 4 +-
.../next/user/txgroup/transaction-group/index.html | 4 +-
build/docs/ops/config-center/index.html | 4 +-
build/docs/ops/deploy-by-docker-142/index.html | 4 +-
.../ops/deploy-by-docker-compose-142/index.html | 4 +-
build/docs/ops/deploy-by-docker-compose/index.html | 4 +-
build/docs/ops/deploy-by-docker/index.html | 4 +-
build/docs/ops/deploy-by-helm/index.html | 4 +-
build/docs/ops/deploy-by-kubernetes/index.html | 4 +-
build/docs/ops/deploy-guide-beginner/index.html | 4 +-
build/docs/ops/deploy-ha/index.html | 4 +-
build/docs/ops/deploy-server-raft/index.html | 4 +-
build/docs/ops/deploy-server/index.html | 4 +-
.../ops/multi-configuration-isolation/index.html | 4 +-
build/docs/ops/upgrade/index.html | 4 +-
build/docs/ops/version-maintain-plan/index.html | 4 +-
build/docs/overview/faq/index.html | 4 +-
build/docs/overview/history/index.html | 4 +-
build/docs/overview/terminology/index.html | 4 +-
build/docs/overview/what-is-seata/index.html | 4 +-
build/docs/release-notes/index.html | 4 +-
build/docs/user/api/index.html | 4 +-
build/docs/user/apm/prometheus/index.html | 4 +-
build/docs/user/apm/skywalking/index.html | 4 +-
.../appendix/global-transaction-status/index.html | 4 +-
build/docs/user/appendix/isolation/index.html | 4 +-
build/docs/user/configuration/apollo/index.html | 4 +-
build/docs/user/configuration/consul/index.html | 4 +-
build/docs/user/configuration/etcd3/index.html | 4 +-
build/docs/user/configuration/index.html | 4 +-
build/docs/user/configuration/nacos/index.html | 4 +-
build/docs/user/configuration/zookeeper/index.html | 4 +-
build/docs/user/configurations/index.html | 4 +-
build/docs/user/configurations090/index.html | 4 +-
build/docs/user/configurations100/index.html | 4 +-
build/docs/user/datasource/index.html | 4 +-
build/docs/user/microservice/index.html | 4 +-
build/docs/user/mode/at/index.html | 4 +-
build/docs/user/mode/saga/index.html | 4 +-
build/docs/user/mode/tcc/index.html | 4 +-
build/docs/user/mode/xa/index.html | 4 +-
build/docs/user/ormframework/index.html | 4 +-
build/docs/user/performance/index.html | 4 +-
build/docs/user/quickstart/index.html | 4 +-
build/docs/user/registry/consul/index.html | 4 +-
build/docs/user/registry/etcd3/index.html | 4 +-
build/docs/user/registry/eureka/index.html | 4 +-
build/docs/user/registry/index.html | 4 +-
build/docs/user/registry/nacos/index.html | 4 +-
build/docs/user/registry/namingserver/index.html | 4 +-
build/docs/user/registry/zookeeper/index.html | 4 +-
build/docs/user/spring/index.html | 4 +-
build/docs/user/sqlreference/dml/index.html | 4 +-
build/docs/user/sqlreference/function/index.html | 4 +-
.../user/sqlreference/sql-decoration/index.html | 4 +-
.../user/sqlreference/sql-restrictions/index.html | 4 +-
.../txgroup/transaction-group-and-ha/index.html | 4 +-
.../docs/user/txgroup/transaction-group/index.html | 4 +-
.../v1.0/dev/domain/overviewDomainModel/index.html | 4 +-
build/docs/v1.0/dev/domain/rm/index.html | 4 +-
build/docs/v1.0/dev/domain/tc/index.html | 4 +-
build/docs/v1.0/dev/domain/tm/index.html | 4 +-
build/docs/v1.0/dev/mode/at-mode/index.html | 4 +-
build/docs/v1.0/dev/mode/saga-mode/index.html | 4 +-
build/docs/v1.0/dev/mode/tcc-mode/index.html | 4 +-
build/docs/v1.0/dev/mode/xa-mode/index.html | 4 +-
build/docs/v1.0/dev/seata-mertics/index.html | 4 +-
.../label-an-issue-guide_dev/index.html | 4 +-
.../committer-guide/website-guide_dev/index.html | 4 +-
.../top-contributer_dev/index.html | 4 +-
.../new-contributor-guide_dev/index.html | 4 +-
.../reporting-security-issues_dev/index.html | 4 +-
.../test-coverage-guide_dev/index.html | 4 +-
build/docs/v1.0/developers/guide_dev/index.html | 4 +-
build/docs/v1.0/ops/config-center/index.html | 4 +-
.../docs/v1.0/ops/deploy-by-docker-142/index.html | 4 +-
.../ops/deploy-by-docker-compose-142/index.html | 4 +-
.../v1.0/ops/deploy-by-docker-compose/index.html | 4 +-
build/docs/v1.0/ops/deploy-by-docker/index.html | 4 +-
build/docs/v1.0/ops/deploy-by-helm/index.html | 4 +-
.../docs/v1.0/ops/deploy-by-kubernetes/index.html | 4 +-
.../docs/v1.0/ops/deploy-guide-beginner/index.html | 4 +-
build/docs/v1.0/ops/deploy-ha/index.html | 4 +-
build/docs/v1.0/ops/deploy-server/index.html | 4 +-
.../ops/multi-configuration-isolation/index.html | 4 +-
build/docs/v1.0/ops/upgrade/index.html | 4 +-
build/docs/v1.0/overview/faq/index.html | 4 +-
build/docs/v1.0/overview/terminology/index.html | 4 +-
build/docs/v1.0/overview/what-is-seata/index.html | 4 +-
build/docs/v1.0/release-notes/index.html | 4 +-
build/docs/v1.0/user/api/index.html | 4 +-
build/docs/v1.0/user/apm/prometheus/index.html | 4 +-
build/docs/v1.0/user/apm/skywalking/index.html | 4 +-
.../appendix/global-transaction-status/index.html | 4 +-
build/docs/v1.0/user/appendix/isolation/index.html | 4 +-
.../docs/v1.0/user/configuration/apollo/index.html | 4 +-
.../docs/v1.0/user/configuration/consul/index.html | 4 +-
.../docs/v1.0/user/configuration/etcd3/index.html | 4 +-
build/docs/v1.0/user/configuration/index.html | 4 +-
.../docs/v1.0/user/configuration/nacos/index.html | 4 +-
.../v1.0/user/configuration/zookeeper/index.html | 4 +-
build/docs/v1.0/user/configurations/index.html | 4 +-
build/docs/v1.0/user/configurations090/index.html | 4 +-
build/docs/v1.0/user/configurations100/index.html | 4 +-
build/docs/v1.0/user/datasource/index.html | 4 +-
build/docs/v1.0/user/microservice/index.html | 4 +-
build/docs/v1.0/user/mode/at/index.html | 4 +-
build/docs/v1.0/user/mode/saga/index.html | 4 +-
build/docs/v1.0/user/mode/tcc/index.html | 4 +-
build/docs/v1.0/user/mode/xa/index.html | 4 +-
build/docs/v1.0/user/ormframework/index.html | 4 +-
build/docs/v1.0/user/performance/index.html | 4 +-
build/docs/v1.0/user/quickstart/index.html | 4 +-
build/docs/v1.0/user/registry/consul/index.html | 4 +-
build/docs/v1.0/user/registry/etcd3/index.html | 4 +-
build/docs/v1.0/user/registry/eureka/index.html | 4 +-
build/docs/v1.0/user/registry/index.html | 4 +-
build/docs/v1.0/user/registry/nacos/index.html | 4 +-
build/docs/v1.0/user/registry/zookeeper/index.html | 4 +-
build/docs/v1.0/user/spring/index.html | 4 +-
build/docs/v1.0/user/sqlreference/dml/index.html | 4 +-
.../v1.0/user/sqlreference/function/index.html | 4 +-
.../user/sqlreference/sql-decoration/index.html | 4 +-
.../user/sqlreference/sql-restrictions/index.html | 4 +-
.../txgroup/transaction-group-and-ha/index.html | 4 +-
.../v1.0/user/txgroup/transaction-group/index.html | 4 +-
.../v1.1/dev/domain/overviewDomainModel/index.html | 4 +-
build/docs/v1.1/dev/domain/rm/index.html | 4 +-
build/docs/v1.1/dev/domain/tc/index.html | 4 +-
build/docs/v1.1/dev/domain/tm/index.html | 4 +-
build/docs/v1.1/dev/mode/at-mode/index.html | 4 +-
build/docs/v1.1/dev/mode/saga-mode/index.html | 4 +-
build/docs/v1.1/dev/mode/tcc-mode/index.html | 4 +-
build/docs/v1.1/dev/mode/xa-mode/index.html | 4 +-
build/docs/v1.1/dev/seata-mertics/index.html | 4 +-
.../label-an-issue-guide_dev/index.html | 4 +-
.../committer-guide/website-guide_dev/index.html | 4 +-
.../top-contributer_dev/index.html | 4 +-
.../new-contributor-guide_dev/index.html | 4 +-
.../reporting-security-issues_dev/index.html | 4 +-
.../test-coverage-guide_dev/index.html | 4 +-
build/docs/v1.1/developers/guide_dev/index.html | 4 +-
build/docs/v1.1/ops/config-center/index.html | 4 +-
.../docs/v1.1/ops/deploy-by-docker-142/index.html | 4 +-
.../ops/deploy-by-docker-compose-142/index.html | 4 +-
.../v1.1/ops/deploy-by-docker-compose/index.html | 4 +-
build/docs/v1.1/ops/deploy-by-docker/index.html | 4 +-
build/docs/v1.1/ops/deploy-by-helm/index.html | 4 +-
.../docs/v1.1/ops/deploy-by-kubernetes/index.html | 4 +-
.../docs/v1.1/ops/deploy-guide-beginner/index.html | 4 +-
build/docs/v1.1/ops/deploy-ha/index.html | 4 +-
build/docs/v1.1/ops/deploy-server/index.html | 4 +-
.../ops/multi-configuration-isolation/index.html | 4 +-
build/docs/v1.1/ops/upgrade/index.html | 4 +-
build/docs/v1.1/overview/faq/index.html | 4 +-
build/docs/v1.1/overview/terminology/index.html | 4 +-
build/docs/v1.1/overview/what-is-seata/index.html | 4 +-
build/docs/v1.1/release-notes/index.html | 4 +-
build/docs/v1.1/user/api/index.html | 4 +-
build/docs/v1.1/user/apm/prometheus/index.html | 4 +-
build/docs/v1.1/user/apm/skywalking/index.html | 4 +-
.../appendix/global-transaction-status/index.html | 4 +-
build/docs/v1.1/user/appendix/isolation/index.html | 4 +-
.../docs/v1.1/user/configuration/apollo/index.html | 4 +-
.../docs/v1.1/user/configuration/consul/index.html | 4 +-
.../docs/v1.1/user/configuration/etcd3/index.html | 4 +-
build/docs/v1.1/user/configuration/index.html | 4 +-
.../docs/v1.1/user/configuration/nacos/index.html | 4 +-
.../v1.1/user/configuration/zookeeper/index.html | 4 +-
build/docs/v1.1/user/configurations/index.html | 4 +-
build/docs/v1.1/user/configurations090/index.html | 4 +-
build/docs/v1.1/user/configurations100/index.html | 4 +-
build/docs/v1.1/user/datasource/index.html | 4 +-
build/docs/v1.1/user/microservice/index.html | 4 +-
build/docs/v1.1/user/mode/at/index.html | 4 +-
build/docs/v1.1/user/mode/saga/index.html | 4 +-
build/docs/v1.1/user/mode/tcc/index.html | 4 +-
build/docs/v1.1/user/mode/xa/index.html | 4 +-
build/docs/v1.1/user/ormframework/index.html | 4 +-
build/docs/v1.1/user/performance/index.html | 4 +-
build/docs/v1.1/user/quickstart/index.html | 4 +-
build/docs/v1.1/user/registry/consul/index.html | 4 +-
build/docs/v1.1/user/registry/etcd3/index.html | 4 +-
build/docs/v1.1/user/registry/eureka/index.html | 4 +-
build/docs/v1.1/user/registry/index.html | 4 +-
build/docs/v1.1/user/registry/nacos/index.html | 4 +-
build/docs/v1.1/user/registry/zookeeper/index.html | 4 +-
build/docs/v1.1/user/spring/index.html | 4 +-
build/docs/v1.1/user/sqlreference/dml/index.html | 4 +-
.../v1.1/user/sqlreference/function/index.html | 4 +-
.../user/sqlreference/sql-decoration/index.html | 4 +-
.../user/sqlreference/sql-restrictions/index.html | 4 +-
.../txgroup/transaction-group-and-ha/index.html | 4 +-
.../v1.1/user/txgroup/transaction-group/index.html | 4 +-
.../v1.2/dev/domain/overviewDomainModel/index.html | 4 +-
build/docs/v1.2/dev/domain/rm/index.html | 4 +-
build/docs/v1.2/dev/domain/tc/index.html | 4 +-
build/docs/v1.2/dev/domain/tm/index.html | 4 +-
build/docs/v1.2/dev/mode/at-mode/index.html | 4 +-
build/docs/v1.2/dev/mode/saga-mode/index.html | 4 +-
build/docs/v1.2/dev/mode/tcc-mode/index.html | 4 +-
build/docs/v1.2/dev/mode/xa-mode/index.html | 4 +-
build/docs/v1.2/dev/seata-mertics/index.html | 4 +-
.../label-an-issue-guide_dev/index.html | 4 +-
.../committer-guide/website-guide_dev/index.html | 4 +-
.../top-contributer_dev/index.html | 4 +-
.../new-contributor-guide_dev/index.html | 4 +-
.../reporting-security-issues_dev/index.html | 4 +-
.../test-coverage-guide_dev/index.html | 4 +-
build/docs/v1.2/developers/guide_dev/index.html | 4 +-
build/docs/v1.2/ops/config-center/index.html | 4 +-
.../docs/v1.2/ops/deploy-by-docker-142/index.html | 4 +-
.../ops/deploy-by-docker-compose-142/index.html | 4 +-
.../v1.2/ops/deploy-by-docker-compose/index.html | 4 +-
build/docs/v1.2/ops/deploy-by-docker/index.html | 4 +-
build/docs/v1.2/ops/deploy-by-helm/index.html | 4 +-
.../docs/v1.2/ops/deploy-by-kubernetes/index.html | 4 +-
.../docs/v1.2/ops/deploy-guide-beginner/index.html | 4 +-
build/docs/v1.2/ops/deploy-ha/index.html | 4 +-
build/docs/v1.2/ops/deploy-server/index.html | 4 +-
.../ops/multi-configuration-isolation/index.html | 4 +-
build/docs/v1.2/ops/upgrade/index.html | 4 +-
build/docs/v1.2/overview/faq/index.html | 4 +-
build/docs/v1.2/overview/terminology/index.html | 4 +-
build/docs/v1.2/overview/what-is-seata/index.html | 4 +-
build/docs/v1.2/release-notes/index.html | 4 +-
build/docs/v1.2/user/api/index.html | 4 +-
build/docs/v1.2/user/apm/prometheus/index.html | 4 +-
build/docs/v1.2/user/apm/skywalking/index.html | 4 +-
.../appendix/global-transaction-status/index.html | 4 +-
build/docs/v1.2/user/appendix/isolation/index.html | 4 +-
.../docs/v1.2/user/configuration/apollo/index.html | 4 +-
.../docs/v1.2/user/configuration/consul/index.html | 4 +-
.../docs/v1.2/user/configuration/etcd3/index.html | 4 +-
build/docs/v1.2/user/configuration/index.html | 4 +-
.../docs/v1.2/user/configuration/nacos/index.html | 4 +-
.../v1.2/user/configuration/zookeeper/index.html | 4 +-
build/docs/v1.2/user/configurations/index.html | 4 +-
build/docs/v1.2/user/configurations090/index.html | 4 +-
build/docs/v1.2/user/configurations100/index.html | 4 +-
build/docs/v1.2/user/datasource/index.html | 4 +-
build/docs/v1.2/user/microservice/index.html | 4 +-
build/docs/v1.2/user/mode/at/index.html | 4 +-
build/docs/v1.2/user/mode/saga/index.html | 4 +-
build/docs/v1.2/user/mode/tcc/index.html | 4 +-
build/docs/v1.2/user/mode/xa/index.html | 4 +-
build/docs/v1.2/user/ormframework/index.html | 4 +-
build/docs/v1.2/user/performance/index.html | 4 +-
build/docs/v1.2/user/quickstart/index.html | 4 +-
build/docs/v1.2/user/registry/consul/index.html | 4 +-
build/docs/v1.2/user/registry/etcd3/index.html | 4 +-
build/docs/v1.2/user/registry/eureka/index.html | 4 +-
build/docs/v1.2/user/registry/index.html | 4 +-
build/docs/v1.2/user/registry/nacos/index.html | 4 +-
build/docs/v1.2/user/registry/zookeeper/index.html | 4 +-
build/docs/v1.2/user/spring/index.html | 4 +-
build/docs/v1.2/user/sqlreference/dml/index.html | 4 +-
.../v1.2/user/sqlreference/function/index.html | 4 +-
.../user/sqlreference/sql-decoration/index.html | 4 +-
.../user/sqlreference/sql-restrictions/index.html | 4 +-
.../txgroup/transaction-group-and-ha/index.html | 4 +-
.../v1.2/user/txgroup/transaction-group/index.html | 4 +-
.../v1.3/dev/domain/overviewDomainModel/index.html | 4 +-
build/docs/v1.3/dev/domain/rm/index.html | 4 +-
build/docs/v1.3/dev/domain/tc/index.html | 4 +-
build/docs/v1.3/dev/domain/tm/index.html | 4 +-
build/docs/v1.3/dev/mode/at-mode/index.html | 4 +-
build/docs/v1.3/dev/mode/saga-mode/index.html | 4 +-
build/docs/v1.3/dev/mode/tcc-mode/index.html | 4 +-
build/docs/v1.3/dev/mode/xa-mode/index.html | 4 +-
build/docs/v1.3/dev/seata-mertics/index.html | 4 +-
.../label-an-issue-guide_dev/index.html | 4 +-
.../committer-guide/website-guide_dev/index.html | 4 +-
.../top-contributer_dev/index.html | 4 +-
.../new-contributor-guide_dev/index.html | 4 +-
.../reporting-security-issues_dev/index.html | 4 +-
.../test-coverage-guide_dev/index.html | 4 +-
build/docs/v1.3/developers/guide_dev/index.html | 4 +-
build/docs/v1.3/ops/config-center/index.html | 4 +-
.../docs/v1.3/ops/deploy-by-docker-142/index.html | 4 +-
.../ops/deploy-by-docker-compose-142/index.html | 4 +-
.../v1.3/ops/deploy-by-docker-compose/index.html | 4 +-
build/docs/v1.3/ops/deploy-by-docker/index.html | 4 +-
build/docs/v1.3/ops/deploy-by-helm/index.html | 4 +-
.../docs/v1.3/ops/deploy-by-kubernetes/index.html | 4 +-
.../docs/v1.3/ops/deploy-guide-beginner/index.html | 4 +-
build/docs/v1.3/ops/deploy-ha/index.html | 4 +-
build/docs/v1.3/ops/deploy-server/index.html | 4 +-
.../ops/multi-configuration-isolation/index.html | 4 +-
build/docs/v1.3/ops/upgrade/index.html | 4 +-
build/docs/v1.3/overview/faq/index.html | 4 +-
build/docs/v1.3/overview/terminology/index.html | 4 +-
build/docs/v1.3/overview/what-is-seata/index.html | 4 +-
build/docs/v1.3/release-notes/index.html | 4 +-
build/docs/v1.3/user/api/index.html | 4 +-
build/docs/v1.3/user/apm/prometheus/index.html | 4 +-
build/docs/v1.3/user/apm/skywalking/index.html | 4 +-
.../appendix/global-transaction-status/index.html | 4 +-
build/docs/v1.3/user/appendix/isolation/index.html | 4 +-
.../docs/v1.3/user/configuration/apollo/index.html | 4 +-
.../docs/v1.3/user/configuration/consul/index.html | 4 +-
.../docs/v1.3/user/configuration/etcd3/index.html | 4 +-
build/docs/v1.3/user/configuration/index.html | 4 +-
.../docs/v1.3/user/configuration/nacos/index.html | 4 +-
.../v1.3/user/configuration/zookeeper/index.html | 4 +-
build/docs/v1.3/user/configurations/index.html | 4 +-
build/docs/v1.3/user/configurations090/index.html | 4 +-
build/docs/v1.3/user/configurations100/index.html | 4 +-
build/docs/v1.3/user/datasource/index.html | 4 +-
build/docs/v1.3/user/microservice/index.html | 4 +-
build/docs/v1.3/user/mode/at/index.html | 4 +-
build/docs/v1.3/user/mode/saga/index.html | 4 +-
build/docs/v1.3/user/mode/tcc/index.html | 4 +-
build/docs/v1.3/user/mode/xa/index.html | 4 +-
build/docs/v1.3/user/ormframework/index.html | 4 +-
build/docs/v1.3/user/performance/index.html | 4 +-
build/docs/v1.3/user/quickstart/index.html | 4 +-
build/docs/v1.3/user/registry/consul/index.html | 4 +-
build/docs/v1.3/user/registry/etcd3/index.html | 4 +-
build/docs/v1.3/user/registry/eureka/index.html | 4 +-
build/docs/v1.3/user/registry/index.html | 4 +-
build/docs/v1.3/user/registry/nacos/index.html | 4 +-
build/docs/v1.3/user/registry/zookeeper/index.html | 4 +-
build/docs/v1.3/user/spring/index.html | 4 +-
build/docs/v1.3/user/sqlreference/dml/index.html | 4 +-
.../v1.3/user/sqlreference/function/index.html | 4 +-
.../user/sqlreference/sql-decoration/index.html | 4 +-
.../user/sqlreference/sql-restrictions/index.html | 4 +-
.../txgroup/transaction-group-and-ha/index.html | 4 +-
.../v1.3/user/txgroup/transaction-group/index.html | 4 +-
.../v1.4/dev/domain/overviewDomainModel/index.html | 4 +-
build/docs/v1.4/dev/domain/rm/index.html | 4 +-
build/docs/v1.4/dev/domain/tc/index.html | 4 +-
build/docs/v1.4/dev/domain/tm/index.html | 4 +-
build/docs/v1.4/dev/mode/at-mode/index.html | 4 +-
build/docs/v1.4/dev/mode/saga-mode/index.html | 4 +-
build/docs/v1.4/dev/mode/tcc-mode/index.html | 4 +-
build/docs/v1.4/dev/mode/xa-mode/index.html | 4 +-
build/docs/v1.4/dev/seata-mertics/index.html | 4 +-
.../label-an-issue-guide_dev/index.html | 4 +-
.../committer-guide/website-guide_dev/index.html | 4 +-
.../top-contributer_dev/index.html | 4 +-
.../new-contributor-guide_dev/index.html | 4 +-
.../reporting-security-issues_dev/index.html | 4 +-
.../test-coverage-guide_dev/index.html | 4 +-
build/docs/v1.4/developers/guide_dev/index.html | 4 +-
build/docs/v1.4/ops/config-center/index.html | 4 +-
.../docs/v1.4/ops/deploy-by-docker-142/index.html | 4 +-
.../ops/deploy-by-docker-compose-142/index.html | 4 +-
.../v1.4/ops/deploy-by-docker-compose/index.html | 4 +-
build/docs/v1.4/ops/deploy-by-docker/index.html | 4 +-
build/docs/v1.4/ops/deploy-by-helm/index.html | 4 +-
.../docs/v1.4/ops/deploy-by-kubernetes/index.html | 4 +-
.../docs/v1.4/ops/deploy-guide-beginner/index.html | 4 +-
build/docs/v1.4/ops/deploy-ha/index.html | 4 +-
build/docs/v1.4/ops/deploy-server/index.html | 4 +-
.../ops/multi-configuration-isolation/index.html | 4 +-
build/docs/v1.4/ops/upgrade/index.html | 4 +-
build/docs/v1.4/overview/faq/index.html | 4 +-
build/docs/v1.4/overview/terminology/index.html | 4 +-
build/docs/v1.4/overview/what-is-seata/index.html | 4 +-
build/docs/v1.4/release-notes/index.html | 4 +-
build/docs/v1.4/user/api/index.html | 4 +-
build/docs/v1.4/user/apm/prometheus/index.html | 4 +-
build/docs/v1.4/user/apm/skywalking/index.html | 4 +-
.../appendix/global-transaction-status/index.html | 4 +-
build/docs/v1.4/user/appendix/isolation/index.html | 4 +-
.../docs/v1.4/user/configuration/apollo/index.html | 4 +-
.../docs/v1.4/user/configuration/consul/index.html | 4 +-
.../docs/v1.4/user/configuration/etcd3/index.html | 4 +-
build/docs/v1.4/user/configuration/index.html | 4 +-
.../docs/v1.4/user/configuration/nacos/index.html | 4 +-
.../v1.4/user/configuration/zookeeper/index.html | 4 +-
build/docs/v1.4/user/configurations/index.html | 4 +-
build/docs/v1.4/user/configurations090/index.html | 4 +-
build/docs/v1.4/user/configurations100/index.html | 4 +-
build/docs/v1.4/user/datasource/index.html | 4 +-
build/docs/v1.4/user/microservice/index.html | 4 +-
build/docs/v1.4/user/mode/at/index.html | 4 +-
build/docs/v1.4/user/mode/saga/index.html | 4 +-
build/docs/v1.4/user/mode/tcc/index.html | 4 +-
build/docs/v1.4/user/mode/xa/index.html | 4 +-
build/docs/v1.4/user/ormframework/index.html | 4 +-
build/docs/v1.4/user/performance/index.html | 4 +-
build/docs/v1.4/user/quickstart/index.html | 4 +-
build/docs/v1.4/user/registry/consul/index.html | 4 +-
build/docs/v1.4/user/registry/etcd3/index.html | 4 +-
build/docs/v1.4/user/registry/eureka/index.html | 4 +-
build/docs/v1.4/user/registry/index.html | 4 +-
build/docs/v1.4/user/registry/nacos/index.html | 4 +-
build/docs/v1.4/user/registry/zookeeper/index.html | 4 +-
build/docs/v1.4/user/spring/index.html | 4 +-
build/docs/v1.4/user/sqlreference/dml/index.html | 4 +-
.../v1.4/user/sqlreference/function/index.html | 4 +-
.../user/sqlreference/sql-decoration/index.html | 4 +-
.../user/sqlreference/sql-restrictions/index.html | 4 +-
.../txgroup/transaction-group-and-ha/index.html | 4 +-
.../v1.4/user/txgroup/transaction-group/index.html | 4 +-
.../v1.5/dev/domain/overviewDomainModel/index.html | 4 +-
build/docs/v1.5/dev/domain/rm/index.html | 4 +-
build/docs/v1.5/dev/domain/tc/index.html | 4 +-
build/docs/v1.5/dev/domain/tm/index.html | 4 +-
build/docs/v1.5/dev/mode/at-mode/index.html | 4 +-
build/docs/v1.5/dev/mode/saga-mode/index.html | 4 +-
build/docs/v1.5/dev/mode/tcc-mode/index.html | 4 +-
build/docs/v1.5/dev/mode/xa-mode/index.html | 4 +-
build/docs/v1.5/dev/seata-mertics/index.html | 4 +-
.../label-an-issue-guide_dev/index.html | 4 +-
.../committer-guide/website-guide_dev/index.html | 4 +-
.../top-contributer_dev/index.html | 4 +-
.../new-contributor-guide_dev/index.html | 4 +-
.../reporting-security-issues_dev/index.html | 4 +-
.../test-coverage-guide_dev/index.html | 4 +-
build/docs/v1.5/developers/guide_dev/index.html | 4 +-
build/docs/v1.5/ops/config-center/index.html | 4 +-
.../docs/v1.5/ops/deploy-by-docker-142/index.html | 4 +-
.../ops/deploy-by-docker-compose-142/index.html | 4 +-
.../v1.5/ops/deploy-by-docker-compose/index.html | 4 +-
build/docs/v1.5/ops/deploy-by-docker/index.html | 4 +-
build/docs/v1.5/ops/deploy-by-helm/index.html | 4 +-
.../docs/v1.5/ops/deploy-by-kubernetes/index.html | 4 +-
.../docs/v1.5/ops/deploy-guide-beginner/index.html | 4 +-
build/docs/v1.5/ops/deploy-ha/index.html | 4 +-
build/docs/v1.5/ops/deploy-server/index.html | 4 +-
.../ops/multi-configuration-isolation/index.html | 4 +-
build/docs/v1.5/ops/upgrade/index.html | 4 +-
build/docs/v1.5/overview/faq/index.html | 4 +-
build/docs/v1.5/overview/terminology/index.html | 4 +-
build/docs/v1.5/overview/what-is-seata/index.html | 4 +-
build/docs/v1.5/release-notes/index.html | 4 +-
build/docs/v1.5/user/api/index.html | 4 +-
build/docs/v1.5/user/apm/prometheus/index.html | 4 +-
build/docs/v1.5/user/apm/skywalking/index.html | 4 +-
.../appendix/global-transaction-status/index.html | 4 +-
build/docs/v1.5/user/appendix/isolation/index.html | 4 +-
.../docs/v1.5/user/configuration/apollo/index.html | 4 +-
.../docs/v1.5/user/configuration/consul/index.html | 4 +-
.../docs/v1.5/user/configuration/etcd3/index.html | 4 +-
build/docs/v1.5/user/configuration/index.html | 4 +-
.../docs/v1.5/user/configuration/nacos/index.html | 4 +-
.../v1.5/user/configuration/zookeeper/index.html | 4 +-
build/docs/v1.5/user/configurations/index.html | 4 +-
build/docs/v1.5/user/configurations090/index.html | 4 +-
build/docs/v1.5/user/configurations100/index.html | 4 +-
build/docs/v1.5/user/datasource/index.html | 4 +-
build/docs/v1.5/user/microservice/index.html | 4 +-
build/docs/v1.5/user/mode/at/index.html | 4 +-
build/docs/v1.5/user/mode/saga/index.html | 4 +-
build/docs/v1.5/user/mode/tcc/index.html | 4 +-
build/docs/v1.5/user/mode/xa/index.html | 4 +-
build/docs/v1.5/user/ormframework/index.html | 4 +-
build/docs/v1.5/user/performance/index.html | 4 +-
build/docs/v1.5/user/quickstart/index.html | 4 +-
build/docs/v1.5/user/registry/consul/index.html | 4 +-
build/docs/v1.5/user/registry/etcd3/index.html | 4 +-
build/docs/v1.5/user/registry/eureka/index.html | 4 +-
build/docs/v1.5/user/registry/index.html | 4 +-
build/docs/v1.5/user/registry/nacos/index.html | 4 +-
build/docs/v1.5/user/registry/zookeeper/index.html | 4 +-
build/docs/v1.5/user/spring/index.html | 4 +-
build/docs/v1.5/user/sqlreference/dml/index.html | 4 +-
.../v1.5/user/sqlreference/function/index.html | 4 +-
.../user/sqlreference/sql-decoration/index.html | 4 +-
.../user/sqlreference/sql-restrictions/index.html | 4 +-
.../txgroup/transaction-group-and-ha/index.html | 4 +-
.../v1.5/user/txgroup/transaction-group/index.html | 4 +-
.../v1.6/dev/domain/overviewDomainModel/index.html | 4 +-
build/docs/v1.6/dev/domain/rm/index.html | 4 +-
build/docs/v1.6/dev/domain/tc/index.html | 4 +-
build/docs/v1.6/dev/domain/tm/index.html | 4 +-
build/docs/v1.6/dev/mode/at-mode/index.html | 4 +-
build/docs/v1.6/dev/mode/saga-mode/index.html | 4 +-
build/docs/v1.6/dev/mode/tcc-mode/index.html | 4 +-
build/docs/v1.6/dev/mode/xa-mode/index.html | 4 +-
build/docs/v1.6/dev/seata-mertics/index.html | 4 +-
.../label-an-issue-guide_dev/index.html | 4 +-
.../committer-guide/website-guide_dev/index.html | 4 +-
.../top-contributer_dev/index.html | 4 +-
.../new-contributor-guide_dev/index.html | 4 +-
.../reporting-security-issues_dev/index.html | 4 +-
.../test-coverage-guide_dev/index.html | 4 +-
build/docs/v1.6/developers/guide_dev/index.html | 4 +-
build/docs/v1.6/ops/config-center/index.html | 4 +-
.../docs/v1.6/ops/deploy-by-docker-142/index.html | 4 +-
.../ops/deploy-by-docker-compose-142/index.html | 4 +-
.../v1.6/ops/deploy-by-docker-compose/index.html | 4 +-
build/docs/v1.6/ops/deploy-by-docker/index.html | 4 +-
build/docs/v1.6/ops/deploy-by-helm/index.html | 4 +-
.../docs/v1.6/ops/deploy-by-kubernetes/index.html | 4 +-
.../docs/v1.6/ops/deploy-guide-beginner/index.html | 4 +-
build/docs/v1.6/ops/deploy-ha/index.html | 4 +-
build/docs/v1.6/ops/deploy-server/index.html | 4 +-
.../ops/multi-configuration-isolation/index.html | 4 +-
build/docs/v1.6/ops/upgrade/index.html | 4 +-
build/docs/v1.6/overview/faq/index.html | 4 +-
build/docs/v1.6/overview/terminology/index.html | 4 +-
build/docs/v1.6/overview/what-is-seata/index.html | 4 +-
build/docs/v1.6/release-notes/index.html | 4 +-
build/docs/v1.6/user/api/index.html | 4 +-
build/docs/v1.6/user/apm/prometheus/index.html | 4 +-
build/docs/v1.6/user/apm/skywalking/index.html | 4 +-
.../appendix/global-transaction-status/index.html | 4 +-
build/docs/v1.6/user/appendix/isolation/index.html | 4 +-
.../docs/v1.6/user/configuration/apollo/index.html | 4 +-
.../docs/v1.6/user/configuration/consul/index.html | 4 +-
.../docs/v1.6/user/configuration/etcd3/index.html | 4 +-
build/docs/v1.6/user/configuration/index.html | 4 +-
.../docs/v1.6/user/configuration/nacos/index.html | 4 +-
.../v1.6/user/configuration/zookeeper/index.html | 4 +-
build/docs/v1.6/user/configurations/index.html | 4 +-
build/docs/v1.6/user/configurations090/index.html | 4 +-
build/docs/v1.6/user/configurations100/index.html | 4 +-
build/docs/v1.6/user/datasource/index.html | 4 +-
build/docs/v1.6/user/microservice/index.html | 4 +-
build/docs/v1.6/user/mode/at/index.html | 4 +-
build/docs/v1.6/user/mode/saga/index.html | 4 +-
build/docs/v1.6/user/mode/tcc/index.html | 4 +-
build/docs/v1.6/user/mode/xa/index.html | 4 +-
build/docs/v1.6/user/ormframework/index.html | 4 +-
build/docs/v1.6/user/performance/index.html | 4 +-
build/docs/v1.6/user/quickstart/index.html | 4 +-
build/docs/v1.6/user/registry/consul/index.html | 4 +-
build/docs/v1.6/user/registry/etcd3/index.html | 4 +-
build/docs/v1.6/user/registry/eureka/index.html | 4 +-
build/docs/v1.6/user/registry/index.html | 4 +-
build/docs/v1.6/user/registry/nacos/index.html | 4 +-
build/docs/v1.6/user/registry/zookeeper/index.html | 4 +-
build/docs/v1.6/user/spring/index.html | 4 +-
build/docs/v1.6/user/sqlreference/dml/index.html | 4 +-
.../v1.6/user/sqlreference/function/index.html | 4 +-
.../user/sqlreference/sql-decoration/index.html | 4 +-
.../user/sqlreference/sql-restrictions/index.html | 4 +-
.../txgroup/transaction-group-and-ha/index.html | 4 +-
.../v1.6/user/txgroup/transaction-group/index.html | 4 +-
.../v1.7/dev/domain/overviewDomainModel/index.html | 4 +-
build/docs/v1.7/dev/domain/rm/index.html | 4 +-
build/docs/v1.7/dev/domain/tc/index.html | 4 +-
build/docs/v1.7/dev/domain/tm/index.html | 4 +-
build/docs/v1.7/dev/mode/at-mode/index.html | 4 +-
build/docs/v1.7/dev/mode/saga-mode/index.html | 4 +-
build/docs/v1.7/dev/mode/tcc-mode/index.html | 4 +-
build/docs/v1.7/dev/mode/xa-mode/index.html | 4 +-
build/docs/v1.7/dev/seata-mertics/index.html | 4 +-
.../label-an-issue-guide_dev/index.html | 4 +-
.../committer-guide/website-guide_dev/index.html | 4 +-
.../top-contributer_dev/index.html | 4 +-
.../new-contributor-guide_dev/index.html | 4 +-
.../reporting-security-issues_dev/index.html | 4 +-
.../test-coverage-guide_dev/index.html | 4 +-
build/docs/v1.7/developers/guide_dev/index.html | 4 +-
build/docs/v1.7/ops/config-center/index.html | 4 +-
.../docs/v1.7/ops/deploy-by-docker-142/index.html | 4 +-
.../ops/deploy-by-docker-compose-142/index.html | 4 +-
.../v1.7/ops/deploy-by-docker-compose/index.html | 4 +-
build/docs/v1.7/ops/deploy-by-docker/index.html | 4 +-
build/docs/v1.7/ops/deploy-by-helm/index.html | 4 +-
.../docs/v1.7/ops/deploy-by-kubernetes/index.html | 4 +-
.../docs/v1.7/ops/deploy-guide-beginner/index.html | 4 +-
build/docs/v1.7/ops/deploy-ha/index.html | 4 +-
build/docs/v1.7/ops/deploy-server/index.html | 4 +-
.../ops/multi-configuration-isolation/index.html | 4 +-
build/docs/v1.7/ops/upgrade/index.html | 4 +-
build/docs/v1.7/overview/faq/index.html | 4 +-
build/docs/v1.7/overview/terminology/index.html | 4 +-
build/docs/v1.7/overview/what-is-seata/index.html | 4 +-
build/docs/v1.7/release-notes/index.html | 4 +-
build/docs/v1.7/user/api/index.html | 4 +-
build/docs/v1.7/user/apm/prometheus/index.html | 4 +-
build/docs/v1.7/user/apm/skywalking/index.html | 4 +-
.../appendix/global-transaction-status/index.html | 4 +-
build/docs/v1.7/user/appendix/isolation/index.html | 4 +-
.../docs/v1.7/user/configuration/apollo/index.html | 4 +-
.../docs/v1.7/user/configuration/consul/index.html | 4 +-
.../docs/v1.7/user/configuration/etcd3/index.html | 4 +-
build/docs/v1.7/user/configuration/index.html | 4 +-
.../docs/v1.7/user/configuration/nacos/index.html | 4 +-
.../v1.7/user/configuration/zookeeper/index.html | 4 +-
build/docs/v1.7/user/configurations/index.html | 4 +-
build/docs/v1.7/user/configurations090/index.html | 4 +-
build/docs/v1.7/user/configurations100/index.html | 4 +-
build/docs/v1.7/user/datasource/index.html | 4 +-
build/docs/v1.7/user/microservice/index.html | 4 +-
build/docs/v1.7/user/mode/at/index.html | 4 +-
build/docs/v1.7/user/mode/saga/index.html | 4 +-
build/docs/v1.7/user/mode/tcc/index.html | 4 +-
build/docs/v1.7/user/mode/xa/index.html | 4 +-
build/docs/v1.7/user/ormframework/index.html | 4 +-
build/docs/v1.7/user/performance/index.html | 4 +-
build/docs/v1.7/user/quickstart/index.html | 4 +-
build/docs/v1.7/user/registry/consul/index.html | 4 +-
build/docs/v1.7/user/registry/etcd3/index.html | 4 +-
build/docs/v1.7/user/registry/eureka/index.html | 4 +-
build/docs/v1.7/user/registry/index.html | 4 +-
build/docs/v1.7/user/registry/nacos/index.html | 4 +-
build/docs/v1.7/user/registry/zookeeper/index.html | 4 +-
build/docs/v1.7/user/spring/index.html | 4 +-
build/docs/v1.7/user/sqlreference/dml/index.html | 4 +-
.../v1.7/user/sqlreference/function/index.html | 4 +-
.../user/sqlreference/sql-decoration/index.html | 4 +-
.../user/sqlreference/sql-restrictions/index.html | 4 +-
.../txgroup/transaction-group-and-ha/index.html | 4 +-
.../v1.7/user/txgroup/transaction-group/index.html | 4 +-
.../v1.8/dev/domain/overviewDomainModel/index.html | 4 +-
build/docs/v1.8/dev/domain/rm/index.html | 4 +-
build/docs/v1.8/dev/domain/tc/index.html | 4 +-
build/docs/v1.8/dev/domain/tm/index.html | 4 +-
build/docs/v1.8/dev/mode/at-mode/index.html | 4 +-
build/docs/v1.8/dev/mode/saga-mode/index.html | 4 +-
build/docs/v1.8/dev/mode/tcc-mode/index.html | 4 +-
build/docs/v1.8/dev/mode/xa-mode/index.html | 4 +-
build/docs/v1.8/dev/seata-mertics/index.html | 4 +-
.../label-an-issue-guide_dev/index.html | 4 +-
.../committer-guide/website-guide_dev/index.html | 4 +-
.../top-contributer_dev/index.html | 4 +-
.../new-contributor-guide_dev/index.html | 4 +-
.../reporting-security-issues_dev/index.html | 4 +-
.../test-coverage-guide_dev/index.html | 4 +-
build/docs/v1.8/developers/guide_dev/index.html | 4 +-
build/docs/v1.8/ops/config-center/index.html | 4 +-
.../docs/v1.8/ops/deploy-by-docker-142/index.html | 4 +-
.../ops/deploy-by-docker-compose-142/index.html | 4 +-
.../v1.8/ops/deploy-by-docker-compose/index.html | 4 +-
build/docs/v1.8/ops/deploy-by-docker/index.html | 4 +-
build/docs/v1.8/ops/deploy-by-helm/index.html | 4 +-
.../docs/v1.8/ops/deploy-by-kubernetes/index.html | 4 +-
.../docs/v1.8/ops/deploy-guide-beginner/index.html | 4 +-
build/docs/v1.8/ops/deploy-ha/index.html | 4 +-
build/docs/v1.8/ops/deploy-server/index.html | 4 +-
.../ops/multi-configuration-isolation/index.html | 4 +-
build/docs/v1.8/ops/upgrade/index.html | 4 +-
build/docs/v1.8/overview/faq/index.html | 4 +-
build/docs/v1.8/overview/history/index.html | 4 +-
build/docs/v1.8/overview/terminology/index.html | 4 +-
build/docs/v1.8/overview/what-is-seata/index.html | 4 +-
build/docs/v1.8/release-notes/index.html | 4 +-
build/docs/v1.8/user/api/index.html | 4 +-
build/docs/v1.8/user/apm/prometheus/index.html | 4 +-
build/docs/v1.8/user/apm/skywalking/index.html | 4 +-
.../appendix/global-transaction-status/index.html | 4 +-
build/docs/v1.8/user/appendix/isolation/index.html | 4 +-
.../docs/v1.8/user/configuration/apollo/index.html | 4 +-
.../docs/v1.8/user/configuration/consul/index.html | 4 +-
.../docs/v1.8/user/configuration/etcd3/index.html | 4 +-
build/docs/v1.8/user/configuration/index.html | 4 +-
.../docs/v1.8/user/configuration/nacos/index.html | 4 +-
.../v1.8/user/configuration/zookeeper/index.html | 4 +-
build/docs/v1.8/user/configurations/index.html | 4 +-
build/docs/v1.8/user/configurations090/index.html | 4 +-
build/docs/v1.8/user/configurations100/index.html | 4 +-
build/docs/v1.8/user/datasource/index.html | 4 +-
build/docs/v1.8/user/microservice/index.html | 4 +-
build/docs/v1.8/user/mode/at/index.html | 4 +-
build/docs/v1.8/user/mode/saga/index.html | 4 +-
build/docs/v1.8/user/mode/tcc/index.html | 4 +-
build/docs/v1.8/user/mode/xa/index.html | 4 +-
build/docs/v1.8/user/ormframework/index.html | 4 +-
build/docs/v1.8/user/performance/index.html | 4 +-
build/docs/v1.8/user/quickstart/index.html | 4 +-
build/docs/v1.8/user/registry/consul/index.html | 4 +-
build/docs/v1.8/user/registry/etcd3/index.html | 4 +-
build/docs/v1.8/user/registry/eureka/index.html | 4 +-
build/docs/v1.8/user/registry/index.html | 4 +-
build/docs/v1.8/user/registry/nacos/index.html | 4 +-
build/docs/v1.8/user/registry/zookeeper/index.html | 4 +-
build/docs/v1.8/user/spring/index.html | 4 +-
build/docs/v1.8/user/sqlreference/dml/index.html | 4 +-
.../v1.8/user/sqlreference/function/index.html | 4 +-
.../user/sqlreference/sql-decoration/index.html | 4 +-
.../user/sqlreference/sql-restrictions/index.html | 4 +-
.../txgroup/transaction-group-and-ha/index.html | 4 +-
.../v1.8/user/txgroup/transaction-group/index.html | 4 +-
.../v2.0/dev/domain/overviewDomainModel/index.html | 4 +-
build/docs/v2.0/dev/domain/rm/index.html | 4 +-
build/docs/v2.0/dev/domain/tc/index.html | 4 +-
build/docs/v2.0/dev/domain/tm/index.html | 4 +-
build/docs/v2.0/dev/mode/at-mode/index.html | 4 +-
build/docs/v2.0/dev/mode/saga-mode/index.html | 4 +-
build/docs/v2.0/dev/mode/tcc-mode/index.html | 4 +-
build/docs/v2.0/dev/mode/xa-mode/index.html | 4 +-
build/docs/v2.0/dev/seata-mertics/index.html | 4 +-
.../label-an-issue-guide_dev/index.html | 4 +-
.../committer-guide/website-guide_dev/index.html | 4 +-
.../top-contributer_dev/index.html | 4 +-
.../new-contributor-guide_dev/index.html | 4 +-
.../reporting-security-issues_dev/index.html | 4 +-
.../test-coverage-guide_dev/index.html | 4 +-
build/docs/v2.0/developers/guide_dev/index.html | 4 +-
build/docs/v2.0/ops/config-center/index.html | 4 +-
.../docs/v2.0/ops/deploy-by-docker-142/index.html | 4 +-
.../ops/deploy-by-docker-compose-142/index.html | 4 +-
.../v2.0/ops/deploy-by-docker-compose/index.html | 4 +-
build/docs/v2.0/ops/deploy-by-docker/index.html | 4 +-
build/docs/v2.0/ops/deploy-by-helm/index.html | 4 +-
.../docs/v2.0/ops/deploy-by-kubernetes/index.html | 4 +-
.../docs/v2.0/ops/deploy-guide-beginner/index.html | 4 +-
build/docs/v2.0/ops/deploy-ha/index.html | 4 +-
build/docs/v2.0/ops/deploy-server-raft/index.html | 4 +-
build/docs/v2.0/ops/deploy-server/index.html | 4 +-
.../ops/multi-configuration-isolation/index.html | 4 +-
build/docs/v2.0/ops/upgrade/index.html | 4 +-
.../docs/v2.0/ops/version-maintain-plan/index.html | 4 +-
build/docs/v2.0/overview/faq/index.html | 4 +-
build/docs/v2.0/overview/history/index.html | 4 +-
build/docs/v2.0/overview/terminology/index.html | 4 +-
build/docs/v2.0/overview/what-is-seata/index.html | 4 +-
build/docs/v2.0/release-notes/index.html | 4 +-
build/docs/v2.0/user/api/index.html | 4 +-
build/docs/v2.0/user/apm/prometheus/index.html | 4 +-
build/docs/v2.0/user/apm/skywalking/index.html | 4 +-
.../appendix/global-transaction-status/index.html | 4 +-
build/docs/v2.0/user/appendix/isolation/index.html | 4 +-
.../docs/v2.0/user/configuration/apollo/index.html | 4 +-
.../docs/v2.0/user/configuration/consul/index.html | 4 +-
.../docs/v2.0/user/configuration/etcd3/index.html | 4 +-
build/docs/v2.0/user/configuration/index.html | 4 +-
.../docs/v2.0/user/configuration/nacos/index.html | 4 +-
.../v2.0/user/configuration/zookeeper/index.html | 4 +-
build/docs/v2.0/user/configurations/index.html | 4 +-
build/docs/v2.0/user/configurations090/index.html | 4 +-
build/docs/v2.0/user/configurations100/index.html | 4 +-
build/docs/v2.0/user/datasource/index.html | 4 +-
build/docs/v2.0/user/microservice/index.html | 4 +-
build/docs/v2.0/user/mode/at/index.html | 4 +-
build/docs/v2.0/user/mode/saga/index.html | 4 +-
build/docs/v2.0/user/mode/tcc/index.html | 4 +-
build/docs/v2.0/user/mode/xa/index.html | 4 +-
build/docs/v2.0/user/ormframework/index.html | 4 +-
build/docs/v2.0/user/performance/index.html | 4 +-
build/docs/v2.0/user/quickstart/index.html | 4 +-
build/docs/v2.0/user/registry/consul/index.html | 4 +-
build/docs/v2.0/user/registry/etcd3/index.html | 4 +-
build/docs/v2.0/user/registry/eureka/index.html | 4 +-
build/docs/v2.0/user/registry/index.html | 4 +-
build/docs/v2.0/user/registry/nacos/index.html | 4 +-
build/docs/v2.0/user/registry/zookeeper/index.html | 4 +-
build/docs/v2.0/user/spring/index.html | 4 +-
build/docs/v2.0/user/sqlreference/dml/index.html | 4 +-
.../v2.0/user/sqlreference/function/index.html | 4 +-
.../user/sqlreference/sql-decoration/index.html | 4 +-
.../user/sqlreference/sql-restrictions/index.html | 4 +-
.../txgroup/transaction-group-and-ha/index.html | 4 +-
.../v2.0/user/txgroup/transaction-group/index.html | 4 +-
.../v2.1/dev/domain/overviewDomainModel/index.html | 4 +-
build/docs/v2.1/dev/domain/rm/index.html | 4 +-
build/docs/v2.1/dev/domain/tc/index.html | 4 +-
build/docs/v2.1/dev/domain/tm/index.html | 4 +-
build/docs/v2.1/dev/mode/at-mode/index.html | 4 +-
build/docs/v2.1/dev/mode/saga-mode/index.html | 4 +-
build/docs/v2.1/dev/mode/tcc-mode/index.html | 4 +-
build/docs/v2.1/dev/mode/xa-mode/index.html | 4 +-
build/docs/v2.1/dev/seata-mertics/index.html | 4 +-
.../label-an-issue-guide_dev/index.html | 4 +-
.../committer-guide/website-guide_dev/index.html | 4 +-
.../top-contributer_dev/index.html | 4 +-
.../new-contributor-guide_dev/index.html | 4 +-
.../reporting-security-issues_dev/index.html | 4 +-
.../test-coverage-guide_dev/index.html | 4 +-
build/docs/v2.1/developers/guide_dev/index.html | 4 +-
build/docs/v2.1/ops/config-center/index.html | 4 +-
.../docs/v2.1/ops/deploy-by-docker-142/index.html | 4 +-
.../ops/deploy-by-docker-compose-142/index.html | 4 +-
.../v2.1/ops/deploy-by-docker-compose/index.html | 4 +-
build/docs/v2.1/ops/deploy-by-docker/index.html | 4 +-
build/docs/v2.1/ops/deploy-by-helm/index.html | 4 +-
.../docs/v2.1/ops/deploy-by-kubernetes/index.html | 4 +-
.../docs/v2.1/ops/deploy-guide-beginner/index.html | 4 +-
build/docs/v2.1/ops/deploy-ha/index.html | 4 +-
build/docs/v2.1/ops/deploy-server-raft/index.html | 4 +-
build/docs/v2.1/ops/deploy-server/index.html | 4 +-
.../ops/multi-configuration-isolation/index.html | 4 +-
build/docs/v2.1/ops/upgrade/index.html | 4 +-
.../docs/v2.1/ops/version-maintain-plan/index.html | 4 +-
build/docs/v2.1/overview/faq/index.html | 4 +-
build/docs/v2.1/overview/history/index.html | 4 +-
build/docs/v2.1/overview/terminology/index.html | 4 +-
build/docs/v2.1/overview/what-is-seata/index.html | 4 +-
build/docs/v2.1/release-notes/index.html | 4 +-
build/docs/v2.1/user/api/index.html | 4 +-
build/docs/v2.1/user/apm/prometheus/index.html | 4 +-
build/docs/v2.1/user/apm/skywalking/index.html | 4 +-
.../appendix/global-transaction-status/index.html | 4 +-
build/docs/v2.1/user/appendix/isolation/index.html | 4 +-
.../docs/v2.1/user/configuration/apollo/index.html | 4 +-
.../docs/v2.1/user/configuration/consul/index.html | 4 +-
.../docs/v2.1/user/configuration/etcd3/index.html | 4 +-
build/docs/v2.1/user/configuration/index.html | 4 +-
.../docs/v2.1/user/configuration/nacos/index.html | 4 +-
.../v2.1/user/configuration/zookeeper/index.html | 4 +-
build/docs/v2.1/user/configurations/index.html | 4 +-
build/docs/v2.1/user/configurations090/index.html | 4 +-
build/docs/v2.1/user/configurations100/index.html | 4 +-
build/docs/v2.1/user/datasource/index.html | 4 +-
build/docs/v2.1/user/microservice/index.html | 4 +-
build/docs/v2.1/user/mode/at/index.html | 4 +-
build/docs/v2.1/user/mode/saga/index.html | 4 +-
build/docs/v2.1/user/mode/tcc/index.html | 4 +-
build/docs/v2.1/user/mode/xa/index.html | 4 +-
build/docs/v2.1/user/ormframework/index.html | 4 +-
build/docs/v2.1/user/performance/index.html | 4 +-
build/docs/v2.1/user/quickstart/index.html | 4 +-
build/docs/v2.1/user/registry/consul/index.html | 4 +-
build/docs/v2.1/user/registry/etcd3/index.html | 4 +-
build/docs/v2.1/user/registry/eureka/index.html | 4 +-
build/docs/v2.1/user/registry/index.html | 4 +-
build/docs/v2.1/user/registry/nacos/index.html | 4 +-
build/docs/v2.1/user/registry/zookeeper/index.html | 4 +-
build/docs/v2.1/user/spring/index.html | 4 +-
build/docs/v2.1/user/sqlreference/dml/index.html | 4 +-
.../v2.1/user/sqlreference/function/index.html | 4 +-
.../user/sqlreference/sql-decoration/index.html | 4 +-
.../user/sqlreference/sql-restrictions/index.html | 4 +-
.../txgroup/transaction-group-and-ha/index.html | 4 +-
.../v2.1/user/txgroup/transaction-group/index.html | 4 +-
build/home/feature/index.html | 4 +-
build/home/introduction/index.html | 4 +-
build/home/top/index.html | 4 +-
build/img/blog/2024121301.png | Bin 0 -> 365111 bytes
build/img/blog/2024121302.png | Bin 0 -> 318738 bytes
build/img/blog/2024121303.png | Bin 0 -> 419640 bytes
build/img/blog/2024121304.png | Bin 0 -> 413464 bytes
build/img/blog/2024121305.png | Bin 0 -> 358454 bytes
build/img/blog/2024121306.jpeg | Bin 0 -> 92986 bytes
build/index.html | 4 +-
build/markdown-page/index.html | 4 +-
build/search/index.html | 4 +-
build/solution/index.html | 4 +-
build/unversioned/download/seata-server/index.html | 4 +-
.../release-history/seata-server/index.html | 4 +-
build/users/index.html | 4 +-
build/zh-cn/404.html | 4 +-
...2024121301-4613ead894d7510e65d88296eb86e297.png | Bin 0 -> 365111 bytes
...2024121302-39625f525d6da1bbc7ad4509c94718eb.png | Bin 0 -> 318738 bytes
...2024121303-bad6bb1db830335d72e2037ea7dbf4de.png | Bin 0 -> 419640 bytes
...2024121304-fcc9119043d66143a841d2008ef136f5.png | Bin 0 -> 413464 bytes
...2024121305-327ecb450c5fd7f7fc636165421972b2.png | Bin 0 -> 358454 bytes
...024121306-5568d956a86d67c43e4d76837dd5c8b8.jpeg | Bin 0 -> 92986 bytes
build/zh-cn/assets/js/17fbb55d.1a92045c.js | 1 +
build/zh-cn/assets/js/2f917717.865ae696.js | 1 +
build/zh-cn/assets/js/3a67a931.1d939766.js | 1 +
build/zh-cn/assets/js/465ed234.1886ae45.js | 1 +
build/zh-cn/assets/js/6b1d283c.2683ee0f.js | 1 +
build/zh-cn/assets/js/77df707c.d7e3a22f.js | 1 +
build/zh-cn/assets/js/7c04fe45.fb2f7b60.js | 1 +
build/zh-cn/assets/js/814f3328.92b1da4f.js | 1 +
build/zh-cn/assets/js/81cde232.e34a0f99.js | 1 +
build/zh-cn/assets/js/b73dc115.54f0190d.js | 1 +
build/zh-cn/assets/js/b91266d6.8b669b8f.js | 1 +
build/zh-cn/assets/js/d504b8f0.1978e6a2.js | 1 +
build/zh-cn/assets/js/dc05b4b1.d03aca48.js | 1 +
build/zh-cn/assets/js/main.dd5af082.js | 2 +
build/zh-cn/assets/js/main.dd5af082.js.LICENSE.txt | 64 +
build/zh-cn/assets/js/runtime~main.178f39f2.js | 1 +
build/zh-cn/blog/archive/index.html | 6 +-
build/zh-cn/blog/atom.xml | 182 +--
.../index.html | 26 +-
build/zh-cn/blog/explore-seata-journey/index.html | 16 +-
.../blog/how-to-support-spring-cloud/index.html | 16 +-
.../zh-cn/blog/how-to-write-unit-tests/index.html | 14 +-
build/zh-cn/blog/index.html | 167 ++-
.../index.html | 14 +-
.../integrate-seata-with-spring-cloud/index.html | 18 +-
build/zh-cn/blog/iscas2023/index.html | 12 +-
.../zh-cn/blog/manual-transaction-mode/index.html | 6 +-
build/zh-cn/blog/page/2/index.html | 243 ++--
build/zh-cn/blog/page/3/index.html | 240 ++--
build/zh-cn/blog/page/4/index.html | 174 ++-
build/zh-cn/blog/page/5/index.html | 272 ++---
build/zh-cn/blog/page/6/index.html | 321 ++---
build/zh-cn/blog/page/7/index.html | 104 +-
.../index.html | 8 +-
build/zh-cn/blog/rss.xml | 176 +--
build/zh-cn/blog/seata-1.5.2/index.html | 6 +-
build/zh-cn/blog/seata-1.6.0/index.html | 10 +-
.../blog/seata-analysis-UUID-generator/index.html | 16 +-
.../blog/seata-analysis-config-modular/index.html | 10 +-
.../blog/seata-analysis-core-modular/index.html | 14 +-
.../seata-analysis-dubbo-transmit-xid/index.html | 8 +-
.../zh-cn/blog/seata-analysis-go-server/index.html | 12 +-
.../blog/seata-analysis-java-client/index.html | 22 +-
.../blog/seata-analysis-java-server/index.html | 34 +-
build/zh-cn/blog/seata-analysis-simple/index.html | 22 +-
.../blog/seata-analysis-tcc-modular/index.html | 14 +-
build/zh-cn/blog/seata-at-demo-in-mac/index.html | 14 +-
build/zh-cn/blog/seata-at-lock/index.html | 12 +-
build/zh-cn/blog/seata-at-mode-design/index.html | 18 +-
.../blog/seata-at-mode-start-rm-tm/index.html | 10 +-
build/zh-cn/blog/seata-at-mode-start/index.html | 16 +-
build/zh-cn/blog/seata-at-tcc-saga/index.html | 30 +-
.../blog/seata-client-start-analysis-01/index.html | 20 +-
.../blog/seata-client-start-analysis-02/index.html | 18 +-
.../index.html | 6 +-
build/zh-cn/blog/seata-config-center/index.html | 8 +-
build/zh-cn/blog/seata-config-manager/index.html | 12 +-
.../seata-connect-data-and-application/index.html | 24 +-
build/zh-cn/blog/seata-datasource-proxy/index.html | 30 +-
build/zh-cn/blog/seata-dsproxy-deadlock/index.html | 14 +-
.../index.html | 14 +-
.../seata-feature-undo-log-compress/index.html | 16 +-
build/zh-cn/blog/seata-go-1.2.0/index.html | 8 +-
.../seata-golang-communication-mode/index.html | 12 +-
build/zh-cn/blog/seata-grpc-client/index.html | 75 ++
build/zh-cn/blog/seata-ha-practice/index.html | 8 +-
build/zh-cn/blog/seata-meetup-hangzhou/index.html | 10 +-
.../blog/seata-mybatisplus-analysis/index.html | 10 +-
build/zh-cn/blog/seata-nacos-analysis/index.html | 6 +-
build/zh-cn/blog/seata-nacos-docker/index.html | 8 +-
build/zh-cn/blog/seata-namingserver/index.html | 14 +-
.../blog/seata-observable-practice/index.html | 16 +-
build/zh-cn/blog/seata-quick-start/index.html | 16 +-
.../zh-cn/blog/seata-raft-config-center/index.html | 18 +-
.../seata-raft-detailed-explanation/index.html | 24 +-
.../blog/seata-rpc-multi-protocol01/index.html | 12 +-
.../blog/seata-rpc-multi-protocol02/index.html | 12 +-
build/zh-cn/blog/seata-rpc-refactor/index.html | 22 +-
.../zh-cn/blog/seata-snowflake-explain/index.html | 14 +-
.../seata-sourcecode-client-bootstrap/index.html | 6 +-
.../seata-sourcecode-server-bootstrap/index.html | 16 +-
.../blog/seata-spring-boot-aop-aspectj/index.html | 6 +-
build/zh-cn/blog/seata-tcc-fence/index.html | 18 +-
build/zh-cn/blog/seata-tcc/index.html | 24 +-
build/zh-cn/blog/seata-xa-introduce/index.html | 28 +-
.../springboot-dubbo-mybatisplus-seata/index.html | 14 +-
build/zh-cn/blog/tags/index.html | 6 +-
build/zh-cn/blog/tags/seata/index.html | 26 +-
.../index.html | 12 +-
.../blog/tcc-mode-design-principle/index.html | 16 +-
build/zh-cn/community/contactItem/index.html | 4 +-
build/zh-cn/community/contributorItem/index.html | 4 +-
build/zh-cn/community/eventCard/index.html | 4 +-
build/zh-cn/community/index.html | 4 +-
.../docs/dev/domain/overviewDomainModel/index.html | 4 +-
build/zh-cn/docs/dev/domain/rm/index.html | 4 +-
build/zh-cn/docs/dev/domain/tc/index.html | 4 +-
build/zh-cn/docs/dev/domain/tm/index.html | 4 +-
build/zh-cn/docs/dev/mode/at-mode/index.html | 4 +-
build/zh-cn/docs/dev/mode/saga-mode/index.html | 4 +-
build/zh-cn/docs/dev/mode/tcc-mode/index.html | 4 +-
build/zh-cn/docs/dev/mode/xa-mode/index.html | 4 +-
build/zh-cn/docs/dev/seata-mertics/index.html | 4 +-
.../label-an-issue-guide_dev/index.html | 4 +-
.../committer-guide/website-guide_dev/index.html | 4 +-
.../top-contributer_dev/index.html | 4 +-
.../new-contributor-guide_dev/index.html | 4 +-
.../reporting-security-issues_dev/index.html | 4 +-
.../test-coverage-guide_dev/index.html | 4 +-
build/zh-cn/docs/developers/guide_dev/index.html | 4 +-
.../ppmc-guide/release-guide_dev/index.html | 4 +-
.../next/dev/domain/overviewDomainModel/index.html | 4 +-
build/zh-cn/docs/next/dev/domain/rm/index.html | 4 +-
build/zh-cn/docs/next/dev/domain/tc/index.html | 4 +-
build/zh-cn/docs/next/dev/domain/tm/index.html | 4 +-
build/zh-cn/docs/next/dev/mode/at-mode/index.html | 4 +-
.../zh-cn/docs/next/dev/mode/saga-mode/index.html | 4 +-
build/zh-cn/docs/next/dev/mode/tcc-mode/index.html | 4 +-
build/zh-cn/docs/next/dev/mode/xa-mode/index.html | 4 +-
build/zh-cn/docs/next/dev/seata-mertics/index.html | 4 +-
.../label-an-issue-guide_dev/index.html | 4 +-
.../committer-guide/website-guide_dev/index.html | 4 +-
.../top-contributer_dev/index.html | 4 +-
.../new-contributor-guide_dev/index.html | 4 +-
.../reporting-security-issues_dev/index.html | 4 +-
.../test-coverage-guide_dev/index.html | 4 +-
.../docs/next/developers/guide_dev/index.html | 4 +-
.../ppmc-guide/release-guide_dev/index.html | 4 +-
build/zh-cn/docs/next/ops/config-center/index.html | 4 +-
.../docs/next/ops/deploy-by-docker-142/index.html | 4 +-
.../ops/deploy-by-docker-compose-142/index.html | 4 +-
.../next/ops/deploy-by-docker-compose/index.html | 4 +-
.../docs/next/ops/deploy-by-docker/index.html | 4 +-
.../zh-cn/docs/next/ops/deploy-by-helm/index.html | 4 +-
.../docs/next/ops/deploy-by-kubernetes/index.html | 4 +-
.../docs/next/ops/deploy-guide-beginner/index.html | 4 +-
build/zh-cn/docs/next/ops/deploy-ha/index.html | 4 +-
.../docs/next/ops/deploy-server-raft/index.html | 4 +-
build/zh-cn/docs/next/ops/deploy-server/index.html | 4 +-
.../ops/multi-configuration-isolation/index.html | 4 +-
build/zh-cn/docs/next/ops/upgrade/index.html | 4 +-
build/zh-cn/docs/next/overview/faq/index.html | 4 +-
build/zh-cn/docs/next/overview/history/index.html | 4 +-
.../docs/next/overview/terminology/index.html | 4 +-
.../docs/next/overview/what-is-seata/index.html | 4 +-
build/zh-cn/docs/next/release-notes/index.html | 4 +-
build/zh-cn/docs/next/user/api/index.html | 4 +-
.../zh-cn/docs/next/user/apm/prometheus/index.html | 4 +-
.../zh-cn/docs/next/user/apm/skywalking/index.html | 4 +-
.../appendix/global-transaction-status/index.html | 4 +-
.../docs/next/user/appendix/isolation/index.html | 4 +-
.../docs/next/user/configuration/apollo/index.html | 4 +-
.../docs/next/user/configuration/consul/index.html | 4 +-
.../docs/next/user/configuration/etcd3/index.html | 4 +-
.../zh-cn/docs/next/user/configuration/index.html | 4 +-
.../docs/next/user/configuration/nacos/index.html | 4 +-
.../next/user/configuration/zookeeper/index.html | 4 +-
.../zh-cn/docs/next/user/configurations/index.html | 4 +-
.../docs/next/user/configurations090/index.html | 4 +-
.../docs/next/user/configurations100/index.html | 4 +-
build/zh-cn/docs/next/user/datasource/index.html | 4 +-
build/zh-cn/docs/next/user/microservice/index.html | 4 +-
build/zh-cn/docs/next/user/mode/at/index.html | 4 +-
build/zh-cn/docs/next/user/mode/saga/index.html | 4 +-
build/zh-cn/docs/next/user/mode/tcc/index.html | 4 +-
build/zh-cn/docs/next/user/mode/xa/index.html | 4 +-
build/zh-cn/docs/next/user/ormframework/index.html | 4 +-
build/zh-cn/docs/next/user/performance/index.html | 4 +-
build/zh-cn/docs/next/user/quickstart/index.html | 4 +-
.../docs/next/user/registry/consul/index.html | 4 +-
.../zh-cn/docs/next/user/registry/etcd3/index.html | 4 +-
.../docs/next/user/registry/eureka/index.html | 4 +-
build/zh-cn/docs/next/user/registry/index.html | 4 +-
.../zh-cn/docs/next/user/registry/nacos/index.html | 4 +-
.../next/user/registry/namingserver/index.html | 4 +-
.../docs/next/user/registry/zookeeper/index.html | 4 +-
build/zh-cn/docs/next/user/spring/index.html | 4 +-
.../docs/next/user/sqlreference/dml/index.html | 4 +-
.../next/user/sqlreference/function/index.html | 4 +-
.../user/sqlreference/sql-decoration/index.html | 4 +-
.../user/sqlreference/sql-restrictions/index.html | 4 +-
.../txgroup/transaction-group-and-ha/index.html | 4 +-
.../next/user/txgroup/transaction-group/index.html | 4 +-
build/zh-cn/docs/ops/config-center/index.html | 4 +-
.../zh-cn/docs/ops/deploy-by-docker-142/index.html | 4 +-
.../ops/deploy-by-docker-compose-142/index.html | 4 +-
.../docs/ops/deploy-by-docker-compose/index.html | 4 +-
build/zh-cn/docs/ops/deploy-by-docker/index.html | 4 +-
build/zh-cn/docs/ops/deploy-by-helm/index.html | 4 +-
.../zh-cn/docs/ops/deploy-by-kubernetes/index.html | 4 +-
.../docs/ops/deploy-guide-beginner/index.html | 4 +-
build/zh-cn/docs/ops/deploy-ha/index.html | 4 +-
build/zh-cn/docs/ops/deploy-server-raft/index.html | 4 +-
build/zh-cn/docs/ops/deploy-server/index.html | 4 +-
.../ops/multi-configuration-isolation/index.html | 4 +-
build/zh-cn/docs/ops/upgrade/index.html | 4 +-
.../docs/ops/version-maintain-plan/index.html | 4 +-
build/zh-cn/docs/overview/faq/index.html | 4 +-
build/zh-cn/docs/overview/history/index.html | 4 +-
build/zh-cn/docs/overview/terminology/index.html | 4 +-
build/zh-cn/docs/overview/what-is-seata/index.html | 4 +-
build/zh-cn/docs/release-notes/index.html | 4 +-
build/zh-cn/docs/user/api/index.html | 4 +-
build/zh-cn/docs/user/apm/prometheus/index.html | 4 +-
build/zh-cn/docs/user/apm/skywalking/index.html | 4 +-
.../appendix/global-transaction-status/index.html | 4 +-
.../zh-cn/docs/user/appendix/isolation/index.html | 4 +-
.../docs/user/configuration/apollo/index.html | 4 +-
.../docs/user/configuration/consul/index.html | 4 +-
.../zh-cn/docs/user/configuration/etcd3/index.html | 4 +-
build/zh-cn/docs/user/configuration/index.html | 4 +-
.../zh-cn/docs/user/configuration/nacos/index.html | 4 +-
.../docs/user/configuration/zookeeper/index.html | 4 +-
build/zh-cn/docs/user/configurations/index.html | 4 +-
build/zh-cn/docs/user/configurations090/index.html | 4 +-
build/zh-cn/docs/user/configurations100/index.html | 4 +-
build/zh-cn/docs/user/datasource/index.html | 4 +-
build/zh-cn/docs/user/microservice/index.html | 4 +-
build/zh-cn/docs/user/mode/at/index.html | 4 +-
build/zh-cn/docs/user/mode/saga/index.html | 4 +-
build/zh-cn/docs/user/mode/tcc/index.html | 4 +-
build/zh-cn/docs/user/mode/xa/index.html | 4 +-
build/zh-cn/docs/user/ormframework/index.html | 4 +-
build/zh-cn/docs/user/performance/index.html | 4 +-
build/zh-cn/docs/user/quickstart/index.html | 4 +-
build/zh-cn/docs/user/registry/consul/index.html | 4 +-
build/zh-cn/docs/user/registry/etcd3/index.html | 4 +-
build/zh-cn/docs/user/registry/eureka/index.html | 4 +-
build/zh-cn/docs/user/registry/index.html | 4 +-
build/zh-cn/docs/user/registry/nacos/index.html | 4 +-
.../docs/user/registry/namingserver/index.html | 4 +-
.../zh-cn/docs/user/registry/zookeeper/index.html | 4 +-
build/zh-cn/docs/user/spring/index.html | 4 +-
build/zh-cn/docs/user/sqlreference/dml/index.html | 4 +-
.../docs/user/sqlreference/function/index.html | 4 +-
.../user/sqlreference/sql-decoration/index.html | 4 +-
.../user/sqlreference/sql-restrictions/index.html | 4 +-
.../txgroup/transaction-group-and-ha/index.html | 4 +-
.../docs/user/txgroup/transaction-group/index.html | 4 +-
.../v1.0/dev/domain/overviewDomainModel/index.html | 4 +-
build/zh-cn/docs/v1.0/dev/domain/rm/index.html | 4 +-
build/zh-cn/docs/v1.0/dev/domain/tc/index.html | 4 +-
build/zh-cn/docs/v1.0/dev/domain/tm/index.html | 4 +-
build/zh-cn/docs/v1.0/dev/mode/at-mode/index.html | 4 +-
.../zh-cn/docs/v1.0/dev/mode/saga-mode/index.html | 4 +-
build/zh-cn/docs/v1.0/dev/mode/tcc-mode/index.html | 4 +-
build/zh-cn/docs/v1.0/dev/mode/xa-mode/index.html | 4 +-
build/zh-cn/docs/v1.0/dev/seata-mertics/index.html | 4 +-
.../label-an-issue-guide_dev/index.html | 4 +-
.../committer-guide/website-guide_dev/index.html | 4 +-
.../top-contributer_dev/index.html | 4 +-
.../new-contributor-guide_dev/index.html | 4 +-
.../reporting-security-issues_dev/index.html | 4 +-
.../test-coverage-guide_dev/index.html | 4 +-
.../docs/v1.0/developers/guide_dev/index.html | 4 +-
build/zh-cn/docs/v1.0/ops/config-center/index.html | 4 +-
.../docs/v1.0/ops/deploy-by-docker-142/index.html | 4 +-
.../ops/deploy-by-docker-compose-142/index.html | 4 +-
.../v1.0/ops/deploy-by-docker-compose/index.html | 4 +-
.../docs/v1.0/ops/deploy-by-docker/index.html | 4 +-
.../zh-cn/docs/v1.0/ops/deploy-by-helm/index.html | 4 +-
.../docs/v1.0/ops/deploy-by-kubernetes/index.html | 4 +-
.../docs/v1.0/ops/deploy-guide-beginner/index.html | 4 +-
build/zh-cn/docs/v1.0/ops/deploy-ha/index.html | 4 +-
build/zh-cn/docs/v1.0/ops/deploy-server/index.html | 4 +-
.../ops/multi-configuration-isolation/index.html | 4 +-
build/zh-cn/docs/v1.0/ops/upgrade/index.html | 4 +-
build/zh-cn/docs/v1.0/overview/faq/index.html | 4 +-
.../docs/v1.0/overview/terminology/index.html | 4 +-
.../docs/v1.0/overview/what-is-seata/index.html | 4 +-
build/zh-cn/docs/v1.0/release-notes/index.html | 4 +-
build/zh-cn/docs/v1.0/user/api/index.html | 4 +-
.../zh-cn/docs/v1.0/user/apm/prometheus/index.html | 4 +-
.../zh-cn/docs/v1.0/user/apm/skywalking/index.html | 4 +-
.../appendix/global-transaction-status/index.html | 4 +-
.../docs/v1.0/user/appendix/isolation/index.html | 4 +-
.../docs/v1.0/user/configuration/apollo/index.html | 4 +-
.../docs/v1.0/user/configuration/consul/index.html | 4 +-
.../docs/v1.0/user/configuration/etcd3/index.html | 4 +-
.../zh-cn/docs/v1.0/user/configuration/index.html | 4 +-
.../docs/v1.0/user/configuration/nacos/index.html | 4 +-
.../v1.0/user/configuration/zookeeper/index.html | 4 +-
.../zh-cn/docs/v1.0/user/configurations/index.html | 4 +-
.../docs/v1.0/user/configurations090/index.html | 4 +-
.../docs/v1.0/user/configurations100/index.html | 4 +-
build/zh-cn/docs/v1.0/user/datasource/index.html | 4 +-
build/zh-cn/docs/v1.0/user/microservice/index.html | 4 +-
build/zh-cn/docs/v1.0/user/mode/at/index.html | 4 +-
build/zh-cn/docs/v1.0/user/mode/saga/index.html | 4 +-
build/zh-cn/docs/v1.0/user/mode/tcc/index.html | 4 +-
build/zh-cn/docs/v1.0/user/mode/xa/index.html | 4 +-
build/zh-cn/docs/v1.0/user/ormframework/index.html | 4 +-
build/zh-cn/docs/v1.0/user/performance/index.html | 4 +-
build/zh-cn/docs/v1.0/user/quickstart/index.html | 4 +-
.../docs/v1.0/user/registry/consul/index.html | 4 +-
.../zh-cn/docs/v1.0/user/registry/etcd3/index.html | 4 +-
.../docs/v1.0/user/registry/eureka/index.html | 4 +-
build/zh-cn/docs/v1.0/user/registry/index.html | 4 +-
.../zh-cn/docs/v1.0/user/registry/nacos/index.html | 4 +-
.../docs/v1.0/user/registry/zookeeper/index.html | 4 +-
build/zh-cn/docs/v1.0/user/spring/index.html | 4 +-
.../docs/v1.0/user/sqlreference/dml/index.html | 4 +-
.../v1.0/user/sqlreference/function/index.html | 4 +-
.../user/sqlreference/sql-decoration/index.html | 4 +-
.../user/sqlreference/sql-restrictions/index.html | 4 +-
.../txgroup/transaction-group-and-ha/index.html | 4 +-
.../v1.0/user/txgroup/transaction-group/index.html | 4 +-
.../v1.1/dev/domain/overviewDomainModel/index.html | 4 +-
build/zh-cn/docs/v1.1/dev/domain/rm/index.html | 4 +-
build/zh-cn/docs/v1.1/dev/domain/tc/index.html | 4 +-
build/zh-cn/docs/v1.1/dev/domain/tm/index.html | 4 +-
build/zh-cn/docs/v1.1/dev/mode/at-mode/index.html | 4 +-
.../zh-cn/docs/v1.1/dev/mode/saga-mode/index.html | 4 +-
build/zh-cn/docs/v1.1/dev/mode/tcc-mode/index.html | 4 +-
build/zh-cn/docs/v1.1/dev/mode/xa-mode/index.html | 4 +-
build/zh-cn/docs/v1.1/dev/seata-mertics/index.html | 4 +-
.../label-an-issue-guide_dev/index.html | 4 +-
.../committer-guide/website-guide_dev/index.html | 4 +-
.../top-contributer_dev/index.html | 4 +-
.../new-contributor-guide_dev/index.html | 4 +-
.../reporting-security-issues_dev/index.html | 4 +-
.../test-coverage-guide_dev/index.html | 4 +-
.../docs/v1.1/developers/guide_dev/index.html | 4 +-
build/zh-cn/docs/v1.1/ops/config-center/index.html | 4 +-
.../docs/v1.1/ops/deploy-by-docker-142/index.html | 4 +-
.../ops/deploy-by-docker-compose-142/index.html | 4 +-
.../v1.1/ops/deploy-by-docker-compose/index.html | 4 +-
.../docs/v1.1/ops/deploy-by-docker/index.html | 4 +-
.../zh-cn/docs/v1.1/ops/deploy-by-helm/index.html | 4 +-
.../docs/v1.1/ops/deploy-by-kubernetes/index.html | 4 +-
.../docs/v1.1/ops/deploy-guide-beginner/index.html | 4 +-
build/zh-cn/docs/v1.1/ops/deploy-ha/index.html | 4 +-
build/zh-cn/docs/v1.1/ops/deploy-server/index.html | 4 +-
.../ops/multi-configuration-isolation/index.html | 4 +-
build/zh-cn/docs/v1.1/ops/upgrade/index.html | 4 +-
build/zh-cn/docs/v1.1/overview/faq/index.html | 4 +-
.../docs/v1.1/overview/terminology/index.html | 4 +-
.../docs/v1.1/overview/what-is-seata/index.html | 4 +-
build/zh-cn/docs/v1.1/release-notes/index.html | 4 +-
build/zh-cn/docs/v1.1/user/api/index.html | 4 +-
.../zh-cn/docs/v1.1/user/apm/prometheus/index.html | 4 +-
.../zh-cn/docs/v1.1/user/apm/skywalking/index.html | 4 +-
.../appendix/global-transaction-status/index.html | 4 +-
.../docs/v1.1/user/appendix/isolation/index.html | 4 +-
.../docs/v1.1/user/configuration/apollo/index.html | 4 +-
.../docs/v1.1/user/configuration/consul/index.html | 4 +-
.../docs/v1.1/user/configuration/etcd3/index.html | 4 +-
.../zh-cn/docs/v1.1/user/configuration/index.html | 4 +-
.../docs/v1.1/user/configuration/nacos/index.html | 4 +-
.../v1.1/user/configuration/zookeeper/index.html | 4 +-
.../zh-cn/docs/v1.1/user/configurations/index.html | 4 +-
.../docs/v1.1/user/configurations090/index.html | 4 +-
.../docs/v1.1/user/configurations100/index.html | 4 +-
build/zh-cn/docs/v1.1/user/datasource/index.html | 4 +-
build/zh-cn/docs/v1.1/user/microservice/index.html | 4 +-
build/zh-cn/docs/v1.1/user/mode/at/index.html | 4 +-
build/zh-cn/docs/v1.1/user/mode/saga/index.html | 4 +-
build/zh-cn/docs/v1.1/user/mode/tcc/index.html | 4 +-
build/zh-cn/docs/v1.1/user/mode/xa/index.html | 4 +-
build/zh-cn/docs/v1.1/user/ormframework/index.html | 4 +-
build/zh-cn/docs/v1.1/user/performance/index.html | 4 +-
build/zh-cn/docs/v1.1/user/quickstart/index.html | 4 +-
.../docs/v1.1/user/registry/consul/index.html | 4 +-
.../zh-cn/docs/v1.1/user/registry/etcd3/index.html | 4 +-
.../docs/v1.1/user/registry/eureka/index.html | 4 +-
build/zh-cn/docs/v1.1/user/registry/index.html | 4 +-
.../zh-cn/docs/v1.1/user/registry/nacos/index.html | 4 +-
.../docs/v1.1/user/registry/zookeeper/index.html | 4 +-
build/zh-cn/docs/v1.1/user/spring/index.html | 4 +-
.../docs/v1.1/user/sqlreference/dml/index.html | 4 +-
.../v1.1/user/sqlreference/function/index.html | 4 +-
.../user/sqlreference/sql-decoration/index.html | 4 +-
.../user/sqlreference/sql-restrictions/index.html | 4 +-
.../txgroup/transaction-group-and-ha/index.html | 4 +-
.../v1.1/user/txgroup/transaction-group/index.html | 4 +-
.../v1.2/dev/domain/overviewDomainModel/index.html | 4 +-
build/zh-cn/docs/v1.2/dev/domain/rm/index.html | 4 +-
build/zh-cn/docs/v1.2/dev/domain/tc/index.html | 4 +-
build/zh-cn/docs/v1.2/dev/domain/tm/index.html | 4 +-
build/zh-cn/docs/v1.2/dev/mode/at-mode/index.html | 4 +-
.../zh-cn/docs/v1.2/dev/mode/saga-mode/index.html | 4 +-
build/zh-cn/docs/v1.2/dev/mode/tcc-mode/index.html | 4 +-
build/zh-cn/docs/v1.2/dev/mode/xa-mode/index.html | 4 +-
build/zh-cn/docs/v1.2/dev/seata-mertics/index.html | 4 +-
.../label-an-issue-guide_dev/index.html | 4 +-
.../committer-guide/website-guide_dev/index.html | 4 +-
.../top-contributer_dev/index.html | 4 +-
.../new-contributor-guide_dev/index.html | 4 +-
.../reporting-security-issues_dev/index.html | 4 +-
.../test-coverage-guide_dev/index.html | 4 +-
.../docs/v1.2/developers/guide_dev/index.html | 4 +-
build/zh-cn/docs/v1.2/ops/config-center/index.html | 4 +-
.../docs/v1.2/ops/deploy-by-docker-142/index.html | 4 +-
.../ops/deploy-by-docker-compose-142/index.html | 4 +-
.../v1.2/ops/deploy-by-docker-compose/index.html | 4 +-
.../docs/v1.2/ops/deploy-by-docker/index.html | 4 +-
.../zh-cn/docs/v1.2/ops/deploy-by-helm/index.html | 4 +-
.../docs/v1.2/ops/deploy-by-kubernetes/index.html | 4 +-
.../docs/v1.2/ops/deploy-guide-beginner/index.html | 4 +-
build/zh-cn/docs/v1.2/ops/deploy-ha/index.html | 4 +-
build/zh-cn/docs/v1.2/ops/deploy-server/index.html | 4 +-
.../ops/multi-configuration-isolation/index.html | 4 +-
build/zh-cn/docs/v1.2/ops/upgrade/index.html | 4 +-
build/zh-cn/docs/v1.2/overview/faq/index.html | 4 +-
.../docs/v1.2/overview/terminology/index.html | 4 +-
.../docs/v1.2/overview/what-is-seata/index.html | 4 +-
build/zh-cn/docs/v1.2/release-notes/index.html | 4 +-
build/zh-cn/docs/v1.2/user/api/index.html | 4 +-
.../zh-cn/docs/v1.2/user/apm/prometheus/index.html | 4 +-
.../zh-cn/docs/v1.2/user/apm/skywalking/index.html | 4 +-
.../appendix/global-transaction-status/index.html | 4 +-
.../docs/v1.2/user/appendix/isolation/index.html | 4 +-
.../docs/v1.2/user/configuration/apollo/index.html | 4 +-
.../docs/v1.2/user/configuration/consul/index.html | 4 +-
.../docs/v1.2/user/configuration/etcd3/index.html | 4 +-
.../zh-cn/docs/v1.2/user/configuration/index.html | 4 +-
.../docs/v1.2/user/configuration/nacos/index.html | 4 +-
.../v1.2/user/configuration/zookeeper/index.html | 4 +-
.../zh-cn/docs/v1.2/user/configurations/index.html | 4 +-
.../docs/v1.2/user/configurations090/index.html | 4 +-
.../docs/v1.2/user/configurations100/index.html | 4 +-
build/zh-cn/docs/v1.2/user/datasource/index.html | 4 +-
build/zh-cn/docs/v1.2/user/microservice/index.html | 4 +-
build/zh-cn/docs/v1.2/user/mode/at/index.html | 4 +-
build/zh-cn/docs/v1.2/user/mode/saga/index.html | 4 +-
build/zh-cn/docs/v1.2/user/mode/tcc/index.html | 4 +-
build/zh-cn/docs/v1.2/user/mode/xa/index.html | 4 +-
build/zh-cn/docs/v1.2/user/ormframework/index.html | 4 +-
build/zh-cn/docs/v1.2/user/performance/index.html | 4 +-
build/zh-cn/docs/v1.2/user/quickstart/index.html | 4 +-
.../docs/v1.2/user/registry/consul/index.html | 4 +-
.../zh-cn/docs/v1.2/user/registry/etcd3/index.html | 4 +-
.../docs/v1.2/user/registry/eureka/index.html | 4 +-
build/zh-cn/docs/v1.2/user/registry/index.html | 4 +-
.../zh-cn/docs/v1.2/user/registry/nacos/index.html | 4 +-
.../docs/v1.2/user/registry/zookeeper/index.html | 4 +-
build/zh-cn/docs/v1.2/user/spring/index.html | 4 +-
.../docs/v1.2/user/sqlreference/dml/index.html | 4 +-
.../v1.2/user/sqlreference/function/index.html | 4 +-
.../user/sqlreference/sql-decoration/index.html | 4 +-
.../user/sqlreference/sql-restrictions/index.html | 4 +-
.../txgroup/transaction-group-and-ha/index.html | 4 +-
.../v1.2/user/txgroup/transaction-group/index.html | 4 +-
.../v1.3/dev/domain/overviewDomainModel/index.html | 4 +-
build/zh-cn/docs/v1.3/dev/domain/rm/index.html | 4 +-
build/zh-cn/docs/v1.3/dev/domain/tc/index.html | 4 +-
build/zh-cn/docs/v1.3/dev/domain/tm/index.html | 4 +-
build/zh-cn/docs/v1.3/dev/mode/at-mode/index.html | 4 +-
.../zh-cn/docs/v1.3/dev/mode/saga-mode/index.html | 4 +-
build/zh-cn/docs/v1.3/dev/mode/tcc-mode/index.html | 4 +-
build/zh-cn/docs/v1.3/dev/mode/xa-mode/index.html | 4 +-
build/zh-cn/docs/v1.3/dev/seata-mertics/index.html | 4 +-
.../label-an-issue-guide_dev/index.html | 4 +-
.../committer-guide/website-guide_dev/index.html | 4 +-
.../top-contributer_dev/index.html | 4 +-
.../new-contributor-guide_dev/index.html | 4 +-
.../reporting-security-issues_dev/index.html | 4 +-
.../test-coverage-guide_dev/index.html | 4 +-
.../docs/v1.3/developers/guide_dev/index.html | 4 +-
build/zh-cn/docs/v1.3/ops/config-center/index.html | 4 +-
.../docs/v1.3/ops/deploy-by-docker-142/index.html | 4 +-
.../ops/deploy-by-docker-compose-142/index.html | 4 +-
.../v1.3/ops/deploy-by-docker-compose/index.html | 4 +-
.../docs/v1.3/ops/deploy-by-docker/index.html | 4 +-
.../zh-cn/docs/v1.3/ops/deploy-by-helm/index.html | 4 +-
.../docs/v1.3/ops/deploy-by-kubernetes/index.html | 4 +-
.../docs/v1.3/ops/deploy-guide-beginner/index.html | 4 +-
build/zh-cn/docs/v1.3/ops/deploy-ha/index.html | 4 +-
build/zh-cn/docs/v1.3/ops/deploy-server/index.html | 4 +-
.../ops/multi-configuration-isolation/index.html | 4 +-
build/zh-cn/docs/v1.3/ops/upgrade/index.html | 4 +-
build/zh-cn/docs/v1.3/overview/faq/index.html | 4 +-
.../docs/v1.3/overview/terminology/index.html | 4 +-
.../docs/v1.3/overview/what-is-seata/index.html | 4 +-
build/zh-cn/docs/v1.3/release-notes/index.html | 4 +-
build/zh-cn/docs/v1.3/user/api/index.html | 4 +-
.../zh-cn/docs/v1.3/user/apm/prometheus/index.html | 4 +-
.../zh-cn/docs/v1.3/user/apm/skywalking/index.html | 4 +-
.../appendix/global-transaction-status/index.html | 4 +-
.../docs/v1.3/user/appendix/isolation/index.html | 4 +-
.../docs/v1.3/user/configuration/apollo/index.html | 4 +-
.../docs/v1.3/user/configuration/consul/index.html | 4 +-
.../docs/v1.3/user/configuration/etcd3/index.html | 4 +-
.../zh-cn/docs/v1.3/user/configuration/index.html | 4 +-
.../docs/v1.3/user/configuration/nacos/index.html | 4 +-
.../v1.3/user/configuration/zookeeper/index.html | 4 +-
.../zh-cn/docs/v1.3/user/configurations/index.html | 4 +-
.../docs/v1.3/user/configurations090/index.html | 4 +-
.../docs/v1.3/user/configurations100/index.html | 4 +-
build/zh-cn/docs/v1.3/user/datasource/index.html | 4 +-
build/zh-cn/docs/v1.3/user/microservice/index.html | 4 +-
build/zh-cn/docs/v1.3/user/mode/at/index.html | 4 +-
build/zh-cn/docs/v1.3/user/mode/saga/index.html | 4 +-
build/zh-cn/docs/v1.3/user/mode/tcc/index.html | 4 +-
build/zh-cn/docs/v1.3/user/mode/xa/index.html | 4 +-
build/zh-cn/docs/v1.3/user/ormframework/index.html | 4 +-
build/zh-cn/docs/v1.3/user/performance/index.html | 4 +-
build/zh-cn/docs/v1.3/user/quickstart/index.html | 4 +-
.../docs/v1.3/user/registry/consul/index.html | 4 +-
.../zh-cn/docs/v1.3/user/registry/etcd3/index.html | 4 +-
.../docs/v1.3/user/registry/eureka/index.html | 4 +-
build/zh-cn/docs/v1.3/user/registry/index.html | 4 +-
.../zh-cn/docs/v1.3/user/registry/nacos/index.html | 4 +-
.../docs/v1.3/user/registry/zookeeper/index.html | 4 +-
build/zh-cn/docs/v1.3/user/spring/index.html | 4 +-
.../docs/v1.3/user/sqlreference/dml/index.html | 4 +-
.../v1.3/user/sqlreference/function/index.html | 4 +-
.../user/sqlreference/sql-decoration/index.html | 4 +-
.../user/sqlreference/sql-restrictions/index.html | 4 +-
.../txgroup/transaction-group-and-ha/index.html | 4 +-
.../v1.3/user/txgroup/transaction-group/index.html | 4 +-
.../v1.4/dev/domain/overviewDomainModel/index.html | 4 +-
build/zh-cn/docs/v1.4/dev/domain/rm/index.html | 4 +-
build/zh-cn/docs/v1.4/dev/domain/tc/index.html | 4 +-
build/zh-cn/docs/v1.4/dev/domain/tm/index.html | 4 +-
build/zh-cn/docs/v1.4/dev/mode/at-mode/index.html | 4 +-
.../zh-cn/docs/v1.4/dev/mode/saga-mode/index.html | 4 +-
build/zh-cn/docs/v1.4/dev/mode/tcc-mode/index.html | 4 +-
build/zh-cn/docs/v1.4/dev/mode/xa-mode/index.html | 4 +-
build/zh-cn/docs/v1.4/dev/seata-mertics/index.html | 4 +-
.../label-an-issue-guide_dev/index.html | 4 +-
.../committer-guide/website-guide_dev/index.html | 4 +-
.../top-contributer_dev/index.html | 4 +-
.../new-contributor-guide_dev/index.html | 4 +-
.../reporting-security-issues_dev/index.html | 4 +-
.../test-coverage-guide_dev/index.html | 4 +-
.../docs/v1.4/developers/guide_dev/index.html | 4 +-
build/zh-cn/docs/v1.4/ops/config-center/index.html | 4 +-
.../docs/v1.4/ops/deploy-by-docker-142/index.html | 4 +-
.../ops/deploy-by-docker-compose-142/index.html | 4 +-
.../v1.4/ops/deploy-by-docker-compose/index.html | 4 +-
.../docs/v1.4/ops/deploy-by-docker/index.html | 4 +-
.../zh-cn/docs/v1.4/ops/deploy-by-helm/index.html | 4 +-
.../docs/v1.4/ops/deploy-by-kubernetes/index.html | 4 +-
.../docs/v1.4/ops/deploy-guide-beginner/index.html | 4 +-
build/zh-cn/docs/v1.4/ops/deploy-ha/index.html | 4 +-
build/zh-cn/docs/v1.4/ops/deploy-server/index.html | 4 +-
.../ops/multi-configuration-isolation/index.html | 4 +-
build/zh-cn/docs/v1.4/ops/upgrade/index.html | 4 +-
build/zh-cn/docs/v1.4/overview/faq/index.html | 4 +-
.../docs/v1.4/overview/terminology/index.html | 4 +-
.../docs/v1.4/overview/what-is-seata/index.html | 4 +-
build/zh-cn/docs/v1.4/release-notes/index.html | 4 +-
build/zh-cn/docs/v1.4/user/api/index.html | 4 +-
.../zh-cn/docs/v1.4/user/apm/prometheus/index.html | 4 +-
.../zh-cn/docs/v1.4/user/apm/skywalking/index.html | 4 +-
.../appendix/global-transaction-status/index.html | 4 +-
.../docs/v1.4/user/appendix/isolation/index.html | 4 +-
.../docs/v1.4/user/configuration/apollo/index.html | 4 +-
.../docs/v1.4/user/configuration/consul/index.html | 4 +-
.../docs/v1.4/user/configuration/etcd3/index.html | 4 +-
.../zh-cn/docs/v1.4/user/configuration/index.html | 4 +-
.../docs/v1.4/user/configuration/nacos/index.html | 4 +-
.../v1.4/user/configuration/zookeeper/index.html | 4 +-
.../zh-cn/docs/v1.4/user/configurations/index.html | 4 +-
.../docs/v1.4/user/configurations090/index.html | 4 +-
.../docs/v1.4/user/configurations100/index.html | 4 +-
build/zh-cn/docs/v1.4/user/datasource/index.html | 4 +-
build/zh-cn/docs/v1.4/user/microservice/index.html | 4 +-
build/zh-cn/docs/v1.4/user/mode/at/index.html | 4 +-
build/zh-cn/docs/v1.4/user/mode/saga/index.html | 4 +-
build/zh-cn/docs/v1.4/user/mode/tcc/index.html | 4 +-
build/zh-cn/docs/v1.4/user/mode/xa/index.html | 4 +-
build/zh-cn/docs/v1.4/user/ormframework/index.html | 4 +-
build/zh-cn/docs/v1.4/user/performance/index.html | 4 +-
build/zh-cn/docs/v1.4/user/quickstart/index.html | 4 +-
.../docs/v1.4/user/registry/consul/index.html | 4 +-
.../zh-cn/docs/v1.4/user/registry/etcd3/index.html | 4 +-
.../docs/v1.4/user/registry/eureka/index.html | 4 +-
build/zh-cn/docs/v1.4/user/registry/index.html | 4 +-
.../zh-cn/docs/v1.4/user/registry/nacos/index.html | 4 +-
.../docs/v1.4/user/registry/zookeeper/index.html | 4 +-
build/zh-cn/docs/v1.4/user/spring/index.html | 4 +-
.../docs/v1.4/user/sqlreference/dml/index.html | 4 +-
.../v1.4/user/sqlreference/function/index.html | 4 +-
.../user/sqlreference/sql-decoration/index.html | 4 +-
.../user/sqlreference/sql-restrictions/index.html | 4 +-
.../txgroup/transaction-group-and-ha/index.html | 4 +-
.../v1.4/user/txgroup/transaction-group/index.html | 4 +-
.../v1.5/dev/domain/overviewDomainModel/index.html | 4 +-
build/zh-cn/docs/v1.5/dev/domain/rm/index.html | 4 +-
build/zh-cn/docs/v1.5/dev/domain/tc/index.html | 4 +-
build/zh-cn/docs/v1.5/dev/domain/tm/index.html | 4 +-
build/zh-cn/docs/v1.5/dev/mode/at-mode/index.html | 4 +-
.../zh-cn/docs/v1.5/dev/mode/saga-mode/index.html | 4 +-
build/zh-cn/docs/v1.5/dev/mode/tcc-mode/index.html | 4 +-
build/zh-cn/docs/v1.5/dev/mode/xa-mode/index.html | 4 +-
build/zh-cn/docs/v1.5/dev/seata-mertics/index.html | 4 +-
.../label-an-issue-guide_dev/index.html | 4 +-
.../committer-guide/website-guide_dev/index.html | 4 +-
.../top-contributer_dev/index.html | 4 +-
.../new-contributor-guide_dev/index.html | 4 +-
.../reporting-security-issues_dev/index.html | 4 +-
.../test-coverage-guide_dev/index.html | 4 +-
.../docs/v1.5/developers/guide_dev/index.html | 4 +-
build/zh-cn/docs/v1.5/ops/config-center/index.html | 4 +-
.../docs/v1.5/ops/deploy-by-docker-142/index.html | 4 +-
.../ops/deploy-by-docker-compose-142/index.html | 4 +-
.../v1.5/ops/deploy-by-docker-compose/index.html | 4 +-
.../docs/v1.5/ops/deploy-by-docker/index.html | 4 +-
.../zh-cn/docs/v1.5/ops/deploy-by-helm/index.html | 4 +-
.../docs/v1.5/ops/deploy-by-kubernetes/index.html | 4 +-
.../docs/v1.5/ops/deploy-guide-beginner/index.html | 4 +-
build/zh-cn/docs/v1.5/ops/deploy-ha/index.html | 4 +-
build/zh-cn/docs/v1.5/ops/deploy-server/index.html | 4 +-
.../ops/multi-configuration-isolation/index.html | 4 +-
build/zh-cn/docs/v1.5/ops/upgrade/index.html | 4 +-
build/zh-cn/docs/v1.5/overview/faq/index.html | 4 +-
.../docs/v1.5/overview/terminology/index.html | 4 +-
.../docs/v1.5/overview/what-is-seata/index.html | 4 +-
build/zh-cn/docs/v1.5/release-notes/index.html | 4 +-
build/zh-cn/docs/v1.5/user/api/index.html | 4 +-
.../zh-cn/docs/v1.5/user/apm/prometheus/index.html | 4 +-
.../zh-cn/docs/v1.5/user/apm/skywalking/index.html | 4 +-
.../appendix/global-transaction-status/index.html | 4 +-
.../docs/v1.5/user/appendix/isolation/index.html | 4 +-
.../docs/v1.5/user/configuration/apollo/index.html | 4 +-
.../docs/v1.5/user/configuration/consul/index.html | 4 +-
.../docs/v1.5/user/configuration/etcd3/index.html | 4 +-
.../zh-cn/docs/v1.5/user/configuration/index.html | 4 +-
.../docs/v1.5/user/configuration/nacos/index.html | 4 +-
.../v1.5/user/configuration/zookeeper/index.html | 4 +-
.../zh-cn/docs/v1.5/user/configurations/index.html | 4 +-
.../docs/v1.5/user/configurations090/index.html | 4 +-
.../docs/v1.5/user/configurations100/index.html | 4 +-
build/zh-cn/docs/v1.5/user/datasource/index.html | 4 +-
build/zh-cn/docs/v1.5/user/microservice/index.html | 4 +-
build/zh-cn/docs/v1.5/user/mode/at/index.html | 4 +-
build/zh-cn/docs/v1.5/user/mode/saga/index.html | 4 +-
build/zh-cn/docs/v1.5/user/mode/tcc/index.html | 4 +-
build/zh-cn/docs/v1.5/user/mode/xa/index.html | 4 +-
build/zh-cn/docs/v1.5/user/ormframework/index.html | 4 +-
build/zh-cn/docs/v1.5/user/performance/index.html | 4 +-
build/zh-cn/docs/v1.5/user/quickstart/index.html | 4 +-
.../docs/v1.5/user/registry/consul/index.html | 4 +-
.../zh-cn/docs/v1.5/user/registry/etcd3/index.html | 4 +-
.../docs/v1.5/user/registry/eureka/index.html | 4 +-
build/zh-cn/docs/v1.5/user/registry/index.html | 4 +-
.../zh-cn/docs/v1.5/user/registry/nacos/index.html | 4 +-
.../docs/v1.5/user/registry/zookeeper/index.html | 4 +-
build/zh-cn/docs/v1.5/user/spring/index.html | 4 +-
.../docs/v1.5/user/sqlreference/dml/index.html | 4 +-
.../v1.5/user/sqlreference/function/index.html | 4 +-
.../user/sqlreference/sql-decoration/index.html | 4 +-
.../user/sqlreference/sql-restrictions/index.html | 4 +-
.../txgroup/transaction-group-and-ha/index.html | 4 +-
.../v1.5/user/txgroup/transaction-group/index.html | 4 +-
.../v1.6/dev/domain/overviewDomainModel/index.html | 4 +-
build/zh-cn/docs/v1.6/dev/domain/rm/index.html | 4 +-
build/zh-cn/docs/v1.6/dev/domain/tc/index.html | 4 +-
build/zh-cn/docs/v1.6/dev/domain/tm/index.html | 4 +-
build/zh-cn/docs/v1.6/dev/mode/at-mode/index.html | 4 +-
.../zh-cn/docs/v1.6/dev/mode/saga-mode/index.html | 4 +-
build/zh-cn/docs/v1.6/dev/mode/tcc-mode/index.html | 4 +-
build/zh-cn/docs/v1.6/dev/mode/xa-mode/index.html | 4 +-
build/zh-cn/docs/v1.6/dev/seata-mertics/index.html | 4 +-
.../label-an-issue-guide_dev/index.html | 4 +-
.../committer-guide/website-guide_dev/index.html | 4 +-
.../top-contributer_dev/index.html | 4 +-
.../new-contributor-guide_dev/index.html | 4 +-
.../reporting-security-issues_dev/index.html | 4 +-
.../test-coverage-guide_dev/index.html | 4 +-
.../docs/v1.6/developers/guide_dev/index.html | 4 +-
build/zh-cn/docs/v1.6/ops/config-center/index.html | 4 +-
.../docs/v1.6/ops/deploy-by-docker-142/index.html | 4 +-
.../ops/deploy-by-docker-compose-142/index.html | 4 +-
.../v1.6/ops/deploy-by-docker-compose/index.html | 4 +-
.../docs/v1.6/ops/deploy-by-docker/index.html | 4 +-
.../zh-cn/docs/v1.6/ops/deploy-by-helm/index.html | 4 +-
.../docs/v1.6/ops/deploy-by-kubernetes/index.html | 4 +-
.../docs/v1.6/ops/deploy-guide-beginner/index.html | 4 +-
build/zh-cn/docs/v1.6/ops/deploy-ha/index.html | 4 +-
build/zh-cn/docs/v1.6/ops/deploy-server/index.html | 4 +-
.../ops/multi-configuration-isolation/index.html | 4 +-
build/zh-cn/docs/v1.6/ops/upgrade/index.html | 4 +-
build/zh-cn/docs/v1.6/overview/faq/index.html | 4 +-
.../docs/v1.6/overview/terminology/index.html | 4 +-
.../docs/v1.6/overview/what-is-seata/index.html | 4 +-
build/zh-cn/docs/v1.6/release-notes/index.html | 4 +-
build/zh-cn/docs/v1.6/user/api/index.html | 4 +-
.../zh-cn/docs/v1.6/user/apm/prometheus/index.html | 4 +-
.../zh-cn/docs/v1.6/user/apm/skywalking/index.html | 4 +-
.../appendix/global-transaction-status/index.html | 4 +-
.../docs/v1.6/user/appendix/isolation/index.html | 4 +-
.../docs/v1.6/user/configuration/apollo/index.html | 4 +-
.../docs/v1.6/user/configuration/consul/index.html | 4 +-
.../docs/v1.6/user/configuration/etcd3/index.html | 4 +-
.../zh-cn/docs/v1.6/user/configuration/index.html | 4 +-
.../docs/v1.6/user/configuration/nacos/index.html | 4 +-
.../v1.6/user/configuration/zookeeper/index.html | 4 +-
.../zh-cn/docs/v1.6/user/configurations/index.html | 4 +-
.../docs/v1.6/user/configurations090/index.html | 4 +-
.../docs/v1.6/user/configurations100/index.html | 4 +-
build/zh-cn/docs/v1.6/user/datasource/index.html | 4 +-
build/zh-cn/docs/v1.6/user/microservice/index.html | 4 +-
build/zh-cn/docs/v1.6/user/mode/at/index.html | 4 +-
build/zh-cn/docs/v1.6/user/mode/saga/index.html | 4 +-
build/zh-cn/docs/v1.6/user/mode/tcc/index.html | 4 +-
build/zh-cn/docs/v1.6/user/mode/xa/index.html | 4 +-
build/zh-cn/docs/v1.6/user/ormframework/index.html | 4 +-
build/zh-cn/docs/v1.6/user/performance/index.html | 4 +-
build/zh-cn/docs/v1.6/user/quickstart/index.html | 4 +-
.../docs/v1.6/user/registry/consul/index.html | 4 +-
.../zh-cn/docs/v1.6/user/registry/etcd3/index.html | 4 +-
.../docs/v1.6/user/registry/eureka/index.html | 4 +-
build/zh-cn/docs/v1.6/user/registry/index.html | 4 +-
.../zh-cn/docs/v1.6/user/registry/nacos/index.html | 4 +-
.../docs/v1.6/user/registry/zookeeper/index.html | 4 +-
build/zh-cn/docs/v1.6/user/spring/index.html | 4 +-
.../docs/v1.6/user/sqlreference/dml/index.html | 4 +-
.../v1.6/user/sqlreference/function/index.html | 4 +-
.../user/sqlreference/sql-decoration/index.html | 4 +-
.../user/sqlreference/sql-restrictions/index.html | 4 +-
.../txgroup/transaction-group-and-ha/index.html | 4 +-
.../v1.6/user/txgroup/transaction-group/index.html | 4 +-
.../v1.7/dev/domain/overviewDomainModel/index.html | 4 +-
build/zh-cn/docs/v1.7/dev/domain/rm/index.html | 4 +-
build/zh-cn/docs/v1.7/dev/domain/tc/index.html | 4 +-
build/zh-cn/docs/v1.7/dev/domain/tm/index.html | 4 +-
build/zh-cn/docs/v1.7/dev/mode/at-mode/index.html | 4 +-
.../zh-cn/docs/v1.7/dev/mode/saga-mode/index.html | 4 +-
build/zh-cn/docs/v1.7/dev/mode/tcc-mode/index.html | 4 +-
build/zh-cn/docs/v1.7/dev/mode/xa-mode/index.html | 4 +-
build/zh-cn/docs/v1.7/dev/seata-mertics/index.html | 4 +-
.../label-an-issue-guide_dev/index.html | 4 +-
.../committer-guide/website-guide_dev/index.html | 4 +-
.../top-contributer_dev/index.html | 4 +-
.../new-contributor-guide_dev/index.html | 4 +-
.../reporting-security-issues_dev/index.html | 4 +-
.../test-coverage-guide_dev/index.html | 4 +-
.../docs/v1.7/developers/guide_dev/index.html | 4 +-
build/zh-cn/docs/v1.7/ops/config-center/index.html | 4 +-
.../docs/v1.7/ops/deploy-by-docker-142/index.html | 4 +-
.../ops/deploy-by-docker-compose-142/index.html | 4 +-
.../v1.7/ops/deploy-by-docker-compose/index.html | 4 +-
.../docs/v1.7/ops/deploy-by-docker/index.html | 4 +-
.../zh-cn/docs/v1.7/ops/deploy-by-helm/index.html | 4 +-
.../docs/v1.7/ops/deploy-by-kubernetes/index.html | 4 +-
.../docs/v1.7/ops/deploy-guide-beginner/index.html | 4 +-
build/zh-cn/docs/v1.7/ops/deploy-ha/index.html | 4 +-
build/zh-cn/docs/v1.7/ops/deploy-server/index.html | 4 +-
.../ops/multi-configuration-isolation/index.html | 4 +-
build/zh-cn/docs/v1.7/ops/upgrade/index.html | 4 +-
build/zh-cn/docs/v1.7/overview/faq/index.html | 4 +-
.../docs/v1.7/overview/terminology/index.html | 4 +-
.../docs/v1.7/overview/what-is-seata/index.html | 4 +-
build/zh-cn/docs/v1.7/release-notes/index.html | 4 +-
build/zh-cn/docs/v1.7/user/api/index.html | 4 +-
.../zh-cn/docs/v1.7/user/apm/prometheus/index.html | 4 +-
.../zh-cn/docs/v1.7/user/apm/skywalking/index.html | 4 +-
.../appendix/global-transaction-status/index.html | 4 +-
.../docs/v1.7/user/appendix/isolation/index.html | 4 +-
.../docs/v1.7/user/configuration/apollo/index.html | 4 +-
.../docs/v1.7/user/configuration/consul/index.html | 4 +-
.../docs/v1.7/user/configuration/etcd3/index.html | 4 +-
.../zh-cn/docs/v1.7/user/configuration/index.html | 4 +-
.../docs/v1.7/user/configuration/nacos/index.html | 4 +-
.../v1.7/user/configuration/zookeeper/index.html | 4 +-
.../zh-cn/docs/v1.7/user/configurations/index.html | 4 +-
.../docs/v1.7/user/configurations090/index.html | 4 +-
.../docs/v1.7/user/configurations100/index.html | 4 +-
build/zh-cn/docs/v1.7/user/datasource/index.html | 4 +-
build/zh-cn/docs/v1.7/user/microservice/index.html | 4 +-
build/zh-cn/docs/v1.7/user/mode/at/index.html | 4 +-
build/zh-cn/docs/v1.7/user/mode/saga/index.html | 4 +-
build/zh-cn/docs/v1.7/user/mode/tcc/index.html | 4 +-
build/zh-cn/docs/v1.7/user/mode/xa/index.html | 4 +-
build/zh-cn/docs/v1.7/user/ormframework/index.html | 4 +-
build/zh-cn/docs/v1.7/user/performance/index.html | 4 +-
build/zh-cn/docs/v1.7/user/quickstart/index.html | 4 +-
.../docs/v1.7/user/registry/consul/index.html | 4 +-
.../zh-cn/docs/v1.7/user/registry/etcd3/index.html | 4 +-
.../docs/v1.7/user/registry/eureka/index.html | 4 +-
build/zh-cn/docs/v1.7/user/registry/index.html | 4 +-
.../zh-cn/docs/v1.7/user/registry/nacos/index.html | 4 +-
.../docs/v1.7/user/registry/zookeeper/index.html | 4 +-
build/zh-cn/docs/v1.7/user/spring/index.html | 4 +-
.../docs/v1.7/user/sqlreference/dml/index.html | 4 +-
.../v1.7/user/sqlreference/function/index.html | 4 +-
.../user/sqlreference/sql-decoration/index.html | 4 +-
.../user/sqlreference/sql-restrictions/index.html | 4 +-
.../txgroup/transaction-group-and-ha/index.html | 4 +-
.../v1.7/user/txgroup/transaction-group/index.html | 4 +-
.../v1.8/dev/domain/overviewDomainModel/index.html | 4 +-
build/zh-cn/docs/v1.8/dev/domain/rm/index.html | 4 +-
build/zh-cn/docs/v1.8/dev/domain/tc/index.html | 4 +-
build/zh-cn/docs/v1.8/dev/domain/tm/index.html | 4 +-
build/zh-cn/docs/v1.8/dev/mode/at-mode/index.html | 4 +-
.../zh-cn/docs/v1.8/dev/mode/saga-mode/index.html | 4 +-
build/zh-cn/docs/v1.8/dev/mode/tcc-mode/index.html | 4 +-
build/zh-cn/docs/v1.8/dev/mode/xa-mode/index.html | 4 +-
build/zh-cn/docs/v1.8/dev/seata-mertics/index.html | 4 +-
.../label-an-issue-guide_dev/index.html | 4 +-
.../committer-guide/website-guide_dev/index.html | 4 +-
.../top-contributer_dev/index.html | 4 +-
.../new-contributor-guide_dev/index.html | 4 +-
.../reporting-security-issues_dev/index.html | 4 +-
.../test-coverage-guide_dev/index.html | 4 +-
.../docs/v1.8/developers/guide_dev/index.html | 4 +-
build/zh-cn/docs/v1.8/ops/config-center/index.html | 4 +-
.../docs/v1.8/ops/deploy-by-docker-142/index.html | 4 +-
.../ops/deploy-by-docker-compose-142/index.html | 4 +-
.../v1.8/ops/deploy-by-docker-compose/index.html | 4 +-
.../docs/v1.8/ops/deploy-by-docker/index.html | 4 +-
.../zh-cn/docs/v1.8/ops/deploy-by-helm/index.html | 4 +-
.../docs/v1.8/ops/deploy-by-kubernetes/index.html | 4 +-
.../docs/v1.8/ops/deploy-guide-beginner/index.html | 4 +-
build/zh-cn/docs/v1.8/ops/deploy-ha/index.html | 4 +-
build/zh-cn/docs/v1.8/ops/deploy-server/index.html | 4 +-
.../ops/multi-configuration-isolation/index.html | 4 +-
build/zh-cn/docs/v1.8/ops/upgrade/index.html | 4 +-
build/zh-cn/docs/v1.8/overview/faq/index.html | 4 +-
build/zh-cn/docs/v1.8/overview/history/index.html | 4 +-
.../docs/v1.8/overview/terminology/index.html | 4 +-
.../docs/v1.8/overview/what-is-seata/index.html | 4 +-
build/zh-cn/docs/v1.8/release-notes/index.html | 4 +-
build/zh-cn/docs/v1.8/user/api/index.html | 4 +-
.../zh-cn/docs/v1.8/user/apm/prometheus/index.html | 4 +-
.../zh-cn/docs/v1.8/user/apm/skywalking/index.html | 4 +-
.../appendix/global-transaction-status/index.html | 4 +-
.../docs/v1.8/user/appendix/isolation/index.html | 4 +-
.../docs/v1.8/user/configuration/apollo/index.html | 4 +-
.../docs/v1.8/user/configuration/consul/index.html | 4 +-
.../docs/v1.8/user/configuration/etcd3/index.html | 4 +-
.../zh-cn/docs/v1.8/user/configuration/index.html | 4 +-
.../docs/v1.8/user/configuration/nacos/index.html | 4 +-
.../v1.8/user/configuration/zookeeper/index.html | 4 +-
.../zh-cn/docs/v1.8/user/configurations/index.html | 4 +-
.../docs/v1.8/user/configurations090/index.html | 4 +-
.../docs/v1.8/user/configurations100/index.html | 4 +-
build/zh-cn/docs/v1.8/user/datasource/index.html | 4 +-
build/zh-cn/docs/v1.8/user/microservice/index.html | 4 +-
build/zh-cn/docs/v1.8/user/mode/at/index.html | 4 +-
build/zh-cn/docs/v1.8/user/mode/saga/index.html | 4 +-
build/zh-cn/docs/v1.8/user/mode/tcc/index.html | 4 +-
build/zh-cn/docs/v1.8/user/mode/xa/index.html | 4 +-
build/zh-cn/docs/v1.8/user/ormframework/index.html | 4 +-
build/zh-cn/docs/v1.8/user/performance/index.html | 4 +-
build/zh-cn/docs/v1.8/user/quickstart/index.html | 4 +-
.../docs/v1.8/user/registry/consul/index.html | 4 +-
.../zh-cn/docs/v1.8/user/registry/etcd3/index.html | 4 +-
.../docs/v1.8/user/registry/eureka/index.html | 4 +-
build/zh-cn/docs/v1.8/user/registry/index.html | 4 +-
.../zh-cn/docs/v1.8/user/registry/nacos/index.html | 4 +-
.../docs/v1.8/user/registry/zookeeper/index.html | 4 +-
build/zh-cn/docs/v1.8/user/spring/index.html | 4 +-
.../docs/v1.8/user/sqlreference/dml/index.html | 4 +-
.../v1.8/user/sqlreference/function/index.html | 4 +-
.../user/sqlreference/sql-decoration/index.html | 4 +-
.../user/sqlreference/sql-restrictions/index.html | 4 +-
.../txgroup/transaction-group-and-ha/index.html | 4 +-
.../v1.8/user/txgroup/transaction-group/index.html | 4 +-
.../v2.0/dev/domain/overviewDomainModel/index.html | 4 +-
build/zh-cn/docs/v2.0/dev/domain/rm/index.html | 4 +-
build/zh-cn/docs/v2.0/dev/domain/tc/index.html | 4 +-
build/zh-cn/docs/v2.0/dev/domain/tm/index.html | 4 +-
build/zh-cn/docs/v2.0/dev/mode/at-mode/index.html | 4 +-
.../zh-cn/docs/v2.0/dev/mode/saga-mode/index.html | 4 +-
build/zh-cn/docs/v2.0/dev/mode/tcc-mode/index.html | 4 +-
build/zh-cn/docs/v2.0/dev/mode/xa-mode/index.html | 4 +-
build/zh-cn/docs/v2.0/dev/seata-mertics/index.html | 4 +-
.../label-an-issue-guide_dev/index.html | 4 +-
.../committer-guide/website-guide_dev/index.html | 4 +-
.../top-contributer_dev/index.html | 4 +-
.../new-contributor-guide_dev/index.html | 4 +-
.../reporting-security-issues_dev/index.html | 4 +-
.../test-coverage-guide_dev/index.html | 4 +-
.../docs/v2.0/developers/guide_dev/index.html | 4 +-
build/zh-cn/docs/v2.0/ops/config-center/index.html | 4 +-
.../docs/v2.0/ops/deploy-by-docker-142/index.html | 4 +-
.../ops/deploy-by-docker-compose-142/index.html | 4 +-
.../v2.0/ops/deploy-by-docker-compose/index.html | 4 +-
.../docs/v2.0/ops/deploy-by-docker/index.html | 4 +-
.../zh-cn/docs/v2.0/ops/deploy-by-helm/index.html | 4 +-
.../docs/v2.0/ops/deploy-by-kubernetes/index.html | 4 +-
.../docs/v2.0/ops/deploy-guide-beginner/index.html | 4 +-
build/zh-cn/docs/v2.0/ops/deploy-ha/index.html | 4 +-
.../docs/v2.0/ops/deploy-server-raft/index.html | 4 +-
build/zh-cn/docs/v2.0/ops/deploy-server/index.html | 4 +-
.../ops/multi-configuration-isolation/index.html | 4 +-
build/zh-cn/docs/v2.0/ops/upgrade/index.html | 4 +-
.../docs/v2.0/ops/version-maintain-plan/index.html | 4 +-
build/zh-cn/docs/v2.0/overview/faq/index.html | 4 +-
build/zh-cn/docs/v2.0/overview/history/index.html | 4 +-
.../docs/v2.0/overview/terminology/index.html | 4 +-
.../docs/v2.0/overview/what-is-seata/index.html | 4 +-
build/zh-cn/docs/v2.0/release-notes/index.html | 4 +-
build/zh-cn/docs/v2.0/user/api/index.html | 4 +-
.../zh-cn/docs/v2.0/user/apm/prometheus/index.html | 4 +-
.../zh-cn/docs/v2.0/user/apm/skywalking/index.html | 4 +-
.../appendix/global-transaction-status/index.html | 4 +-
.../docs/v2.0/user/appendix/isolation/index.html | 4 +-
.../docs/v2.0/user/configuration/apollo/index.html | 4 +-
.../docs/v2.0/user/configuration/consul/index.html | 4 +-
.../docs/v2.0/user/configuration/etcd3/index.html | 4 +-
.../zh-cn/docs/v2.0/user/configuration/index.html | 4 +-
.../docs/v2.0/user/configuration/nacos/index.html | 4 +-
.../v2.0/user/configuration/zookeeper/index.html | 4 +-
.../zh-cn/docs/v2.0/user/configurations/index.html | 4 +-
.../docs/v2.0/user/configurations090/index.html | 4 +-
.../docs/v2.0/user/configurations100/index.html | 4 +-
build/zh-cn/docs/v2.0/user/datasource/index.html | 4 +-
build/zh-cn/docs/v2.0/user/microservice/index.html | 4 +-
build/zh-cn/docs/v2.0/user/mode/at/index.html | 4 +-
build/zh-cn/docs/v2.0/user/mode/saga/index.html | 4 +-
build/zh-cn/docs/v2.0/user/mode/tcc/index.html | 4 +-
build/zh-cn/docs/v2.0/user/mode/xa/index.html | 4 +-
build/zh-cn/docs/v2.0/user/ormframework/index.html | 4 +-
build/zh-cn/docs/v2.0/user/performance/index.html | 4 +-
build/zh-cn/docs/v2.0/user/quickstart/index.html | 4 +-
.../docs/v2.0/user/registry/consul/index.html | 4 +-
.../zh-cn/docs/v2.0/user/registry/etcd3/index.html | 4 +-
.../docs/v2.0/user/registry/eureka/index.html | 4 +-
build/zh-cn/docs/v2.0/user/registry/index.html | 4 +-
.../zh-cn/docs/v2.0/user/registry/nacos/index.html | 4 +-
.../docs/v2.0/user/registry/zookeeper/index.html | 4 +-
build/zh-cn/docs/v2.0/user/spring/index.html | 4 +-
.../docs/v2.0/user/sqlreference/dml/index.html | 4 +-
.../v2.0/user/sqlreference/function/index.html | 4 +-
.../user/sqlreference/sql-decoration/index.html | 4 +-
.../user/sqlreference/sql-restrictions/index.html | 4 +-
.../txgroup/transaction-group-and-ha/index.html | 4 +-
.../v2.0/user/txgroup/transaction-group/index.html | 4 +-
.../v2.1/dev/domain/overviewDomainModel/index.html | 4 +-
build/zh-cn/docs/v2.1/dev/domain/rm/index.html | 4 +-
build/zh-cn/docs/v2.1/dev/domain/tc/index.html | 4 +-
build/zh-cn/docs/v2.1/dev/domain/tm/index.html | 4 +-
build/zh-cn/docs/v2.1/dev/mode/at-mode/index.html | 4 +-
.../zh-cn/docs/v2.1/dev/mode/saga-mode/index.html | 4 +-
build/zh-cn/docs/v2.1/dev/mode/tcc-mode/index.html | 4 +-
build/zh-cn/docs/v2.1/dev/mode/xa-mode/index.html | 4 +-
build/zh-cn/docs/v2.1/dev/seata-mertics/index.html | 4 +-
.../label-an-issue-guide_dev/index.html | 4 +-
.../committer-guide/website-guide_dev/index.html | 4 +-
.../top-contributer_dev/index.html | 4 +-
.../new-contributor-guide_dev/index.html | 4 +-
.../reporting-security-issues_dev/index.html | 4 +-
.../test-coverage-guide_dev/index.html | 4 +-
.../docs/v2.1/developers/guide_dev/index.html | 4 +-
build/zh-cn/docs/v2.1/ops/config-center/index.html | 4 +-
.../docs/v2.1/ops/deploy-by-docker-142/index.html | 4 +-
.../ops/deploy-by-docker-compose-142/index.html | 4 +-
.../v2.1/ops/deploy-by-docker-compose/index.html | 4 +-
.../docs/v2.1/ops/deploy-by-docker/index.html | 4 +-
.../zh-cn/docs/v2.1/ops/deploy-by-helm/index.html | 4 +-
.../docs/v2.1/ops/deploy-by-kubernetes/index.html | 4 +-
.../docs/v2.1/ops/deploy-guide-beginner/index.html | 4 +-
build/zh-cn/docs/v2.1/ops/deploy-ha/index.html | 4 +-
.../docs/v2.1/ops/deploy-server-raft/index.html | 4 +-
build/zh-cn/docs/v2.1/ops/deploy-server/index.html | 4 +-
.../ops/multi-configuration-isolation/index.html | 4 +-
build/zh-cn/docs/v2.1/ops/upgrade/index.html | 4 +-
.../docs/v2.1/ops/version-maintain-plan/index.html | 4 +-
build/zh-cn/docs/v2.1/overview/faq/index.html | 4 +-
build/zh-cn/docs/v2.1/overview/history/index.html | 4 +-
.../docs/v2.1/overview/terminology/index.html | 4 +-
.../docs/v2.1/overview/what-is-seata/index.html | 4 +-
build/zh-cn/docs/v2.1/release-notes/index.html | 4 +-
build/zh-cn/docs/v2.1/user/api/index.html | 4 +-
.../zh-cn/docs/v2.1/user/apm/prometheus/index.html | 4 +-
.../zh-cn/docs/v2.1/user/apm/skywalking/index.html | 4 +-
.../appendix/global-transaction-status/index.html | 4 +-
.../docs/v2.1/user/appendix/isolation/index.html | 4 +-
.../docs/v2.1/user/configuration/apollo/index.html | 4 +-
.../docs/v2.1/user/configuration/consul/index.html | 4 +-
.../docs/v2.1/user/configuration/etcd3/index.html | 4 +-
.../zh-cn/docs/v2.1/user/configuration/index.html | 4 +-
.../docs/v2.1/user/configuration/nacos/index.html | 4 +-
.../v2.1/user/configuration/zookeeper/index.html | 4 +-
.../zh-cn/docs/v2.1/user/configurations/index.html | 4 +-
.../docs/v2.1/user/configurations090/index.html | 4 +-
.../docs/v2.1/user/configurations100/index.html | 4 +-
build/zh-cn/docs/v2.1/user/datasource/index.html | 4 +-
build/zh-cn/docs/v2.1/user/microservice/index.html | 4 +-
build/zh-cn/docs/v2.1/user/mode/at/index.html | 4 +-
build/zh-cn/docs/v2.1/user/mode/saga/index.html | 4 +-
build/zh-cn/docs/v2.1/user/mode/tcc/index.html | 4 +-
build/zh-cn/docs/v2.1/user/mode/xa/index.html | 4 +-
build/zh-cn/docs/v2.1/user/ormframework/index.html | 4 +-
build/zh-cn/docs/v2.1/user/performance/index.html | 4 +-
build/zh-cn/docs/v2.1/user/quickstart/index.html | 4 +-
.../docs/v2.1/user/registry/consul/index.html | 4 +-
.../zh-cn/docs/v2.1/user/registry/etcd3/index.html | 4 +-
.../docs/v2.1/user/registry/eureka/index.html | 4 +-
build/zh-cn/docs/v2.1/user/registry/index.html | 4 +-
.../zh-cn/docs/v2.1/user/registry/nacos/index.html | 4 +-
.../docs/v2.1/user/registry/zookeeper/index.html | 4 +-
build/zh-cn/docs/v2.1/user/spring/index.html | 4 +-
.../docs/v2.1/user/sqlreference/dml/index.html | 4 +-
.../v2.1/user/sqlreference/function/index.html | 4 +-
.../user/sqlreference/sql-decoration/index.html | 4 +-
.../user/sqlreference/sql-restrictions/index.html | 4 +-
.../txgroup/transaction-group-and-ha/index.html | 4 +-
.../v2.1/user/txgroup/transaction-group/index.html | 4 +-
build/zh-cn/home/feature/index.html | 4 +-
build/zh-cn/home/introduction/index.html | 4 +-
build/zh-cn/home/top/index.html | 4 +-
build/zh-cn/img/blog/2024121301.png | Bin 0 -> 365111 bytes
build/zh-cn/img/blog/2024121302.png | Bin 0 -> 318738 bytes
build/zh-cn/img/blog/2024121303.png | Bin 0 -> 419640 bytes
build/zh-cn/img/blog/2024121304.png | Bin 0 -> 413464 bytes
build/zh-cn/img/blog/2024121305.png | Bin 0 -> 358454 bytes
build/zh-cn/img/blog/2024121306.jpeg | Bin 0 -> 92986 bytes
build/zh-cn/index.html | 4 +-
build/zh-cn/markdown-page/index.html | 4 +-
build/zh-cn/search/index.html | 4 +-
build/zh-cn/solution/index.html | 4 +-
.../unversioned/download/seata-server/index.html | 4 +-
.../release-history/seata-server/index.html | 4 +-
build/zh-cn/users/index.html | 4 +-
community/contactItem/index.html | 4 +-
community/contributorItem/index.html | 4 +-
community/eventCard/index.html | 4 +-
community/index.html | 4 +-
docs/dev/domain/overviewDomainModel/index.html | 4 +-
docs/dev/domain/rm/index.html | 4 +-
docs/dev/domain/tc/index.html | 4 +-
docs/dev/domain/tm/index.html | 4 +-
docs/dev/mode/at-mode/index.html | 4 +-
docs/dev/mode/saga-mode/index.html | 4 +-
docs/dev/mode/tcc-mode/index.html | 4 +-
docs/dev/mode/xa-mode/index.html | 4 +-
docs/dev/seata-mertics/index.html | 4 +-
.../label-an-issue-guide_dev/index.html | 4 +-
.../committer-guide/website-guide_dev/index.html | 4 +-
.../top-contributer_dev/index.html | 4 +-
.../new-contributor-guide_dev/index.html | 4 +-
.../reporting-security-issues_dev/index.html | 4 +-
.../test-coverage-guide_dev/index.html | 4 +-
docs/developers/guide_dev/index.html | 4 +-
.../ppmc-guide/release-guide_dev/index.html | 4 +-
.../next/dev/domain/overviewDomainModel/index.html | 4 +-
docs/next/dev/domain/rm/index.html | 4 +-
docs/next/dev/domain/tc/index.html | 4 +-
docs/next/dev/domain/tm/index.html | 4 +-
docs/next/dev/mode/at-mode/index.html | 4 +-
docs/next/dev/mode/saga-mode/index.html | 4 +-
docs/next/dev/mode/tcc-mode/index.html | 4 +-
docs/next/dev/mode/xa-mode/index.html | 4 +-
docs/next/dev/seata-mertics/index.html | 4 +-
.../label-an-issue-guide_dev/index.html | 4 +-
.../committer-guide/website-guide_dev/index.html | 4 +-
.../top-contributer_dev/index.html | 4 +-
.../new-contributor-guide_dev/index.html | 4 +-
.../reporting-security-issues_dev/index.html | 4 +-
.../test-coverage-guide_dev/index.html | 4 +-
docs/next/developers/guide_dev/index.html | 4 +-
.../ppmc-guide/release-guide_dev/index.html | 4 +-
docs/next/ops/config-center/index.html | 4 +-
docs/next/ops/deploy-by-docker-142/index.html | 4 +-
.../ops/deploy-by-docker-compose-142/index.html | 4 +-
docs/next/ops/deploy-by-docker-compose/index.html | 4 +-
docs/next/ops/deploy-by-docker/index.html | 4 +-
docs/next/ops/deploy-by-helm/index.html | 4 +-
docs/next/ops/deploy-by-kubernetes/index.html | 4 +-
docs/next/ops/deploy-guide-beginner/index.html | 4 +-
docs/next/ops/deploy-ha/index.html | 4 +-
docs/next/ops/deploy-server-raft/index.html | 4 +-
docs/next/ops/deploy-server/index.html | 4 +-
.../ops/multi-configuration-isolation/index.html | 4 +-
docs/next/ops/upgrade/index.html | 4 +-
docs/next/overview/faq/index.html | 4 +-
docs/next/overview/history/index.html | 4 +-
docs/next/overview/terminology/index.html | 4 +-
docs/next/overview/what-is-seata/index.html | 4 +-
docs/next/release-notes/index.html | 4 +-
docs/next/user/api/index.html | 4 +-
docs/next/user/apm/prometheus/index.html | 4 +-
docs/next/user/apm/skywalking/index.html | 4 +-
.../appendix/global-transaction-status/index.html | 4 +-
docs/next/user/appendix/isolation/index.html | 4 +-
docs/next/user/configuration/apollo/index.html | 4 +-
docs/next/user/configuration/consul/index.html | 4 +-
docs/next/user/configuration/etcd3/index.html | 4 +-
docs/next/user/configuration/index.html | 4 +-
docs/next/user/configuration/nacos/index.html | 4 +-
docs/next/user/configuration/zookeeper/index.html | 4 +-
docs/next/user/configurations/index.html | 4 +-
docs/next/user/configurations090/index.html | 4 +-
docs/next/user/configurations100/index.html | 4 +-
docs/next/user/datasource/index.html | 4 +-
docs/next/user/microservice/index.html | 4 +-
docs/next/user/mode/at/index.html | 4 +-
docs/next/user/mode/saga/index.html | 4 +-
docs/next/user/mode/tcc/index.html | 4 +-
docs/next/user/mode/xa/index.html | 4 +-
docs/next/user/ormframework/index.html | 4 +-
docs/next/user/performance/index.html | 4 +-
docs/next/user/quickstart/index.html | 4 +-
docs/next/user/registry/consul/index.html | 4 +-
docs/next/user/registry/etcd3/index.html | 4 +-
docs/next/user/registry/eureka/index.html | 4 +-
docs/next/user/registry/index.html | 4 +-
docs/next/user/registry/nacos/index.html | 4 +-
docs/next/user/registry/namingserver/index.html | 4 +-
docs/next/user/registry/zookeeper/index.html | 4 +-
docs/next/user/spring/index.html | 4 +-
docs/next/user/sqlreference/dml/index.html | 4 +-
docs/next/user/sqlreference/function/index.html | 4 +-
.../user/sqlreference/sql-decoration/index.html | 4 +-
.../user/sqlreference/sql-restrictions/index.html | 4 +-
.../txgroup/transaction-group-and-ha/index.html | 4 +-
.../next/user/txgroup/transaction-group/index.html | 4 +-
docs/ops/config-center/index.html | 4 +-
docs/ops/deploy-by-docker-142/index.html | 4 +-
docs/ops/deploy-by-docker-compose-142/index.html | 4 +-
docs/ops/deploy-by-docker-compose/index.html | 4 +-
docs/ops/deploy-by-docker/index.html | 4 +-
docs/ops/deploy-by-helm/index.html | 4 +-
docs/ops/deploy-by-kubernetes/index.html | 4 +-
docs/ops/deploy-guide-beginner/index.html | 4 +-
docs/ops/deploy-ha/index.html | 4 +-
docs/ops/deploy-server-raft/index.html | 4 +-
docs/ops/deploy-server/index.html | 4 +-
docs/ops/multi-configuration-isolation/index.html | 4 +-
docs/ops/upgrade/index.html | 4 +-
docs/ops/version-maintain-plan/index.html | 4 +-
docs/overview/faq/index.html | 4 +-
docs/overview/history/index.html | 4 +-
docs/overview/terminology/index.html | 4 +-
docs/overview/what-is-seata/index.html | 4 +-
docs/release-notes/index.html | 4 +-
docs/user/api/index.html | 4 +-
docs/user/apm/prometheus/index.html | 4 +-
docs/user/apm/skywalking/index.html | 4 +-
.../appendix/global-transaction-status/index.html | 4 +-
docs/user/appendix/isolation/index.html | 4 +-
docs/user/configuration/apollo/index.html | 4 +-
docs/user/configuration/consul/index.html | 4 +-
docs/user/configuration/etcd3/index.html | 4 +-
docs/user/configuration/index.html | 4 +-
docs/user/configuration/nacos/index.html | 4 +-
docs/user/configuration/zookeeper/index.html | 4 +-
docs/user/configurations/index.html | 4 +-
docs/user/configurations090/index.html | 4 +-
docs/user/configurations100/index.html | 4 +-
docs/user/datasource/index.html | 4 +-
docs/user/microservice/index.html | 4 +-
docs/user/mode/at/index.html | 4 +-
docs/user/mode/saga/index.html | 4 +-
docs/user/mode/tcc/index.html | 4 +-
docs/user/mode/xa/index.html | 4 +-
docs/user/ormframework/index.html | 4 +-
docs/user/performance/index.html | 4 +-
docs/user/quickstart/index.html | 4 +-
docs/user/registry/consul/index.html | 4 +-
docs/user/registry/etcd3/index.html | 4 +-
docs/user/registry/eureka/index.html | 4 +-
docs/user/registry/index.html | 4 +-
docs/user/registry/nacos/index.html | 4 +-
docs/user/registry/namingserver/index.html | 4 +-
docs/user/registry/zookeeper/index.html | 4 +-
docs/user/spring/index.html | 4 +-
docs/user/sqlreference/dml/index.html | 4 +-
docs/user/sqlreference/function/index.html | 4 +-
docs/user/sqlreference/sql-decoration/index.html | 4 +-
docs/user/sqlreference/sql-restrictions/index.html | 4 +-
.../txgroup/transaction-group-and-ha/index.html | 4 +-
docs/user/txgroup/transaction-group/index.html | 4 +-
.../v1.0/dev/domain/overviewDomainModel/index.html | 4 +-
docs/v1.0/dev/domain/rm/index.html | 4 +-
docs/v1.0/dev/domain/tc/index.html | 4 +-
docs/v1.0/dev/domain/tm/index.html | 4 +-
docs/v1.0/dev/mode/at-mode/index.html | 4 +-
docs/v1.0/dev/mode/saga-mode/index.html | 4 +-
docs/v1.0/dev/mode/tcc-mode/index.html | 4 +-
docs/v1.0/dev/mode/xa-mode/index.html | 4 +-
docs/v1.0/dev/seata-mertics/index.html | 4 +-
.../label-an-issue-guide_dev/index.html | 4 +-
.../committer-guide/website-guide_dev/index.html | 4 +-
.../top-contributer_dev/index.html | 4 +-
.../new-contributor-guide_dev/index.html | 4 +-
.../reporting-security-issues_dev/index.html | 4 +-
.../test-coverage-guide_dev/index.html | 4 +-
docs/v1.0/developers/guide_dev/index.html | 4 +-
docs/v1.0/ops/config-center/index.html | 4 +-
docs/v1.0/ops/deploy-by-docker-142/index.html | 4 +-
.../ops/deploy-by-docker-compose-142/index.html | 4 +-
docs/v1.0/ops/deploy-by-docker-compose/index.html | 4 +-
docs/v1.0/ops/deploy-by-docker/index.html | 4 +-
docs/v1.0/ops/deploy-by-helm/index.html | 4 +-
docs/v1.0/ops/deploy-by-kubernetes/index.html | 4 +-
docs/v1.0/ops/deploy-guide-beginner/index.html | 4 +-
docs/v1.0/ops/deploy-ha/index.html | 4 +-
docs/v1.0/ops/deploy-server/index.html | 4 +-
.../ops/multi-configuration-isolation/index.html | 4 +-
docs/v1.0/ops/upgrade/index.html | 4 +-
docs/v1.0/overview/faq/index.html | 4 +-
docs/v1.0/overview/terminology/index.html | 4 +-
docs/v1.0/overview/what-is-seata/index.html | 4 +-
docs/v1.0/release-notes/index.html | 4 +-
docs/v1.0/user/api/index.html | 4 +-
docs/v1.0/user/apm/prometheus/index.html | 4 +-
docs/v1.0/user/apm/skywalking/index.html | 4 +-
.../appendix/global-transaction-status/index.html | 4 +-
docs/v1.0/user/appendix/isolation/index.html | 4 +-
docs/v1.0/user/configuration/apollo/index.html | 4 +-
docs/v1.0/user/configuration/consul/index.html | 4 +-
docs/v1.0/user/configuration/etcd3/index.html | 4 +-
docs/v1.0/user/configuration/index.html | 4 +-
docs/v1.0/user/configuration/nacos/index.html | 4 +-
docs/v1.0/user/configuration/zookeeper/index.html | 4 +-
docs/v1.0/user/configurations/index.html | 4 +-
docs/v1.0/user/configurations090/index.html | 4 +-
docs/v1.0/user/configurations100/index.html | 4 +-
docs/v1.0/user/datasource/index.html | 4 +-
docs/v1.0/user/microservice/index.html | 4 +-
docs/v1.0/user/mode/at/index.html | 4 +-
docs/v1.0/user/mode/saga/index.html | 4 +-
docs/v1.0/user/mode/tcc/index.html | 4 +-
docs/v1.0/user/mode/xa/index.html | 4 +-
docs/v1.0/user/ormframework/index.html | 4 +-
docs/v1.0/user/performance/index.html | 4 +-
docs/v1.0/user/quickstart/index.html | 4 +-
docs/v1.0/user/registry/consul/index.html | 4 +-
docs/v1.0/user/registry/etcd3/index.html | 4 +-
docs/v1.0/user/registry/eureka/index.html | 4 +-
docs/v1.0/user/registry/index.html | 4 +-
docs/v1.0/user/registry/nacos/index.html | 4 +-
docs/v1.0/user/registry/zookeeper/index.html | 4 +-
docs/v1.0/user/spring/index.html | 4 +-
docs/v1.0/user/sqlreference/dml/index.html | 4 +-
docs/v1.0/user/sqlreference/function/index.html | 4 +-
.../user/sqlreference/sql-decoration/index.html | 4 +-
.../user/sqlreference/sql-restrictions/index.html | 4 +-
.../txgroup/transaction-group-and-ha/index.html | 4 +-
.../v1.0/user/txgroup/transaction-group/index.html | 4 +-
.../v1.1/dev/domain/overviewDomainModel/index.html | 4 +-
docs/v1.1/dev/domain/rm/index.html | 4 +-
docs/v1.1/dev/domain/tc/index.html | 4 +-
docs/v1.1/dev/domain/tm/index.html | 4 +-
docs/v1.1/dev/mode/at-mode/index.html | 4 +-
docs/v1.1/dev/mode/saga-mode/index.html | 4 +-
docs/v1.1/dev/mode/tcc-mode/index.html | 4 +-
docs/v1.1/dev/mode/xa-mode/index.html | 4 +-
docs/v1.1/dev/seata-mertics/index.html | 4 +-
.../label-an-issue-guide_dev/index.html | 4 +-
.../committer-guide/website-guide_dev/index.html | 4 +-
.../top-contributer_dev/index.html | 4 +-
.../new-contributor-guide_dev/index.html | 4 +-
.../reporting-security-issues_dev/index.html | 4 +-
.../test-coverage-guide_dev/index.html | 4 +-
docs/v1.1/developers/guide_dev/index.html | 4 +-
docs/v1.1/ops/config-center/index.html | 4 +-
docs/v1.1/ops/deploy-by-docker-142/index.html | 4 +-
.../ops/deploy-by-docker-compose-142/index.html | 4 +-
docs/v1.1/ops/deploy-by-docker-compose/index.html | 4 +-
docs/v1.1/ops/deploy-by-docker/index.html | 4 +-
docs/v1.1/ops/deploy-by-helm/index.html | 4 +-
docs/v1.1/ops/deploy-by-kubernetes/index.html | 4 +-
docs/v1.1/ops/deploy-guide-beginner/index.html | 4 +-
docs/v1.1/ops/deploy-ha/index.html | 4 +-
docs/v1.1/ops/deploy-server/index.html | 4 +-
.../ops/multi-configuration-isolation/index.html | 4 +-
docs/v1.1/ops/upgrade/index.html | 4 +-
docs/v1.1/overview/faq/index.html | 4 +-
docs/v1.1/overview/terminology/index.html | 4 +-
docs/v1.1/overview/what-is-seata/index.html | 4 +-
docs/v1.1/release-notes/index.html | 4 +-
docs/v1.1/user/api/index.html | 4 +-
docs/v1.1/user/apm/prometheus/index.html | 4 +-
docs/v1.1/user/apm/skywalking/index.html | 4 +-
.../appendix/global-transaction-status/index.html | 4 +-
docs/v1.1/user/appendix/isolation/index.html | 4 +-
docs/v1.1/user/configuration/apollo/index.html | 4 +-
docs/v1.1/user/configuration/consul/index.html | 4 +-
docs/v1.1/user/configuration/etcd3/index.html | 4 +-
docs/v1.1/user/configuration/index.html | 4 +-
docs/v1.1/user/configuration/nacos/index.html | 4 +-
docs/v1.1/user/configuration/zookeeper/index.html | 4 +-
docs/v1.1/user/configurations/index.html | 4 +-
docs/v1.1/user/configurations090/index.html | 4 +-
docs/v1.1/user/configurations100/index.html | 4 +-
docs/v1.1/user/datasource/index.html | 4 +-
docs/v1.1/user/microservice/index.html | 4 +-
docs/v1.1/user/mode/at/index.html | 4 +-
docs/v1.1/user/mode/saga/index.html | 4 +-
docs/v1.1/user/mode/tcc/index.html | 4 +-
docs/v1.1/user/mode/xa/index.html | 4 +-
docs/v1.1/user/ormframework/index.html | 4 +-
docs/v1.1/user/performance/index.html | 4 +-
docs/v1.1/user/quickstart/index.html | 4 +-
docs/v1.1/user/registry/consul/index.html | 4 +-
docs/v1.1/user/registry/etcd3/index.html | 4 +-
docs/v1.1/user/registry/eureka/index.html | 4 +-
docs/v1.1/user/registry/index.html | 4 +-
docs/v1.1/user/registry/nacos/index.html | 4 +-
docs/v1.1/user/registry/zookeeper/index.html | 4 +-
docs/v1.1/user/spring/index.html | 4 +-
docs/v1.1/user/sqlreference/dml/index.html | 4 +-
docs/v1.1/user/sqlreference/function/index.html | 4 +-
.../user/sqlreference/sql-decoration/index.html | 4 +-
.../user/sqlreference/sql-restrictions/index.html | 4 +-
.../txgroup/transaction-group-and-ha/index.html | 4 +-
.../v1.1/user/txgroup/transaction-group/index.html | 4 +-
.../v1.2/dev/domain/overviewDomainModel/index.html | 4 +-
docs/v1.2/dev/domain/rm/index.html | 4 +-
docs/v1.2/dev/domain/tc/index.html | 4 +-
docs/v1.2/dev/domain/tm/index.html | 4 +-
docs/v1.2/dev/mode/at-mode/index.html | 4 +-
docs/v1.2/dev/mode/saga-mode/index.html | 4 +-
docs/v1.2/dev/mode/tcc-mode/index.html | 4 +-
docs/v1.2/dev/mode/xa-mode/index.html | 4 +-
docs/v1.2/dev/seata-mertics/index.html | 4 +-
.../label-an-issue-guide_dev/index.html | 4 +-
.../committer-guide/website-guide_dev/index.html | 4 +-
.../top-contributer_dev/index.html | 4 +-
.../new-contributor-guide_dev/index.html | 4 +-
.../reporting-security-issues_dev/index.html | 4 +-
.../test-coverage-guide_dev/index.html | 4 +-
docs/v1.2/developers/guide_dev/index.html | 4 +-
docs/v1.2/ops/config-center/index.html | 4 +-
docs/v1.2/ops/deploy-by-docker-142/index.html | 4 +-
.../ops/deploy-by-docker-compose-142/index.html | 4 +-
docs/v1.2/ops/deploy-by-docker-compose/index.html | 4 +-
docs/v1.2/ops/deploy-by-docker/index.html | 4 +-
docs/v1.2/ops/deploy-by-helm/index.html | 4 +-
docs/v1.2/ops/deploy-by-kubernetes/index.html | 4 +-
docs/v1.2/ops/deploy-guide-beginner/index.html | 4 +-
docs/v1.2/ops/deploy-ha/index.html | 4 +-
docs/v1.2/ops/deploy-server/index.html | 4 +-
.../ops/multi-configuration-isolation/index.html | 4 +-
docs/v1.2/ops/upgrade/index.html | 4 +-
docs/v1.2/overview/faq/index.html | 4 +-
docs/v1.2/overview/terminology/index.html | 4 +-
docs/v1.2/overview/what-is-seata/index.html | 4 +-
docs/v1.2/release-notes/index.html | 4 +-
docs/v1.2/user/api/index.html | 4 +-
docs/v1.2/user/apm/prometheus/index.html | 4 +-
docs/v1.2/user/apm/skywalking/index.html | 4 +-
.../appendix/global-transaction-status/index.html | 4 +-
docs/v1.2/user/appendix/isolation/index.html | 4 +-
docs/v1.2/user/configuration/apollo/index.html | 4 +-
docs/v1.2/user/configuration/consul/index.html | 4 +-
docs/v1.2/user/configuration/etcd3/index.html | 4 +-
docs/v1.2/user/configuration/index.html | 4 +-
docs/v1.2/user/configuration/nacos/index.html | 4 +-
docs/v1.2/user/configuration/zookeeper/index.html | 4 +-
docs/v1.2/user/configurations/index.html | 4 +-
docs/v1.2/user/configurations090/index.html | 4 +-
docs/v1.2/user/configurations100/index.html | 4 +-
docs/v1.2/user/datasource/index.html | 4 +-
docs/v1.2/user/microservice/index.html | 4 +-
docs/v1.2/user/mode/at/index.html | 4 +-
docs/v1.2/user/mode/saga/index.html | 4 +-
docs/v1.2/user/mode/tcc/index.html | 4 +-
docs/v1.2/user/mode/xa/index.html | 4 +-
docs/v1.2/user/ormframework/index.html | 4 +-
docs/v1.2/user/performance/index.html | 4 +-
docs/v1.2/user/quickstart/index.html | 4 +-
docs/v1.2/user/registry/consul/index.html | 4 +-
docs/v1.2/user/registry/etcd3/index.html | 4 +-
docs/v1.2/user/registry/eureka/index.html | 4 +-
docs/v1.2/user/registry/index.html | 4 +-
docs/v1.2/user/registry/nacos/index.html | 4 +-
docs/v1.2/user/registry/zookeeper/index.html | 4 +-
docs/v1.2/user/spring/index.html | 4 +-
docs/v1.2/user/sqlreference/dml/index.html | 4 +-
docs/v1.2/user/sqlreference/function/index.html | 4 +-
.../user/sqlreference/sql-decoration/index.html | 4 +-
.../user/sqlreference/sql-restrictions/index.html | 4 +-
.../txgroup/transaction-group-and-ha/index.html | 4 +-
.../v1.2/user/txgroup/transaction-group/index.html | 4 +-
.../v1.3/dev/domain/overviewDomainModel/index.html | 4 +-
docs/v1.3/dev/domain/rm/index.html | 4 +-
docs/v1.3/dev/domain/tc/index.html | 4 +-
docs/v1.3/dev/domain/tm/index.html | 4 +-
docs/v1.3/dev/mode/at-mode/index.html | 4 +-
docs/v1.3/dev/mode/saga-mode/index.html | 4 +-
docs/v1.3/dev/mode/tcc-mode/index.html | 4 +-
docs/v1.3/dev/mode/xa-mode/index.html | 4 +-
docs/v1.3/dev/seata-mertics/index.html | 4 +-
.../label-an-issue-guide_dev/index.html | 4 +-
.../committer-guide/website-guide_dev/index.html | 4 +-
.../top-contributer_dev/index.html | 4 +-
.../new-contributor-guide_dev/index.html | 4 +-
.../reporting-security-issues_dev/index.html | 4 +-
.../test-coverage-guide_dev/index.html | 4 +-
docs/v1.3/developers/guide_dev/index.html | 4 +-
docs/v1.3/ops/config-center/index.html | 4 +-
docs/v1.3/ops/deploy-by-docker-142/index.html | 4 +-
.../ops/deploy-by-docker-compose-142/index.html | 4 +-
docs/v1.3/ops/deploy-by-docker-compose/index.html | 4 +-
docs/v1.3/ops/deploy-by-docker/index.html | 4 +-
docs/v1.3/ops/deploy-by-helm/index.html | 4 +-
docs/v1.3/ops/deploy-by-kubernetes/index.html | 4 +-
docs/v1.3/ops/deploy-guide-beginner/index.html | 4 +-
docs/v1.3/ops/deploy-ha/index.html | 4 +-
docs/v1.3/ops/deploy-server/index.html | 4 +-
.../ops/multi-configuration-isolation/index.html | 4 +-
docs/v1.3/ops/upgrade/index.html | 4 +-
docs/v1.3/overview/faq/index.html | 4 +-
docs/v1.3/overview/terminology/index.html | 4 +-
docs/v1.3/overview/what-is-seata/index.html | 4 +-
docs/v1.3/release-notes/index.html | 4 +-
docs/v1.3/user/api/index.html | 4 +-
docs/v1.3/user/apm/prometheus/index.html | 4 +-
docs/v1.3/user/apm/skywalking/index.html | 4 +-
.../appendix/global-transaction-status/index.html | 4 +-
docs/v1.3/user/appendix/isolation/index.html | 4 +-
docs/v1.3/user/configuration/apollo/index.html | 4 +-
docs/v1.3/user/configuration/consul/index.html | 4 +-
docs/v1.3/user/configuration/etcd3/index.html | 4 +-
docs/v1.3/user/configuration/index.html | 4 +-
docs/v1.3/user/configuration/nacos/index.html | 4 +-
docs/v1.3/user/configuration/zookeeper/index.html | 4 +-
docs/v1.3/user/configurations/index.html | 4 +-
docs/v1.3/user/configurations090/index.html | 4 +-
docs/v1.3/user/configurations100/index.html | 4 +-
docs/v1.3/user/datasource/index.html | 4 +-
docs/v1.3/user/microservice/index.html | 4 +-
docs/v1.3/user/mode/at/index.html | 4 +-
docs/v1.3/user/mode/saga/index.html | 4 +-
docs/v1.3/user/mode/tcc/index.html | 4 +-
docs/v1.3/user/mode/xa/index.html | 4 +-
docs/v1.3/user/ormframework/index.html | 4 +-
docs/v1.3/user/performance/index.html | 4 +-
docs/v1.3/user/quickstart/index.html | 4 +-
docs/v1.3/user/registry/consul/index.html | 4 +-
docs/v1.3/user/registry/etcd3/index.html | 4 +-
docs/v1.3/user/registry/eureka/index.html | 4 +-
docs/v1.3/user/registry/index.html | 4 +-
docs/v1.3/user/registry/nacos/index.html | 4 +-
docs/v1.3/user/registry/zookeeper/index.html | 4 +-
docs/v1.3/user/spring/index.html | 4 +-
docs/v1.3/user/sqlreference/dml/index.html | 4 +-
docs/v1.3/user/sqlreference/function/index.html | 4 +-
.../user/sqlreference/sql-decoration/index.html | 4 +-
.../user/sqlreference/sql-restrictions/index.html | 4 +-
.../txgroup/transaction-group-and-ha/index.html | 4 +-
.../v1.3/user/txgroup/transaction-group/index.html | 4 +-
.../v1.4/dev/domain/overviewDomainModel/index.html | 4 +-
docs/v1.4/dev/domain/rm/index.html | 4 +-
docs/v1.4/dev/domain/tc/index.html | 4 +-
docs/v1.4/dev/domain/tm/index.html | 4 +-
docs/v1.4/dev/mode/at-mode/index.html | 4 +-
docs/v1.4/dev/mode/saga-mode/index.html | 4 +-
docs/v1.4/dev/mode/tcc-mode/index.html | 4 +-
docs/v1.4/dev/mode/xa-mode/index.html | 4 +-
docs/v1.4/dev/seata-mertics/index.html | 4 +-
.../label-an-issue-guide_dev/index.html | 4 +-
.../committer-guide/website-guide_dev/index.html | 4 +-
.../top-contributer_dev/index.html | 4 +-
.../new-contributor-guide_dev/index.html | 4 +-
.../reporting-security-issues_dev/index.html | 4 +-
.../test-coverage-guide_dev/index.html | 4 +-
docs/v1.4/developers/guide_dev/index.html | 4 +-
docs/v1.4/ops/config-center/index.html | 4 +-
docs/v1.4/ops/deploy-by-docker-142/index.html | 4 +-
.../ops/deploy-by-docker-compose-142/index.html | 4 +-
docs/v1.4/ops/deploy-by-docker-compose/index.html | 4 +-
docs/v1.4/ops/deploy-by-docker/index.html | 4 +-
docs/v1.4/ops/deploy-by-helm/index.html | 4 +-
docs/v1.4/ops/deploy-by-kubernetes/index.html | 4 +-
docs/v1.4/ops/deploy-guide-beginner/index.html | 4 +-
docs/v1.4/ops/deploy-ha/index.html | 4 +-
docs/v1.4/ops/deploy-server/index.html | 4 +-
.../ops/multi-configuration-isolation/index.html | 4 +-
docs/v1.4/ops/upgrade/index.html | 4 +-
docs/v1.4/overview/faq/index.html | 4 +-
docs/v1.4/overview/terminology/index.html | 4 +-
docs/v1.4/overview/what-is-seata/index.html | 4 +-
docs/v1.4/release-notes/index.html | 4 +-
docs/v1.4/user/api/index.html | 4 +-
docs/v1.4/user/apm/prometheus/index.html | 4 +-
docs/v1.4/user/apm/skywalking/index.html | 4 +-
.../appendix/global-transaction-status/index.html | 4 +-
docs/v1.4/user/appendix/isolation/index.html | 4 +-
docs/v1.4/user/configuration/apollo/index.html | 4 +-
docs/v1.4/user/configuration/consul/index.html | 4 +-
docs/v1.4/user/configuration/etcd3/index.html | 4 +-
docs/v1.4/user/configuration/index.html | 4 +-
docs/v1.4/user/configuration/nacos/index.html | 4 +-
docs/v1.4/user/configuration/zookeeper/index.html | 4 +-
docs/v1.4/user/configurations/index.html | 4 +-
docs/v1.4/user/configurations090/index.html | 4 +-
docs/v1.4/user/configurations100/index.html | 4 +-
docs/v1.4/user/datasource/index.html | 4 +-
docs/v1.4/user/microservice/index.html | 4 +-
docs/v1.4/user/mode/at/index.html | 4 +-
docs/v1.4/user/mode/saga/index.html | 4 +-
docs/v1.4/user/mode/tcc/index.html | 4 +-
docs/v1.4/user/mode/xa/index.html | 4 +-
docs/v1.4/user/ormframework/index.html | 4 +-
docs/v1.4/user/performance/index.html | 4 +-
docs/v1.4/user/quickstart/index.html | 4 +-
docs/v1.4/user/registry/consul/index.html | 4 +-
docs/v1.4/user/registry/etcd3/index.html | 4 +-
docs/v1.4/user/registry/eureka/index.html | 4 +-
docs/v1.4/user/registry/index.html | 4 +-
docs/v1.4/user/registry/nacos/index.html | 4 +-
docs/v1.4/user/registry/zookeeper/index.html | 4 +-
docs/v1.4/user/spring/index.html | 4 +-
docs/v1.4/user/sqlreference/dml/index.html | 4 +-
docs/v1.4/user/sqlreference/function/index.html | 4 +-
.../user/sqlreference/sql-decoration/index.html | 4 +-
.../user/sqlreference/sql-restrictions/index.html | 4 +-
.../txgroup/transaction-group-and-ha/index.html | 4 +-
.../v1.4/user/txgroup/transaction-group/index.html | 4 +-
.../v1.5/dev/domain/overviewDomainModel/index.html | 4 +-
docs/v1.5/dev/domain/rm/index.html | 4 +-
docs/v1.5/dev/domain/tc/index.html | 4 +-
docs/v1.5/dev/domain/tm/index.html | 4 +-
docs/v1.5/dev/mode/at-mode/index.html | 4 +-
docs/v1.5/dev/mode/saga-mode/index.html | 4 +-
docs/v1.5/dev/mode/tcc-mode/index.html | 4 +-
docs/v1.5/dev/mode/xa-mode/index.html | 4 +-
docs/v1.5/dev/seata-mertics/index.html | 4 +-
.../label-an-issue-guide_dev/index.html | 4 +-
.../committer-guide/website-guide_dev/index.html | 4 +-
.../top-contributer_dev/index.html | 4 +-
.../new-contributor-guide_dev/index.html | 4 +-
.../reporting-security-issues_dev/index.html | 4 +-
.../test-coverage-guide_dev/index.html | 4 +-
docs/v1.5/developers/guide_dev/index.html | 4 +-
docs/v1.5/ops/config-center/index.html | 4 +-
docs/v1.5/ops/deploy-by-docker-142/index.html | 4 +-
.../ops/deploy-by-docker-compose-142/index.html | 4 +-
docs/v1.5/ops/deploy-by-docker-compose/index.html | 4 +-
docs/v1.5/ops/deploy-by-docker/index.html | 4 +-
docs/v1.5/ops/deploy-by-helm/index.html | 4 +-
docs/v1.5/ops/deploy-by-kubernetes/index.html | 4 +-
docs/v1.5/ops/deploy-guide-beginner/index.html | 4 +-
docs/v1.5/ops/deploy-ha/index.html | 4 +-
docs/v1.5/ops/deploy-server/index.html | 4 +-
.../ops/multi-configuration-isolation/index.html | 4 +-
docs/v1.5/ops/upgrade/index.html | 4 +-
docs/v1.5/overview/faq/index.html | 4 +-
docs/v1.5/overview/terminology/index.html | 4 +-
docs/v1.5/overview/what-is-seata/index.html | 4 +-
docs/v1.5/release-notes/index.html | 4 +-
docs/v1.5/user/api/index.html | 4 +-
docs/v1.5/user/apm/prometheus/index.html | 4 +-
docs/v1.5/user/apm/skywalking/index.html | 4 +-
.../appendix/global-transaction-status/index.html | 4 +-
docs/v1.5/user/appendix/isolation/index.html | 4 +-
docs/v1.5/user/configuration/apollo/index.html | 4 +-
docs/v1.5/user/configuration/consul/index.html | 4 +-
docs/v1.5/user/configuration/etcd3/index.html | 4 +-
docs/v1.5/user/configuration/index.html | 4 +-
docs/v1.5/user/configuration/nacos/index.html | 4 +-
docs/v1.5/user/configuration/zookeeper/index.html | 4 +-
docs/v1.5/user/configurations/index.html | 4 +-
docs/v1.5/user/configurations090/index.html | 4 +-
docs/v1.5/user/configurations100/index.html | 4 +-
docs/v1.5/user/datasource/index.html | 4 +-
docs/v1.5/user/microservice/index.html | 4 +-
docs/v1.5/user/mode/at/index.html | 4 +-
docs/v1.5/user/mode/saga/index.html | 4 +-
docs/v1.5/user/mode/tcc/index.html | 4 +-
docs/v1.5/user/mode/xa/index.html | 4 +-
docs/v1.5/user/ormframework/index.html | 4 +-
docs/v1.5/user/performance/index.html | 4 +-
docs/v1.5/user/quickstart/index.html | 4 +-
docs/v1.5/user/registry/consul/index.html | 4 +-
docs/v1.5/user/registry/etcd3/index.html | 4 +-
docs/v1.5/user/registry/eureka/index.html | 4 +-
docs/v1.5/user/registry/index.html | 4 +-
docs/v1.5/user/registry/nacos/index.html | 4 +-
docs/v1.5/user/registry/zookeeper/index.html | 4 +-
docs/v1.5/user/spring/index.html | 4 +-
docs/v1.5/user/sqlreference/dml/index.html | 4 +-
docs/v1.5/user/sqlreference/function/index.html | 4 +-
.../user/sqlreference/sql-decoration/index.html | 4 +-
.../user/sqlreference/sql-restrictions/index.html | 4 +-
.../txgroup/transaction-group-and-ha/index.html | 4 +-
.../v1.5/user/txgroup/transaction-group/index.html | 4 +-
.../v1.6/dev/domain/overviewDomainModel/index.html | 4 +-
docs/v1.6/dev/domain/rm/index.html | 4 +-
docs/v1.6/dev/domain/tc/index.html | 4 +-
docs/v1.6/dev/domain/tm/index.html | 4 +-
docs/v1.6/dev/mode/at-mode/index.html | 4 +-
docs/v1.6/dev/mode/saga-mode/index.html | 4 +-
docs/v1.6/dev/mode/tcc-mode/index.html | 4 +-
docs/v1.6/dev/mode/xa-mode/index.html | 4 +-
docs/v1.6/dev/seata-mertics/index.html | 4 +-
.../label-an-issue-guide_dev/index.html | 4 +-
.../committer-guide/website-guide_dev/index.html | 4 +-
.../top-contributer_dev/index.html | 4 +-
.../new-contributor-guide_dev/index.html | 4 +-
.../reporting-security-issues_dev/index.html | 4 +-
.../test-coverage-guide_dev/index.html | 4 +-
docs/v1.6/developers/guide_dev/index.html | 4 +-
docs/v1.6/ops/config-center/index.html | 4 +-
docs/v1.6/ops/deploy-by-docker-142/index.html | 4 +-
.../ops/deploy-by-docker-compose-142/index.html | 4 +-
docs/v1.6/ops/deploy-by-docker-compose/index.html | 4 +-
docs/v1.6/ops/deploy-by-docker/index.html | 4 +-
docs/v1.6/ops/deploy-by-helm/index.html | 4 +-
docs/v1.6/ops/deploy-by-kubernetes/index.html | 4 +-
docs/v1.6/ops/deploy-guide-beginner/index.html | 4 +-
docs/v1.6/ops/deploy-ha/index.html | 4 +-
docs/v1.6/ops/deploy-server/index.html | 4 +-
.../ops/multi-configuration-isolation/index.html | 4 +-
docs/v1.6/ops/upgrade/index.html | 4 +-
docs/v1.6/overview/faq/index.html | 4 +-
docs/v1.6/overview/terminology/index.html | 4 +-
docs/v1.6/overview/what-is-seata/index.html | 4 +-
docs/v1.6/release-notes/index.html | 4 +-
docs/v1.6/user/api/index.html | 4 +-
docs/v1.6/user/apm/prometheus/index.html | 4 +-
docs/v1.6/user/apm/skywalking/index.html | 4 +-
.../appendix/global-transaction-status/index.html | 4 +-
docs/v1.6/user/appendix/isolation/index.html | 4 +-
docs/v1.6/user/configuration/apollo/index.html | 4 +-
docs/v1.6/user/configuration/consul/index.html | 4 +-
docs/v1.6/user/configuration/etcd3/index.html | 4 +-
docs/v1.6/user/configuration/index.html | 4 +-
docs/v1.6/user/configuration/nacos/index.html | 4 +-
docs/v1.6/user/configuration/zookeeper/index.html | 4 +-
docs/v1.6/user/configurations/index.html | 4 +-
docs/v1.6/user/configurations090/index.html | 4 +-
docs/v1.6/user/configurations100/index.html | 4 +-
docs/v1.6/user/datasource/index.html | 4 +-
docs/v1.6/user/microservice/index.html | 4 +-
docs/v1.6/user/mode/at/index.html | 4 +-
docs/v1.6/user/mode/saga/index.html | 4 +-
docs/v1.6/user/mode/tcc/index.html | 4 +-
docs/v1.6/user/mode/xa/index.html | 4 +-
docs/v1.6/user/ormframework/index.html | 4 +-
docs/v1.6/user/performance/index.html | 4 +-
docs/v1.6/user/quickstart/index.html | 4 +-
docs/v1.6/user/registry/consul/index.html | 4 +-
docs/v1.6/user/registry/etcd3/index.html | 4 +-
docs/v1.6/user/registry/eureka/index.html | 4 +-
docs/v1.6/user/registry/index.html | 4 +-
docs/v1.6/user/registry/nacos/index.html | 4 +-
docs/v1.6/user/registry/zookeeper/index.html | 4 +-
docs/v1.6/user/spring/index.html | 4 +-
docs/v1.6/user/sqlreference/dml/index.html | 4 +-
docs/v1.6/user/sqlreference/function/index.html | 4 +-
.../user/sqlreference/sql-decoration/index.html | 4 +-
.../user/sqlreference/sql-restrictions/index.html | 4 +-
.../txgroup/transaction-group-and-ha/index.html | 4 +-
.../v1.6/user/txgroup/transaction-group/index.html | 4 +-
.../v1.7/dev/domain/overviewDomainModel/index.html | 4 +-
docs/v1.7/dev/domain/rm/index.html | 4 +-
docs/v1.7/dev/domain/tc/index.html | 4 +-
docs/v1.7/dev/domain/tm/index.html | 4 +-
docs/v1.7/dev/mode/at-mode/index.html | 4 +-
docs/v1.7/dev/mode/saga-mode/index.html | 4 +-
docs/v1.7/dev/mode/tcc-mode/index.html | 4 +-
docs/v1.7/dev/mode/xa-mode/index.html | 4 +-
docs/v1.7/dev/seata-mertics/index.html | 4 +-
.../label-an-issue-guide_dev/index.html | 4 +-
.../committer-guide/website-guide_dev/index.html | 4 +-
.../top-contributer_dev/index.html | 4 +-
.../new-contributor-guide_dev/index.html | 4 +-
.../reporting-security-issues_dev/index.html | 4 +-
.../test-coverage-guide_dev/index.html | 4 +-
docs/v1.7/developers/guide_dev/index.html | 4 +-
docs/v1.7/ops/config-center/index.html | 4 +-
docs/v1.7/ops/deploy-by-docker-142/index.html | 4 +-
.../ops/deploy-by-docker-compose-142/index.html | 4 +-
docs/v1.7/ops/deploy-by-docker-compose/index.html | 4 +-
docs/v1.7/ops/deploy-by-docker/index.html | 4 +-
docs/v1.7/ops/deploy-by-helm/index.html | 4 +-
docs/v1.7/ops/deploy-by-kubernetes/index.html | 4 +-
docs/v1.7/ops/deploy-guide-beginner/index.html | 4 +-
docs/v1.7/ops/deploy-ha/index.html | 4 +-
docs/v1.7/ops/deploy-server/index.html | 4 +-
.../ops/multi-configuration-isolation/index.html | 4 +-
docs/v1.7/ops/upgrade/index.html | 4 +-
docs/v1.7/overview/faq/index.html | 4 +-
docs/v1.7/overview/terminology/index.html | 4 +-
docs/v1.7/overview/what-is-seata/index.html | 4 +-
docs/v1.7/release-notes/index.html | 4 +-
docs/v1.7/user/api/index.html | 4 +-
docs/v1.7/user/apm/prometheus/index.html | 4 +-
docs/v1.7/user/apm/skywalking/index.html | 4 +-
.../appendix/global-transaction-status/index.html | 4 +-
docs/v1.7/user/appendix/isolation/index.html | 4 +-
docs/v1.7/user/configuration/apollo/index.html | 4 +-
docs/v1.7/user/configuration/consul/index.html | 4 +-
docs/v1.7/user/configuration/etcd3/index.html | 4 +-
docs/v1.7/user/configuration/index.html | 4 +-
docs/v1.7/user/configuration/nacos/index.html | 4 +-
docs/v1.7/user/configuration/zookeeper/index.html | 4 +-
docs/v1.7/user/configurations/index.html | 4 +-
docs/v1.7/user/configurations090/index.html | 4 +-
docs/v1.7/user/configurations100/index.html | 4 +-
docs/v1.7/user/datasource/index.html | 4 +-
docs/v1.7/user/microservice/index.html | 4 +-
docs/v1.7/user/mode/at/index.html | 4 +-
docs/v1.7/user/mode/saga/index.html | 4 +-
docs/v1.7/user/mode/tcc/index.html | 4 +-
docs/v1.7/user/mode/xa/index.html | 4 +-
docs/v1.7/user/ormframework/index.html | 4 +-
docs/v1.7/user/performance/index.html | 4 +-
docs/v1.7/user/quickstart/index.html | 4 +-
docs/v1.7/user/registry/consul/index.html | 4 +-
docs/v1.7/user/registry/etcd3/index.html | 4 +-
docs/v1.7/user/registry/eureka/index.html | 4 +-
docs/v1.7/user/registry/index.html | 4 +-
docs/v1.7/user/registry/nacos/index.html | 4 +-
docs/v1.7/user/registry/zookeeper/index.html | 4 +-
docs/v1.7/user/spring/index.html | 4 +-
docs/v1.7/user/sqlreference/dml/index.html | 4 +-
docs/v1.7/user/sqlreference/function/index.html | 4 +-
.../user/sqlreference/sql-decoration/index.html | 4 +-
.../user/sqlreference/sql-restrictions/index.html | 4 +-
.../txgroup/transaction-group-and-ha/index.html | 4 +-
.../v1.7/user/txgroup/transaction-group/index.html | 4 +-
.../v1.8/dev/domain/overviewDomainModel/index.html | 4 +-
docs/v1.8/dev/domain/rm/index.html | 4 +-
docs/v1.8/dev/domain/tc/index.html | 4 +-
docs/v1.8/dev/domain/tm/index.html | 4 +-
docs/v1.8/dev/mode/at-mode/index.html | 4 +-
docs/v1.8/dev/mode/saga-mode/index.html | 4 +-
docs/v1.8/dev/mode/tcc-mode/index.html | 4 +-
docs/v1.8/dev/mode/xa-mode/index.html | 4 +-
docs/v1.8/dev/seata-mertics/index.html | 4 +-
.../label-an-issue-guide_dev/index.html | 4 +-
.../committer-guide/website-guide_dev/index.html | 4 +-
.../top-contributer_dev/index.html | 4 +-
.../new-contributor-guide_dev/index.html | 4 +-
.../reporting-security-issues_dev/index.html | 4 +-
.../test-coverage-guide_dev/index.html | 4 +-
docs/v1.8/developers/guide_dev/index.html | 4 +-
docs/v1.8/ops/config-center/index.html | 4 +-
docs/v1.8/ops/deploy-by-docker-142/index.html | 4 +-
.../ops/deploy-by-docker-compose-142/index.html | 4 +-
docs/v1.8/ops/deploy-by-docker-compose/index.html | 4 +-
docs/v1.8/ops/deploy-by-docker/index.html | 4 +-
docs/v1.8/ops/deploy-by-helm/index.html | 4 +-
docs/v1.8/ops/deploy-by-kubernetes/index.html | 4 +-
docs/v1.8/ops/deploy-guide-beginner/index.html | 4 +-
docs/v1.8/ops/deploy-ha/index.html | 4 +-
docs/v1.8/ops/deploy-server/index.html | 4 +-
.../ops/multi-configuration-isolation/index.html | 4 +-
docs/v1.8/ops/upgrade/index.html | 4 +-
docs/v1.8/overview/faq/index.html | 4 +-
docs/v1.8/overview/history/index.html | 4 +-
docs/v1.8/overview/terminology/index.html | 4 +-
docs/v1.8/overview/what-is-seata/index.html | 4 +-
docs/v1.8/release-notes/index.html | 4 +-
docs/v1.8/user/api/index.html | 4 +-
docs/v1.8/user/apm/prometheus/index.html | 4 +-
docs/v1.8/user/apm/skywalking/index.html | 4 +-
.../appendix/global-transaction-status/index.html | 4 +-
docs/v1.8/user/appendix/isolation/index.html | 4 +-
docs/v1.8/user/configuration/apollo/index.html | 4 +-
docs/v1.8/user/configuration/consul/index.html | 4 +-
docs/v1.8/user/configuration/etcd3/index.html | 4 +-
docs/v1.8/user/configuration/index.html | 4 +-
docs/v1.8/user/configuration/nacos/index.html | 4 +-
docs/v1.8/user/configuration/zookeeper/index.html | 4 +-
docs/v1.8/user/configurations/index.html | 4 +-
docs/v1.8/user/configurations090/index.html | 4 +-
docs/v1.8/user/configurations100/index.html | 4 +-
docs/v1.8/user/datasource/index.html | 4 +-
docs/v1.8/user/microservice/index.html | 4 +-
docs/v1.8/user/mode/at/index.html | 4 +-
docs/v1.8/user/mode/saga/index.html | 4 +-
docs/v1.8/user/mode/tcc/index.html | 4 +-
docs/v1.8/user/mode/xa/index.html | 4 +-
docs/v1.8/user/ormframework/index.html | 4 +-
docs/v1.8/user/performance/index.html | 4 +-
docs/v1.8/user/quickstart/index.html | 4 +-
docs/v1.8/user/registry/consul/index.html | 4 +-
docs/v1.8/user/registry/etcd3/index.html | 4 +-
docs/v1.8/user/registry/eureka/index.html | 4 +-
docs/v1.8/user/registry/index.html | 4 +-
docs/v1.8/user/registry/nacos/index.html | 4 +-
docs/v1.8/user/registry/zookeeper/index.html | 4 +-
docs/v1.8/user/spring/index.html | 4 +-
docs/v1.8/user/sqlreference/dml/index.html | 4 +-
docs/v1.8/user/sqlreference/function/index.html | 4 +-
.../user/sqlreference/sql-decoration/index.html | 4 +-
.../user/sqlreference/sql-restrictions/index.html | 4 +-
.../txgroup/transaction-group-and-ha/index.html | 4 +-
.../v1.8/user/txgroup/transaction-group/index.html | 4 +-
.../v2.0/dev/domain/overviewDomainModel/index.html | 4 +-
docs/v2.0/dev/domain/rm/index.html | 4 +-
docs/v2.0/dev/domain/tc/index.html | 4 +-
docs/v2.0/dev/domain/tm/index.html | 4 +-
docs/v2.0/dev/mode/at-mode/index.html | 4 +-
docs/v2.0/dev/mode/saga-mode/index.html | 4 +-
docs/v2.0/dev/mode/tcc-mode/index.html | 4 +-
docs/v2.0/dev/mode/xa-mode/index.html | 4 +-
docs/v2.0/dev/seata-mertics/index.html | 4 +-
.../label-an-issue-guide_dev/index.html | 4 +-
.../committer-guide/website-guide_dev/index.html | 4 +-
.../top-contributer_dev/index.html | 4 +-
.../new-contributor-guide_dev/index.html | 4 +-
.../reporting-security-issues_dev/index.html | 4 +-
.../test-coverage-guide_dev/index.html | 4 +-
docs/v2.0/developers/guide_dev/index.html | 4 +-
docs/v2.0/ops/config-center/index.html | 4 +-
docs/v2.0/ops/deploy-by-docker-142/index.html | 4 +-
.../ops/deploy-by-docker-compose-142/index.html | 4 +-
docs/v2.0/ops/deploy-by-docker-compose/index.html | 4 +-
docs/v2.0/ops/deploy-by-docker/index.html | 4 +-
docs/v2.0/ops/deploy-by-helm/index.html | 4 +-
docs/v2.0/ops/deploy-by-kubernetes/index.html | 4 +-
docs/v2.0/ops/deploy-guide-beginner/index.html | 4 +-
docs/v2.0/ops/deploy-ha/index.html | 4 +-
docs/v2.0/ops/deploy-server-raft/index.html | 4 +-
docs/v2.0/ops/deploy-server/index.html | 4 +-
.../ops/multi-configuration-isolation/index.html | 4 +-
docs/v2.0/ops/upgrade/index.html | 4 +-
docs/v2.0/ops/version-maintain-plan/index.html | 4 +-
docs/v2.0/overview/faq/index.html | 4 +-
docs/v2.0/overview/history/index.html | 4 +-
docs/v2.0/overview/terminology/index.html | 4 +-
docs/v2.0/overview/what-is-seata/index.html | 4 +-
docs/v2.0/release-notes/index.html | 4 +-
docs/v2.0/user/api/index.html | 4 +-
docs/v2.0/user/apm/prometheus/index.html | 4 +-
docs/v2.0/user/apm/skywalking/index.html | 4 +-
.../appendix/global-transaction-status/index.html | 4 +-
docs/v2.0/user/appendix/isolation/index.html | 4 +-
docs/v2.0/user/configuration/apollo/index.html | 4 +-
docs/v2.0/user/configuration/consul/index.html | 4 +-
docs/v2.0/user/configuration/etcd3/index.html | 4 +-
docs/v2.0/user/configuration/index.html | 4 +-
docs/v2.0/user/configuration/nacos/index.html | 4 +-
docs/v2.0/user/configuration/zookeeper/index.html | 4 +-
docs/v2.0/user/configurations/index.html | 4 +-
docs/v2.0/user/configurations090/index.html | 4 +-
docs/v2.0/user/configurations100/index.html | 4 +-
docs/v2.0/user/datasource/index.html | 4 +-
docs/v2.0/user/microservice/index.html | 4 +-
docs/v2.0/user/mode/at/index.html | 4 +-
docs/v2.0/user/mode/saga/index.html | 4 +-
docs/v2.0/user/mode/tcc/index.html | 4 +-
docs/v2.0/user/mode/xa/index.html | 4 +-
docs/v2.0/user/ormframework/index.html | 4 +-
docs/v2.0/user/performance/index.html | 4 +-
docs/v2.0/user/quickstart/index.html | 4 +-
docs/v2.0/user/registry/consul/index.html | 4 +-
docs/v2.0/user/registry/etcd3/index.html | 4 +-
docs/v2.0/user/registry/eureka/index.html | 4 +-
docs/v2.0/user/registry/index.html | 4 +-
docs/v2.0/user/registry/nacos/index.html | 4 +-
docs/v2.0/user/registry/zookeeper/index.html | 4 +-
docs/v2.0/user/spring/index.html | 4 +-
docs/v2.0/user/sqlreference/dml/index.html | 4 +-
docs/v2.0/user/sqlreference/function/index.html | 4 +-
.../user/sqlreference/sql-decoration/index.html | 4 +-
.../user/sqlreference/sql-restrictions/index.html | 4 +-
.../txgroup/transaction-group-and-ha/index.html | 4 +-
.../v2.0/user/txgroup/transaction-group/index.html | 4 +-
.../v2.1/dev/domain/overviewDomainModel/index.html | 4 +-
docs/v2.1/dev/domain/rm/index.html | 4 +-
docs/v2.1/dev/domain/tc/index.html | 4 +-
docs/v2.1/dev/domain/tm/index.html | 4 +-
docs/v2.1/dev/mode/at-mode/index.html | 4 +-
docs/v2.1/dev/mode/saga-mode/index.html | 4 +-
docs/v2.1/dev/mode/tcc-mode/index.html | 4 +-
docs/v2.1/dev/mode/xa-mode/index.html | 4 +-
docs/v2.1/dev/seata-mertics/index.html | 4 +-
.../label-an-issue-guide_dev/index.html | 4 +-
.../committer-guide/website-guide_dev/index.html | 4 +-
.../top-contributer_dev/index.html | 4 +-
.../new-contributor-guide_dev/index.html | 4 +-
.../reporting-security-issues_dev/index.html | 4 +-
.../test-coverage-guide_dev/index.html | 4 +-
docs/v2.1/developers/guide_dev/index.html | 4 +-
docs/v2.1/ops/config-center/index.html | 4 +-
docs/v2.1/ops/deploy-by-docker-142/index.html | 4 +-
.../ops/deploy-by-docker-compose-142/index.html | 4 +-
docs/v2.1/ops/deploy-by-docker-compose/index.html | 4 +-
docs/v2.1/ops/deploy-by-docker/index.html | 4 +-
docs/v2.1/ops/deploy-by-helm/index.html | 4 +-
docs/v2.1/ops/deploy-by-kubernetes/index.html | 4 +-
docs/v2.1/ops/deploy-guide-beginner/index.html | 4 +-
docs/v2.1/ops/deploy-ha/index.html | 4 +-
docs/v2.1/ops/deploy-server-raft/index.html | 4 +-
docs/v2.1/ops/deploy-server/index.html | 4 +-
.../ops/multi-configuration-isolation/index.html | 4 +-
docs/v2.1/ops/upgrade/index.html | 4 +-
docs/v2.1/ops/version-maintain-plan/index.html | 4 +-
docs/v2.1/overview/faq/index.html | 4 +-
docs/v2.1/overview/history/index.html | 4 +-
docs/v2.1/overview/terminology/index.html | 4 +-
docs/v2.1/overview/what-is-seata/index.html | 4 +-
docs/v2.1/release-notes/index.html | 4 +-
docs/v2.1/user/api/index.html | 4 +-
docs/v2.1/user/apm/prometheus/index.html | 4 +-
docs/v2.1/user/apm/skywalking/index.html | 4 +-
.../appendix/global-transaction-status/index.html | 4 +-
docs/v2.1/user/appendix/isolation/index.html | 4 +-
docs/v2.1/user/configuration/apollo/index.html | 4 +-
docs/v2.1/user/configuration/consul/index.html | 4 +-
docs/v2.1/user/configuration/etcd3/index.html | 4 +-
docs/v2.1/user/configuration/index.html | 4 +-
docs/v2.1/user/configuration/nacos/index.html | 4 +-
docs/v2.1/user/configuration/zookeeper/index.html | 4 +-
docs/v2.1/user/configurations/index.html | 4 +-
docs/v2.1/user/configurations090/index.html | 4 +-
docs/v2.1/user/configurations100/index.html | 4 +-
docs/v2.1/user/datasource/index.html | 4 +-
docs/v2.1/user/microservice/index.html | 4 +-
docs/v2.1/user/mode/at/index.html | 4 +-
docs/v2.1/user/mode/saga/index.html | 4 +-
docs/v2.1/user/mode/tcc/index.html | 4 +-
docs/v2.1/user/mode/xa/index.html | 4 +-
docs/v2.1/user/ormframework/index.html | 4 +-
docs/v2.1/user/performance/index.html | 4 +-
docs/v2.1/user/quickstart/index.html | 4 +-
docs/v2.1/user/registry/consul/index.html | 4 +-
docs/v2.1/user/registry/etcd3/index.html | 4 +-
docs/v2.1/user/registry/eureka/index.html | 4 +-
docs/v2.1/user/registry/index.html | 4 +-
docs/v2.1/user/registry/nacos/index.html | 4 +-
docs/v2.1/user/registry/zookeeper/index.html | 4 +-
docs/v2.1/user/spring/index.html | 4 +-
docs/v2.1/user/sqlreference/dml/index.html | 4 +-
docs/v2.1/user/sqlreference/function/index.html | 4 +-
.../user/sqlreference/sql-decoration/index.html | 4 +-
.../user/sqlreference/sql-restrictions/index.html | 4 +-
.../txgroup/transaction-group-and-ha/index.html | 4 +-
.../v2.1/user/txgroup/transaction-group/index.html | 4 +-
home/feature/index.html | 4 +-
home/introduction/index.html | 4 +-
home/top/index.html | 4 +-
img/blog/2024121301.png | Bin 0 -> 365111 bytes
img/blog/2024121302.png | Bin 0 -> 318738 bytes
img/blog/2024121303.png | Bin 0 -> 419640 bytes
img/blog/2024121304.png | Bin 0 -> 413464 bytes
img/blog/2024121305.png | Bin 0 -> 358454 bytes
img/blog/2024121306.jpeg | Bin 0 -> 92986 bytes
index.html | 4 +-
markdown-page/index.html | 4 +-
search/index.html | 4 +-
site.txt | 1261 ++++++++++----------
sitemap.xml | 2 +-
solution/index.html | 4 +-
unversioned/download/seata-server/index.html | 4 +-
.../release-history/seata-server/index.html | 4 +-
users/index.html | 4 +-
zh-cn/404.html | 4 +-
...2024121301-4613ead894d7510e65d88296eb86e297.png | Bin 0 -> 365111 bytes
...2024121302-39625f525d6da1bbc7ad4509c94718eb.png | Bin 0 -> 318738 bytes
...2024121303-bad6bb1db830335d72e2037ea7dbf4de.png | Bin 0 -> 419640 bytes
...2024121304-fcc9119043d66143a841d2008ef136f5.png | Bin 0 -> 413464 bytes
...2024121305-327ecb450c5fd7f7fc636165421972b2.png | Bin 0 -> 358454 bytes
...024121306-5568d956a86d67c43e4d76837dd5c8b8.jpeg | Bin 0 -> 92986 bytes
zh-cn/assets/js/17fbb55d.1a92045c.js | 1 +
zh-cn/assets/js/2f917717.865ae696.js | 1 +
zh-cn/assets/js/3a67a931.1d939766.js | 1 +
zh-cn/assets/js/465ed234.1886ae45.js | 1 +
zh-cn/assets/js/6b1d283c.2683ee0f.js | 1 +
zh-cn/assets/js/77df707c.d7e3a22f.js | 1 +
zh-cn/assets/js/7c04fe45.fb2f7b60.js | 1 +
zh-cn/assets/js/814f3328.92b1da4f.js | 1 +
zh-cn/assets/js/81cde232.e34a0f99.js | 1 +
zh-cn/assets/js/b73dc115.54f0190d.js | 1 +
zh-cn/assets/js/b91266d6.8b669b8f.js | 1 +
zh-cn/assets/js/d504b8f0.1978e6a2.js | 1 +
zh-cn/assets/js/dc05b4b1.d03aca48.js | 1 +
zh-cn/assets/js/main.dd5af082.js | 2 +
zh-cn/assets/js/main.dd5af082.js.LICENSE.txt | 64 +
zh-cn/assets/js/runtime~main.178f39f2.js | 1 +
zh-cn/blog/archive/index.html | 6 +-
zh-cn/blog/atom.xml | 182 +--
.../index.html | 26 +-
zh-cn/blog/explore-seata-journey/index.html | 16 +-
zh-cn/blog/how-to-support-spring-cloud/index.html | 16 +-
zh-cn/blog/how-to-write-unit-tests/index.html | 14 +-
zh-cn/blog/index.html | 167 ++-
.../index.html | 14 +-
.../integrate-seata-with-spring-cloud/index.html | 18 +-
zh-cn/blog/iscas2023/index.html | 12 +-
zh-cn/blog/manual-transaction-mode/index.html | 6 +-
zh-cn/blog/page/2/index.html | 243 ++--
zh-cn/blog/page/3/index.html | 240 ++--
zh-cn/blog/page/4/index.html | 174 ++-
zh-cn/blog/page/5/index.html | 272 ++---
zh-cn/blog/page/6/index.html | 321 ++---
zh-cn/blog/page/7/index.html | 104 +-
.../index.html | 8 +-
zh-cn/blog/rss.xml | 176 +--
zh-cn/blog/seata-1.5.2/index.html | 6 +-
zh-cn/blog/seata-1.6.0/index.html | 10 +-
.../blog/seata-analysis-UUID-generator/index.html | 16 +-
.../blog/seata-analysis-config-modular/index.html | 10 +-
zh-cn/blog/seata-analysis-core-modular/index.html | 14 +-
.../seata-analysis-dubbo-transmit-xid/index.html | 8 +-
zh-cn/blog/seata-analysis-go-server/index.html | 12 +-
zh-cn/blog/seata-analysis-java-client/index.html | 22 +-
zh-cn/blog/seata-analysis-java-server/index.html | 34 +-
zh-cn/blog/seata-analysis-simple/index.html | 22 +-
zh-cn/blog/seata-analysis-tcc-modular/index.html | 14 +-
zh-cn/blog/seata-at-demo-in-mac/index.html | 14 +-
zh-cn/blog/seata-at-lock/index.html | 12 +-
zh-cn/blog/seata-at-mode-design/index.html | 18 +-
zh-cn/blog/seata-at-mode-start-rm-tm/index.html | 10 +-
zh-cn/blog/seata-at-mode-start/index.html | 16 +-
zh-cn/blog/seata-at-tcc-saga/index.html | 30 +-
.../blog/seata-client-start-analysis-01/index.html | 20 +-
.../blog/seata-client-start-analysis-02/index.html | 18 +-
.../index.html | 6 +-
zh-cn/blog/seata-config-center/index.html | 8 +-
zh-cn/blog/seata-config-manager/index.html | 12 +-
.../seata-connect-data-and-application/index.html | 24 +-
zh-cn/blog/seata-datasource-proxy/index.html | 30 +-
zh-cn/blog/seata-dsproxy-deadlock/index.html | 14 +-
.../index.html | 14 +-
.../seata-feature-undo-log-compress/index.html | 16 +-
zh-cn/blog/seata-go-1.2.0/index.html | 8 +-
.../seata-golang-communication-mode/index.html | 12 +-
zh-cn/blog/seata-grpc-client/index.html | 75 ++
zh-cn/blog/seata-ha-practice/index.html | 8 +-
zh-cn/blog/seata-meetup-hangzhou/index.html | 10 +-
zh-cn/blog/seata-mybatisplus-analysis/index.html | 10 +-
zh-cn/blog/seata-nacos-analysis/index.html | 6 +-
zh-cn/blog/seata-nacos-docker/index.html | 8 +-
zh-cn/blog/seata-namingserver/index.html | 14 +-
zh-cn/blog/seata-observable-practice/index.html | 16 +-
zh-cn/blog/seata-quick-start/index.html | 16 +-
zh-cn/blog/seata-raft-config-center/index.html | 18 +-
.../seata-raft-detailed-explanation/index.html | 24 +-
zh-cn/blog/seata-rpc-multi-protocol01/index.html | 12 +-
zh-cn/blog/seata-rpc-multi-protocol02/index.html | 12 +-
zh-cn/blog/seata-rpc-refactor/index.html | 22 +-
zh-cn/blog/seata-snowflake-explain/index.html | 14 +-
.../seata-sourcecode-client-bootstrap/index.html | 6 +-
.../seata-sourcecode-server-bootstrap/index.html | 16 +-
.../blog/seata-spring-boot-aop-aspectj/index.html | 6 +-
zh-cn/blog/seata-tcc-fence/index.html | 18 +-
zh-cn/blog/seata-tcc/index.html | 24 +-
zh-cn/blog/seata-xa-introduce/index.html | 28 +-
.../springboot-dubbo-mybatisplus-seata/index.html | 14 +-
zh-cn/blog/tags/index.html | 6 +-
zh-cn/blog/tags/seata/index.html | 26 +-
.../index.html | 12 +-
zh-cn/blog/tcc-mode-design-principle/index.html | 16 +-
zh-cn/community/contactItem/index.html | 4 +-
zh-cn/community/contributorItem/index.html | 4 +-
zh-cn/community/eventCard/index.html | 4 +-
zh-cn/community/index.html | 4 +-
.../docs/dev/domain/overviewDomainModel/index.html | 4 +-
zh-cn/docs/dev/domain/rm/index.html | 4 +-
zh-cn/docs/dev/domain/tc/index.html | 4 +-
zh-cn/docs/dev/domain/tm/index.html | 4 +-
zh-cn/docs/dev/mode/at-mode/index.html | 4 +-
zh-cn/docs/dev/mode/saga-mode/index.html | 4 +-
zh-cn/docs/dev/mode/tcc-mode/index.html | 4 +-
zh-cn/docs/dev/mode/xa-mode/index.html | 4 +-
zh-cn/docs/dev/seata-mertics/index.html | 4 +-
.../label-an-issue-guide_dev/index.html | 4 +-
.../committer-guide/website-guide_dev/index.html | 4 +-
.../top-contributer_dev/index.html | 4 +-
.../new-contributor-guide_dev/index.html | 4 +-
.../reporting-security-issues_dev/index.html | 4 +-
.../test-coverage-guide_dev/index.html | 4 +-
zh-cn/docs/developers/guide_dev/index.html | 4 +-
.../ppmc-guide/release-guide_dev/index.html | 4 +-
.../next/dev/domain/overviewDomainModel/index.html | 4 +-
zh-cn/docs/next/dev/domain/rm/index.html | 4 +-
zh-cn/docs/next/dev/domain/tc/index.html | 4 +-
zh-cn/docs/next/dev/domain/tm/index.html | 4 +-
zh-cn/docs/next/dev/mode/at-mode/index.html | 4 +-
zh-cn/docs/next/dev/mode/saga-mode/index.html | 4 +-
zh-cn/docs/next/dev/mode/tcc-mode/index.html | 4 +-
zh-cn/docs/next/dev/mode/xa-mode/index.html | 4 +-
zh-cn/docs/next/dev/seata-mertics/index.html | 4 +-
.../label-an-issue-guide_dev/index.html | 4 +-
.../committer-guide/website-guide_dev/index.html | 4 +-
.../top-contributer_dev/index.html | 4 +-
.../new-contributor-guide_dev/index.html | 4 +-
.../reporting-security-issues_dev/index.html | 4 +-
.../test-coverage-guide_dev/index.html | 4 +-
zh-cn/docs/next/developers/guide_dev/index.html | 4 +-
.../ppmc-guide/release-guide_dev/index.html | 4 +-
zh-cn/docs/next/ops/config-center/index.html | 4 +-
.../docs/next/ops/deploy-by-docker-142/index.html | 4 +-
.../ops/deploy-by-docker-compose-142/index.html | 4 +-
.../next/ops/deploy-by-docker-compose/index.html | 4 +-
zh-cn/docs/next/ops/deploy-by-docker/index.html | 4 +-
zh-cn/docs/next/ops/deploy-by-helm/index.html | 4 +-
.../docs/next/ops/deploy-by-kubernetes/index.html | 4 +-
.../docs/next/ops/deploy-guide-beginner/index.html | 4 +-
zh-cn/docs/next/ops/deploy-ha/index.html | 4 +-
zh-cn/docs/next/ops/deploy-server-raft/index.html | 4 +-
zh-cn/docs/next/ops/deploy-server/index.html | 4 +-
.../ops/multi-configuration-isolation/index.html | 4 +-
zh-cn/docs/next/ops/upgrade/index.html | 4 +-
zh-cn/docs/next/overview/faq/index.html | 4 +-
zh-cn/docs/next/overview/history/index.html | 4 +-
zh-cn/docs/next/overview/terminology/index.html | 4 +-
zh-cn/docs/next/overview/what-is-seata/index.html | 4 +-
zh-cn/docs/next/release-notes/index.html | 4 +-
zh-cn/docs/next/user/api/index.html | 4 +-
zh-cn/docs/next/user/apm/prometheus/index.html | 4 +-
zh-cn/docs/next/user/apm/skywalking/index.html | 4 +-
.../appendix/global-transaction-status/index.html | 4 +-
zh-cn/docs/next/user/appendix/isolation/index.html | 4 +-
.../docs/next/user/configuration/apollo/index.html | 4 +-
.../docs/next/user/configuration/consul/index.html | 4 +-
.../docs/next/user/configuration/etcd3/index.html | 4 +-
zh-cn/docs/next/user/configuration/index.html | 4 +-
.../docs/next/user/configuration/nacos/index.html | 4 +-
.../next/user/configuration/zookeeper/index.html | 4 +-
zh-cn/docs/next/user/configurations/index.html | 4 +-
zh-cn/docs/next/user/configurations090/index.html | 4 +-
zh-cn/docs/next/user/configurations100/index.html | 4 +-
zh-cn/docs/next/user/datasource/index.html | 4 +-
zh-cn/docs/next/user/microservice/index.html | 4 +-
zh-cn/docs/next/user/mode/at/index.html | 4 +-
zh-cn/docs/next/user/mode/saga/index.html | 4 +-
zh-cn/docs/next/user/mode/tcc/index.html | 4 +-
zh-cn/docs/next/user/mode/xa/index.html | 4 +-
zh-cn/docs/next/user/ormframework/index.html | 4 +-
zh-cn/docs/next/user/performance/index.html | 4 +-
zh-cn/docs/next/user/quickstart/index.html | 4 +-
zh-cn/docs/next/user/registry/consul/index.html | 4 +-
zh-cn/docs/next/user/registry/etcd3/index.html | 4 +-
zh-cn/docs/next/user/registry/eureka/index.html | 4 +-
zh-cn/docs/next/user/registry/index.html | 4 +-
zh-cn/docs/next/user/registry/nacos/index.html | 4 +-
.../next/user/registry/namingserver/index.html | 4 +-
zh-cn/docs/next/user/registry/zookeeper/index.html | 4 +-
zh-cn/docs/next/user/spring/index.html | 4 +-
zh-cn/docs/next/user/sqlreference/dml/index.html | 4 +-
.../next/user/sqlreference/function/index.html | 4 +-
.../user/sqlreference/sql-decoration/index.html | 4 +-
.../user/sqlreference/sql-restrictions/index.html | 4 +-
.../txgroup/transaction-group-and-ha/index.html | 4 +-
.../next/user/txgroup/transaction-group/index.html | 4 +-
zh-cn/docs/ops/config-center/index.html | 4 +-
zh-cn/docs/ops/deploy-by-docker-142/index.html | 4 +-
.../ops/deploy-by-docker-compose-142/index.html | 4 +-
zh-cn/docs/ops/deploy-by-docker-compose/index.html | 4 +-
zh-cn/docs/ops/deploy-by-docker/index.html | 4 +-
zh-cn/docs/ops/deploy-by-helm/index.html | 4 +-
zh-cn/docs/ops/deploy-by-kubernetes/index.html | 4 +-
zh-cn/docs/ops/deploy-guide-beginner/index.html | 4 +-
zh-cn/docs/ops/deploy-ha/index.html | 4 +-
zh-cn/docs/ops/deploy-server-raft/index.html | 4 +-
zh-cn/docs/ops/deploy-server/index.html | 4 +-
.../ops/multi-configuration-isolation/index.html | 4 +-
zh-cn/docs/ops/upgrade/index.html | 4 +-
zh-cn/docs/ops/version-maintain-plan/index.html | 4 +-
zh-cn/docs/overview/faq/index.html | 4 +-
zh-cn/docs/overview/history/index.html | 4 +-
zh-cn/docs/overview/terminology/index.html | 4 +-
zh-cn/docs/overview/what-is-seata/index.html | 4 +-
zh-cn/docs/release-notes/index.html | 4 +-
zh-cn/docs/user/api/index.html | 4 +-
zh-cn/docs/user/apm/prometheus/index.html | 4 +-
zh-cn/docs/user/apm/skywalking/index.html | 4 +-
.../appendix/global-transaction-status/index.html | 4 +-
zh-cn/docs/user/appendix/isolation/index.html | 4 +-
zh-cn/docs/user/configuration/apollo/index.html | 4 +-
zh-cn/docs/user/configuration/consul/index.html | 4 +-
zh-cn/docs/user/configuration/etcd3/index.html | 4 +-
zh-cn/docs/user/configuration/index.html | 4 +-
zh-cn/docs/user/configuration/nacos/index.html | 4 +-
zh-cn/docs/user/configuration/zookeeper/index.html | 4 +-
zh-cn/docs/user/configurations/index.html | 4 +-
zh-cn/docs/user/configurations090/index.html | 4 +-
zh-cn/docs/user/configurations100/index.html | 4 +-
zh-cn/docs/user/datasource/index.html | 4 +-
zh-cn/docs/user/microservice/index.html | 4 +-
zh-cn/docs/user/mode/at/index.html | 4 +-
zh-cn/docs/user/mode/saga/index.html | 4 +-
zh-cn/docs/user/mode/tcc/index.html | 4 +-
zh-cn/docs/user/mode/xa/index.html | 4 +-
zh-cn/docs/user/ormframework/index.html | 4 +-
zh-cn/docs/user/performance/index.html | 4 +-
zh-cn/docs/user/quickstart/index.html | 4 +-
zh-cn/docs/user/registry/consul/index.html | 4 +-
zh-cn/docs/user/registry/etcd3/index.html | 4 +-
zh-cn/docs/user/registry/eureka/index.html | 4 +-
zh-cn/docs/user/registry/index.html | 4 +-
zh-cn/docs/user/registry/nacos/index.html | 4 +-
zh-cn/docs/user/registry/namingserver/index.html | 4 +-
zh-cn/docs/user/registry/zookeeper/index.html | 4 +-
zh-cn/docs/user/spring/index.html | 4 +-
zh-cn/docs/user/sqlreference/dml/index.html | 4 +-
zh-cn/docs/user/sqlreference/function/index.html | 4 +-
.../user/sqlreference/sql-decoration/index.html | 4 +-
.../user/sqlreference/sql-restrictions/index.html | 4 +-
.../txgroup/transaction-group-and-ha/index.html | 4 +-
.../docs/user/txgroup/transaction-group/index.html | 4 +-
.../v1.0/dev/domain/overviewDomainModel/index.html | 4 +-
zh-cn/docs/v1.0/dev/domain/rm/index.html | 4 +-
zh-cn/docs/v1.0/dev/domain/tc/index.html | 4 +-
zh-cn/docs/v1.0/dev/domain/tm/index.html | 4 +-
zh-cn/docs/v1.0/dev/mode/at-mode/index.html | 4 +-
zh-cn/docs/v1.0/dev/mode/saga-mode/index.html | 4 +-
zh-cn/docs/v1.0/dev/mode/tcc-mode/index.html | 4 +-
zh-cn/docs/v1.0/dev/mode/xa-mode/index.html | 4 +-
zh-cn/docs/v1.0/dev/seata-mertics/index.html | 4 +-
.../label-an-issue-guide_dev/index.html | 4 +-
.../committer-guide/website-guide_dev/index.html | 4 +-
.../top-contributer_dev/index.html | 4 +-
.../new-contributor-guide_dev/index.html | 4 +-
.../reporting-security-issues_dev/index.html | 4 +-
.../test-coverage-guide_dev/index.html | 4 +-
zh-cn/docs/v1.0/developers/guide_dev/index.html | 4 +-
zh-cn/docs/v1.0/ops/config-center/index.html | 4 +-
.../docs/v1.0/ops/deploy-by-docker-142/index.html | 4 +-
.../ops/deploy-by-docker-compose-142/index.html | 4 +-
.../v1.0/ops/deploy-by-docker-compose/index.html | 4 +-
zh-cn/docs/v1.0/ops/deploy-by-docker/index.html | 4 +-
zh-cn/docs/v1.0/ops/deploy-by-helm/index.html | 4 +-
.../docs/v1.0/ops/deploy-by-kubernetes/index.html | 4 +-
.../docs/v1.0/ops/deploy-guide-beginner/index.html | 4 +-
zh-cn/docs/v1.0/ops/deploy-ha/index.html | 4 +-
zh-cn/docs/v1.0/ops/deploy-server/index.html | 4 +-
.../ops/multi-configuration-isolation/index.html | 4 +-
zh-cn/docs/v1.0/ops/upgrade/index.html | 4 +-
zh-cn/docs/v1.0/overview/faq/index.html | 4 +-
zh-cn/docs/v1.0/overview/terminology/index.html | 4 +-
zh-cn/docs/v1.0/overview/what-is-seata/index.html | 4 +-
zh-cn/docs/v1.0/release-notes/index.html | 4 +-
zh-cn/docs/v1.0/user/api/index.html | 4 +-
zh-cn/docs/v1.0/user/apm/prometheus/index.html | 4 +-
zh-cn/docs/v1.0/user/apm/skywalking/index.html | 4 +-
.../appendix/global-transaction-status/index.html | 4 +-
zh-cn/docs/v1.0/user/appendix/isolation/index.html | 4 +-
.../docs/v1.0/user/configuration/apollo/index.html | 4 +-
.../docs/v1.0/user/configuration/consul/index.html | 4 +-
.../docs/v1.0/user/configuration/etcd3/index.html | 4 +-
zh-cn/docs/v1.0/user/configuration/index.html | 4 +-
.../docs/v1.0/user/configuration/nacos/index.html | 4 +-
.../v1.0/user/configuration/zookeeper/index.html | 4 +-
zh-cn/docs/v1.0/user/configurations/index.html | 4 +-
zh-cn/docs/v1.0/user/configurations090/index.html | 4 +-
zh-cn/docs/v1.0/user/configurations100/index.html | 4 +-
zh-cn/docs/v1.0/user/datasource/index.html | 4 +-
zh-cn/docs/v1.0/user/microservice/index.html | 4 +-
zh-cn/docs/v1.0/user/mode/at/index.html | 4 +-
zh-cn/docs/v1.0/user/mode/saga/index.html | 4 +-
zh-cn/docs/v1.0/user/mode/tcc/index.html | 4 +-
zh-cn/docs/v1.0/user/mode/xa/index.html | 4 +-
zh-cn/docs/v1.0/user/ormframework/index.html | 4 +-
zh-cn/docs/v1.0/user/performance/index.html | 4 +-
zh-cn/docs/v1.0/user/quickstart/index.html | 4 +-
zh-cn/docs/v1.0/user/registry/consul/index.html | 4 +-
zh-cn/docs/v1.0/user/registry/etcd3/index.html | 4 +-
zh-cn/docs/v1.0/user/registry/eureka/index.html | 4 +-
zh-cn/docs/v1.0/user/registry/index.html | 4 +-
zh-cn/docs/v1.0/user/registry/nacos/index.html | 4 +-
zh-cn/docs/v1.0/user/registry/zookeeper/index.html | 4 +-
zh-cn/docs/v1.0/user/spring/index.html | 4 +-
zh-cn/docs/v1.0/user/sqlreference/dml/index.html | 4 +-
.../v1.0/user/sqlreference/function/index.html | 4 +-
.../user/sqlreference/sql-decoration/index.html | 4 +-
.../user/sqlreference/sql-restrictions/index.html | 4 +-
.../txgroup/transaction-group-and-ha/index.html | 4 +-
.../v1.0/user/txgroup/transaction-group/index.html | 4 +-
.../v1.1/dev/domain/overviewDomainModel/index.html | 4 +-
zh-cn/docs/v1.1/dev/domain/rm/index.html | 4 +-
zh-cn/docs/v1.1/dev/domain/tc/index.html | 4 +-
zh-cn/docs/v1.1/dev/domain/tm/index.html | 4 +-
zh-cn/docs/v1.1/dev/mode/at-mode/index.html | 4 +-
zh-cn/docs/v1.1/dev/mode/saga-mode/index.html | 4 +-
zh-cn/docs/v1.1/dev/mode/tcc-mode/index.html | 4 +-
zh-cn/docs/v1.1/dev/mode/xa-mode/index.html | 4 +-
zh-cn/docs/v1.1/dev/seata-mertics/index.html | 4 +-
.../label-an-issue-guide_dev/index.html | 4 +-
.../committer-guide/website-guide_dev/index.html | 4 +-
.../top-contributer_dev/index.html | 4 +-
.../new-contributor-guide_dev/index.html | 4 +-
.../reporting-security-issues_dev/index.html | 4 +-
.../test-coverage-guide_dev/index.html | 4 +-
zh-cn/docs/v1.1/developers/guide_dev/index.html | 4 +-
zh-cn/docs/v1.1/ops/config-center/index.html | 4 +-
.../docs/v1.1/ops/deploy-by-docker-142/index.html | 4 +-
.../ops/deploy-by-docker-compose-142/index.html | 4 +-
.../v1.1/ops/deploy-by-docker-compose/index.html | 4 +-
zh-cn/docs/v1.1/ops/deploy-by-docker/index.html | 4 +-
zh-cn/docs/v1.1/ops/deploy-by-helm/index.html | 4 +-
.../docs/v1.1/ops/deploy-by-kubernetes/index.html | 4 +-
.../docs/v1.1/ops/deploy-guide-beginner/index.html | 4 +-
zh-cn/docs/v1.1/ops/deploy-ha/index.html | 4 +-
zh-cn/docs/v1.1/ops/deploy-server/index.html | 4 +-
.../ops/multi-configuration-isolation/index.html | 4 +-
zh-cn/docs/v1.1/ops/upgrade/index.html | 4 +-
zh-cn/docs/v1.1/overview/faq/index.html | 4 +-
zh-cn/docs/v1.1/overview/terminology/index.html | 4 +-
zh-cn/docs/v1.1/overview/what-is-seata/index.html | 4 +-
zh-cn/docs/v1.1/release-notes/index.html | 4 +-
zh-cn/docs/v1.1/user/api/index.html | 4 +-
zh-cn/docs/v1.1/user/apm/prometheus/index.html | 4 +-
zh-cn/docs/v1.1/user/apm/skywalking/index.html | 4 +-
.../appendix/global-transaction-status/index.html | 4 +-
zh-cn/docs/v1.1/user/appendix/isolation/index.html | 4 +-
.../docs/v1.1/user/configuration/apollo/index.html | 4 +-
.../docs/v1.1/user/configuration/consul/index.html | 4 +-
.../docs/v1.1/user/configuration/etcd3/index.html | 4 +-
zh-cn/docs/v1.1/user/configuration/index.html | 4 +-
.../docs/v1.1/user/configuration/nacos/index.html | 4 +-
.../v1.1/user/configuration/zookeeper/index.html | 4 +-
zh-cn/docs/v1.1/user/configurations/index.html | 4 +-
zh-cn/docs/v1.1/user/configurations090/index.html | 4 +-
zh-cn/docs/v1.1/user/configurations100/index.html | 4 +-
zh-cn/docs/v1.1/user/datasource/index.html | 4 +-
zh-cn/docs/v1.1/user/microservice/index.html | 4 +-
zh-cn/docs/v1.1/user/mode/at/index.html | 4 +-
zh-cn/docs/v1.1/user/mode/saga/index.html | 4 +-
zh-cn/docs/v1.1/user/mode/tcc/index.html | 4 +-
zh-cn/docs/v1.1/user/mode/xa/index.html | 4 +-
zh-cn/docs/v1.1/user/ormframework/index.html | 4 +-
zh-cn/docs/v1.1/user/performance/index.html | 4 +-
zh-cn/docs/v1.1/user/quickstart/index.html | 4 +-
zh-cn/docs/v1.1/user/registry/consul/index.html | 4 +-
zh-cn/docs/v1.1/user/registry/etcd3/index.html | 4 +-
zh-cn/docs/v1.1/user/registry/eureka/index.html | 4 +-
zh-cn/docs/v1.1/user/registry/index.html | 4 +-
zh-cn/docs/v1.1/user/registry/nacos/index.html | 4 +-
zh-cn/docs/v1.1/user/registry/zookeeper/index.html | 4 +-
zh-cn/docs/v1.1/user/spring/index.html | 4 +-
zh-cn/docs/v1.1/user/sqlreference/dml/index.html | 4 +-
.../v1.1/user/sqlreference/function/index.html | 4 +-
.../user/sqlreference/sql-decoration/index.html | 4 +-
.../user/sqlreference/sql-restrictions/index.html | 4 +-
.../txgroup/transaction-group-and-ha/index.html | 4 +-
.../v1.1/user/txgroup/transaction-group/index.html | 4 +-
.../v1.2/dev/domain/overviewDomainModel/index.html | 4 +-
zh-cn/docs/v1.2/dev/domain/rm/index.html | 4 +-
zh-cn/docs/v1.2/dev/domain/tc/index.html | 4 +-
zh-cn/docs/v1.2/dev/domain/tm/index.html | 4 +-
zh-cn/docs/v1.2/dev/mode/at-mode/index.html | 4 +-
zh-cn/docs/v1.2/dev/mode/saga-mode/index.html | 4 +-
zh-cn/docs/v1.2/dev/mode/tcc-mode/index.html | 4 +-
zh-cn/docs/v1.2/dev/mode/xa-mode/index.html | 4 +-
zh-cn/docs/v1.2/dev/seata-mertics/index.html | 4 +-
.../label-an-issue-guide_dev/index.html | 4 +-
.../committer-guide/website-guide_dev/index.html | 4 +-
.../top-contributer_dev/index.html | 4 +-
.../new-contributor-guide_dev/index.html | 4 +-
.../reporting-security-issues_dev/index.html | 4 +-
.../test-coverage-guide_dev/index.html | 4 +-
zh-cn/docs/v1.2/developers/guide_dev/index.html | 4 +-
zh-cn/docs/v1.2/ops/config-center/index.html | 4 +-
.../docs/v1.2/ops/deploy-by-docker-142/index.html | 4 +-
.../ops/deploy-by-docker-compose-142/index.html | 4 +-
.../v1.2/ops/deploy-by-docker-compose/index.html | 4 +-
zh-cn/docs/v1.2/ops/deploy-by-docker/index.html | 4 +-
zh-cn/docs/v1.2/ops/deploy-by-helm/index.html | 4 +-
.../docs/v1.2/ops/deploy-by-kubernetes/index.html | 4 +-
.../docs/v1.2/ops/deploy-guide-beginner/index.html | 4 +-
zh-cn/docs/v1.2/ops/deploy-ha/index.html | 4 +-
zh-cn/docs/v1.2/ops/deploy-server/index.html | 4 +-
.../ops/multi-configuration-isolation/index.html | 4 +-
zh-cn/docs/v1.2/ops/upgrade/index.html | 4 +-
zh-cn/docs/v1.2/overview/faq/index.html | 4 +-
zh-cn/docs/v1.2/overview/terminology/index.html | 4 +-
zh-cn/docs/v1.2/overview/what-is-seata/index.html | 4 +-
zh-cn/docs/v1.2/release-notes/index.html | 4 +-
zh-cn/docs/v1.2/user/api/index.html | 4 +-
zh-cn/docs/v1.2/user/apm/prometheus/index.html | 4 +-
zh-cn/docs/v1.2/user/apm/skywalking/index.html | 4 +-
.../appendix/global-transaction-status/index.html | 4 +-
zh-cn/docs/v1.2/user/appendix/isolation/index.html | 4 +-
.../docs/v1.2/user/configuration/apollo/index.html | 4 +-
.../docs/v1.2/user/configuration/consul/index.html | 4 +-
.../docs/v1.2/user/configuration/etcd3/index.html | 4 +-
zh-cn/docs/v1.2/user/configuration/index.html | 4 +-
.../docs/v1.2/user/configuration/nacos/index.html | 4 +-
.../v1.2/user/configuration/zookeeper/index.html | 4 +-
zh-cn/docs/v1.2/user/configurations/index.html | 4 +-
zh-cn/docs/v1.2/user/configurations090/index.html | 4 +-
zh-cn/docs/v1.2/user/configurations100/index.html | 4 +-
zh-cn/docs/v1.2/user/datasource/index.html | 4 +-
zh-cn/docs/v1.2/user/microservice/index.html | 4 +-
zh-cn/docs/v1.2/user/mode/at/index.html | 4 +-
zh-cn/docs/v1.2/user/mode/saga/index.html | 4 +-
zh-cn/docs/v1.2/user/mode/tcc/index.html | 4 +-
zh-cn/docs/v1.2/user/mode/xa/index.html | 4 +-
zh-cn/docs/v1.2/user/ormframework/index.html | 4 +-
zh-cn/docs/v1.2/user/performance/index.html | 4 +-
zh-cn/docs/v1.2/user/quickstart/index.html | 4 +-
zh-cn/docs/v1.2/user/registry/consul/index.html | 4 +-
zh-cn/docs/v1.2/user/registry/etcd3/index.html | 4 +-
zh-cn/docs/v1.2/user/registry/eureka/index.html | 4 +-
zh-cn/docs/v1.2/user/registry/index.html | 4 +-
zh-cn/docs/v1.2/user/registry/nacos/index.html | 4 +-
zh-cn/docs/v1.2/user/registry/zookeeper/index.html | 4 +-
zh-cn/docs/v1.2/user/spring/index.html | 4 +-
zh-cn/docs/v1.2/user/sqlreference/dml/index.html | 4 +-
.../v1.2/user/sqlreference/function/index.html | 4 +-
.../user/sqlreference/sql-decoration/index.html | 4 +-
.../user/sqlreference/sql-restrictions/index.html | 4 +-
.../txgroup/transaction-group-and-ha/index.html | 4 +-
.../v1.2/user/txgroup/transaction-group/index.html | 4 +-
.../v1.3/dev/domain/overviewDomainModel/index.html | 4 +-
zh-cn/docs/v1.3/dev/domain/rm/index.html | 4 +-
zh-cn/docs/v1.3/dev/domain/tc/index.html | 4 +-
zh-cn/docs/v1.3/dev/domain/tm/index.html | 4 +-
zh-cn/docs/v1.3/dev/mode/at-mode/index.html | 4 +-
zh-cn/docs/v1.3/dev/mode/saga-mode/index.html | 4 +-
zh-cn/docs/v1.3/dev/mode/tcc-mode/index.html | 4 +-
zh-cn/docs/v1.3/dev/mode/xa-mode/index.html | 4 +-
zh-cn/docs/v1.3/dev/seata-mertics/index.html | 4 +-
.../label-an-issue-guide_dev/index.html | 4 +-
.../committer-guide/website-guide_dev/index.html | 4 +-
.../top-contributer_dev/index.html | 4 +-
.../new-contributor-guide_dev/index.html | 4 +-
.../reporting-security-issues_dev/index.html | 4 +-
.../test-coverage-guide_dev/index.html | 4 +-
zh-cn/docs/v1.3/developers/guide_dev/index.html | 4 +-
zh-cn/docs/v1.3/ops/config-center/index.html | 4 +-
.../docs/v1.3/ops/deploy-by-docker-142/index.html | 4 +-
.../ops/deploy-by-docker-compose-142/index.html | 4 +-
.../v1.3/ops/deploy-by-docker-compose/index.html | 4 +-
zh-cn/docs/v1.3/ops/deploy-by-docker/index.html | 4 +-
zh-cn/docs/v1.3/ops/deploy-by-helm/index.html | 4 +-
.../docs/v1.3/ops/deploy-by-kubernetes/index.html | 4 +-
.../docs/v1.3/ops/deploy-guide-beginner/index.html | 4 +-
zh-cn/docs/v1.3/ops/deploy-ha/index.html | 4 +-
zh-cn/docs/v1.3/ops/deploy-server/index.html | 4 +-
.../ops/multi-configuration-isolation/index.html | 4 +-
zh-cn/docs/v1.3/ops/upgrade/index.html | 4 +-
zh-cn/docs/v1.3/overview/faq/index.html | 4 +-
zh-cn/docs/v1.3/overview/terminology/index.html | 4 +-
zh-cn/docs/v1.3/overview/what-is-seata/index.html | 4 +-
zh-cn/docs/v1.3/release-notes/index.html | 4 +-
zh-cn/docs/v1.3/user/api/index.html | 4 +-
zh-cn/docs/v1.3/user/apm/prometheus/index.html | 4 +-
zh-cn/docs/v1.3/user/apm/skywalking/index.html | 4 +-
.../appendix/global-transaction-status/index.html | 4 +-
zh-cn/docs/v1.3/user/appendix/isolation/index.html | 4 +-
.../docs/v1.3/user/configuration/apollo/index.html | 4 +-
.../docs/v1.3/user/configuration/consul/index.html | 4 +-
.../docs/v1.3/user/configuration/etcd3/index.html | 4 +-
zh-cn/docs/v1.3/user/configuration/index.html | 4 +-
.../docs/v1.3/user/configuration/nacos/index.html | 4 +-
.../v1.3/user/configuration/zookeeper/index.html | 4 +-
zh-cn/docs/v1.3/user/configurations/index.html | 4 +-
zh-cn/docs/v1.3/user/configurations090/index.html | 4 +-
zh-cn/docs/v1.3/user/configurations100/index.html | 4 +-
zh-cn/docs/v1.3/user/datasource/index.html | 4 +-
zh-cn/docs/v1.3/user/microservice/index.html | 4 +-
zh-cn/docs/v1.3/user/mode/at/index.html | 4 +-
zh-cn/docs/v1.3/user/mode/saga/index.html | 4 +-
zh-cn/docs/v1.3/user/mode/tcc/index.html | 4 +-
zh-cn/docs/v1.3/user/mode/xa/index.html | 4 +-
zh-cn/docs/v1.3/user/ormframework/index.html | 4 +-
zh-cn/docs/v1.3/user/performance/index.html | 4 +-
zh-cn/docs/v1.3/user/quickstart/index.html | 4 +-
zh-cn/docs/v1.3/user/registry/consul/index.html | 4 +-
zh-cn/docs/v1.3/user/registry/etcd3/index.html | 4 +-
zh-cn/docs/v1.3/user/registry/eureka/index.html | 4 +-
zh-cn/docs/v1.3/user/registry/index.html | 4 +-
zh-cn/docs/v1.3/user/registry/nacos/index.html | 4 +-
zh-cn/docs/v1.3/user/registry/zookeeper/index.html | 4 +-
zh-cn/docs/v1.3/user/spring/index.html | 4 +-
zh-cn/docs/v1.3/user/sqlreference/dml/index.html | 4 +-
.../v1.3/user/sqlreference/function/index.html | 4 +-
.../user/sqlreference/sql-decoration/index.html | 4 +-
.../user/sqlreference/sql-restrictions/index.html | 4 +-
.../txgroup/transaction-group-and-ha/index.html | 4 +-
.../v1.3/user/txgroup/transaction-group/index.html | 4 +-
.../v1.4/dev/domain/overviewDomainModel/index.html | 4 +-
zh-cn/docs/v1.4/dev/domain/rm/index.html | 4 +-
zh-cn/docs/v1.4/dev/domain/tc/index.html | 4 +-
zh-cn/docs/v1.4/dev/domain/tm/index.html | 4 +-
zh-cn/docs/v1.4/dev/mode/at-mode/index.html | 4 +-
zh-cn/docs/v1.4/dev/mode/saga-mode/index.html | 4 +-
zh-cn/docs/v1.4/dev/mode/tcc-mode/index.html | 4 +-
zh-cn/docs/v1.4/dev/mode/xa-mode/index.html | 4 +-
zh-cn/docs/v1.4/dev/seata-mertics/index.html | 4 +-
.../label-an-issue-guide_dev/index.html | 4 +-
.../committer-guide/website-guide_dev/index.html | 4 +-
.../top-contributer_dev/index.html | 4 +-
.../new-contributor-guide_dev/index.html | 4 +-
.../reporting-security-issues_dev/index.html | 4 +-
.../test-coverage-guide_dev/index.html | 4 +-
zh-cn/docs/v1.4/developers/guide_dev/index.html | 4 +-
zh-cn/docs/v1.4/ops/config-center/index.html | 4 +-
.../docs/v1.4/ops/deploy-by-docker-142/index.html | 4 +-
.../ops/deploy-by-docker-compose-142/index.html | 4 +-
.../v1.4/ops/deploy-by-docker-compose/index.html | 4 +-
zh-cn/docs/v1.4/ops/deploy-by-docker/index.html | 4 +-
zh-cn/docs/v1.4/ops/deploy-by-helm/index.html | 4 +-
.../docs/v1.4/ops/deploy-by-kubernetes/index.html | 4 +-
.../docs/v1.4/ops/deploy-guide-beginner/index.html | 4 +-
zh-cn/docs/v1.4/ops/deploy-ha/index.html | 4 +-
zh-cn/docs/v1.4/ops/deploy-server/index.html | 4 +-
.../ops/multi-configuration-isolation/index.html | 4 +-
zh-cn/docs/v1.4/ops/upgrade/index.html | 4 +-
zh-cn/docs/v1.4/overview/faq/index.html | 4 +-
zh-cn/docs/v1.4/overview/terminology/index.html | 4 +-
zh-cn/docs/v1.4/overview/what-is-seata/index.html | 4 +-
zh-cn/docs/v1.4/release-notes/index.html | 4 +-
zh-cn/docs/v1.4/user/api/index.html | 4 +-
zh-cn/docs/v1.4/user/apm/prometheus/index.html | 4 +-
zh-cn/docs/v1.4/user/apm/skywalking/index.html | 4 +-
.../appendix/global-transaction-status/index.html | 4 +-
zh-cn/docs/v1.4/user/appendix/isolation/index.html | 4 +-
.../docs/v1.4/user/configuration/apollo/index.html | 4 +-
.../docs/v1.4/user/configuration/consul/index.html | 4 +-
.../docs/v1.4/user/configuration/etcd3/index.html | 4 +-
zh-cn/docs/v1.4/user/configuration/index.html | 4 +-
.../docs/v1.4/user/configuration/nacos/index.html | 4 +-
.../v1.4/user/configuration/zookeeper/index.html | 4 +-
zh-cn/docs/v1.4/user/configurations/index.html | 4 +-
zh-cn/docs/v1.4/user/configurations090/index.html | 4 +-
zh-cn/docs/v1.4/user/configurations100/index.html | 4 +-
zh-cn/docs/v1.4/user/datasource/index.html | 4 +-
zh-cn/docs/v1.4/user/microservice/index.html | 4 +-
zh-cn/docs/v1.4/user/mode/at/index.html | 4 +-
zh-cn/docs/v1.4/user/mode/saga/index.html | 4 +-
zh-cn/docs/v1.4/user/mode/tcc/index.html | 4 +-
zh-cn/docs/v1.4/user/mode/xa/index.html | 4 +-
zh-cn/docs/v1.4/user/ormframework/index.html | 4 +-
zh-cn/docs/v1.4/user/performance/index.html | 4 +-
zh-cn/docs/v1.4/user/quickstart/index.html | 4 +-
zh-cn/docs/v1.4/user/registry/consul/index.html | 4 +-
zh-cn/docs/v1.4/user/registry/etcd3/index.html | 4 +-
zh-cn/docs/v1.4/user/registry/eureka/index.html | 4 +-
zh-cn/docs/v1.4/user/registry/index.html | 4 +-
zh-cn/docs/v1.4/user/registry/nacos/index.html | 4 +-
zh-cn/docs/v1.4/user/registry/zookeeper/index.html | 4 +-
zh-cn/docs/v1.4/user/spring/index.html | 4 +-
zh-cn/docs/v1.4/user/sqlreference/dml/index.html | 4 +-
.../v1.4/user/sqlreference/function/index.html | 4 +-
.../user/sqlreference/sql-decoration/index.html | 4 +-
.../user/sqlreference/sql-restrictions/index.html | 4 +-
.../txgroup/transaction-group-and-ha/index.html | 4 +-
.../v1.4/user/txgroup/transaction-group/index.html | 4 +-
.../v1.5/dev/domain/overviewDomainModel/index.html | 4 +-
zh-cn/docs/v1.5/dev/domain/rm/index.html | 4 +-
zh-cn/docs/v1.5/dev/domain/tc/index.html | 4 +-
zh-cn/docs/v1.5/dev/domain/tm/index.html | 4 +-
zh-cn/docs/v1.5/dev/mode/at-mode/index.html | 4 +-
zh-cn/docs/v1.5/dev/mode/saga-mode/index.html | 4 +-
zh-cn/docs/v1.5/dev/mode/tcc-mode/index.html | 4 +-
zh-cn/docs/v1.5/dev/mode/xa-mode/index.html | 4 +-
zh-cn/docs/v1.5/dev/seata-mertics/index.html | 4 +-
.../label-an-issue-guide_dev/index.html | 4 +-
.../committer-guide/website-guide_dev/index.html | 4 +-
.../top-contributer_dev/index.html | 4 +-
.../new-contributor-guide_dev/index.html | 4 +-
.../reporting-security-issues_dev/index.html | 4 +-
.../test-coverage-guide_dev/index.html | 4 +-
zh-cn/docs/v1.5/developers/guide_dev/index.html | 4 +-
zh-cn/docs/v1.5/ops/config-center/index.html | 4 +-
.../docs/v1.5/ops/deploy-by-docker-142/index.html | 4 +-
.../ops/deploy-by-docker-compose-142/index.html | 4 +-
.../v1.5/ops/deploy-by-docker-compose/index.html | 4 +-
zh-cn/docs/v1.5/ops/deploy-by-docker/index.html | 4 +-
zh-cn/docs/v1.5/ops/deploy-by-helm/index.html | 4 +-
.../docs/v1.5/ops/deploy-by-kubernetes/index.html | 4 +-
.../docs/v1.5/ops/deploy-guide-beginner/index.html | 4 +-
zh-cn/docs/v1.5/ops/deploy-ha/index.html | 4 +-
zh-cn/docs/v1.5/ops/deploy-server/index.html | 4 +-
.../ops/multi-configuration-isolation/index.html | 4 +-
zh-cn/docs/v1.5/ops/upgrade/index.html | 4 +-
zh-cn/docs/v1.5/overview/faq/index.html | 4 +-
zh-cn/docs/v1.5/overview/terminology/index.html | 4 +-
zh-cn/docs/v1.5/overview/what-is-seata/index.html | 4 +-
zh-cn/docs/v1.5/release-notes/index.html | 4 +-
zh-cn/docs/v1.5/user/api/index.html | 4 +-
zh-cn/docs/v1.5/user/apm/prometheus/index.html | 4 +-
zh-cn/docs/v1.5/user/apm/skywalking/index.html | 4 +-
.../appendix/global-transaction-status/index.html | 4 +-
zh-cn/docs/v1.5/user/appendix/isolation/index.html | 4 +-
.../docs/v1.5/user/configuration/apollo/index.html | 4 +-
.../docs/v1.5/user/configuration/consul/index.html | 4 +-
.../docs/v1.5/user/configuration/etcd3/index.html | 4 +-
zh-cn/docs/v1.5/user/configuration/index.html | 4 +-
.../docs/v1.5/user/configuration/nacos/index.html | 4 +-
.../v1.5/user/configuration/zookeeper/index.html | 4 +-
zh-cn/docs/v1.5/user/configurations/index.html | 4 +-
zh-cn/docs/v1.5/user/configurations090/index.html | 4 +-
zh-cn/docs/v1.5/user/configurations100/index.html | 4 +-
zh-cn/docs/v1.5/user/datasource/index.html | 4 +-
zh-cn/docs/v1.5/user/microservice/index.html | 4 +-
zh-cn/docs/v1.5/user/mode/at/index.html | 4 +-
zh-cn/docs/v1.5/user/mode/saga/index.html | 4 +-
zh-cn/docs/v1.5/user/mode/tcc/index.html | 4 +-
zh-cn/docs/v1.5/user/mode/xa/index.html | 4 +-
zh-cn/docs/v1.5/user/ormframework/index.html | 4 +-
zh-cn/docs/v1.5/user/performance/index.html | 4 +-
zh-cn/docs/v1.5/user/quickstart/index.html | 4 +-
zh-cn/docs/v1.5/user/registry/consul/index.html | 4 +-
zh-cn/docs/v1.5/user/registry/etcd3/index.html | 4 +-
zh-cn/docs/v1.5/user/registry/eureka/index.html | 4 +-
zh-cn/docs/v1.5/user/registry/index.html | 4 +-
zh-cn/docs/v1.5/user/registry/nacos/index.html | 4 +-
zh-cn/docs/v1.5/user/registry/zookeeper/index.html | 4 +-
zh-cn/docs/v1.5/user/spring/index.html | 4 +-
zh-cn/docs/v1.5/user/sqlreference/dml/index.html | 4 +-
.../v1.5/user/sqlreference/function/index.html | 4 +-
.../user/sqlreference/sql-decoration/index.html | 4 +-
.../user/sqlreference/sql-restrictions/index.html | 4 +-
.../txgroup/transaction-group-and-ha/index.html | 4 +-
.../v1.5/user/txgroup/transaction-group/index.html | 4 +-
.../v1.6/dev/domain/overviewDomainModel/index.html | 4 +-
zh-cn/docs/v1.6/dev/domain/rm/index.html | 4 +-
zh-cn/docs/v1.6/dev/domain/tc/index.html | 4 +-
zh-cn/docs/v1.6/dev/domain/tm/index.html | 4 +-
zh-cn/docs/v1.6/dev/mode/at-mode/index.html | 4 +-
zh-cn/docs/v1.6/dev/mode/saga-mode/index.html | 4 +-
zh-cn/docs/v1.6/dev/mode/tcc-mode/index.html | 4 +-
zh-cn/docs/v1.6/dev/mode/xa-mode/index.html | 4 +-
zh-cn/docs/v1.6/dev/seata-mertics/index.html | 4 +-
.../label-an-issue-guide_dev/index.html | 4 +-
.../committer-guide/website-guide_dev/index.html | 4 +-
.../top-contributer_dev/index.html | 4 +-
.../new-contributor-guide_dev/index.html | 4 +-
.../reporting-security-issues_dev/index.html | 4 +-
.../test-coverage-guide_dev/index.html | 4 +-
zh-cn/docs/v1.6/developers/guide_dev/index.html | 4 +-
zh-cn/docs/v1.6/ops/config-center/index.html | 4 +-
.../docs/v1.6/ops/deploy-by-docker-142/index.html | 4 +-
.../ops/deploy-by-docker-compose-142/index.html | 4 +-
.../v1.6/ops/deploy-by-docker-compose/index.html | 4 +-
zh-cn/docs/v1.6/ops/deploy-by-docker/index.html | 4 +-
zh-cn/docs/v1.6/ops/deploy-by-helm/index.html | 4 +-
.../docs/v1.6/ops/deploy-by-kubernetes/index.html | 4 +-
.../docs/v1.6/ops/deploy-guide-beginner/index.html | 4 +-
zh-cn/docs/v1.6/ops/deploy-ha/index.html | 4 +-
zh-cn/docs/v1.6/ops/deploy-server/index.html | 4 +-
.../ops/multi-configuration-isolation/index.html | 4 +-
zh-cn/docs/v1.6/ops/upgrade/index.html | 4 +-
zh-cn/docs/v1.6/overview/faq/index.html | 4 +-
zh-cn/docs/v1.6/overview/terminology/index.html | 4 +-
zh-cn/docs/v1.6/overview/what-is-seata/index.html | 4 +-
zh-cn/docs/v1.6/release-notes/index.html | 4 +-
zh-cn/docs/v1.6/user/api/index.html | 4 +-
zh-cn/docs/v1.6/user/apm/prometheus/index.html | 4 +-
zh-cn/docs/v1.6/user/apm/skywalking/index.html | 4 +-
.../appendix/global-transaction-status/index.html | 4 +-
zh-cn/docs/v1.6/user/appendix/isolation/index.html | 4 +-
.../docs/v1.6/user/configuration/apollo/index.html | 4 +-
.../docs/v1.6/user/configuration/consul/index.html | 4 +-
.../docs/v1.6/user/configuration/etcd3/index.html | 4 +-
zh-cn/docs/v1.6/user/configuration/index.html | 4 +-
.../docs/v1.6/user/configuration/nacos/index.html | 4 +-
.../v1.6/user/configuration/zookeeper/index.html | 4 +-
zh-cn/docs/v1.6/user/configurations/index.html | 4 +-
zh-cn/docs/v1.6/user/configurations090/index.html | 4 +-
zh-cn/docs/v1.6/user/configurations100/index.html | 4 +-
zh-cn/docs/v1.6/user/datasource/index.html | 4 +-
zh-cn/docs/v1.6/user/microservice/index.html | 4 +-
zh-cn/docs/v1.6/user/mode/at/index.html | 4 +-
zh-cn/docs/v1.6/user/mode/saga/index.html | 4 +-
zh-cn/docs/v1.6/user/mode/tcc/index.html | 4 +-
zh-cn/docs/v1.6/user/mode/xa/index.html | 4 +-
zh-cn/docs/v1.6/user/ormframework/index.html | 4 +-
zh-cn/docs/v1.6/user/performance/index.html | 4 +-
zh-cn/docs/v1.6/user/quickstart/index.html | 4 +-
zh-cn/docs/v1.6/user/registry/consul/index.html | 4 +-
zh-cn/docs/v1.6/user/registry/etcd3/index.html | 4 +-
zh-cn/docs/v1.6/user/registry/eureka/index.html | 4 +-
zh-cn/docs/v1.6/user/registry/index.html | 4 +-
zh-cn/docs/v1.6/user/registry/nacos/index.html | 4 +-
zh-cn/docs/v1.6/user/registry/zookeeper/index.html | 4 +-
zh-cn/docs/v1.6/user/spring/index.html | 4 +-
zh-cn/docs/v1.6/user/sqlreference/dml/index.html | 4 +-
.../v1.6/user/sqlreference/function/index.html | 4 +-
.../user/sqlreference/sql-decoration/index.html | 4 +-
.../user/sqlreference/sql-restrictions/index.html | 4 +-
.../txgroup/transaction-group-and-ha/index.html | 4 +-
.../v1.6/user/txgroup/transaction-group/index.html | 4 +-
.../v1.7/dev/domain/overviewDomainModel/index.html | 4 +-
zh-cn/docs/v1.7/dev/domain/rm/index.html | 4 +-
zh-cn/docs/v1.7/dev/domain/tc/index.html | 4 +-
zh-cn/docs/v1.7/dev/domain/tm/index.html | 4 +-
zh-cn/docs/v1.7/dev/mode/at-mode/index.html | 4 +-
zh-cn/docs/v1.7/dev/mode/saga-mode/index.html | 4 +-
zh-cn/docs/v1.7/dev/mode/tcc-mode/index.html | 4 +-
zh-cn/docs/v1.7/dev/mode/xa-mode/index.html | 4 +-
zh-cn/docs/v1.7/dev/seata-mertics/index.html | 4 +-
.../label-an-issue-guide_dev/index.html | 4 +-
.../committer-guide/website-guide_dev/index.html | 4 +-
.../top-contributer_dev/index.html | 4 +-
.../new-contributor-guide_dev/index.html | 4 +-
.../reporting-security-issues_dev/index.html | 4 +-
.../test-coverage-guide_dev/index.html | 4 +-
zh-cn/docs/v1.7/developers/guide_dev/index.html | 4 +-
zh-cn/docs/v1.7/ops/config-center/index.html | 4 +-
.../docs/v1.7/ops/deploy-by-docker-142/index.html | 4 +-
.../ops/deploy-by-docker-compose-142/index.html | 4 +-
.../v1.7/ops/deploy-by-docker-compose/index.html | 4 +-
zh-cn/docs/v1.7/ops/deploy-by-docker/index.html | 4 +-
zh-cn/docs/v1.7/ops/deploy-by-helm/index.html | 4 +-
.../docs/v1.7/ops/deploy-by-kubernetes/index.html | 4 +-
.../docs/v1.7/ops/deploy-guide-beginner/index.html | 4 +-
zh-cn/docs/v1.7/ops/deploy-ha/index.html | 4 +-
zh-cn/docs/v1.7/ops/deploy-server/index.html | 4 +-
.../ops/multi-configuration-isolation/index.html | 4 +-
zh-cn/docs/v1.7/ops/upgrade/index.html | 4 +-
zh-cn/docs/v1.7/overview/faq/index.html | 4 +-
zh-cn/docs/v1.7/overview/terminology/index.html | 4 +-
zh-cn/docs/v1.7/overview/what-is-seata/index.html | 4 +-
zh-cn/docs/v1.7/release-notes/index.html | 4 +-
zh-cn/docs/v1.7/user/api/index.html | 4 +-
zh-cn/docs/v1.7/user/apm/prometheus/index.html | 4 +-
zh-cn/docs/v1.7/user/apm/skywalking/index.html | 4 +-
.../appendix/global-transaction-status/index.html | 4 +-
zh-cn/docs/v1.7/user/appendix/isolation/index.html | 4 +-
.../docs/v1.7/user/configuration/apollo/index.html | 4 +-
.../docs/v1.7/user/configuration/consul/index.html | 4 +-
.../docs/v1.7/user/configuration/etcd3/index.html | 4 +-
zh-cn/docs/v1.7/user/configuration/index.html | 4 +-
.../docs/v1.7/user/configuration/nacos/index.html | 4 +-
.../v1.7/user/configuration/zookeeper/index.html | 4 +-
zh-cn/docs/v1.7/user/configurations/index.html | 4 +-
zh-cn/docs/v1.7/user/configurations090/index.html | 4 +-
zh-cn/docs/v1.7/user/configurations100/index.html | 4 +-
zh-cn/docs/v1.7/user/datasource/index.html | 4 +-
zh-cn/docs/v1.7/user/microservice/index.html | 4 +-
zh-cn/docs/v1.7/user/mode/at/index.html | 4 +-
zh-cn/docs/v1.7/user/mode/saga/index.html | 4 +-
zh-cn/docs/v1.7/user/mode/tcc/index.html | 4 +-
zh-cn/docs/v1.7/user/mode/xa/index.html | 4 +-
zh-cn/docs/v1.7/user/ormframework/index.html | 4 +-
zh-cn/docs/v1.7/user/performance/index.html | 4 +-
zh-cn/docs/v1.7/user/quickstart/index.html | 4 +-
zh-cn/docs/v1.7/user/registry/consul/index.html | 4 +-
zh-cn/docs/v1.7/user/registry/etcd3/index.html | 4 +-
zh-cn/docs/v1.7/user/registry/eureka/index.html | 4 +-
zh-cn/docs/v1.7/user/registry/index.html | 4 +-
zh-cn/docs/v1.7/user/registry/nacos/index.html | 4 +-
zh-cn/docs/v1.7/user/registry/zookeeper/index.html | 4 +-
zh-cn/docs/v1.7/user/spring/index.html | 4 +-
zh-cn/docs/v1.7/user/sqlreference/dml/index.html | 4 +-
.../v1.7/user/sqlreference/function/index.html | 4 +-
.../user/sqlreference/sql-decoration/index.html | 4 +-
.../user/sqlreference/sql-restrictions/index.html | 4 +-
.../txgroup/transaction-group-and-ha/index.html | 4 +-
.../v1.7/user/txgroup/transaction-group/index.html | 4 +-
.../v1.8/dev/domain/overviewDomainModel/index.html | 4 +-
zh-cn/docs/v1.8/dev/domain/rm/index.html | 4 +-
zh-cn/docs/v1.8/dev/domain/tc/index.html | 4 +-
zh-cn/docs/v1.8/dev/domain/tm/index.html | 4 +-
zh-cn/docs/v1.8/dev/mode/at-mode/index.html | 4 +-
zh-cn/docs/v1.8/dev/mode/saga-mode/index.html | 4 +-
zh-cn/docs/v1.8/dev/mode/tcc-mode/index.html | 4 +-
zh-cn/docs/v1.8/dev/mode/xa-mode/index.html | 4 +-
zh-cn/docs/v1.8/dev/seata-mertics/index.html | 4 +-
.../label-an-issue-guide_dev/index.html | 4 +-
.../committer-guide/website-guide_dev/index.html | 4 +-
.../top-contributer_dev/index.html | 4 +-
.../new-contributor-guide_dev/index.html | 4 +-
.../reporting-security-issues_dev/index.html | 4 +-
.../test-coverage-guide_dev/index.html | 4 +-
zh-cn/docs/v1.8/developers/guide_dev/index.html | 4 +-
zh-cn/docs/v1.8/ops/config-center/index.html | 4 +-
.../docs/v1.8/ops/deploy-by-docker-142/index.html | 4 +-
.../ops/deploy-by-docker-compose-142/index.html | 4 +-
.../v1.8/ops/deploy-by-docker-compose/index.html | 4 +-
zh-cn/docs/v1.8/ops/deploy-by-docker/index.html | 4 +-
zh-cn/docs/v1.8/ops/deploy-by-helm/index.html | 4 +-
.../docs/v1.8/ops/deploy-by-kubernetes/index.html | 4 +-
.../docs/v1.8/ops/deploy-guide-beginner/index.html | 4 +-
zh-cn/docs/v1.8/ops/deploy-ha/index.html | 4 +-
zh-cn/docs/v1.8/ops/deploy-server/index.html | 4 +-
.../ops/multi-configuration-isolation/index.html | 4 +-
zh-cn/docs/v1.8/ops/upgrade/index.html | 4 +-
zh-cn/docs/v1.8/overview/faq/index.html | 4 +-
zh-cn/docs/v1.8/overview/history/index.html | 4 +-
zh-cn/docs/v1.8/overview/terminology/index.html | 4 +-
zh-cn/docs/v1.8/overview/what-is-seata/index.html | 4 +-
zh-cn/docs/v1.8/release-notes/index.html | 4 +-
zh-cn/docs/v1.8/user/api/index.html | 4 +-
zh-cn/docs/v1.8/user/apm/prometheus/index.html | 4 +-
zh-cn/docs/v1.8/user/apm/skywalking/index.html | 4 +-
.../appendix/global-transaction-status/index.html | 4 +-
zh-cn/docs/v1.8/user/appendix/isolation/index.html | 4 +-
.../docs/v1.8/user/configuration/apollo/index.html | 4 +-
.../docs/v1.8/user/configuration/consul/index.html | 4 +-
.../docs/v1.8/user/configuration/etcd3/index.html | 4 +-
zh-cn/docs/v1.8/user/configuration/index.html | 4 +-
.../docs/v1.8/user/configuration/nacos/index.html | 4 +-
.../v1.8/user/configuration/zookeeper/index.html | 4 +-
zh-cn/docs/v1.8/user/configurations/index.html | 4 +-
zh-cn/docs/v1.8/user/configurations090/index.html | 4 +-
zh-cn/docs/v1.8/user/configurations100/index.html | 4 +-
zh-cn/docs/v1.8/user/datasource/index.html | 4 +-
zh-cn/docs/v1.8/user/microservice/index.html | 4 +-
zh-cn/docs/v1.8/user/mode/at/index.html | 4 +-
zh-cn/docs/v1.8/user/mode/saga/index.html | 4 +-
zh-cn/docs/v1.8/user/mode/tcc/index.html | 4 +-
zh-cn/docs/v1.8/user/mode/xa/index.html | 4 +-
zh-cn/docs/v1.8/user/ormframework/index.html | 4 +-
zh-cn/docs/v1.8/user/performance/index.html | 4 +-
zh-cn/docs/v1.8/user/quickstart/index.html | 4 +-
zh-cn/docs/v1.8/user/registry/consul/index.html | 4 +-
zh-cn/docs/v1.8/user/registry/etcd3/index.html | 4 +-
zh-cn/docs/v1.8/user/registry/eureka/index.html | 4 +-
zh-cn/docs/v1.8/user/registry/index.html | 4 +-
zh-cn/docs/v1.8/user/registry/nacos/index.html | 4 +-
zh-cn/docs/v1.8/user/registry/zookeeper/index.html | 4 +-
zh-cn/docs/v1.8/user/spring/index.html | 4 +-
zh-cn/docs/v1.8/user/sqlreference/dml/index.html | 4 +-
.../v1.8/user/sqlreference/function/index.html | 4 +-
.../user/sqlreference/sql-decoration/index.html | 4 +-
.../user/sqlreference/sql-restrictions/index.html | 4 +-
.../txgroup/transaction-group-and-ha/index.html | 4 +-
.../v1.8/user/txgroup/transaction-group/index.html | 4 +-
.../v2.0/dev/domain/overviewDomainModel/index.html | 4 +-
zh-cn/docs/v2.0/dev/domain/rm/index.html | 4 +-
zh-cn/docs/v2.0/dev/domain/tc/index.html | 4 +-
zh-cn/docs/v2.0/dev/domain/tm/index.html | 4 +-
zh-cn/docs/v2.0/dev/mode/at-mode/index.html | 4 +-
zh-cn/docs/v2.0/dev/mode/saga-mode/index.html | 4 +-
zh-cn/docs/v2.0/dev/mode/tcc-mode/index.html | 4 +-
zh-cn/docs/v2.0/dev/mode/xa-mode/index.html | 4 +-
zh-cn/docs/v2.0/dev/seata-mertics/index.html | 4 +-
.../label-an-issue-guide_dev/index.html | 4 +-
.../committer-guide/website-guide_dev/index.html | 4 +-
.../top-contributer_dev/index.html | 4 +-
.../new-contributor-guide_dev/index.html | 4 +-
.../reporting-security-issues_dev/index.html | 4 +-
.../test-coverage-guide_dev/index.html | 4 +-
zh-cn/docs/v2.0/developers/guide_dev/index.html | 4 +-
zh-cn/docs/v2.0/ops/config-center/index.html | 4 +-
.../docs/v2.0/ops/deploy-by-docker-142/index.html | 4 +-
.../ops/deploy-by-docker-compose-142/index.html | 4 +-
.../v2.0/ops/deploy-by-docker-compose/index.html | 4 +-
zh-cn/docs/v2.0/ops/deploy-by-docker/index.html | 4 +-
zh-cn/docs/v2.0/ops/deploy-by-helm/index.html | 4 +-
.../docs/v2.0/ops/deploy-by-kubernetes/index.html | 4 +-
.../docs/v2.0/ops/deploy-guide-beginner/index.html | 4 +-
zh-cn/docs/v2.0/ops/deploy-ha/index.html | 4 +-
zh-cn/docs/v2.0/ops/deploy-server-raft/index.html | 4 +-
zh-cn/docs/v2.0/ops/deploy-server/index.html | 4 +-
.../ops/multi-configuration-isolation/index.html | 4 +-
zh-cn/docs/v2.0/ops/upgrade/index.html | 4 +-
.../docs/v2.0/ops/version-maintain-plan/index.html | 4 +-
zh-cn/docs/v2.0/overview/faq/index.html | 4 +-
zh-cn/docs/v2.0/overview/history/index.html | 4 +-
zh-cn/docs/v2.0/overview/terminology/index.html | 4 +-
zh-cn/docs/v2.0/overview/what-is-seata/index.html | 4 +-
zh-cn/docs/v2.0/release-notes/index.html | 4 +-
zh-cn/docs/v2.0/user/api/index.html | 4 +-
zh-cn/docs/v2.0/user/apm/prometheus/index.html | 4 +-
zh-cn/docs/v2.0/user/apm/skywalking/index.html | 4 +-
.../appendix/global-transaction-status/index.html | 4 +-
zh-cn/docs/v2.0/user/appendix/isolation/index.html | 4 +-
.../docs/v2.0/user/configuration/apollo/index.html | 4 +-
.../docs/v2.0/user/configuration/consul/index.html | 4 +-
.../docs/v2.0/user/configuration/etcd3/index.html | 4 +-
zh-cn/docs/v2.0/user/configuration/index.html | 4 +-
.../docs/v2.0/user/configuration/nacos/index.html | 4 +-
.../v2.0/user/configuration/zookeeper/index.html | 4 +-
zh-cn/docs/v2.0/user/configurations/index.html | 4 +-
zh-cn/docs/v2.0/user/configurations090/index.html | 4 +-
zh-cn/docs/v2.0/user/configurations100/index.html | 4 +-
zh-cn/docs/v2.0/user/datasource/index.html | 4 +-
zh-cn/docs/v2.0/user/microservice/index.html | 4 +-
zh-cn/docs/v2.0/user/mode/at/index.html | 4 +-
zh-cn/docs/v2.0/user/mode/saga/index.html | 4 +-
zh-cn/docs/v2.0/user/mode/tcc/index.html | 4 +-
zh-cn/docs/v2.0/user/mode/xa/index.html | 4 +-
zh-cn/docs/v2.0/user/ormframework/index.html | 4 +-
zh-cn/docs/v2.0/user/performance/index.html | 4 +-
zh-cn/docs/v2.0/user/quickstart/index.html | 4 +-
zh-cn/docs/v2.0/user/registry/consul/index.html | 4 +-
zh-cn/docs/v2.0/user/registry/etcd3/index.html | 4 +-
zh-cn/docs/v2.0/user/registry/eureka/index.html | 4 +-
zh-cn/docs/v2.0/user/registry/index.html | 4 +-
zh-cn/docs/v2.0/user/registry/nacos/index.html | 4 +-
zh-cn/docs/v2.0/user/registry/zookeeper/index.html | 4 +-
zh-cn/docs/v2.0/user/spring/index.html | 4 +-
zh-cn/docs/v2.0/user/sqlreference/dml/index.html | 4 +-
.../v2.0/user/sqlreference/function/index.html | 4 +-
.../user/sqlreference/sql-decoration/index.html | 4 +-
.../user/sqlreference/sql-restrictions/index.html | 4 +-
.../txgroup/transaction-group-and-ha/index.html | 4 +-
.../v2.0/user/txgroup/transaction-group/index.html | 4 +-
.../v2.1/dev/domain/overviewDomainModel/index.html | 4 +-
zh-cn/docs/v2.1/dev/domain/rm/index.html | 4 +-
zh-cn/docs/v2.1/dev/domain/tc/index.html | 4 +-
zh-cn/docs/v2.1/dev/domain/tm/index.html | 4 +-
zh-cn/docs/v2.1/dev/mode/at-mode/index.html | 4 +-
zh-cn/docs/v2.1/dev/mode/saga-mode/index.html | 4 +-
zh-cn/docs/v2.1/dev/mode/tcc-mode/index.html | 4 +-
zh-cn/docs/v2.1/dev/mode/xa-mode/index.html | 4 +-
zh-cn/docs/v2.1/dev/seata-mertics/index.html | 4 +-
.../label-an-issue-guide_dev/index.html | 4 +-
.../committer-guide/website-guide_dev/index.html | 4 +-
.../top-contributer_dev/index.html | 4 +-
.../new-contributor-guide_dev/index.html | 4 +-
.../reporting-security-issues_dev/index.html | 4 +-
.../test-coverage-guide_dev/index.html | 4 +-
zh-cn/docs/v2.1/developers/guide_dev/index.html | 4 +-
zh-cn/docs/v2.1/ops/config-center/index.html | 4 +-
.../docs/v2.1/ops/deploy-by-docker-142/index.html | 4 +-
.../ops/deploy-by-docker-compose-142/index.html | 4 +-
.../v2.1/ops/deploy-by-docker-compose/index.html | 4 +-
zh-cn/docs/v2.1/ops/deploy-by-docker/index.html | 4 +-
zh-cn/docs/v2.1/ops/deploy-by-helm/index.html | 4 +-
.../docs/v2.1/ops/deploy-by-kubernetes/index.html | 4 +-
.../docs/v2.1/ops/deploy-guide-beginner/index.html | 4 +-
zh-cn/docs/v2.1/ops/deploy-ha/index.html | 4 +-
zh-cn/docs/v2.1/ops/deploy-server-raft/index.html | 4 +-
zh-cn/docs/v2.1/ops/deploy-server/index.html | 4 +-
.../ops/multi-configuration-isolation/index.html | 4 +-
zh-cn/docs/v2.1/ops/upgrade/index.html | 4 +-
.../docs/v2.1/ops/version-maintain-plan/index.html | 4 +-
zh-cn/docs/v2.1/overview/faq/index.html | 4 +-
zh-cn/docs/v2.1/overview/history/index.html | 4 +-
zh-cn/docs/v2.1/overview/terminology/index.html | 4 +-
zh-cn/docs/v2.1/overview/what-is-seata/index.html | 4 +-
zh-cn/docs/v2.1/release-notes/index.html | 4 +-
zh-cn/docs/v2.1/user/api/index.html | 4 +-
zh-cn/docs/v2.1/user/apm/prometheus/index.html | 4 +-
zh-cn/docs/v2.1/user/apm/skywalking/index.html | 4 +-
.../appendix/global-transaction-status/index.html | 4 +-
zh-cn/docs/v2.1/user/appendix/isolation/index.html | 4 +-
.../docs/v2.1/user/configuration/apollo/index.html | 4 +-
.../docs/v2.1/user/configuration/consul/index.html | 4 +-
.../docs/v2.1/user/configuration/etcd3/index.html | 4 +-
zh-cn/docs/v2.1/user/configuration/index.html | 4 +-
.../docs/v2.1/user/configuration/nacos/index.html | 4 +-
.../v2.1/user/configuration/zookeeper/index.html | 4 +-
zh-cn/docs/v2.1/user/configurations/index.html | 4 +-
zh-cn/docs/v2.1/user/configurations090/index.html | 4 +-
zh-cn/docs/v2.1/user/configurations100/index.html | 4 +-
zh-cn/docs/v2.1/user/datasource/index.html | 4 +-
zh-cn/docs/v2.1/user/microservice/index.html | 4 +-
zh-cn/docs/v2.1/user/mode/at/index.html | 4 +-
zh-cn/docs/v2.1/user/mode/saga/index.html | 4 +-
zh-cn/docs/v2.1/user/mode/tcc/index.html | 4 +-
zh-cn/docs/v2.1/user/mode/xa/index.html | 4 +-
zh-cn/docs/v2.1/user/ormframework/index.html | 4 +-
zh-cn/docs/v2.1/user/performance/index.html | 4 +-
zh-cn/docs/v2.1/user/quickstart/index.html | 4 +-
zh-cn/docs/v2.1/user/registry/consul/index.html | 4 +-
zh-cn/docs/v2.1/user/registry/etcd3/index.html | 4 +-
zh-cn/docs/v2.1/user/registry/eureka/index.html | 4 +-
zh-cn/docs/v2.1/user/registry/index.html | 4 +-
zh-cn/docs/v2.1/user/registry/nacos/index.html | 4 +-
zh-cn/docs/v2.1/user/registry/zookeeper/index.html | 4 +-
zh-cn/docs/v2.1/user/spring/index.html | 4 +-
zh-cn/docs/v2.1/user/sqlreference/dml/index.html | 4 +-
.../v2.1/user/sqlreference/function/index.html | 4 +-
.../user/sqlreference/sql-decoration/index.html | 4 +-
.../user/sqlreference/sql-restrictions/index.html | 4 +-
.../txgroup/transaction-group-and-ha/index.html | 4 +-
.../v2.1/user/txgroup/transaction-group/index.html | 4 +-
zh-cn/home/feature/index.html | 4 +-
zh-cn/home/introduction/index.html | 4 +-
zh-cn/home/top/index.html | 4 +-
zh-cn/img/blog/2024121301.png | Bin 0 -> 365111 bytes
zh-cn/img/blog/2024121302.png | Bin 0 -> 318738 bytes
zh-cn/img/blog/2024121303.png | Bin 0 -> 419640 bytes
zh-cn/img/blog/2024121304.png | Bin 0 -> 413464 bytes
zh-cn/img/blog/2024121305.png | Bin 0 -> 358454 bytes
zh-cn/img/blog/2024121306.jpeg | Bin 0 -> 92986 bytes
zh-cn/index.html | 4 +-
zh-cn/markdown-page/index.html | 4 +-
zh-cn/search/index.html | 4 +-
zh-cn/solution/index.html | 4 +-
zh-cn/unversioned/download/seata-server/index.html | 4 +-
.../release-history/seata-server/index.html | 4 +-
zh-cn/users/index.html | 4 +-
4073 files changed, 13172 insertions(+), 12863 deletions(-)
diff --git a/assets/images/2024121301-4613ead894d7510e65d88296eb86e297.png b/assets/images/2024121301-4613ead894d7510e65d88296eb86e297.png
new file mode 100644
index 00000000000..3856775cc08
Binary files /dev/null and b/assets/images/2024121301-4613ead894d7510e65d88296eb86e297.png differ
diff --git a/assets/images/2024121302-39625f525d6da1bbc7ad4509c94718eb.png b/assets/images/2024121302-39625f525d6da1bbc7ad4509c94718eb.png
new file mode 100644
index 00000000000..1e0be016c37
Binary files /dev/null and b/assets/images/2024121302-39625f525d6da1bbc7ad4509c94718eb.png differ
diff --git a/assets/images/2024121303-bad6bb1db830335d72e2037ea7dbf4de.png b/assets/images/2024121303-bad6bb1db830335d72e2037ea7dbf4de.png
new file mode 100644
index 00000000000..e15065568f6
Binary files /dev/null and b/assets/images/2024121303-bad6bb1db830335d72e2037ea7dbf4de.png differ
diff --git a/assets/images/2024121304-fcc9119043d66143a841d2008ef136f5.png b/assets/images/2024121304-fcc9119043d66143a841d2008ef136f5.png
new file mode 100644
index 00000000000..77c070ea486
Binary files /dev/null and b/assets/images/2024121304-fcc9119043d66143a841d2008ef136f5.png differ
diff --git a/assets/images/2024121305-327ecb450c5fd7f7fc636165421972b2.png b/assets/images/2024121305-327ecb450c5fd7f7fc636165421972b2.png
new file mode 100644
index 00000000000..577930adac9
Binary files /dev/null and b/assets/images/2024121305-327ecb450c5fd7f7fc636165421972b2.png differ
diff --git a/assets/images/2024121306-5568d956a86d67c43e4d76837dd5c8b8.jpeg b/assets/images/2024121306-5568d956a86d67c43e4d76837dd5c8b8.jpeg
new file mode 100644
index 00000000000..809ef714268
Binary files /dev/null and b/assets/images/2024121306-5568d956a86d67c43e4d76837dd5c8b8.jpeg differ
diff --git a/assets/js/11ce4159.9318726b.js b/assets/js/11ce4159.9318726b.js
new file mode 100644
index 00000000000..538949b4d11
--- /dev/null
+++ b/assets/js/11ce4159.9318726b.js
@@ -0,0 +1 @@
+"use strict";(self.webpackChunkseata_website=self.webpackChunkseata_website||[]).push([[11194],{18225:e=>{e.exports=JSON.parse('{"permalink":"/blog/page/5","page":5,"postsPerPage":10,"totalPages":7,"totalCount":62,"previousPage":"/blog/page/4","nextPage":"/blog/page/6","blogDescription":"Blog","blogTitle":"Blog"}')}}]);
\ No newline at end of file
diff --git a/assets/js/1dc3c500.ea283c57.js b/assets/js/1dc3c500.ea283c57.js
new file mode 100644
index 00000000000..9d264ffb6a3
--- /dev/null
+++ b/assets/js/1dc3c500.ea283c57.js
@@ -0,0 +1 @@
+"use strict";(self.webpackChunkseata_website=self.webpackChunkseata_website||[]).push([[49146],{35305:(e,n,i)=>{i.r(n),i.d(n,{assets:()=>c,contentTitle:()=>o,default:()=>h,frontMatter:()=>r,metadata:()=>s,toc:()=>l});var t=i(74848),a=i(28453);const r={title:"Seata Raft Configuration Center",author:"JiangYichen - Tsinghua University, participant in Seata Summer of Code",description:"In this blog, I will share the Seata Configuration Center based on Raft and RocksDB design and how it is us [...]
\ No newline at end of file
diff --git a/assets/js/2d6322e8.0f290bfd.js b/assets/js/2d6322e8.0f290bfd.js
new file mode 100644
index 00000000000..f6693b71953
--- /dev/null
+++ b/assets/js/2d6322e8.0f290bfd.js
@@ -0,0 +1 @@
+"use strict";(self.webpackChunkseata_website=self.webpackChunkseata_website||[]).push([[38127],{89120:(e,t,n)=>{n.r(t),n.d(t,{assets:()=>i,contentTitle:()=>s,default:()=>m,frontMatter:()=>o,metadata:()=>c,toc:()=>u});var a=n(74848),r=n(28453);const o={},s=void 0,c={permalink:"/blog/seata-namingserver",editUrl:"https://github.com/apache/incubator-seata-website/blob/docusaurus/blog/seata-namingserver.md",source:"@site/blog/seata-namingserver.md",title:"seata-namingserver",description:"Plac [...]
\ No newline at end of file
diff --git a/assets/js/44ac4dbb.8a588fe0.js b/assets/js/44ac4dbb.8a588fe0.js
new file mode 100644
index 00000000000..794363c4519
--- /dev/null
+++ b/assets/js/44ac4dbb.8a588fe0.js
@@ -0,0 +1 @@
+"use strict";(self.webpackChunkseata_website=self.webpackChunkseata_website||[]).push([[43431],{89189:e=>{e.exports=JSON.parse('{"permalink":"/blog/page/6","page":6,"postsPerPage":10,"totalPages":7,"totalCount":62,"previousPage":"/blog/page/5","nextPage":"/blog/page/7","blogDescription":"Blog","blogTitle":"Blog"}')}}]);
\ No newline at end of file
diff --git a/assets/js/52099127.5f140573.js b/assets/js/52099127.5f140573.js
new file mode 100644
index 00000000000..4c2d805640f
--- /dev/null
+++ b/assets/js/52099127.5f140573.js
@@ -0,0 +1 @@
+"use strict";(self.webpackChunkseata_website=self.webpackChunkseata_website||[]).push([[76204],{93031:e=>{e.exports=JSON.parse('{"permalink":"/blog/page/7","page":7,"postsPerPage":10,"totalPages":7,"totalCount":62,"previousPage":"/blog/page/6","blogDescription":"Blog","blogTitle":"Blog"}')}}]);
\ No newline at end of file
diff --git a/assets/js/5c941569.831d6e25.js b/assets/js/5c941569.831d6e25.js
new file mode 100644
index 00000000000..a2ffd2266f7
--- /dev/null
+++ b/assets/js/5c941569.831d6e25.js
@@ -0,0 +1 @@
+"use strict";(self.webpackChunkseata_website=self.webpackChunkseata_website||[]).push([[42193],{72780:(e,t,n)=>{n.r(t),n.d(t,{assets:()=>i,contentTitle:()=>s,default:()=>m,frontMatter:()=>o,metadata:()=>c,toc:()=>u});var a=n(74848),r=n(28453);const o={},s=void 0,c={permalink:"/blog/seata-namingserver",editUrl:"https://github.com/apache/incubator-seata-website/blob/docusaurus/blog/seata-namingserver.md",source:"@site/blog/seata-namingserver.md",title:"seata-namingserver",description:"Plac [...]
\ No newline at end of file
diff --git a/assets/js/7d9726a8.2f524a19.js b/assets/js/7d9726a8.2f524a19.js
new file mode 100644
index 00000000000..00b5e8139af
--- /dev/null
+++ b/assets/js/7d9726a8.2f524a19.js
@@ -0,0 +1 @@
+"use strict";(self.webpackChunkseata_website=self.webpackChunkseata_website||[]).push([[10469],{51396:e=>{e.exports=JSON.parse('{"permalink":"/blog/page/4","page":4,"postsPerPage":10,"totalPages":7,"totalCount":62,"previousPage":"/blog/page/3","nextPage":"/blog/page/5","blogDescription":"Blog","blogTitle":"Blog"}')}}]);
\ No newline at end of file
diff --git a/assets/js/814f3328.42bfeb1c.js b/assets/js/814f3328.42bfeb1c.js
new file mode 100644
index 00000000000..9e019bbad50
--- /dev/null
+++ b/assets/js/814f3328.42bfeb1c.js
@@ -0,0 +1 @@
+"use strict";(self.webpackChunkseata_website=self.webpackChunkseata_website||[]).push([[67472],{55513:e=>{e.exports=JSON.parse('{"title":"All Posts","items":[{"title":"seata-namingserver","permalink":"/blog/seata-namingserver","unlisted":false},{"title":"Go Language Client Communication with Seata Server","permalink":"/blog/seata-grpc-client","unlisted":false},{"title":"Seata Raft Configuration Center","permalink":"/blog/seata-raft-config-center","unlisted":false},{"title":"Seata\'s RPC [...]
\ No newline at end of file
diff --git a/assets/js/8eb4e46b.acb9610d.js b/assets/js/8eb4e46b.acb9610d.js
new file mode 100644
index 00000000000..500cf3af9d9
--- /dev/null
+++ b/assets/js/8eb4e46b.acb9610d.js
@@ -0,0 +1 @@
+"use strict";(self.webpackChunkseata_website=self.webpackChunkseata_website||[]).push([[65767],{20541:e=>{e.exports=JSON.parse('{"permalink":"/blog/page/2","page":2,"postsPerPage":10,"totalPages":7,"totalCount":62,"previousPage":"/blog","nextPage":"/blog/page/3","blogDescription":"Blog","blogTitle":"Blog"}')}}]);
\ No newline at end of file
diff --git a/assets/js/8f32d218.e50ccc03.js b/assets/js/8f32d218.e50ccc03.js
new file mode 100644
index 00000000000..f3d49452315
--- /dev/null
+++ b/assets/js/8f32d218.e50ccc03.js
@@ -0,0 +1 @@
+"use strict";(self.webpackChunkseata_website=self.webpackChunkseata_website||[]).push([[44071],{94351:(e,n,t)=>{t.r(n),t.d(n,{assets:()=>c,contentTitle:()=>i,default:()=>p,frontMatter:()=>r,metadata:()=>s,toc:()=>l});var a=t(74848),o=t(28453);const r={title:"Go Language Client Communication with Seata Server",author:"Wang Mingjun, Seata Open Source Summer Student Participant",description:"This article takes Go language as an example to demonstrate Seata's multi-language client communicat [...]
\ No newline at end of file
diff --git a/assets/js/92999a1c.3f3d9d67.js b/assets/js/92999a1c.3f3d9d67.js
new file mode 100644
index 00000000000..cd12fe56527
--- /dev/null
+++ b/assets/js/92999a1c.3f3d9d67.js
@@ -0,0 +1 @@
+"use strict";(self.webpackChunkseata_website=self.webpackChunkseata_website||[]).push([[18790],{81116:e=>{e.exports=JSON.parse('{"permalink":"/blog/page/3","page":3,"postsPerPage":10,"totalPages":7,"totalCount":62,"previousPage":"/blog/page/2","nextPage":"/blog/page/4","blogDescription":"Blog","blogTitle":"Blog"}')}}]);
\ No newline at end of file
diff --git a/assets/js/b2b675dd.8bb91942.js b/assets/js/b2b675dd.8bb91942.js
new file mode 100644
index 00000000000..0d8dafce0d0
--- /dev/null
+++ b/assets/js/b2b675dd.8bb91942.js
@@ -0,0 +1 @@
+"use strict";(self.webpackChunkseata_website=self.webpackChunkseata_website||[]).push([[11991],{29775:e=>{e.exports=JSON.parse('{"permalink":"/blog","page":1,"postsPerPage":10,"totalPages":7,"totalCount":62,"nextPage":"/blog/page/2","blogDescription":"Blog","blogTitle":"Blog"}')}}]);
\ No newline at end of file
diff --git a/assets/js/b2f554cd.9ea9c4f0.js b/assets/js/b2f554cd.9ea9c4f0.js
new file mode 100644
index 00000000000..8106a6c30e9
--- /dev/null
+++ b/assets/js/b2f554cd.9ea9c4f0.js
@@ -0,0 +1 @@
+"use strict";(self.webpackChunkseata_website=self.webpackChunkseata_website||[]).push([[95894],{76042:e=>{e.exports=JSON.parse('{"blogPosts":[{"id":"/seata-namingserver","metadata":{"permalink":"/blog/seata-namingserver","editUrl":"https://github.com/apache/incubator-seata-website/blob/docusaurus/blog/seata-namingserver.md","source":"@site/blog/seata-namingserver.md","title":"seata-namingserver","description":"Placeholder. DO NOT DELETE.","date":"2024-12-13T16:25:48.000Z","formattedDate" [...]
\ No newline at end of file
diff --git a/assets/js/d1400855.24cc561c.js b/assets/js/d1400855.24cc561c.js
new file mode 100644
index 00000000000..d0a259205cd
--- /dev/null
+++ b/assets/js/d1400855.24cc561c.js
@@ -0,0 +1 @@
+"use strict";(self.webpackChunkseata_website=self.webpackChunkseata_website||[]).push([[86616],{58071:(e,n,i)=>{i.r(n),i.d(n,{assets:()=>c,contentTitle:()=>o,default:()=>h,frontMatter:()=>r,metadata:()=>s,toc:()=>l});var t=i(74848),a=i(28453);const r={title:"Seata Raft Configuration Center",author:"JiangYichen - Tsinghua University, participant in Seata Summer of Code",description:"In this blog, I will share the Seata Configuration Center based on Raft and RocksDB design and how it is us [...]
\ No newline at end of file
diff --git a/assets/js/ef915a9a.5686e2ca.js b/assets/js/ef915a9a.5686e2ca.js
new file mode 100644
index 00000000000..919f1f9e53b
--- /dev/null
+++ b/assets/js/ef915a9a.5686e2ca.js
@@ -0,0 +1 @@
+"use strict";(self.webpackChunkseata_website=self.webpackChunkseata_website||[]).push([[23128],{2285:(e,n,t)=>{t.r(n),t.d(n,{assets:()=>c,contentTitle:()=>i,default:()=>p,frontMatter:()=>r,metadata:()=>s,toc:()=>l});var a=t(74848),o=t(28453);const r={title:"Go Language Client Communication with Seata Server",author:"Wang Mingjun, Seata Open Source Summer Student Participant",description:"This article takes Go language as an example to demonstrate Seata's multi-language client communicati [...]
\ No newline at end of file
diff --git a/assets/js/main.aeea7339.js b/assets/js/main.aeea7339.js
new file mode 100644
index 00000000000..ea66dee3109
--- /dev/null
+++ b/assets/js/main.aeea7339.js
@@ -0,0 +1,2 @@
+/*! For license information please see main.aeea7339.js.LICENSE.txt */
+(self.webpackChunkseata_website=self.webpackChunkseata_website||[]).push([[38792],{89188:(e,o,t)=>{"use strict";t.d(o,{W:()=>s});var n=t(96540);function s(){return n.createElement("svg",{width:"20",height:"20",className:"DocSearch-Search-Icon",viewBox:"0 0 20 20"},n.createElement("path",{d:"M14.386 14.386l4.0877 4.0877-4.0877-4.0877c-2.9418 2.9419-7.7115 2.9419-10.6533 0-2.9419-2.9418-2.9419-7.7115 0-10.6533 2.9418-2.9419 7.7115-2.9419 10.6533 0 2.9419 2.9418 2.9419 7.7115 0 10.6533z",st [...]
\ No newline at end of file
diff --git a/assets/js/main.aeea7339.js.LICENSE.txt b/assets/js/main.aeea7339.js.LICENSE.txt
new file mode 100644
index 00000000000..91dc8949981
--- /dev/null
+++ b/assets/js/main.aeea7339.js.LICENSE.txt
@@ -0,0 +1,64 @@
+/* NProgress, (c) 2013, 2014 Rico Sta. Cruz - http://ricostacruz.com/nprogress
+ * @license MIT */
+
+/*! Bundled license information:
+
+prismjs/prism.js:
+ (**
+ * Prism: Lightweight, robust, elegant syntax highlighting
+ *
+ * @license MIT <https://opensource.org/licenses/MIT>
+ * @author Lea Verou <https://lea.verou.me>
+ * @namespace
+ * @public
+ *)
+*/
+
+/**
+ * @license React
+ * react-dom.production.min.js
+ *
+ * Copyright (c) Facebook, Inc. and its affiliates.
+ *
+ * This source code is licensed under the MIT license found in the
+ * LICENSE file in the root directory of this source tree.
+ */
+
+/**
+ * @license React
+ * react-jsx-runtime.production.min.js
+ *
+ * Copyright (c) Facebook, Inc. and its affiliates.
+ *
+ * This source code is licensed under the MIT license found in the
+ * LICENSE file in the root directory of this source tree.
+ */
+
+/**
+ * @license React
+ * react.production.min.js
+ *
+ * Copyright (c) Facebook, Inc. and its affiliates.
+ *
+ * This source code is licensed under the MIT license found in the
+ * LICENSE file in the root directory of this source tree.
+ */
+
+/**
+ * @license React
+ * scheduler.production.min.js
+ *
+ * Copyright (c) Facebook, Inc. and its affiliates.
+ *
+ * This source code is licensed under the MIT license found in the
+ * LICENSE file in the root directory of this source tree.
+ */
+
+/** @license React v16.13.1
+ * react-is.production.min.js
+ *
+ * Copyright (c) Facebook, Inc. and its affiliates.
+ *
+ * This source code is licensed under the MIT license found in the
+ * LICENSE file in the root directory of this source tree.
+ */
diff --git a/assets/js/runtime~main.762ed5c0.js b/assets/js/runtime~main.762ed5c0.js
new file mode 100644
index 00000000000..7c8920e5906
--- /dev/null
+++ b/assets/js/runtime~main.762ed5c0.js
@@ -0,0 +1 @@
+(()=>{"use strict";var e,c,b,f,a,d={},t={};function r(e){var c=t[e];if(void 0!==c)return c.exports;var b=t[e]={exports:{}};return d[e].call(b.exports,b,b.exports,r),b.exports}r.m=d,e=[],r.O=(c,b,f,a)=>{if(!b){var d=1/0;for(i=0;i<e.length;i++){b=e[i][0],f=e[i][1],a=e[i][2];for(var t=!0,o=0;o<b.length;o++)(!1&a||d>=a)&&Object.keys(r.O).every((e=>r.O[e](b[o])))?b.splice(o--,1):(t=!1,a<d&&(d=a));if(t){e.splice(i--,1);var n=f();void 0!==n&&(c=n)}}return c}a=a||0;for(var i=e.length;i>0&&e[i-1] [...]
\ No newline at end of file
diff --git a/blog/archive/index.html b/blog/archive/index.html
index b39d1e02c13..584f7cc9547 100644
--- a/blog/archive/index.html
+++ b/blog/archive/index.html
@@ -11,11 +11,11 @@
<meta name="aes-config" content="pid=xux-opensource&user_type=101&uid=&username=&dim10=seata"><link rel="stylesheet" href="/assets/css/styles.9644caf2.css">
-<script src="/assets/js/runtime~main.bf98ee01.js" defer="defer"></script>
-<script src="/assets/js/main.8371dd70.js" defer="defer"></script>
+<script src="/assets/js/runtime~main.762ed5c0.js" defer="defer"></script>
+<script src="/assets/js/main.aeea7339.js" defer="defer"></script>
</head>
<body class="navigation-with-keyboard">
-<script>!function(){function t(t){document.documentElement.setAttribute("data-theme",t)}var e=function(){try{return new URLSearchParams(window.location.search).get("docusaurus-theme")}catch(t){}}()||function(){try{return localStorage.getItem("theme")}catch(t){}}();t(null!==e?e:"light")}(),function(){try{const c=new URLSearchParams(window.location.search).entries();for(var[t,e]of c)if(t.startsWith("docusaurus-data-")){var a=t.replace("docusaurus-data-","data-");document.documentElement.se [...]
+<script>!function(){function t(t){document.documentElement.setAttribute("data-theme",t)}var e=function(){try{return new URLSearchParams(window.location.search).get("docusaurus-theme")}catch(t){}}()||function(){try{return localStorage.getItem("theme")}catch(t){}}();t(null!==e?e:"light")}(),function(){try{const c=new URLSearchParams(window.location.search).entries();for(var[t,e]of c)if(t.startsWith("docusaurus-data-")){var a=t.replace("docusaurus-data-","data-");document.documentElement.se [...]
<div class="fs-12">
<div class="center-div">
<span>Apache Seata (incubating) is an effort undergoing incubation at The Apache Software Foundation (ASF), sponsored by the Apache Incubator. Incubation is required of all newly accepted projects until a further review indicates that the infrastructure, communications, and decision making process have stabilized in a manner consistent with other successful ASF projects. While incubation status is not necessarily a reflection of the completeness or stability of the [...]
diff --git a/blog/atom.xml b/blog/atom.xml
index 890dfeb8c43..36fa5640e93 100644
--- a/blog/atom.xml
+++ b/blog/atom.xml
@@ -2,7 +2,7 @@
<feed xmlns="http://www.w3.org/2005/Atom">
<id>https://seata.apache.org/blog</id>
<title>Apache Seata Blog</title>
- <updated>2024-11-26T03:53:20.000Z</updated>
+ <updated>2024-12-13T16:25:48.000Z</updated>
<generator>https://github.com/jpmonette/feed</generator>
<link rel="alternate" href="https://seata.apache.org/blog"/>
<subtitle>Apache Seata Blog</subtitle>
@@ -11,10 +11,65 @@
<title type="html"><![CDATA[seata-namingserver]]></title>
<id>https://seata.apache.org/blog/seata-namingserver</id>
<link href="https://seata.apache.org/blog/seata-namingserver"/>
- <updated>2024-11-26T03:53:20.000Z</updated>
+ <updated>2024-12-13T16:25:48.000Z</updated>
<summary type="html"><![CDATA[Placeholder. DO NOT DELETE.]]></summary>
<content type="html"><![CDATA[<p>Placeholder. DO NOT DELETE.</p>]]></content>
</entry>
+ <entry>
+ <title type="html"><![CDATA[Go Language Client Communication with Seata Server]]></title>
+ <id>https://seata.apache.org/blog/seata-grpc-client</id>
+ <link href="https://seata.apache.org/blog/seata-grpc-client"/>
+ <updated>2024-11-30T00:00:00.000Z</updated>
+ <summary type="html"><![CDATA[This article takes Go language as an example to demonstrate Seata's multi-language client communication capabilities.]]></summary>
+ <content type="html"><![CDATA[<p>With the merge of PR <a href="https://github.com/apache/incubator-seata/pull/6754" target="_blank" rel="noopener noreferrer">https://github.com/apache/incubator-seata/pull/6754</a>, Seata Server is now capable of recognizing and processing Grpc requests. This means that any language client, by simply including the proto files, can communicate with the Seata Server deployed on the JVM, thereby achieving the full process of distributed transactions.</p>
+<p>Below is a demonstration of this process using Go language as an example.</p>
+<h1>Environment Preparation</h1>
+<p>Goland 2024.2</p>
+<p>Idea 2024.3</p>
+<p>JDK 1.8</p>
+<p>Go 1.23.3</p>
+<p>Seata 2.3.0-SNAPSHOT</p>
+<p>libprotoc 3.21.0</p>
+<h1>Operation Process</h1>
+<h2 class="anchor anchorWithStickyNavbar_LWe7" id="deploy-and-start-seata-server">Deploy and Start Seata Server<a href="https://seata.apache.org/blog/seata-grpc-client#deploy-and-start-seata-server" class="hash-link" aria-label="Direct link to Deploy and Start Seata Server" title="Direct link to Deploy and Start Seata Server"></a></h2>
+<p>Run org.apache.seata.server.ServerApplication#main as shown below:</p>
+<p><img decoding="async" loading="lazy" alt="2024121301.png" src="https://seata.apache.org/assets/images/2024121301-4613ead894d7510e65d88296eb86e297.png" width="2560" height="1504" class="img_ev3q"></p>
+<h2 class="anchor anchorWithStickyNavbar_LWe7" id="proto-file-import">Proto File Import<a href="https://seata.apache.org/blog/seata-grpc-client#proto-file-import" class="hash-link" aria-label="Direct link to Proto File Import" title="Direct link to Proto File Import"></a></h2>
+<p>Import the necessary proto files for the transaction process in the Go project, including various transaction request and response proto files and the proto files for initiating RPC. As shown below:</p>
+<p><img decoding="async" loading="lazy" alt="2024121302.png" src="https://seata.apache.org/assets/images/2024121302-39625f525d6da1bbc7ad4509c94718eb.png" width="2560" height="1504" class="img_ev3q"></p>
+<h2 class="anchor anchorWithStickyNavbar_LWe7" id="grpc-file-generation">Grpc File Generation<a href="https://seata.apache.org/blog/seata-grpc-client#grpc-file-generation" class="hash-link" aria-label="Direct link to Grpc File Generation" title="Direct link to Grpc File Generation"></a></h2>
+<p>In the directory where the proto files were imported in the previous step, execute the command:</p>
+<div class="language-shell codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_biex"><pre tabindex="0" class="prism-code language-shell codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><span class="token-line" style="color:#393A34"><span class="token plain">protoc --go_out=. --go-grpc_out=. .\*.proto</span><br></span></code></pre><div class="but [...]
+<p>After execution, the grpc code will be generated as shown below:</p>
+<p><img decoding="async" loading="lazy" alt="2024121303.png" src="https://seata.apache.org/assets/images/2024121303-bad6bb1db830335d72e2037ea7dbf4de.png" width="2560" height="1504" class="img_ev3q"></p>
+<h2 class="anchor anchorWithStickyNavbar_LWe7" id="grpc-invocation">Grpc Invocation<a href="https://seata.apache.org/blog/seata-grpc-client#grpc-invocation" class="hash-link" aria-label="Direct link to Grpc Invocation" title="Direct link to Grpc Invocation"></a></h2>
+<p>Complete a distributed transaction process in main.go and print the response from Seata Server. The code is as follows:</p>
+<div class="language-go codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_biex"><pre tabindex="0" class="prism-code language-go codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><span class="token-line" style="color:#393A34"><span class="token keyword" style="color:#00009f">func</span><span class="token plain"> </span><span class="token functio [...]
+<p>After running, the Seata Server console prints as follows:</p>
+<p><img decoding="async" loading="lazy" alt="2024121304.png" src="https://seata.apache.org/assets/images/2024121304-fcc9119043d66143a841d2008ef136f5.png" width="2560" height="1504" class="img_ev3q"></p>
+<p>The Go client console prints as follows:</p>
+<p><img decoding="async" loading="lazy" alt="2024121305.png" src="https://seata.apache.org/assets/images/2024121305-327ecb450c5fd7f7fc636165421972b2.png" width="2560" height="1504" class="img_ev3q"></p>
+<h1>Implementation Principle</h1>
+<h2 class="anchor anchorWithStickyNavbar_LWe7" id="proto-design">Proto Design<a href="https://seata.apache.org/blog/seata-grpc-client#proto-design" class="hash-link" aria-label="Direct link to Proto Design" title="Direct link to Proto Design"></a></h2>
+<p>To achieve communication with multi-language grpc clients, Seata Server defines grpcMessage.proto, which defines the GrpcMessageProto that assembles various Seata Message objects and the bidirectional stream interface sendRequest for assembling Seata communication requests. Seata Server uses grpcMessage.proto as a medium to achieve communication with multi-language clients.</p>
+<div class="language-proto codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_biex"><pre tabindex="0" class="prism-code language-proto codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><span class="token-line" style="color:#393A34"><span class="token plain">syntax = "proto3";</span><br></span><span class="token-line" style="color:#393A34"><span [...]
+<p>In addition, GrpcSerializer is defined, adapting to Seata's serialization SPI system, which is used to achieve the mutual conversion of protobuf byte streams and Seata message objects.</p>
+<h2 class="anchor anchorWithStickyNavbar_LWe7" id="grpc-protocol-recognition">Grpc Protocol Recognition<a href="https://seata.apache.org/blog/seata-grpc-client#grpc-protocol-recognition" class="hash-link" aria-label="Direct link to Grpc Protocol Recognition" title="Direct link to Grpc Protocol Recognition"></a></h2>
+<p>Seata Server implements ProtocolDetectHandler and ProtocolDetector. ProtocolDetectHandler, as a ByteToMessageDecoder, will traverse the ProtocolDetector list when receiving a message to find a ProtocolDetector that can recognize the current message. ProtocolDetector distinguishes Seata protocols, Http1.1 protocols, and Http2 protocols through recognizing magic numbers. Once recognized, the ChannelHandler capable of handling the protocol is added to the current Channel's Pipeline.</p>
+<p><img decoding="async" loading="lazy" alt="2024121306.jpeg" src="https://seata.apache.org/assets/images/2024121306-5568d956a86d67c43e4d76837dd5c8b8.jpeg" width="1904" height="1657" class="img_ev3q"></p>
+<h2 class="anchor anchorWithStickyNavbar_LWe7" id="grpc-request-sending-and-processing">Grpc Request Sending and Processing<a href="https://seata.apache.org/blog/seata-grpc-client#grpc-request-sending-and-processing" class="hash-link" aria-label="Direct link to Grpc Request Sending and Processing" title="Direct link to Grpc Request Sending and Processing"></a></h2>
+<p>Seata Server implements GrpcEncoder and GrpcDecoder. GrpcEncoder is responsible for converting Seata's RpcMessage into GrpcMessageProto recognizable by grpc native clients, filling the header with status, contentType, and other protocol headers for communication with grpc native clients. GrpcEncoder also adapts to grpc protocol specifications, writing the compression bit, length, and message body in the order specified by the grpc protocol into the channel.</p>
+<p>GrpcDecoder is responsible for processing requests from grpc native clients. Since grpc clients implement request batching in the underlying transmission through a queue flush, GrpcDecoder is also responsible for unpacking a batch of requests. Finally, GrpcDecoder converts the protobuf byte stream into one or more RpcMessages and passes them to the Seata request processor.</p>
+<h2 class="anchor anchorWithStickyNavbar_LWe7" id="grpc-connection-establishment-and-management">Grpc Connection Establishment and Management<a href="https://seata.apache.org/blog/seata-grpc-client#grpc-connection-establishment-and-management" class="hash-link" aria-label="Direct link to Grpc Connection Establishment and Management" title="Direct link to Grpc Connection Establishment and Management"></a></h2>
+<p>On the server side, simply configure a ProtocolDetectHandler to complete the recognition and establishment of various types of connections.</p>
+<div class="language-java codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_biex"><pre tabindex="0" class="prism-code language-java codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><span class="token-line" style="color:#393A34"><span class="token annotation punctuation" style="color:#393A34">@Override</span><span class="token plain"></span><br [...]
+<p>On the client side, when obtaining a Channel, if the current communication method is Grpc, an Http2MultiStreamChannel is obtained as the parent Channel, and grpc-related handlers are added to this Channel.</p>
+<div class="language-java codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_biex"><pre tabindex="0" class="prism-code language-java codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><span class="token-line" style="color:#393A34"><span class="token keyword" style="color:#00009f">if</span><span class="token plain"> </span><span class="token punct [...]
+<p>Please note that due to network issues, the parsing of the above links was unsuccessful. If you need the content of the parsed web pages, please check the legality of the web page links and try again. If you do not need the parsing of these links, the question can be answered normally.</p>]]></content>
+ <author>
+ <name>Wang Mingjun, Seata Open Source Summer Student Participant</name>
+ </author>
+ </entry>
<entry>
<title type="html"><![CDATA[Seata Raft Configuration Center]]></title>
<id>https://seata.apache.org/blog/seata-raft-config-center</id>
@@ -1611,124 +1666,4 @@ Page splits are unfriendly to I/O, requiring the creation of new data pages, cop
<name>chd</name>
</author>
</entry>
- <entry>
- <title type="html"><![CDATA[Seata Deadlock Issue Caused by ConcurrentHashMap]]></title>
- <id>https://seata.apache.org/blog/seata-dsproxy-deadlock</id>
- <link href="https://seata.apache.org/blog/seata-dsproxy-deadlock"/>
- <updated>2021-03-13T00:00:00.000Z</updated>
- <summary type="html"><![CDATA[This article primarily discusses an online issue, a Seata dynamic data source proxy deadlock caused by a ConcurrentHashMap bug.]]></summary>
- <content type="html"><![CDATA[<ol>
-<li>seata version: 1.4.0, but all versions below 1.4 also have this problem.</li>
-<li>Problem description: In a global transaction, a pure query operation on a branch transaction suddenly gets stuck without any feedback (logs/exceptions) until the RPC timeout on the consumer side</li>
-</ol>
-<p>! <a href="https://p3-juejin.byteimg.com/tos-cn-i-k3u1fbpfcp/03a7f737b56e45b4b74e662033ec74f6~tplv-k3u1fbpfcp-watermark.image" target="_blank" rel="noopener noreferrer">image.png</a></p>
-<h1>Problem Troubleshooting</h1>
-<ol>
-<li>The whole process is in a global transaction, the consumer and provider can be seen as two branches of the global transaction, consumer --> provider.</li>
-<li>the consumer first executes some local logic, and then sends an RPC request to the provider to make sure that the consumer has sent the request and the provider has received it.</li>
-<li>the provider first prints a log, and then executes a pure query SQL, if the SQL is executed properly, it will print the log, but the current phenomenon is that only the log before the execution of the SQL is printed, and no SQL-related logs are printed. Find DBA to check the SQL log, and found that the SQL is not executed.</li>
-<li>Determined that the operation is only a pure query operation under the global transaction, before the operation, the overall process of the global transaction is completely normal.</li>
-<li>In fact, the phenomenon here has been very obvious, but at that time the idea did not change over, has been concerned about the query SQL, always thinking that even if the query timeout and other reasons should be thrown exceptions ah, should not be nothing. DBA can not find the query record, that is not to say that the SQL may not have been executed ah, but in the execution of the SQL before the problem, such as the agent?</li>
-<li>With the help of arthas's watch command, there is no output. The first log output means that the method must have been executed, and the delay in outputting the result means that the current request is stuck, why is it stuck?</li>
-<li>With arthas's thread command <code>thread -b</code>, <code>thread -n</code>, is to find out the current busiest thread. This works very well, there is a thread CPU usage <code>92%</code>, and because of this thread caused the other 20 or so Dubbo threads <code>BLOCKED</code>. The stack information is as follows</li>
-<li>Analysing the stack information, we can clearly find the interface related to seata, which is probably related to seata's data source proxy; at the same time, we found that the thread with the highest CPU usage is stuck in the <code>ConcurrentHashMap#computeIfAbsent</code> method. Is there a bug in the <code>ConcurrentHashMap#computeIfAbsent</code> method?</li>
-<li>By now, we don't know the exact cause of the problem, but it should have something to do with seata's data source proxy, and we need to analyse both the business code and the seata code to find out why.</li>
-</ol>
-<p>! <a href="https://p1-juejin.byteimg.com/tos-cn-i-k3u1fbpfcp/faac0be0982e45a7a43b335e8f8b44bf~tplv-k3u1fbpfcp-watermark.image" target="_blank" rel="noopener noreferrer">image.png</a></p>
-<h2 class="anchor anchorWithStickyNavbar_LWe7" id="problem-analysis">Problem analysis<a href="https://seata.apache.org/blog/seata-dsproxy-deadlock#problem-analysis" class="hash-link" aria-label="Direct link to Problem analysis" title="Direct link to Problem analysis"></a></h2>
-<h3 class="anchor anchorWithStickyNavbar_LWe7" id="concurrenthashmapcomputeifabsent">ConcurrentHashMap##computeIfAbsent<a href="https://seata.apache.org/blog/seata-dsproxy-deadlock#concurrenthashmapcomputeifabsent" class="hash-link" aria-label="Direct link to ConcurrentHashMap##computeIfAbsent" title="Direct link to ConcurrentHashMap##computeIfAbsent"></a></h3>
-<p>This method does have the potential for problems: if two keys have the same hascode, and the computeIfAbsent operation is performed in the corresponding mappingFunction, it will lead to a dead loop, refer to this article for specific analysis: <a href="https://juejin.cn/post/" target="_blank" rel="noopener noreferrer">https://juejin.cn/post/</a> 6844904191077384200</p>
-<h3 class="anchor anchorWithStickyNavbar_LWe7" id="seata-data-source-autoproxy">Seata data source autoproxy<a href="https://seata.apache.org/blog/seata-dsproxy-deadlock#seata-data-source-autoproxy" class="hash-link" aria-label="Direct link to Seata data source autoproxy" title="Direct link to Seata data source autoproxy"></a></h3>
-<p>Related content has been analysed before, let's focus on the following core classes:</p>
-<ol>
-<li>SeataDataSourceBeanPostProcessor</li>
-<li>SeataAutoDataSourceProxyAdvice</li>
-<li>DataSourceProxyHolder</li>
-</ol>
-<h5 class="anchor anchorWithStickyNavbar_LWe7" id="seatadatasourcebeanpostprocessor">SeataDataSourceBeanPostProcessor<a href="https://seata.apache.org/blog/seata-dsproxy-deadlock#seatadatasourcebeanpostprocessor" class="hash-link" aria-label="Direct link to SeataDataSourceBeanPostProcessor" title="Direct link to SeataDataSourceBeanPostProcessor"></a></h5>
-<p>The <code>SeataDataSourceBeanPostProcessor</code> is a <code>BeanPostProcessor</code> implementation class that creates a <code>seataAutoDataSourceProxyDataSource</code> for the data source configured by the business side in the <code>postProcessAfterInitialization</code> method (i.e., after the bean is initialised). proxy data source</p>
-<div class="language-java codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_biex"><pre tabindex="0" class="prism-code language-java codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><span class="token-line" style="color:#393A34"><span class="token keyword" style="color:#00009f">public</span><span class="token plain"> </span><span class="token k [...]
-<h5 class="anchor anchorWithStickyNavbar_LWe7" id="seataautodatasourceproxyadvice">SeataAutoDataSourceProxyAdvice<a href="https://seata.apache.org/blog/seata-dsproxy-deadlock#seataautodatasourceproxyadvice" class="hash-link" aria-label="Direct link to SeataAutoDataSourceProxyAdvice" title="Direct link to SeataAutoDataSourceProxyAdvice"></a></h5>
-<p><code>SeataAutoDataSourceProxyAdvice</code> is a MethodInterceptor, <code>SeataAutoDataSourceProxyCreator</code> in seata creates a dynamic proxy object for <code>Bean</code> of type <code>DataSource</code>, the proxy logic is the <code>SeataAutoDataSourceProxyAdvice#invoke</code> logic. That is: when executing the relevant methods of the <code>DataSourceAOPProxyAdvice</code>, it will go through its <code>invoke</code> method, and in the <code>invoke</code> method, it will find the co [...]
-<div class="language-java codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_biex"><pre tabindex="0" class="prism-code language-java codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><span class="token-line" style="color:#393A34"><span class="token keyword" style="color:#00009f">public</span><span class="token plain"> </span><span class="token k [...]
-<h5 class="anchor anchorWithStickyNavbar_LWe7" id="datasourceproxyholder">DataSourceProxyHolder<a href="https://seata.apache.org/blog/seata-dsproxy-deadlock#datasourceproxyholder" class="hash-link" aria-label="Direct link to DataSourceProxyHolder" title="Direct link to DataSourceProxyHolder"></a></h5>
-<p>The process is clear to us, now there is a question, how to maintain the relationship between <code>native data source</code> and <code>seata proxy data source</code>? It is maintained by <code>DataSourceProxyHolder</code>, which is a singleton object that maintains the relationship between the two through a ConcurrentHashMap: <code>native data source</code> as key --> <code>seata proxy data source</code> as value.</p>
-<div class="language-java codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_biex"><pre tabindex="0" class="prism-code language-java codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><span class="token-line" style="color:#393A34"><span class="token keyword" style="color:#00009f">public</span><span class="token plain"> </span><span class="token k [...]
-<h3 class="anchor anchorWithStickyNavbar_LWe7" id="client-data-source-configuration">Client data source configuration<a href="https://seata.apache.org/blog/seata-dsproxy-deadlock#client-data-source-configuration" class="hash-link" aria-label="Direct link to Client data source configuration" title="Direct link to Client data source configuration"></a></h3>
-<ol>
-<li>Two data sources are configured: <code>DynamicDataSource</code>, <code>P6DataSource</code>, <code>P6DataSource</code>, <code>P6DataSource</code> and <code>P6DataSource</code>.</li>
-<li><code>P6DataSource</code> can be seen as a wrapper for <code>DynamicDataSource</code>. 3.</li>
-<li>Let's not worry about whether this configuration makes sense or not, now we just analyse the problem purely based on this data source configuration.</li>
-</ol>
-<div class="language-java codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_biex"><pre tabindex="0" class="prism-code language-java codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><span class="token-line" style="color:#393A34"><span class="token annotation punctuation" style="color:#393A34">@Qualifier</span><span class="token punctuation" sty [...]
-<h3 class="anchor anchorWithStickyNavbar_LWe7" id="analyse-the-process">Analyse the process<a href="https://seata.apache.org/blog/seata-dsproxy-deadlock#analyse-the-process" class="hash-link" aria-label="Direct link to Analyse the process" title="Direct link to Analyse the process"></a></h3>
-<p><code>Assuming that by now everyone is aware of the problems that may arise from ConcurrentHashMap#computeIfAbsent</code>, it is known that this problem has now arisen, and in combination with the stack information, we can see roughly where this problem has arisen.</p>
-<p>1, <code>ConcurrentHashMap#computeIfAbsent</code> will produce this problem precondition is: <code>two key hashcode is the same</code>; <code>mappingFunction corresponds to a put operation</code>. Combined with our seata usage scenario, the mappingFunction corresponds to <code>DataSourceProxy::new</code>, suggesting that the put operation may be triggered in the DataSourceProxy's constructor method</p>
-<p>! <a href="https://p1-juejin.byteimg.com/tos-cn-i-k3u1fbpfcp/00d8e13f71644c63b3bbb58c93b30e0c~tplv-k3u1fbpfcp-watermark.image" target="_blank" rel="noopener noreferrer">image.png</a></p>
-<div class="language-java codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_biex"><pre tabindex="0" class="prism-code language-java codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><span class="token-line" style="color:#393A34"><span class="token class-name">Execute</span><span class="token plain"> </span><span class="token constant" style="co [...]
-<p>2, What is the <code>AOP proxy data source</code> and <code>native data source</code> stated in step 1? Look at the following diagram
-! <a href="https://p3-juejin.byteimg.com/tos-cn-i-k3u1fbpfcp/3579631f58df4d17bfcd6f28ccc3fd79~tplv-k3u1fbpfcp-watermark.image" target="_blank" rel="noopener noreferrer">image.png</a></p>
-<p>3, the above also said to produce this problem there is a condition <code>two key hashcode the same</code>, but I see that these two data source objects are not overriding the <code>hashcode</code> method, so by definition, these two objects must be different hashcode. After looking at the ConcurrentHashMap problem again, I feel that the statement <code>two keys have the same hashcode</code> is not correct, and <code>two keys will generate hash conflict</code> is more reasonable, whic [...]
-<div class="language-java codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_biex"><pre tabindex="0" class="prism-code language-java codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><span class="token-line" style="color:#393A34"><span class="token keyword" style="color:#00009f">public</span><span class="token plain"> </span><span class="token k [...]
-<ol>
-<li>To make it easier to reproduce the problem, we rewrite the <code>Num#hashCode</code> method to ensure that the constructor input is the hashcode value.</li>
-<li>create a ConcurrentHashMap object, initialCapacity is 8, sizeCtl calculated value is 16, that is, the default length of the array in the map is 16</li>
-<li>create object <code>n1</code>, the input parameter is 3, that is, the hashcode is 3, the calculation of its corresponding array subscript 3</li>
-<li>create object <code>n2</code>, the input parameter is 19, that is, the hashcode is 19, calculate its corresponding array subscript is 3, at this time we can think of <code>n1 and n2 hash conflict</code>.</li>
-<li>create object <code>n3</code> with input 20, i.e., hashcode 20, and its corresponding array subscript is 4.</li>
-<li>execute <code>map.computeIfAbsent(n1, k1 -> map.computeIfAbsent(n3, k2 -> 200))</code>, the programme exits normally: <code>Because there is no hash conflict between n1 and n3, the programme terminates normally</code>.</li>
-<li>Execute <code>map.computeIfAbsent(n1, k1 -> map.computeIfAbsent(n2, k2 -> 200))</code>, the programme exits normally: <code> because n1 and n2 have a hash conflict, so it is in a dead loop</code>.</li>
-</ol>
-<p>4、During the initialisation of the object, hasn't <code>SeataDataSourceBeanPostProcessor</code> already initialised the corresponding data source proxy of the object? Why the corresponding data source proxy is still created in <code>SeataAutoDataSourceProxyAdvice</code>?</p>
-<ol>
-<li>First of all, the <code>SeataDataSourceBeanPostProcessor</code> execution period is later than the creation of the AOP proxy object, so when executing the <code>SeataDataSourceBeanPostProcessor</code> related methods, the <code>SeataAutoDataSourceBeanPostProcessor</code> method is executed. SeataAutoDataSourceProxyAdvice<code>should actually take effect when the</code>SeataDataSourceBeanPostProcessor` related methods are executed.</li>
-<li>when adding elements to the map in <code>SeataDataSourceBeanPostProcessor</code>, the key is <code>AOP proxy datasource</code>; in <code>SeataAutoDataSourceProxyAdvice</code>, the key is <code>native datasource</code>, so the key is not the same as <code>invocation.getThis()</code>, so the key is not the same. `, so the key is not the same</li>
-</ol>
-<p>! <a href="https://p6-juejin.byteimg.com/tos-cn-i-k3u1fbpfcp/747b664a0b6c4f58843947576dd0856e~tplv-k3u1fbpfcp-watermark.image" target="_blank" rel="noopener noreferrer">image.png</a></p>
-<p>5, there is another problem, <code>SeataAutoDataSourceProxyAdvic#invoke</code> method does not filter <code>toString, hashCode</code> and other methods, the proxy object created by cglib will override these methods by default, if these methods of the proxy object are triggered when putting elements into the map. If these methods are triggered when putting elements into the map, the proxy object will re-enter the <code>SeataAutoDataSourceProxyAdvic#invoke</code> cut until the thread st [...]
-<h1>Summary of the problem</h1>
-<ol>
-<li>in two key will produce hash conflict, will trigger <code>ConcurrentHashMap#computeIfAbsent</code> BUG, the performance of this BUG is to make the current thread into a dead loop</li>
-<li>business feedback, the problem is occasional, occasional for two reasons: first, the application is a multi-node deployment, but only one node on the line triggered the BUG (hashcode conflict), so only when the request hits this node may trigger the BUG; second, because each restart object address (hashcode) are not sure, so not triggered after every app restart, but if once triggered, the node will always have this problem. Having a thread that keeps dying and blocking other threads [...]
-<li>when encountering this problem, from the perspective of the whole problem, it is indeed a deadlock, because the dead loop thread occupant lock has not been released, resulting in other threads operating on the map is BLOCKED!</li>
-<li>essentially because <code>ConcurrentHashMap#computeIfAbsent method may trigger a bug</code>, and seata's usage scenario just triggered the bug.</li>
-<li>The following demo is actually a complete simulation of what happens when something goes wrong online, as follows:</li>
-</ol>
-<div class="language-java codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_biex"><pre tabindex="0" class="prism-code language-java codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><span class="token-line" style="color:#393A34"><span class="token keyword" style="color:#00009f">public</span><span class="token plain"> </span><span class="token k [...]
-<p>! <a href="https://p6-juejin.byteimg.com/tos-cn-i-k3u1fbpfcp/d6134c6498fa49c4a68b2745ba0895e3~tplv-k3u1fbpfcp-watermark.image" target="_blank" rel="noopener noreferrer">image.png</a></p>
-<h3 class="anchor anchorWithStickyNavbar_LWe7" id="solving-the-problem">Solving the problem<a href="https://seata.apache.org/blog/seata-dsproxy-deadlock#solving-the-problem" class="hash-link" aria-label="Direct link to Solving the problem" title="Direct link to Solving the problem"></a></h3>
-<p>The problem can be solved in two ways:</p>
-<ol>
-<li>business changes: P6DataSource and DynamicDataSource do not need to be proxied, directly proxy P6DataSource can be, DynamicDataSource does not need to be declared as a bean; or through the excludes property excludes P6DataSource, so that there is no duplicate proxy problem. There will be no problem of duplicate proxies</li>
-<li>Seata refinement: improve the logic related to data source proxy</li>
-</ol>
-<h5 class="anchor anchorWithStickyNavbar_LWe7" id="business-changes">Business changes<a href="https://seata.apache.org/blog/seata-dsproxy-deadlock#business-changes" class="hash-link" aria-label="Direct link to Business changes" title="Direct link to Business changes"></a></h5>
-<ol>
-<li>Data source related configuration can be changed to the following:</li>
-</ol>
-<div class="language-java codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_biex"><pre tabindex="0" class="prism-code language-java codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><span class="token-line" style="color:#393A34"><span class="token annotation punctuation" style="color:#393A34">@Primary</span><span class="token plain"></span><br> [...]
-<ol start="2">
-<li>Or leave the current data source configuration unchanged and add the excludes property</li>
-</ol>
-<div class="language-java codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_biex"><pre tabindex="0" class="prism-code language-java codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><span class="token-line" style="color:#393A34"><span class="token annotation punctuation" style="color:#393A34">@EnableAutoDataSourceProxy</span><span class="token [...]
-<h5 class="anchor anchorWithStickyNavbar_LWe7" id="seata-refinement">Seata refinement<a href="https://seata.apache.org/blog/seata-dsproxy-deadlock#seata-refinement" class="hash-link" aria-label="Direct link to Seata refinement" title="Direct link to Seata refinement"></a></h5>
-<ol>
-<li><code>ConcurrentHashMap#computeIfAbsent</code> method is changed to double check as follows:</li>
-</ol>
-<div class="language-java codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_biex"><pre tabindex="0" class="prism-code language-java codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><span class="token-line" style="color:#393A34"><span class="token class-name">SeataDataSourceProxy</span><span class="token plain"> dsProxy </span><span class="toke [...]
-<p>I wanted to change the <code>CollectionUtils#computeIfAbsent</code> method directly, and the feedback from the group was that this might cause the data source to be created multiple times, which is indeed a problem: as follows</p>
-<div class="language-java codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_biex"><pre tabindex="0" class="prism-code language-java codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><span class="token-line" style="color:#393A34"><span class="token keyword" style="color:#00009f">public</span><span class="token plain"> </span><span class="token k [...]
-<ol start="2">
-<li>Add some filtering to the SeataAutoDataSourceProxyAdvice cutout logic</li>
-</ol>
-<div class="language-java codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_biex"><pre tabindex="0" class="prism-code language-java codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><span class="token-line" style="color:#393A34"><span class="token class-name">Method</span><span class="token plain"> m </span><span class="token operator" style="c [...]
-<h3 class="anchor anchorWithStickyNavbar_LWe7" id="legacy-issues">Legacy issues<a href="https://seata.apache.org/blog/seata-dsproxy-deadlock#legacy-issues" class="hash-link" aria-label="Direct link to Legacy issues" title="Direct link to Legacy issues"></a></h3>
-<p>In the corresponding methods of <code>SeataDataSourceBeanPostProcessor</code> and <code>SeataAutoDataSourceProxyAdvice</code>, the keys corresponding to initialising the <code>seata datasource proxy</code> into the map are fundamentally different, the <code>The key in</code>SeataDataSourceBeanPostProcessor<code>is the</code>AOP proxy data source<code>; the key in </code>SeataAutoDataSourceProxyAdvice<code>is the native object, which results in the unnecessary creation of the</code>sea [...]
-<p>What is the best suggestion for this problem? Is it possible to specify an order for <code>SeataDataSourceBeanPostProcessor</code> to take effect before the AOP proxy object is created?</p>
-<h1>Link to original article</h1>
-<p><a href="https://juejin.cn/post/6939041336964153352/" target="_blank" rel="noopener noreferrer">https://juejin.cn/post/6939041336964153352/</a></p>]]></content>
- <author>
- <name>xiaoyong.luo</name>
- </author>
- </entry>
</feed>
\ No newline at end of file
diff --git a/blog/design-more-flexable-application-by-saga/index.html b/blog/design-more-flexable-application-by-saga/index.html
index dbdb1ecce36..9dcbcfe8dab 100644
--- a/blog/design-more-flexable-application-by-saga/index.html
+++ b/blog/design-more-flexable-application-by-saga/index.html
@@ -11,11 +11,11 @@
<meta name="aes-config" content="pid=xux-opensource&user_type=101&uid=&username=&dim10=seata"><link rel="stylesheet" href="/assets/css/styles.9644caf2.css">
-<script src="/assets/js/runtime~main.bf98ee01.js" defer="defer"></script>
-<script src="/assets/js/main.8371dd70.js" defer="defer"></script>
+<script src="/assets/js/runtime~main.762ed5c0.js" defer="defer"></script>
+<script src="/assets/js/main.aeea7339.js" defer="defer"></script>
</head>
<body class="navigation-with-keyboard">
-<script>!function(){function t(t){document.documentElement.setAttribute("data-theme",t)}var e=function(){try{return new URLSearchParams(window.location.search).get("docusaurus-theme")}catch(t){}}()||function(){try{return localStorage.getItem("theme")}catch(t){}}();t(null!==e?e:"light")}(),function(){try{const c=new URLSearchParams(window.location.search).entries();for(var[t,e]of c)if(t.startsWith("docusaurus-data-")){var a=t.replace("docusaurus-data-","data-");document.documentElement.se [...]
+<script>!function(){function t(t){document.documentElement.setAttribute("data-theme",t)}var e=function(){try{return new URLSearchParams(window.location.search).get("docusaurus-theme")}catch(t){}}()||function(){try{return localStorage.getItem("theme")}catch(t){}}();t(null!==e?e:"light")}(),function(){try{const c=new URLSearchParams(window.location.search).entries();for(var[t,e]of c)if(t.startsWith("docusaurus-data-")){var a=t.replace("docusaurus-data-","data-");document.documentElement.se [...]
<p>Author: Yiyuan (Chen Long), Core Developer of Distributed Transactions at Ant Financial.</p>
<a name="uTwja"></a>
<h1>Pain Points in Financial Distributed Application Development</h1>
diff --git a/blog/explore-seata-journey/index.html b/blog/explore-seata-journey/index.html
index d41dcde0653..b4f11ec019a 100644
--- a/blog/explore-seata-journey/index.html
+++ b/blog/explore-seata-journey/index.html
@@ -11,11 +11,11 @@
<meta name="aes-config" content="pid=xux-opensource&user_type=101&uid=&username=&dim10=seata"><link rel="stylesheet" href="/assets/css/styles.9644caf2.css">
-<script src="/assets/js/runtime~main.bf98ee01.js" defer="defer"></script>
-<script src="/assets/js/main.8371dd70.js" defer="defer"></script>
+<script src="/assets/js/runtime~main.762ed5c0.js" defer="defer"></script>
+<script src="/assets/js/main.aeea7339.js" defer="defer"></script>
</head>
<body class="navigation-with-keyboard">
-<script>!function(){function t(t){document.documentElement.setAttribute("data-theme",t)}var e=function(){try{return new URLSearchParams(window.location.search).get("docusaurus-theme")}catch(t){}}()||function(){try{return localStorage.getItem("theme")}catch(t){}}();t(null!==e?e:"light")}(),function(){try{const c=new URLSearchParams(window.location.search).entries();for(var[t,e]of c)if(t.startsWith("docusaurus-data-")){var a=t.replace("docusaurus-data-","data-");document.documentElement.se [...]
+<script>!function(){function t(t){document.documentElement.setAttribute("data-theme",t)}var e=function(){try{return new URLSearchParams(window.location.search).get("docusaurus-theme")}catch(t){}}()||function(){try{return localStorage.getItem("theme")}catch(t){}}();t(null!==e?e:"light")}(),function(){try{const c=new URLSearchParams(window.location.search).entries();for(var[t,e]of c)if(t.startsWith("docusaurus-data-")){var a=t.replace("docusaurus-data-","data-");document.documentElement.se [...]
<p>Seata is an open-source distributed transaction solution dedicated to providing high-performance and user-friendly distributed transaction services in a microservices architecture. During this year's Summer of Code event, I joined the Apache Seata (Incubator) community, completed the Summer of Code project, and have been actively involved in the community ever since. I was fortunate to share my developer experience at the YunQi Developer Show during the Cloud Conferen</p>
</blockquote>
<h2 class="anchor anchorWithStickyNavbar_LWe7" id="relevant-background">Relevant Background<a href="#relevant-background" class="hash-link" aria-label="Direct link to Relevant Background" title="Direct link to Relevant Background"></a></h2>
diff --git a/blog/how-to-support-spring-cloud/index.html b/blog/how-to-support-spring-cloud/index.html
index 8e5ea4a2117..9a37610be95 100644
--- a/blog/how-to-support-spring-cloud/index.html
+++ b/blog/how-to-support-spring-cloud/index.html
@@ -11,11 +11,11 @@
<meta name="aes-config" content="pid=xux-opensource&user_type=101&uid=&username=&dim10=seata"><link rel="stylesheet" href="/assets/css/styles.9644caf2.css">
-<script src="/assets/js/runtime~main.bf98ee01.js" defer="defer"></script>
-<script src="/assets/js/main.8371dd70.js" defer="defer"></script>
+<script src="/assets/js/runtime~main.762ed5c0.js" defer="defer"></script>
+<script src="/assets/js/main.aeea7339.js" defer="defer"></script>
</head>
<body class="navigation-with-keyboard">
-<script>!function(){function t(t){document.documentElement.setAttribute("data-theme",t)}var e=function(){try{return new URLSearchParams(window.location.search).get("docusaurus-theme")}catch(t){}}()||function(){try{return localStorage.getItem("theme")}catch(t){}}();t(null!==e?e:"light")}(),function(){try{const c=new URLSearchParams(window.location.search).entries();for(var[t,e]of c)if(t.startsWith("docusaurus-data-")){var a=t.replace("docusaurus-data-","data-");document.documentElement.se [...]
+<script>!function(){function t(t){document.documentElement.setAttribute("data-theme",t)}var e=function(){try{return new URLSearchParams(window.location.search).get("docusaurus-theme")}catch(t){}}()||function(){try{return localStorage.getItem("theme")}catch(t){}}();t(null!==e?e:"light")}(),function(){try{const c=new URLSearchParams(window.location.search).entries();for(var[t,e]of c)if(t.startsWith("docusaurus-data-")){var a=t.replace("docusaurus-data-","data-");document.documentElement.se [...]
<p>Common distributed transaction approaches include XA based on 2PC (e.g., Atomikos), TCC (e.g., ByteTCC) focusing on the business layer, and transactional messaging (e.g., RocketMQ Half Message). XA is a protocol for distributed transactions that requires support from local databases. However, the resource locking at the database level can lead to poor performance. On the other hand, TCC, introduced by Alibaba as a preacher, requires a significant amount of business code to ensure tran [...]
<p>Distributed transactions are a widely discussed topic in the industry, and this is one of the reasons why Fescar has gained 6k stars in a short period of time. The name "Fescar" stands for Fast & Easy Commit And Rollback. In simple terms, Fescar drives global transactions by coordinating local RDBMS branch transactions. It is a middleware that operates at the application layer. The main advantages of Fescar are better performance compared to XA, as it does not occupy con [...]
<p>Similar to XA, Fescar divides roles into TC (Transaction Coordinator), RM (Resource Manager), and TM (Transaction Manager). The overall transaction process model of Fescar is as follows:</p>
diff --git a/blog/how-to-write-unit-tests/index.html b/blog/how-to-write-unit-tests/index.html
index e541c3c7977..5c6fe83228b 100644
--- a/blog/how-to-write-unit-tests/index.html
+++ b/blog/how-to-write-unit-tests/index.html
@@ -11,11 +11,11 @@
<meta name="aes-config" content="pid=xux-opensource&user_type=101&uid=&username=&dim10=seata"><link rel="stylesheet" href="/assets/css/styles.9644caf2.css">
-<script src="/assets/js/runtime~main.bf98ee01.js" defer="defer"></script>
-<script src="/assets/js/main.8371dd70.js" defer="defer"></script>
+<script src="/assets/js/runtime~main.762ed5c0.js" defer="defer"></script>
+<script src="/assets/js/main.aeea7339.js" defer="defer"></script>
</head>
<body class="navigation-with-keyboard">
-<script>!function(){function t(t){document.documentElement.setAttribute("data-theme",t)}var e=function(){try{return new URLSearchParams(window.location.search).get("docusaurus-theme")}catch(t){}}()||function(){try{return localStorage.getItem("theme")}catch(t){}}();t(null!==e?e:"light")}(),function(){try{const c=new URLSearchParams(window.location.search).entries();for(var[t,e]of c)if(t.startsWith("docusaurus-data-")){var a=t.replace("docusaurus-data-","data-");document.documentElement.se [...]
+<script>!function(){function t(t){document.documentElement.setAttribute("data-theme",t)}var e=function(){try{return new URLSearchParams(window.location.search).get("docusaurus-theme")}catch(t){}}()||function(){try{return localStorage.getItem("theme")}catch(t){}}();t(null!==e?e:"light")}(),function(){try{const c=new URLSearchParams(window.location.search).entries();for(var[t,e]of c)if(t.startsWith("docusaurus-data-")){var a=t.replace("docusaurus-data-","data-");document.documentElement.se [...]
<p>As the Seata project continues to grow and expand, our contributor community is also continuously growing. With the continuous enhancement of project functionality, the requirements for code quality are also increasing. In this process, we expect every contributor to provide standardized and comprehensive test cases along with their feature code submissions.</p>
<p>An excellent project relies on comprehensive unit tests as a fundamental guarantee. The Test-Driven Development (TDD) concept has been proposed for many years, emphasizing writing test cases before writing functional code. By writing unit tests, developers can gain a deeper understanding of the roles of related classes and methods in the code, grasp the core logic, and become familiar with the running scenarios of various situations. Meanwhile, unit tests also provide stable and secur [...]
<p>In the community's view, contributing reasonable test case code is equally important as contributing functional code. To help developers write high-quality test cases, this article provides some basic standards and recommendations.</p>
diff --git a/blog/index.html b/blog/index.html
index 68ca49741f4..54718c1a3a1 100644
--- a/blog/index.html
+++ b/blog/index.html
@@ -11,11 +11,55 @@
<meta name="aes-config" content="pid=xux-opensource&user_type=101&uid=&username=&dim10=seata"><link rel="stylesheet" href="/assets/css/styles.9644caf2.css">
-<script src="/assets/js/runtime~main.bf98ee01.js" defer="defer"></script>
-<script src="/assets/js/main.8371dd70.js" defer="defer"></script>
+<script src="/assets/js/runtime~main.762ed5c0.js" defer="defer"></script>
+<script src="/assets/js/main.aeea7339.js" defer="defer"></script>
</head>
<body class="navigation-with-keyboard">
-<script>!function(){function t(t){document.documentElement.setAttribute("data-theme",t)}var e=function(){try{return new URLSearchParams(window.location.search).get("docusaurus-theme")}catch(t){}}()||function(){try{return localStorage.getItem("theme")}catch(t){}}();t(null!==e?e:"light")}(),function(){try{const c=new URLSearchParams(window.location.search).entries();for(var[t,e]of c)if(t.startsWith("docusaurus-data-")){var a=t.replace("docusaurus-data-","data-");document.documentElement.se [...]
+<script>!function(){function t(t){document.documentElement.setAttribute("data-theme",t)}var e=function(){try{return new URLSearchParams(window.location.search).get("docusaurus-theme")}catch(t){}}()||function(){try{return localStorage.getItem("theme")}catch(t){}}();t(null!==e?e:"light")}(),function(){try{const c=new URLSearchParams(window.location.search).entries();for(var[t,e]of c)if(t.startsWith("docusaurus-data-")){var a=t.replace("docusaurus-data-","data-");document.documentElement.se [...]
+<p>Below is a demonstration of this process using Go language as an example.</p>
+<h1>Environment Preparation</h1>
+<p>Goland 2024.2</p>
+<p>Idea 2024.3</p>
+<p>JDK 1.8</p>
+<p>Go 1.23.3</p>
+<p>Seata 2.3.0-SNAPSHOT</p>
+<p>libprotoc 3.21.0</p>
+<h1>Operation Process</h1>
+<h2 class="anchor anchorWithStickyNavbar_LWe7" id="deploy-and-start-seata-server">Deploy and Start Seata Server<a href="#deploy-and-start-seata-server" class="hash-link" aria-label="Direct link to Deploy and Start Seata Server" title="Direct link to Deploy and Start Seata Server"></a></h2>
+<p>Run org.apache.seata.server.ServerApplication#main as shown below:</p>
+<p><img decoding="async" loading="lazy" alt="2024121301.png" src="/assets/images/2024121301-4613ead894d7510e65d88296eb86e297.png" width="2560" height="1504" class="img_ev3q"></p>
+<h2 class="anchor anchorWithStickyNavbar_LWe7" id="proto-file-import">Proto File Import<a href="#proto-file-import" class="hash-link" aria-label="Direct link to Proto File Import" title="Direct link to Proto File Import"></a></h2>
+<p>Import the necessary proto files for the transaction process in the Go project, including various transaction request and response proto files and the proto files for initiating RPC. As shown below:</p>
+<p><img decoding="async" loading="lazy" alt="2024121302.png" src="/assets/images/2024121302-39625f525d6da1bbc7ad4509c94718eb.png" width="2560" height="1504" class="img_ev3q"></p>
+<h2 class="anchor anchorWithStickyNavbar_LWe7" id="grpc-file-generation">Grpc File Generation<a href="#grpc-file-generation" class="hash-link" aria-label="Direct link to Grpc File Generation" title="Direct link to Grpc File Generation"></a></h2>
+<p>In the directory where the proto files were imported in the previous step, execute the command:</p>
+<div class="language-shell codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_biex"><pre tabindex="0" class="prism-code language-shell codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><span class="token-line" style="color:#393A34"><span class="token plain">protoc --go_out=. --go-grpc_out=. .\*.proto</span><br></span></code></pre><div class="but [...]
+<p>After execution, the grpc code will be generated as shown below:</p>
+<p><img decoding="async" loading="lazy" alt="2024121303.png" src="/assets/images/2024121303-bad6bb1db830335d72e2037ea7dbf4de.png" width="2560" height="1504" class="img_ev3q"></p>
+<h2 class="anchor anchorWithStickyNavbar_LWe7" id="grpc-invocation">Grpc Invocation<a href="#grpc-invocation" class="hash-link" aria-label="Direct link to Grpc Invocation" title="Direct link to Grpc Invocation"></a></h2>
+<p>Complete a distributed transaction process in main.go and print the response from Seata Server. The code is as follows:</p>
+<div class="language-go codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_biex"><pre tabindex="0" class="prism-code language-go codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><span class="token-line" style="color:#393A34"><span class="token keyword" style="color:#00009f">func</span><span class="token plain"> </span><span class="token functio [...]
+<p>After running, the Seata Server console prints as follows:</p>
+<p><img decoding="async" loading="lazy" alt="2024121304.png" src="/assets/images/2024121304-fcc9119043d66143a841d2008ef136f5.png" width="2560" height="1504" class="img_ev3q"></p>
+<p>The Go client console prints as follows:</p>
+<p><img decoding="async" loading="lazy" alt="2024121305.png" src="/assets/images/2024121305-327ecb450c5fd7f7fc636165421972b2.png" width="2560" height="1504" class="img_ev3q"></p>
+<h1>Implementation Principle</h1>
+<h2 class="anchor anchorWithStickyNavbar_LWe7" id="proto-design">Proto Design<a href="#proto-design" class="hash-link" aria-label="Direct link to Proto Design" title="Direct link to Proto Design"></a></h2>
+<p>To achieve communication with multi-language grpc clients, Seata Server defines grpcMessage.proto, which defines the GrpcMessageProto that assembles various Seata Message objects and the bidirectional stream interface sendRequest for assembling Seata communication requests. Seata Server uses grpcMessage.proto as a medium to achieve communication with multi-language clients.</p>
+<div class="language-proto codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_biex"><pre tabindex="0" class="prism-code language-proto codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><span class="token-line" style="color:#393A34"><span class="token plain">syntax = "proto3";</span><br></span><span class="token-line" style="color:#393A [...]
+<p>In addition, GrpcSerializer is defined, adapting to Seata's serialization SPI system, which is used to achieve the mutual conversion of protobuf byte streams and Seata message objects.</p>
+<h2 class="anchor anchorWithStickyNavbar_LWe7" id="grpc-protocol-recognition">Grpc Protocol Recognition<a href="#grpc-protocol-recognition" class="hash-link" aria-label="Direct link to Grpc Protocol Recognition" title="Direct link to Grpc Protocol Recognition"></a></h2>
+<p>Seata Server implements ProtocolDetectHandler and ProtocolDetector. ProtocolDetectHandler, as a ByteToMessageDecoder, will traverse the ProtocolDetector list when receiving a message to find a ProtocolDetector that can recognize the current message. ProtocolDetector distinguishes Seata protocols, Http1.1 protocols, and Http2 protocols through recognizing magic numbers. Once recognized, the ChannelHandler capable of handling the protocol is added to the current Channel's Pipeline.</p>
+<p><img decoding="async" loading="lazy" alt="2024121306.jpeg" src="/assets/images/2024121306-5568d956a86d67c43e4d76837dd5c8b8.jpeg" width="1904" height="1657" class="img_ev3q"></p>
+<h2 class="anchor anchorWithStickyNavbar_LWe7" id="grpc-request-sending-and-processing">Grpc Request Sending and Processing<a href="#grpc-request-sending-and-processing" class="hash-link" aria-label="Direct link to Grpc Request Sending and Processing" title="Direct link to Grpc Request Sending and Processing"></a></h2>
+<p>Seata Server implements GrpcEncoder and GrpcDecoder. GrpcEncoder is responsible for converting Seata's RpcMessage into GrpcMessageProto recognizable by grpc native clients, filling the header with status, contentType, and other protocol headers for communication with grpc native clients. GrpcEncoder also adapts to grpc protocol specifications, writing the compression bit, length, and message body in the order specified by the grpc protocol into the channel.</p>
+<p>GrpcDecoder is responsible for processing requests from grpc native clients. Since grpc clients implement request batching in the underlying transmission through a queue flush, GrpcDecoder is also responsible for unpacking a batch of requests. Finally, GrpcDecoder converts the protobuf byte stream into one or more RpcMessages and passes them to the Seata request processor.</p>
+<h2 class="anchor anchorWithStickyNavbar_LWe7" id="grpc-connection-establishment-and-management">Grpc Connection Establishment and Management<a href="#grpc-connection-establishment-and-management" class="hash-link" aria-label="Direct link to Grpc Connection Establishment and Management" title="Direct link to Grpc Connection Establishment and Management"></a></h2>
+<p>On the server side, simply configure a ProtocolDetectHandler to complete the recognition and establishment of various types of connections.</p>
+<div class="language-java codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_biex"><pre tabindex="0" class="prism-code language-java codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><span class="token-line" style="color:#393A34"><span class="token annotation punctuation" style="color:#393A34">@Override</span><span class="token plain"></span><br [...]
+<p>On the client side, when obtaining a Channel, if the current communication method is Grpc, an Http2MultiStreamChannel is obtained as the parent Channel, and grpc-related handlers are added to this Channel.</p>
+<div class="language-java codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_biex"><pre tabindex="0" class="prism-code language-java codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><span class="token-line" style="color:#393A34"><span class="token keyword" style="color:#00009f">if</span><span class="token plain"> </span><span class="token punct [...]
+<p>Please note that due to network issues, the parsing of the above links was unsuccessful. If you need the content of the parsed web pages, please check the legality of the web page links and try again. If you do not need the parsing of these links, the question can be answered normally.</p></div><footer class="row docusaurus-mt-lg"></footer></article><article class="margin-bottom--xl" itemprop="blogPost" itemscope="" itemtype="https://schema.org/BlogPosting"><meta itemprop="description [...]
<h1>2. Design Description</h1>
<h2 class="anchor anchorWithStickyNavbar_LWe7" id="21-configuration-center">2.1 Configuration Center<a href="#21-configuration-center" class="hash-link" aria-label="Direct link to 2.1 Configuration Center" title="Direct link to 2.1 Configuration Center"></a></h2>
<p>In the current third-party configuration center implementation, the Client and Server are decoupled when it comes to configuration centers. Both the Client and Server access configuration items through the Configuration instance. The initialization behavior for Configuration is consistent on both the Client and Server sides, involving connecting to the configuration center middleware to fetch configurations and add listeners, etc.
@@ -748,69 +792,7 @@ Prospect: more granular metrics, broader ecological compatibility.</p>
Prospect: trace transaction links according to xid, and quickly locate the root cause of abnormal links.</p>
<h4 class="anchor anchorWithStickyNavbar_LWe7" id="logging">Logging<a href="#logging" class="hash-link" aria-label="Direct link to Logging" title="Direct link to Logging"></a></h4>
<p>Summary: Structured log format.
-Prospect: Evolution of log observable system.</p></div><footer class="row docusaurus-mt-lg"></footer></article><article class="margin-bottom--xl" itemprop="blogPost" itemscope="" itemtype="https://schema.org/BlogPosting"><meta itemprop="description" content="seata-go 1.2.0, ready for production environment!!!"><meta itemprop="keywords" content="seata,distributed transaction,golang,1.2.0"><header><h2 class="title_f1Hy" itemprop="headline"><a itemprop="url" href="/blog/seata-go-1.2.0">seat [...]
-<p>Seata is an open source distributed transaction solution that provides high-performance and easy-to-use distributed transaction services.</p>
-<h3 class="anchor anchorWithStickyNavbar_LWe7" id="release-overview">Release overview<a href="#release-overview" class="hash-link" aria-label="Direct link to Release overview" title="Direct link to Release overview"></a></h3>
-<p>Seata-go version 1.2.0 supports the XA schema, a distributed transaction processing specification proposed by the X/Open organisation, which has the advantage of being non-intrusive to business code. Currently, Seata-go's XA mode supports MySQL databases. So far, seata-go has gathered three transaction modes: AT, TCC and XA. Main features of XA mode.</p>
-<ul>
-<li>Supported XA data source proxy <a href="https://github.com/apache/incubator-seata-go-samples/tree/main/xa" target="_blank" rel="noopener noreferrer">https://github.com/apache/incubator-seata-go-samples/tree/main/xa</a></li>
-<li>XA transaction mode is supported.
-XA related sampes can be found in the following example: <a href="https://github.com/apache/incubator-seata-go-samples/tree/main/xa" target="_blank" rel="noopener noreferrer">https://github.com/apache/incubator-seata-go-samples/tree/main/xa</a></li>
-</ul>
-<h3 class="anchor anchorWithStickyNavbar_LWe7" id="feature">feature<a href="#feature" class="hash-link" aria-label="Direct link to feature" title="Direct link to feature"></a></h3>
-<ul>
-<li>[<a href="https://github.com/apache/incubator-seata-go/pull/467" target="_blank" rel="noopener noreferrer">#467</a>] implements XA schema support for MySQL.</li>
-<li>[<a href="https://github.com/apache/incubator-seata-go/pull/534" target="_blank" rel="noopener noreferrer">#534</a>] Load balancing for session support.</li>
-</ul>
-<h3 class="anchor anchorWithStickyNavbar_LWe7" id="bugfix">bugfix<a href="#bugfix" class="hash-link" aria-label="Direct link to bugfix" title="Direct link to bugfix"></a></h3>
-<ul>
-<li>[<a href="https://github.com/apache/incubator-seata-go/pull/540" target="_blank" rel="noopener noreferrer">#540</a>] Fix a bug in initialising xa mode.</li>
-<li>[<a href="https://github.com/apache/incubator-seata-go/pull/545" target="_blank" rel="noopener noreferrer">#545</a>] Fix a bug in getting db version number in xa mode.</li>
-<li>[<a href="https://github.com/apache/incubator-seata-go/pull/548" target="_blank" rel="noopener noreferrer">#548</a>] Fix bug where starting xa fails.</li>
-<li>[<a href="https://github.com/apache/incubator-seata-go/pull/556" target="_blank" rel="noopener noreferrer">#556</a>] Fix bug in xa datasource.</li>
-<li>[<a href="https://github.com/apache/incubator-seata-go/pull/562" target="_blank" rel="noopener noreferrer">#562</a>] Fix bug with committing xa global transaction</li>
-<li>[<a href="https://github.com/apache/incubator-seata-go/pull/564" target="_blank" rel="noopener noreferrer">#564</a>] Fix bug committing xa branching transactions</li>
-<li>[<a href="https://github.com/apache/incubator-seata-go/pull/566" target="_blank" rel="noopener noreferrer">#566</a>] Fix bug with local transactions using xa data source.</li>
-</ul>
-<h3 class="anchor anchorWithStickyNavbar_LWe7" id="optimise">optimise<a href="#optimise" class="hash-link" aria-label="Direct link to optimise" title="Direct link to optimise"></a></h3>
-<ul>
-<li>[<a href="https://github.com/apache/incubator-seata-go/pull/523" target="_blank" rel="noopener noreferrer">#523</a>] Optimise CI process</li>
-<li>[<a href="https://github.com/apache/incubator-seata-go/pull/525" target="_blank" rel="noopener noreferrer">#525</a>] rename jackson serialisation to json</li>
-<li>[<a href="https://github.com/apache/incubator-seata-go/pull/532" target="_blank" rel="noopener noreferrer">#532</a>] Remove duplicate code</li>
-<li>[<a href="https://github.com/apache/incubator-seata-go/pull/536" target="_blank" rel="noopener noreferrer">#536</a>] optimise go import code formatting</li>
-<li>[<a href="https://github.com/apache/incubator-seata-go/pull/554" target="_blank" rel="noopener noreferrer">#554</a>] optimise xa mode performance</li>
-<li>[<a href="https://github.com/apache/incubator-seata-go/pull/561" target="_blank" rel="noopener noreferrer">#561</a>] Optimise xa mode logging output</li>
-</ul>
-<h3 class="anchor anchorWithStickyNavbar_LWe7" id="test">test<a href="#test" class="hash-link" aria-label="Direct link to test" title="Direct link to test"></a></h3>
-<ul>
-<li>[<a href="https://github.com/apache/incubator-seata-go/pull/535" target="_blank" rel="noopener noreferrer">#535</a>] Add integration tests.</li>
-</ul>
-<h3 class="anchor anchorWithStickyNavbar_LWe7" id="doc">doc<a href="#doc" class="hash-link" aria-label="Direct link to doc" title="Direct link to doc"></a></h3>
-<ul>
-<li>[<a href="https://github.com/apache/incubator-seata-go/pull/550" target="_blank" rel="noopener noreferrer">#550</a>] Added changelog for version 1.2.0.</li>
-</ul>
-<h3 class="anchor anchorWithStickyNavbar_LWe7" id="contributors">contributors<a href="#contributors" class="hash-link" aria-label="Direct link to contributors" title="Direct link to contributors"></a></h3>
-<p>Thanks to these contributors for their code commits. Please report an unintended omission.</p>
-<ul>
-<li><a href="https://github.com/georgehao" target="_blank" rel="noopener noreferrer">georgehao</a></li>
-<li><a href="https://github.com/luky116" target="_blank" rel="noopener noreferrer">luky116</a></li>
-<li><a href="https://github.com/jasondeng1997" target="_blank" rel="noopener noreferrer">jasondeng1997</a></li>
-<li><a href="https://github.com/106umao" target="_blank" rel="noopener noreferrer">106umao</a></li>
-<li><a href="https://github.com/wang1309" target="_blank" rel="noopener noreferrer">wang1309</a></li>
-<li><a href="https://github.com/iSuperCoder" target="_blank" rel="noopener noreferrer">iSuperCoder</a></li>
-<li><a href="https://github.com/Charlie17Li" target="_blank" rel="noopener noreferrer">Charlie17Li</a></li>
-<li><a href="https://github.com/Code-Fight" target="_blank" rel="noopener noreferrer">Code-Fight</a></li>
-<li><a href="https://github.com/Kirhaku" target="_blank" rel="noopener noreferrer">Kirhaku</a></li>
-<li><a href="https://github.com/VaderKai" target="_blank" rel="noopener noreferrer">Vaderkai</a></li>
-</ul>
-<h4 class="anchor anchorWithStickyNavbar_LWe7" id="link">Link<a href="#link" class="hash-link" aria-label="Direct link to Link" title="Direct link to Link"></a></h4>
-<ul>
-<li><a href="https://github.com/apache/incubator-seata" target="_blank" rel="noopener noreferrer">https://github.com/apache/incubator-seata</a></li>
-<li><a href="https://github.com/apache/incubator-seata-go" target="_blank" rel="noopener noreferrer">https://github.com/apache/incubator-seata-go</a></li>
-<li><a href="https://github.com/apache/incubator-seata-samples" target="_blank" rel="noopener noreferrer">https://github.com/apache/incubator-seata-samples</a></li>
-<li><a href="https://github.com/apache/incubator-seata-go-samples" target="_blank" rel="noopener noreferrer">https://github.com/apache/incubator-seata-go-samples</a></li>
-<li><a href="https://seata.apache.org" target="_blank" rel="noopener noreferrer">https://seata.apache.org</a></li>
-</ul></div><footer class="row docusaurus-mt-lg"></footer></article><nav class="pagination-nav" aria-label="Blog list page navigation"><a class="pagination-nav__link pagination-nav__link--next" href="/blog/page/2"><div class="pagination-nav__label">Older Entries</div></a></nav></main></div></div></div><footer class="footer"><div class="container container-fluid"><div class="footer__bottom text--center"><div class="margin-bottom--sm"><a href="https://incubator.apache.org/" target="_blank" [...]
+Prospect: Evolution of log observable system.</p></div><footer class="row docusaurus-mt-lg"></footer></article><nav class="pagination-nav" aria-label="Blog list page navigation"><a class="pagination-nav__link pagination-nav__link--next" href="/blog/page/2"><div class="pagination-nav__label">Older Entries</div></a></nav></main></div></div></div><footer class="footer"><div class="container container-fluid"><div class="footer__bottom text--center"><div class="margin-bottom--sm"><a href="htt [...]
<div class="fs-12">
<div class="center-div">
<span>Apache Seata (incubating) is an effort undergoing incubation at The Apache Software Foundation (ASF), sponsored by the Apache Incubator. Incubation is required of all newly accepted projects until a further review indicates that the infrastructure, communications, and decision making process have stabilized in a manner consistent with other successful ASF projects. While incubation status is not necessarily a reflection of the completeness or stability of the [...]
diff --git a/blog/integrate-seata-tcc-mode-with-spring-cloud/index.html b/blog/integrate-seata-tcc-mode-with-spring-cloud/index.html
index 67c0f1410e2..0cf9c013f6d 100644
--- a/blog/integrate-seata-tcc-mode-with-spring-cloud/index.html
+++ b/blog/integrate-seata-tcc-mode-with-spring-cloud/index.html
@@ -11,11 +11,11 @@
<meta name="aes-config" content="pid=xux-opensource&user_type=101&uid=&username=&dim10=seata"><link rel="stylesheet" href="/assets/css/styles.9644caf2.css">
-<script src="/assets/js/runtime~main.bf98ee01.js" defer="defer"></script>
-<script src="/assets/js/main.8371dd70.js" defer="defer"></script>
+<script src="/assets/js/runtime~main.762ed5c0.js" defer="defer"></script>
+<script src="/assets/js/main.aeea7339.js" defer="defer"></script>
</head>
<body class="navigation-with-keyboard">
-<script>!function(){function t(t){document.documentElement.setAttribute("data-theme",t)}var e=function(){try{return new URLSearchParams(window.location.search).get("docusaurus-theme")}catch(t){}}()||function(){try{return localStorage.getItem("theme")}catch(t){}}();t(null!==e?e:"light")}(),function(){try{const c=new URLSearchParams(window.location.search).entries();for(var[t,e]of c)if(t.startsWith("docusaurus-data-")){var a=t.replace("docusaurus-data-","data-");document.documentElement.se [...]
+<script>!function(){function t(t){document.documentElement.setAttribute("data-theme",t)}var e=function(){try{return new URLSearchParams(window.location.search).get("docusaurus-theme")}catch(t){}}()||function(){try{return localStorage.getItem("theme")}catch(t){}}();t(null!==e?e:"light")}(),function(){try{const c=new URLSearchParams(window.location.search).entries();for(var[t,e]of c)if(t.startsWith("docusaurus-data-")){var a=t.replace("docusaurus-data-","data-");document.documentElement.se [...]
<h1>一、The concept of TCC mode</h1>
<p>In Seata, a distributed global transaction follows a two-phase commit model with a Try-[Confirm/Cancel] pattern. Both the AT (Automatic Transaction) mode and the TCC (Try-Confirm-Cancel) mode in Seata are implementations of the two-phase commit. The main differences between them are as follows:</p>
<p>AT mode is based on relational databases that support local ACID transactions (currently supporting MySQL, Oracle, and PostgreSQL):</p>
diff --git a/blog/integrate-seata-with-spring-cloud/index.html b/blog/integrate-seata-with-spring-cloud/index.html
index 00d0e1441bb..f59aa0389e5 100644
--- a/blog/integrate-seata-with-spring-cloud/index.html
+++ b/blog/integrate-seata-with-spring-cloud/index.html
@@ -11,11 +11,11 @@
<meta name="aes-config" content="pid=xux-opensource&user_type=101&uid=&username=&dim10=seata"><link rel="stylesheet" href="/assets/css/styles.9644caf2.css">
-<script src="/assets/js/runtime~main.bf98ee01.js" defer="defer"></script>
-<script src="/assets/js/main.8371dd70.js" defer="defer"></script>
+<script src="/assets/js/runtime~main.762ed5c0.js" defer="defer"></script>
+<script src="/assets/js/main.aeea7339.js" defer="defer"></script>
</head>
<body class="navigation-with-keyboard">
-<script>!function(){function t(t){document.documentElement.setAttribute("data-theme",t)}var e=function(){try{return new URLSearchParams(window.location.search).get("docusaurus-theme")}catch(t){}}()||function(){try{return localStorage.getItem("theme")}catch(t){}}();t(null!==e?e:"light")}(),function(){try{const c=new URLSearchParams(window.location.search).entries();for(var[t,e]of c)if(t.startsWith("docusaurus-data-")){var a=t.replace("docusaurus-data-","data-");document.documentElement.se [...]
+<script>!function(){function t(t){document.documentElement.setAttribute("data-theme",t)}var e=function(){try{return new URLSearchParams(window.location.search).get("docusaurus-theme")}catch(t){}}()||function(){try{return localStorage.getItem("theme")}catch(t){}}();t(null!==e?e:"light")}(),function(){try{const c=new URLSearchParams(window.location.search).entries();for(var[t,e]of c)if(t.startsWith("docusaurus-data-")){var a=t.replace("docusaurus-data-","data-");document.documentElement.se [...]
<p>SEATA GITHUB: [<a href="https://github.com/apache/incubator-seata" target="_blank" rel="noopener noreferrer">https://github.com/apache/incubator-seata</a>]</p>
<p>We extend our sincere thanks and greetings to the Alibaba team for their contributions in bringing numerous open-source software to developers.</p>
<p>Today, I will share my insights on integrating Seata with Spring Cloud, aiming to help more developers avoid common pitfalls and streamline their setup process.</p>
diff --git a/blog/iscas2023/index.html b/blog/iscas2023/index.html
index 818c0932109..654a91554f3 100644
--- a/blog/iscas2023/index.html
+++ b/blog/iscas2023/index.html
@@ -11,11 +11,11 @@
<meta name="aes-config" content="pid=xux-opensource&user_type=101&uid=&username=&dim10=seata"><link rel="stylesheet" href="/assets/css/styles.9644caf2.css">
-<script src="/assets/js/runtime~main.bf98ee01.js" defer="defer"></script>
-<script src="/assets/js/main.8371dd70.js" defer="defer"></script>
+<script src="/assets/js/runtime~main.762ed5c0.js" defer="defer"></script>
+<script src="/assets/js/main.aeea7339.js" defer="defer"></script>
</head>
<body class="navigation-with-keyboard">
-<script>!function(){function t(t){document.documentElement.setAttribute("data-theme",t)}var e=function(){try{return new URLSearchParams(window.location.search).get("docusaurus-theme")}catch(t){}}()||function(){try{return localStorage.getItem("theme")}catch(t){}}();t(null!==e?e:"light")}(),function(){try{const c=new URLSearchParams(window.location.search).entries();for(var[t,e]of c)if(t.startsWith("docusaurus-data-")){var a=t.replace("docusaurus-data-","data-");document.documentElement.se [...]
+<script>!function(){function t(t){document.documentElement.setAttribute("data-theme",t)}var e=function(){try{return new URLSearchParams(window.location.search).get("docusaurus-theme")}catch(t){}}()||function(){try{return localStorage.getItem("theme")}catch(t){}}();t(null!==e?e:"light")}(),function(){try{const c=new URLSearchParams(window.location.search).entries();for(var[t,e]of c)if(t.startsWith("docusaurus-data-")){var a=t.replace("docusaurus-data-","data-");document.documentElement.se [...]
<p>The registration period for Open Source Summer 2023 runs from <strong>April 29th to June 4th</strong>, and we welcome registration for Seata 2023 topics! Here, you will have the opportunity to delve into the theory and application of distributed transactions, and collaborate with students from different backgrounds to complete practical projects. We look forward to your active participation and contribution, jointly promoting the development of the distributed transaction field.</p>
<p><img decoding="async" loading="lazy" alt="summer2023-1" src="/assets/images/summer2023-1-354d728bacb1640f84811b82ac954a9d.jpg" width="1290" height="2796" class="img_ev3q"></p>
<h3 class="anchor anchorWithStickyNavbar_LWe7" id="seata-open-source-summer-2023">Seata Open Source Summer 2023<a href="#seata-open-source-summer-2023" class="hash-link" aria-label="Direct link to Seata Open Source Summer 2023" title="Direct link to Seata Open Source Summer 2023"></a></h3>
diff --git a/blog/manual-transaction-mode/index.html b/blog/manual-transaction-mode/index.html
index 0118342c36d..b7ba6f46114 100644
--- a/blog/manual-transaction-mode/index.html
+++ b/blog/manual-transaction-mode/index.html
@@ -11,11 +11,11 @@
<meta name="aes-config" content="pid=xux-opensource&user_type=101&uid=&username=&dim10=seata"><link rel="stylesheet" href="/assets/css/styles.9644caf2.css">
-<script src="/assets/js/runtime~main.bf98ee01.js" defer="defer"></script>
-<script src="/assets/js/main.8371dd70.js" defer="defer"></script>
+<script src="/assets/js/runtime~main.762ed5c0.js" defer="defer"></script>
+<script src="/assets/js/main.aeea7339.js" defer="defer"></script>
</head>
<body class="navigation-with-keyboard">
-<script>!function(){function t(t){document.documentElement.setAttribute("data-theme",t)}var e=function(){try{return new URLSearchParams(window.location.search).get("docusaurus-theme")}catch(t){}}()||function(){try{return localStorage.getItem("theme")}catch(t){}}();t(null!==e?e:"light")}(),function(){try{const c=new URLSearchParams(window.location.search).entries();for(var[t,e]of c)if(t.startsWith("docusaurus-data-")){var a=t.replace("docusaurus-data-","data-");document.documentElement.se [...]
+<script>!function(){function t(t){document.documentElement.setAttribute("data-theme",t)}var e=function(){try{return new URLSearchParams(window.location.search).get("docusaurus-theme")}catch(t){}}()||function(){try{return localStorage.getItem("theme")}catch(t){}}();t(null!==e?e:"light")}(),function(){try{const c=new URLSearchParams(window.location.search).entries();for(var[t,e]of c)if(t.startsWith("docusaurus-data-")){var a=t.replace("docusaurus-data-","data-");document.documentElement.se [...]
<ul>
<li>One phase prepare behavior</li>
<li>Two phase commit or rollback behavior</li>
diff --git a/blog/page/2/index.html b/blog/page/2/index.html
index 89900ab6fbc..11465b1a239 100644
--- a/blog/page/2/index.html
+++ b/blog/page/2/index.html
@@ -11,11 +11,73 @@
<meta name="aes-config" content="pid=xux-opensource&user_type=101&uid=&username=&dim10=seata"><link rel="stylesheet" href="/assets/css/styles.9644caf2.css">
-<script src="/assets/js/runtime~main.bf98ee01.js" defer="defer"></script>
-<script src="/assets/js/main.8371dd70.js" defer="defer"></script>
+<script src="/assets/js/runtime~main.762ed5c0.js" defer="defer"></script>
+<script src="/assets/js/main.aeea7339.js" defer="defer"></script>
</head>
<body class="navigation-with-keyboard">
-<script>!function(){function t(t){document.documentElement.setAttribute("data-theme",t)}var e=function(){try{return new URLSearchParams(window.location.search).get("docusaurus-theme")}catch(t){}}()||function(){try{return localStorage.getItem("theme")}catch(t){}}();t(null!==e?e:"light")}(),function(){try{const c=new URLSearchParams(window.location.search).entries();for(var[t,e]of c)if(t.startsWith("docusaurus-data-")){var a=t.replace("docusaurus-data-","data-");document.documentElement.se [...]
+<script>!function(){function t(t){document.documentElement.setAttribute("data-theme",t)}var e=function(){try{return new URLSearchParams(window.location.search).get("docusaurus-theme")}catch(t){}}()||function(){try{return localStorage.getItem("theme")}catch(t){}}();t(null!==e?e:"light")}(),function(){try{const c=new URLSearchParams(window.location.search).entries();for(var[t,e]of c)if(t.startsWith("docusaurus-data-")){var a=t.replace("docusaurus-data-","data-");document.documentElement.se [...]
+<p>Seata is an open source distributed transaction solution that provides high-performance and easy-to-use distributed transaction services.</p>
+<h3 class="anchor anchorWithStickyNavbar_LWe7" id="release-overview">Release overview<a href="#release-overview" class="hash-link" aria-label="Direct link to Release overview" title="Direct link to Release overview"></a></h3>
+<p>Seata-go version 1.2.0 supports the XA schema, a distributed transaction processing specification proposed by the X/Open organisation, which has the advantage of being non-intrusive to business code. Currently, Seata-go's XA mode supports MySQL databases. So far, seata-go has gathered three transaction modes: AT, TCC and XA. Main features of XA mode.</p>
+<ul>
+<li>Supported XA data source proxy <a href="https://github.com/apache/incubator-seata-go-samples/tree/main/xa" target="_blank" rel="noopener noreferrer">https://github.com/apache/incubator-seata-go-samples/tree/main/xa</a></li>
+<li>XA transaction mode is supported.
+XA related sampes can be found in the following example: <a href="https://github.com/apache/incubator-seata-go-samples/tree/main/xa" target="_blank" rel="noopener noreferrer">https://github.com/apache/incubator-seata-go-samples/tree/main/xa</a></li>
+</ul>
+<h3 class="anchor anchorWithStickyNavbar_LWe7" id="feature">feature<a href="#feature" class="hash-link" aria-label="Direct link to feature" title="Direct link to feature"></a></h3>
+<ul>
+<li>[<a href="https://github.com/apache/incubator-seata-go/pull/467" target="_blank" rel="noopener noreferrer">#467</a>] implements XA schema support for MySQL.</li>
+<li>[<a href="https://github.com/apache/incubator-seata-go/pull/534" target="_blank" rel="noopener noreferrer">#534</a>] Load balancing for session support.</li>
+</ul>
+<h3 class="anchor anchorWithStickyNavbar_LWe7" id="bugfix">bugfix<a href="#bugfix" class="hash-link" aria-label="Direct link to bugfix" title="Direct link to bugfix"></a></h3>
+<ul>
+<li>[<a href="https://github.com/apache/incubator-seata-go/pull/540" target="_blank" rel="noopener noreferrer">#540</a>] Fix a bug in initialising xa mode.</li>
+<li>[<a href="https://github.com/apache/incubator-seata-go/pull/545" target="_blank" rel="noopener noreferrer">#545</a>] Fix a bug in getting db version number in xa mode.</li>
+<li>[<a href="https://github.com/apache/incubator-seata-go/pull/548" target="_blank" rel="noopener noreferrer">#548</a>] Fix bug where starting xa fails.</li>
+<li>[<a href="https://github.com/apache/incubator-seata-go/pull/556" target="_blank" rel="noopener noreferrer">#556</a>] Fix bug in xa datasource.</li>
+<li>[<a href="https://github.com/apache/incubator-seata-go/pull/562" target="_blank" rel="noopener noreferrer">#562</a>] Fix bug with committing xa global transaction</li>
+<li>[<a href="https://github.com/apache/incubator-seata-go/pull/564" target="_blank" rel="noopener noreferrer">#564</a>] Fix bug committing xa branching transactions</li>
+<li>[<a href="https://github.com/apache/incubator-seata-go/pull/566" target="_blank" rel="noopener noreferrer">#566</a>] Fix bug with local transactions using xa data source.</li>
+</ul>
+<h3 class="anchor anchorWithStickyNavbar_LWe7" id="optimise">optimise<a href="#optimise" class="hash-link" aria-label="Direct link to optimise" title="Direct link to optimise"></a></h3>
+<ul>
+<li>[<a href="https://github.com/apache/incubator-seata-go/pull/523" target="_blank" rel="noopener noreferrer">#523</a>] Optimise CI process</li>
+<li>[<a href="https://github.com/apache/incubator-seata-go/pull/525" target="_blank" rel="noopener noreferrer">#525</a>] rename jackson serialisation to json</li>
+<li>[<a href="https://github.com/apache/incubator-seata-go/pull/532" target="_blank" rel="noopener noreferrer">#532</a>] Remove duplicate code</li>
+<li>[<a href="https://github.com/apache/incubator-seata-go/pull/536" target="_blank" rel="noopener noreferrer">#536</a>] optimise go import code formatting</li>
+<li>[<a href="https://github.com/apache/incubator-seata-go/pull/554" target="_blank" rel="noopener noreferrer">#554</a>] optimise xa mode performance</li>
+<li>[<a href="https://github.com/apache/incubator-seata-go/pull/561" target="_blank" rel="noopener noreferrer">#561</a>] Optimise xa mode logging output</li>
+</ul>
+<h3 class="anchor anchorWithStickyNavbar_LWe7" id="test">test<a href="#test" class="hash-link" aria-label="Direct link to test" title="Direct link to test"></a></h3>
+<ul>
+<li>[<a href="https://github.com/apache/incubator-seata-go/pull/535" target="_blank" rel="noopener noreferrer">#535</a>] Add integration tests.</li>
+</ul>
+<h3 class="anchor anchorWithStickyNavbar_LWe7" id="doc">doc<a href="#doc" class="hash-link" aria-label="Direct link to doc" title="Direct link to doc"></a></h3>
+<ul>
+<li>[<a href="https://github.com/apache/incubator-seata-go/pull/550" target="_blank" rel="noopener noreferrer">#550</a>] Added changelog for version 1.2.0.</li>
+</ul>
+<h3 class="anchor anchorWithStickyNavbar_LWe7" id="contributors">contributors<a href="#contributors" class="hash-link" aria-label="Direct link to contributors" title="Direct link to contributors"></a></h3>
+<p>Thanks to these contributors for their code commits. Please report an unintended omission.</p>
+<ul>
+<li><a href="https://github.com/georgehao" target="_blank" rel="noopener noreferrer">georgehao</a></li>
+<li><a href="https://github.com/luky116" target="_blank" rel="noopener noreferrer">luky116</a></li>
+<li><a href="https://github.com/jasondeng1997" target="_blank" rel="noopener noreferrer">jasondeng1997</a></li>
+<li><a href="https://github.com/106umao" target="_blank" rel="noopener noreferrer">106umao</a></li>
+<li><a href="https://github.com/wang1309" target="_blank" rel="noopener noreferrer">wang1309</a></li>
+<li><a href="https://github.com/iSuperCoder" target="_blank" rel="noopener noreferrer">iSuperCoder</a></li>
+<li><a href="https://github.com/Charlie17Li" target="_blank" rel="noopener noreferrer">Charlie17Li</a></li>
+<li><a href="https://github.com/Code-Fight" target="_blank" rel="noopener noreferrer">Code-Fight</a></li>
+<li><a href="https://github.com/Kirhaku" target="_blank" rel="noopener noreferrer">Kirhaku</a></li>
+<li><a href="https://github.com/VaderKai" target="_blank" rel="noopener noreferrer">Vaderkai</a></li>
+</ul>
+<h4 class="anchor anchorWithStickyNavbar_LWe7" id="link">Link<a href="#link" class="hash-link" aria-label="Direct link to Link" title="Direct link to Link"></a></h4>
+<ul>
+<li><a href="https://github.com/apache/incubator-seata" target="_blank" rel="noopener noreferrer">https://github.com/apache/incubator-seata</a></li>
+<li><a href="https://github.com/apache/incubator-seata-go" target="_blank" rel="noopener noreferrer">https://github.com/apache/incubator-seata-go</a></li>
+<li><a href="https://github.com/apache/incubator-seata-samples" target="_blank" rel="noopener noreferrer">https://github.com/apache/incubator-seata-samples</a></li>
+<li><a href="https://github.com/apache/incubator-seata-go-samples" target="_blank" rel="noopener noreferrer">https://github.com/apache/incubator-seata-go-samples</a></li>
+<li><a href="https://seata.apache.org" target="_blank" rel="noopener noreferrer">https://seata.apache.org</a></li>
+</ul></div><footer class="row docusaurus-mt-lg"></footer></article><article class="margin-bottom--xl" itemprop="blogPost" itemscope="" itemtype="https://schema.org/BlogPosting"><meta itemprop="description" content="Welcome everyone to register for Seata Open Source Summer 2023 topics"><meta itemprop="keywords" content="open source summer,seata,distributed transaction"><header><h2 class="title_f1Hy" itemprop="headline"><a itemprop="url" href="/blog/iscas2023">6 Major Topics Now Open for S [...]
<p>The registration period for Open Source Summer 2023 runs from <strong>April 29th to June 4th</strong>, and we welcome registration for Seata 2023 topics! Here, you will have the opportunity to delve into the theory and application of distributed transactions, and collaborate with students from different backgrounds to complete practical projects. We look forward to your active participation and contribution, jointly promoting the development of the distributed transaction field.</p>
<p><img decoding="async" loading="lazy" alt="summer2023-1" src="/assets/images/summer2023-1-354d728bacb1640f84811b82ac954a9d.jpg" width="1290" height="2796" class="img_ev3q"></p>
<h3 class="anchor anchorWithStickyNavbar_LWe7" id="seata-open-source-summer-2023">Seata Open Source Summer 2023<a href="#seata-open-source-summer-2023" class="hash-link" aria-label="Direct link to Seata Open Source Summer 2023" title="Direct link to Seata Open Source Summer 2023"></a></h3>
@@ -618,116 +680,7 @@ Page splits are unfriendly to I/O, requiring the creation of new data pages, cop
<p>Decompress the corresponding information when rolling back:</p>
<div class="language-java codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_biex"><pre tabindex="0" class="prism-code language-java codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><span class="token-line" style="color:#393A34"><span class="token keyword" style="color:#00009f">protected</span><span class="token plain"> </span><span class="toke [...]
<h3 class="anchor anchorWithStickyNavbar_LWe7" id="peroration">peroration<a href="#peroration" class="hash-link" aria-label="Direct link to peroration" title="Direct link to peroration"></a></h3>
-<p>By compressing undo_log, Seata can further improve its performance when processing large amounts of data at the framework level. At the same time, it also provides the corresponding switch and relatively reasonable default value, which is convenient for users to use out of the box, but also convenient for users to adjust according to actual needs, so that the corresponding function is more suitable for the actual use scenario.</p></div><footer class="row docusaurus-mt-lg"></footer></a [...]
-<li>seata version: 1.4.0, but all versions below 1.4 also have this problem.</li>
-<li>Problem description: In a global transaction, a pure query operation on a branch transaction suddenly gets stuck without any feedback (logs/exceptions) until the RPC timeout on the consumer side</li>
-</ol>
-<p>! <a href="https://p3-juejin.byteimg.com/tos-cn-i-k3u1fbpfcp/03a7f737b56e45b4b74e662033ec74f6~tplv-k3u1fbpfcp-watermark.image" target="_blank" rel="noopener noreferrer">image.png</a></p>
-<h1>Problem Troubleshooting</h1>
-<ol>
-<li>The whole process is in a global transaction, the consumer and provider can be seen as two branches of the global transaction, consumer --> provider.</li>
-<li>the consumer first executes some local logic, and then sends an RPC request to the provider to make sure that the consumer has sent the request and the provider has received it.</li>
-<li>the provider first prints a log, and then executes a pure query SQL, if the SQL is executed properly, it will print the log, but the current phenomenon is that only the log before the execution of the SQL is printed, and no SQL-related logs are printed. Find DBA to check the SQL log, and found that the SQL is not executed.</li>
-<li>Determined that the operation is only a pure query operation under the global transaction, before the operation, the overall process of the global transaction is completely normal.</li>
-<li>In fact, the phenomenon here has been very obvious, but at that time the idea did not change over, has been concerned about the query SQL, always thinking that even if the query timeout and other reasons should be thrown exceptions ah, should not be nothing. DBA can not find the query record, that is not to say that the SQL may not have been executed ah, but in the execution of the SQL before the problem, such as the agent?</li>
-<li>With the help of arthas's watch command, there is no output. The first log output means that the method must have been executed, and the delay in outputting the result means that the current request is stuck, why is it stuck?</li>
-<li>With arthas's thread command <code>thread -b</code>, <code>thread -n</code>, is to find out the current busiest thread. This works very well, there is a thread CPU usage <code>92%</code>, and because of this thread caused the other 20 or so Dubbo threads <code>BLOCKED</code>. The stack information is as follows</li>
-<li>Analysing the stack information, we can clearly find the interface related to seata, which is probably related to seata's data source proxy; at the same time, we found that the thread with the highest CPU usage is stuck in the <code>ConcurrentHashMap#computeIfAbsent</code> method. Is there a bug in the <code>ConcurrentHashMap#computeIfAbsent</code> method?</li>
-<li>By now, we don't know the exact cause of the problem, but it should have something to do with seata's data source proxy, and we need to analyse both the business code and the seata code to find out why.</li>
-</ol>
-<p>! <a href="https://p1-juejin.byteimg.com/tos-cn-i-k3u1fbpfcp/faac0be0982e45a7a43b335e8f8b44bf~tplv-k3u1fbpfcp-watermark.image" target="_blank" rel="noopener noreferrer">image.png</a></p>
-<h2 class="anchor anchorWithStickyNavbar_LWe7" id="problem-analysis">Problem analysis<a href="#problem-analysis" class="hash-link" aria-label="Direct link to Problem analysis" title="Direct link to Problem analysis"></a></h2>
-<h3 class="anchor anchorWithStickyNavbar_LWe7" id="concurrenthashmapcomputeifabsent">ConcurrentHashMap##computeIfAbsent<a href="#concurrenthashmapcomputeifabsent" class="hash-link" aria-label="Direct link to ConcurrentHashMap##computeIfAbsent" title="Direct link to ConcurrentHashMap##computeIfAbsent"></a></h3>
-<p>This method does have the potential for problems: if two keys have the same hascode, and the computeIfAbsent operation is performed in the corresponding mappingFunction, it will lead to a dead loop, refer to this article for specific analysis: <a href="https://juejin.cn/post/" target="_blank" rel="noopener noreferrer">https://juejin.cn/post/</a> 6844904191077384200</p>
-<h3 class="anchor anchorWithStickyNavbar_LWe7" id="seata-data-source-autoproxy">Seata data source autoproxy<a href="#seata-data-source-autoproxy" class="hash-link" aria-label="Direct link to Seata data source autoproxy" title="Direct link to Seata data source autoproxy"></a></h3>
-<p>Related content has been analysed before, let's focus on the following core classes:</p>
-<ol>
-<li>SeataDataSourceBeanPostProcessor</li>
-<li>SeataAutoDataSourceProxyAdvice</li>
-<li>DataSourceProxyHolder</li>
-</ol>
-<h5 class="anchor anchorWithStickyNavbar_LWe7" id="seatadatasourcebeanpostprocessor">SeataDataSourceBeanPostProcessor<a href="#seatadatasourcebeanpostprocessor" class="hash-link" aria-label="Direct link to SeataDataSourceBeanPostProcessor" title="Direct link to SeataDataSourceBeanPostProcessor"></a></h5>
-<p>The <code>SeataDataSourceBeanPostProcessor</code> is a <code>BeanPostProcessor</code> implementation class that creates a <code>seataAutoDataSourceProxyDataSource</code> for the data source configured by the business side in the <code>postProcessAfterInitialization</code> method (i.e., after the bean is initialised). proxy data source</p>
-<div class="language-java codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_biex"><pre tabindex="0" class="prism-code language-java codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><span class="token-line" style="color:#393A34"><span class="token keyword" style="color:#00009f">public</span><span class="token plain"> </span><span class="token k [...]
-<h5 class="anchor anchorWithStickyNavbar_LWe7" id="seataautodatasourceproxyadvice">SeataAutoDataSourceProxyAdvice<a href="#seataautodatasourceproxyadvice" class="hash-link" aria-label="Direct link to SeataAutoDataSourceProxyAdvice" title="Direct link to SeataAutoDataSourceProxyAdvice"></a></h5>
-<p><code>SeataAutoDataSourceProxyAdvice</code> is a MethodInterceptor, <code>SeataAutoDataSourceProxyCreator</code> in seata creates a dynamic proxy object for <code>Bean</code> of type <code>DataSource</code>, the proxy logic is the <code>SeataAutoDataSourceProxyAdvice#invoke</code> logic. That is: when executing the relevant methods of the <code>DataSourceAOPProxyAdvice</code>, it will go through its <code>invoke</code> method, and in the <code>invoke</code> method, it will find the co [...]
-<div class="language-java codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_biex"><pre tabindex="0" class="prism-code language-java codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><span class="token-line" style="color:#393A34"><span class="token keyword" style="color:#00009f">public</span><span class="token plain"> </span><span class="token k [...]
-<h5 class="anchor anchorWithStickyNavbar_LWe7" id="datasourceproxyholder">DataSourceProxyHolder<a href="#datasourceproxyholder" class="hash-link" aria-label="Direct link to DataSourceProxyHolder" title="Direct link to DataSourceProxyHolder"></a></h5>
-<p>The process is clear to us, now there is a question, how to maintain the relationship between <code>native data source</code> and <code>seata proxy data source</code>? It is maintained by <code>DataSourceProxyHolder</code>, which is a singleton object that maintains the relationship between the two through a ConcurrentHashMap: <code>native data source</code> as key --> <code>seata proxy data source</code> as value.</p>
-<div class="language-java codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_biex"><pre tabindex="0" class="prism-code language-java codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><span class="token-line" style="color:#393A34"><span class="token keyword" style="color:#00009f">public</span><span class="token plain"> </span><span class="token k [...]
-<h3 class="anchor anchorWithStickyNavbar_LWe7" id="client-data-source-configuration">Client data source configuration<a href="#client-data-source-configuration" class="hash-link" aria-label="Direct link to Client data source configuration" title="Direct link to Client data source configuration"></a></h3>
-<ol>
-<li>Two data sources are configured: <code>DynamicDataSource</code>, <code>P6DataSource</code>, <code>P6DataSource</code>, <code>P6DataSource</code> and <code>P6DataSource</code>.</li>
-<li><code>P6DataSource</code> can be seen as a wrapper for <code>DynamicDataSource</code>. 3.</li>
-<li>Let's not worry about whether this configuration makes sense or not, now we just analyse the problem purely based on this data source configuration.</li>
-</ol>
-<div class="language-java codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_biex"><pre tabindex="0" class="prism-code language-java codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><span class="token-line" style="color:#393A34"><span class="token annotation punctuation" style="color:#393A34">@Qualifier</span><span class="token punctuation" sty [...]
-<h3 class="anchor anchorWithStickyNavbar_LWe7" id="analyse-the-process">Analyse the process<a href="#analyse-the-process" class="hash-link" aria-label="Direct link to Analyse the process" title="Direct link to Analyse the process"></a></h3>
-<p><code>Assuming that by now everyone is aware of the problems that may arise from ConcurrentHashMap#computeIfAbsent</code>, it is known that this problem has now arisen, and in combination with the stack information, we can see roughly where this problem has arisen.</p>
-<p>1, <code>ConcurrentHashMap#computeIfAbsent</code> will produce this problem precondition is: <code>two key hashcode is the same</code>; <code>mappingFunction corresponds to a put operation</code>. Combined with our seata usage scenario, the mappingFunction corresponds to <code>DataSourceProxy::new</code>, suggesting that the put operation may be triggered in the DataSourceProxy's constructor method</p>
-<p>! <a href="https://p1-juejin.byteimg.com/tos-cn-i-k3u1fbpfcp/00d8e13f71644c63b3bbb58c93b30e0c~tplv-k3u1fbpfcp-watermark.image" target="_blank" rel="noopener noreferrer">image.png</a></p>
-<div class="language-java codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_biex"><pre tabindex="0" class="prism-code language-java codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><span class="token-line" style="color:#393A34"><span class="token class-name">Execute</span><span class="token plain"> </span><span class="token constant" style="co [...]
-<p>2, What is the <code>AOP proxy data source</code> and <code>native data source</code> stated in step 1? Look at the following diagram
-! <a href="https://p3-juejin.byteimg.com/tos-cn-i-k3u1fbpfcp/3579631f58df4d17bfcd6f28ccc3fd79~tplv-k3u1fbpfcp-watermark.image" target="_blank" rel="noopener noreferrer">image.png</a></p>
-<p>3, the above also said to produce this problem there is a condition <code>two key hashcode the same</code>, but I see that these two data source objects are not overriding the <code>hashcode</code> method, so by definition, these two objects must be different hashcode. After looking at the ConcurrentHashMap problem again, I feel that the statement <code>two keys have the same hashcode</code> is not correct, and <code>two keys will generate hash conflict</code> is more reasonable, whic [...]
-<div class="language-java codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_biex"><pre tabindex="0" class="prism-code language-java codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><span class="token-line" style="color:#393A34"><span class="token keyword" style="color:#00009f">public</span><span class="token plain"> </span><span class="token k [...]
-<ol>
-<li>To make it easier to reproduce the problem, we rewrite the <code>Num#hashCode</code> method to ensure that the constructor input is the hashcode value.</li>
-<li>create a ConcurrentHashMap object, initialCapacity is 8, sizeCtl calculated value is 16, that is, the default length of the array in the map is 16</li>
-<li>create object <code>n1</code>, the input parameter is 3, that is, the hashcode is 3, the calculation of its corresponding array subscript 3</li>
-<li>create object <code>n2</code>, the input parameter is 19, that is, the hashcode is 19, calculate its corresponding array subscript is 3, at this time we can think of <code>n1 and n2 hash conflict</code>.</li>
-<li>create object <code>n3</code> with input 20, i.e., hashcode 20, and its corresponding array subscript is 4.</li>
-<li>execute <code>map.computeIfAbsent(n1, k1 -> map.computeIfAbsent(n3, k2 -> 200))</code>, the programme exits normally: <code>Because there is no hash conflict between n1 and n3, the programme terminates normally</code>.</li>
-<li>Execute <code>map.computeIfAbsent(n1, k1 -> map.computeIfAbsent(n2, k2 -> 200))</code>, the programme exits normally: <code> because n1 and n2 have a hash conflict, so it is in a dead loop</code>.</li>
-</ol>
-<p>4、During the initialisation of the object, hasn't <code>SeataDataSourceBeanPostProcessor</code> already initialised the corresponding data source proxy of the object? Why the corresponding data source proxy is still created in <code>SeataAutoDataSourceProxyAdvice</code>?</p>
-<ol>
-<li>First of all, the <code>SeataDataSourceBeanPostProcessor</code> execution period is later than the creation of the AOP proxy object, so when executing the <code>SeataDataSourceBeanPostProcessor</code> related methods, the <code>SeataAutoDataSourceBeanPostProcessor</code> method is executed. SeataAutoDataSourceProxyAdvice<code>should actually take effect when the</code>SeataDataSourceBeanPostProcessor` related methods are executed.</li>
-<li>when adding elements to the map in <code>SeataDataSourceBeanPostProcessor</code>, the key is <code>AOP proxy datasource</code>; in <code>SeataAutoDataSourceProxyAdvice</code>, the key is <code>native datasource</code>, so the key is not the same as <code>invocation.getThis()</code>, so the key is not the same. `, so the key is not the same</li>
-</ol>
-<p>! <a href="https://p6-juejin.byteimg.com/tos-cn-i-k3u1fbpfcp/747b664a0b6c4f58843947576dd0856e~tplv-k3u1fbpfcp-watermark.image" target="_blank" rel="noopener noreferrer">image.png</a></p>
-<p>5, there is another problem, <code>SeataAutoDataSourceProxyAdvic#invoke</code> method does not filter <code>toString, hashCode</code> and other methods, the proxy object created by cglib will override these methods by default, if these methods of the proxy object are triggered when putting elements into the map. If these methods are triggered when putting elements into the map, the proxy object will re-enter the <code>SeataAutoDataSourceProxyAdvic#invoke</code> cut until the thread st [...]
-<h1>Summary of the problem</h1>
-<ol>
-<li>in two key will produce hash conflict, will trigger <code>ConcurrentHashMap#computeIfAbsent</code> BUG, the performance of this BUG is to make the current thread into a dead loop</li>
-<li>business feedback, the problem is occasional, occasional for two reasons: first, the application is a multi-node deployment, but only one node on the line triggered the BUG (hashcode conflict), so only when the request hits this node may trigger the BUG; second, because each restart object address (hashcode) are not sure, so not triggered after every app restart, but if once triggered, the node will always have this problem. Having a thread that keeps dying and blocking other threads [...]
-<li>when encountering this problem, from the perspective of the whole problem, it is indeed a deadlock, because the dead loop thread occupant lock has not been released, resulting in other threads operating on the map is BLOCKED!</li>
-<li>essentially because <code>ConcurrentHashMap#computeIfAbsent method may trigger a bug</code>, and seata's usage scenario just triggered the bug.</li>
-<li>The following demo is actually a complete simulation of what happens when something goes wrong online, as follows:</li>
-</ol>
-<div class="language-java codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_biex"><pre tabindex="0" class="prism-code language-java codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><span class="token-line" style="color:#393A34"><span class="token keyword" style="color:#00009f">public</span><span class="token plain"> </span><span class="token k [...]
-<p>! <a href="https://p6-juejin.byteimg.com/tos-cn-i-k3u1fbpfcp/d6134c6498fa49c4a68b2745ba0895e3~tplv-k3u1fbpfcp-watermark.image" target="_blank" rel="noopener noreferrer">image.png</a></p>
-<h3 class="anchor anchorWithStickyNavbar_LWe7" id="solving-the-problem">Solving the problem<a href="#solving-the-problem" class="hash-link" aria-label="Direct link to Solving the problem" title="Direct link to Solving the problem"></a></h3>
-<p>The problem can be solved in two ways:</p>
-<ol>
-<li>business changes: P6DataSource and DynamicDataSource do not need to be proxied, directly proxy P6DataSource can be, DynamicDataSource does not need to be declared as a bean; or through the excludes property excludes P6DataSource, so that there is no duplicate proxy problem. There will be no problem of duplicate proxies</li>
-<li>Seata refinement: improve the logic related to data source proxy</li>
-</ol>
-<h5 class="anchor anchorWithStickyNavbar_LWe7" id="business-changes">Business changes<a href="#business-changes" class="hash-link" aria-label="Direct link to Business changes" title="Direct link to Business changes"></a></h5>
-<ol>
-<li>Data source related configuration can be changed to the following:</li>
-</ol>
-<div class="language-java codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_biex"><pre tabindex="0" class="prism-code language-java codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><span class="token-line" style="color:#393A34"><span class="token annotation punctuation" style="color:#393A34">@Primary</span><span class="token plain"></span><br> [...]
-<ol start="2">
-<li>Or leave the current data source configuration unchanged and add the excludes property</li>
-</ol>
-<div class="language-java codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_biex"><pre tabindex="0" class="prism-code language-java codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><span class="token-line" style="color:#393A34"><span class="token annotation punctuation" style="color:#393A34">@EnableAutoDataSourceProxy</span><span class="token [...]
-<h5 class="anchor anchorWithStickyNavbar_LWe7" id="seata-refinement">Seata refinement<a href="#seata-refinement" class="hash-link" aria-label="Direct link to Seata refinement" title="Direct link to Seata refinement"></a></h5>
-<ol>
-<li><code>ConcurrentHashMap#computeIfAbsent</code> method is changed to double check as follows:</li>
-</ol>
-<div class="language-java codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_biex"><pre tabindex="0" class="prism-code language-java codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><span class="token-line" style="color:#393A34"><span class="token class-name">SeataDataSourceProxy</span><span class="token plain"> dsProxy </span><span class="toke [...]
-<p>I wanted to change the <code>CollectionUtils#computeIfAbsent</code> method directly, and the feedback from the group was that this might cause the data source to be created multiple times, which is indeed a problem: as follows</p>
-<div class="language-java codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_biex"><pre tabindex="0" class="prism-code language-java codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><span class="token-line" style="color:#393A34"><span class="token keyword" style="color:#00009f">public</span><span class="token plain"> </span><span class="token k [...]
-<ol start="2">
-<li>Add some filtering to the SeataAutoDataSourceProxyAdvice cutout logic</li>
-</ol>
-<div class="language-java codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_biex"><pre tabindex="0" class="prism-code language-java codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><span class="token-line" style="color:#393A34"><span class="token class-name">Method</span><span class="token plain"> m </span><span class="token operator" style="c [...]
-<h3 class="anchor anchorWithStickyNavbar_LWe7" id="legacy-issues">Legacy issues<a href="#legacy-issues" class="hash-link" aria-label="Direct link to Legacy issues" title="Direct link to Legacy issues"></a></h3>
-<p>In the corresponding methods of <code>SeataDataSourceBeanPostProcessor</code> and <code>SeataAutoDataSourceProxyAdvice</code>, the keys corresponding to initialising the <code>seata datasource proxy</code> into the map are fundamentally different, the <code>The key in</code>SeataDataSourceBeanPostProcessor<code>is the</code>AOP proxy data source<code>; the key in </code>SeataAutoDataSourceProxyAdvice<code>is the native object, which results in the unnecessary creation of the</code>sea [...]
-<p>What is the best suggestion for this problem? Is it possible to specify an order for <code>SeataDataSourceBeanPostProcessor</code> to take effect before the AOP proxy object is created?</p>
-<h1>Link to original article</h1>
-<p><a href="https://juejin.cn/post/6939041336964153352/" target="_blank" rel="noopener noreferrer">https://juejin.cn/post/6939041336964153352/</a></p></div><footer class="row docusaurus-mt-lg"></footer></article><nav class="pagination-nav" aria-label="Blog list page navigation"><a class="pagination-nav__link pagination-nav__link--prev" href="/blog"><div class="pagination-nav__label">Newer Entries</div></a><a class="pagination-nav__link pagination-nav__link--next" href="/blog/page/3"><div [...]
+<p>By compressing undo_log, Seata can further improve its performance when processing large amounts of data at the framework level. At the same time, it also provides the corresponding switch and relatively reasonable default value, which is convenient for users to use out of the box, but also convenient for users to adjust according to actual needs, so that the corresponding function is more suitable for the actual use scenario.</p></div><footer class="row docusaurus-mt-lg"></footer></a [...]
<div class="fs-12">
<div class="center-div">
<span>Apache Seata (incubating) is an effort undergoing incubation at The Apache Software Foundation (ASF), sponsored by the Apache Incubator. Incubation is required of all newly accepted projects until a further review indicates that the infrastructure, communications, and decision making process have stabilized in a manner consistent with other successful ASF projects. While incubation status is not necessarily a reflection of the completeness or stability of the [...]
diff --git a/blog/page/3/index.html b/blog/page/3/index.html
index a7af5573b5a..feb2d34f4e2 100644
--- a/blog/page/3/index.html
+++ b/blog/page/3/index.html
@@ -11,11 +11,120 @@
<meta name="aes-config" content="pid=xux-opensource&user_type=101&uid=&username=&dim10=seata"><link rel="stylesheet" href="/assets/css/styles.9644caf2.css">
-<script src="/assets/js/runtime~main.bf98ee01.js" defer="defer"></script>
-<script src="/assets/js/main.8371dd70.js" defer="defer"></script>
+<script src="/assets/js/runtime~main.762ed5c0.js" defer="defer"></script>
+<script src="/assets/js/main.aeea7339.js" defer="defer"></script>
</head>
<body class="navigation-with-keyboard">
-<script>!function(){function t(t){document.documentElement.setAttribute("data-theme",t)}var e=function(){try{return new URLSearchParams(window.location.search).get("docusaurus-theme")}catch(t){}}()||function(){try{return localStorage.getItem("theme")}catch(t){}}();t(null!==e?e:"light")}(),function(){try{const c=new URLSearchParams(window.location.search).entries();for(var[t,e]of c)if(t.startsWith("docusaurus-data-")){var a=t.replace("docusaurus-data-","data-");document.documentElement.se [...]
+<script>!function(){function t(t){document.documentElement.setAttribute("data-theme",t)}var e=function(){try{return new URLSearchParams(window.location.search).get("docusaurus-theme")}catch(t){}}()||function(){try{return localStorage.getItem("theme")}catch(t){}}();t(null!==e?e:"light")}(),function(){try{const c=new URLSearchParams(window.location.search).entries();for(var[t,e]of c)if(t.startsWith("docusaurus-data-")){var a=t.replace("docusaurus-data-","data-");document.documentElement.se [...]
+<li>seata version: 1.4.0, but all versions below 1.4 also have this problem.</li>
+<li>Problem description: In a global transaction, a pure query operation on a branch transaction suddenly gets stuck without any feedback (logs/exceptions) until the RPC timeout on the consumer side</li>
+</ol>
+<p>! <a href="https://p3-juejin.byteimg.com/tos-cn-i-k3u1fbpfcp/03a7f737b56e45b4b74e662033ec74f6~tplv-k3u1fbpfcp-watermark.image" target="_blank" rel="noopener noreferrer">image.png</a></p>
+<h1>Problem Troubleshooting</h1>
+<ol>
+<li>The whole process is in a global transaction, the consumer and provider can be seen as two branches of the global transaction, consumer --> provider.</li>
+<li>the consumer first executes some local logic, and then sends an RPC request to the provider to make sure that the consumer has sent the request and the provider has received it.</li>
+<li>the provider first prints a log, and then executes a pure query SQL, if the SQL is executed properly, it will print the log, but the current phenomenon is that only the log before the execution of the SQL is printed, and no SQL-related logs are printed. Find DBA to check the SQL log, and found that the SQL is not executed.</li>
+<li>Determined that the operation is only a pure query operation under the global transaction, before the operation, the overall process of the global transaction is completely normal.</li>
+<li>In fact, the phenomenon here has been very obvious, but at that time the idea did not change over, has been concerned about the query SQL, always thinking that even if the query timeout and other reasons should be thrown exceptions ah, should not be nothing. DBA can not find the query record, that is not to say that the SQL may not have been executed ah, but in the execution of the SQL before the problem, such as the agent?</li>
+<li>With the help of arthas's watch command, there is no output. The first log output means that the method must have been executed, and the delay in outputting the result means that the current request is stuck, why is it stuck?</li>
+<li>With arthas's thread command <code>thread -b</code>, <code>thread -n</code>, is to find out the current busiest thread. This works very well, there is a thread CPU usage <code>92%</code>, and because of this thread caused the other 20 or so Dubbo threads <code>BLOCKED</code>. The stack information is as follows</li>
+<li>Analysing the stack information, we can clearly find the interface related to seata, which is probably related to seata's data source proxy; at the same time, we found that the thread with the highest CPU usage is stuck in the <code>ConcurrentHashMap#computeIfAbsent</code> method. Is there a bug in the <code>ConcurrentHashMap#computeIfAbsent</code> method?</li>
+<li>By now, we don't know the exact cause of the problem, but it should have something to do with seata's data source proxy, and we need to analyse both the business code and the seata code to find out why.</li>
+</ol>
+<p>! <a href="https://p1-juejin.byteimg.com/tos-cn-i-k3u1fbpfcp/faac0be0982e45a7a43b335e8f8b44bf~tplv-k3u1fbpfcp-watermark.image" target="_blank" rel="noopener noreferrer">image.png</a></p>
+<h2 class="anchor anchorWithStickyNavbar_LWe7" id="problem-analysis">Problem analysis<a href="#problem-analysis" class="hash-link" aria-label="Direct link to Problem analysis" title="Direct link to Problem analysis"></a></h2>
+<h3 class="anchor anchorWithStickyNavbar_LWe7" id="concurrenthashmapcomputeifabsent">ConcurrentHashMap##computeIfAbsent<a href="#concurrenthashmapcomputeifabsent" class="hash-link" aria-label="Direct link to ConcurrentHashMap##computeIfAbsent" title="Direct link to ConcurrentHashMap##computeIfAbsent"></a></h3>
+<p>This method does have the potential for problems: if two keys have the same hascode, and the computeIfAbsent operation is performed in the corresponding mappingFunction, it will lead to a dead loop, refer to this article for specific analysis: <a href="https://juejin.cn/post/" target="_blank" rel="noopener noreferrer">https://juejin.cn/post/</a> 6844904191077384200</p>
+<h3 class="anchor anchorWithStickyNavbar_LWe7" id="seata-data-source-autoproxy">Seata data source autoproxy<a href="#seata-data-source-autoproxy" class="hash-link" aria-label="Direct link to Seata data source autoproxy" title="Direct link to Seata data source autoproxy"></a></h3>
+<p>Related content has been analysed before, let's focus on the following core classes:</p>
+<ol>
+<li>SeataDataSourceBeanPostProcessor</li>
+<li>SeataAutoDataSourceProxyAdvice</li>
+<li>DataSourceProxyHolder</li>
+</ol>
+<h5 class="anchor anchorWithStickyNavbar_LWe7" id="seatadatasourcebeanpostprocessor">SeataDataSourceBeanPostProcessor<a href="#seatadatasourcebeanpostprocessor" class="hash-link" aria-label="Direct link to SeataDataSourceBeanPostProcessor" title="Direct link to SeataDataSourceBeanPostProcessor"></a></h5>
+<p>The <code>SeataDataSourceBeanPostProcessor</code> is a <code>BeanPostProcessor</code> implementation class that creates a <code>seataAutoDataSourceProxyDataSource</code> for the data source configured by the business side in the <code>postProcessAfterInitialization</code> method (i.e., after the bean is initialised). proxy data source</p>
+<div class="language-java codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_biex"><pre tabindex="0" class="prism-code language-java codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><span class="token-line" style="color:#393A34"><span class="token keyword" style="color:#00009f">public</span><span class="token plain"> </span><span class="token k [...]
+<h5 class="anchor anchorWithStickyNavbar_LWe7" id="seataautodatasourceproxyadvice">SeataAutoDataSourceProxyAdvice<a href="#seataautodatasourceproxyadvice" class="hash-link" aria-label="Direct link to SeataAutoDataSourceProxyAdvice" title="Direct link to SeataAutoDataSourceProxyAdvice"></a></h5>
+<p><code>SeataAutoDataSourceProxyAdvice</code> is a MethodInterceptor, <code>SeataAutoDataSourceProxyCreator</code> in seata creates a dynamic proxy object for <code>Bean</code> of type <code>DataSource</code>, the proxy logic is the <code>SeataAutoDataSourceProxyAdvice#invoke</code> logic. That is: when executing the relevant methods of the <code>DataSourceAOPProxyAdvice</code>, it will go through its <code>invoke</code> method, and in the <code>invoke</code> method, it will find the co [...]
+<div class="language-java codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_biex"><pre tabindex="0" class="prism-code language-java codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><span class="token-line" style="color:#393A34"><span class="token keyword" style="color:#00009f">public</span><span class="token plain"> </span><span class="token k [...]
+<h5 class="anchor anchorWithStickyNavbar_LWe7" id="datasourceproxyholder">DataSourceProxyHolder<a href="#datasourceproxyholder" class="hash-link" aria-label="Direct link to DataSourceProxyHolder" title="Direct link to DataSourceProxyHolder"></a></h5>
+<p>The process is clear to us, now there is a question, how to maintain the relationship between <code>native data source</code> and <code>seata proxy data source</code>? It is maintained by <code>DataSourceProxyHolder</code>, which is a singleton object that maintains the relationship between the two through a ConcurrentHashMap: <code>native data source</code> as key --> <code>seata proxy data source</code> as value.</p>
+<div class="language-java codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_biex"><pre tabindex="0" class="prism-code language-java codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><span class="token-line" style="color:#393A34"><span class="token keyword" style="color:#00009f">public</span><span class="token plain"> </span><span class="token k [...]
+<h3 class="anchor anchorWithStickyNavbar_LWe7" id="client-data-source-configuration">Client data source configuration<a href="#client-data-source-configuration" class="hash-link" aria-label="Direct link to Client data source configuration" title="Direct link to Client data source configuration"></a></h3>
+<ol>
+<li>Two data sources are configured: <code>DynamicDataSource</code>, <code>P6DataSource</code>, <code>P6DataSource</code>, <code>P6DataSource</code> and <code>P6DataSource</code>.</li>
+<li><code>P6DataSource</code> can be seen as a wrapper for <code>DynamicDataSource</code>. 3.</li>
+<li>Let's not worry about whether this configuration makes sense or not, now we just analyse the problem purely based on this data source configuration.</li>
+</ol>
+<div class="language-java codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_biex"><pre tabindex="0" class="prism-code language-java codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><span class="token-line" style="color:#393A34"><span class="token annotation punctuation" style="color:#393A34">@Qualifier</span><span class="token punctuation" sty [...]
+<h3 class="anchor anchorWithStickyNavbar_LWe7" id="analyse-the-process">Analyse the process<a href="#analyse-the-process" class="hash-link" aria-label="Direct link to Analyse the process" title="Direct link to Analyse the process"></a></h3>
+<p><code>Assuming that by now everyone is aware of the problems that may arise from ConcurrentHashMap#computeIfAbsent</code>, it is known that this problem has now arisen, and in combination with the stack information, we can see roughly where this problem has arisen.</p>
+<p>1, <code>ConcurrentHashMap#computeIfAbsent</code> will produce this problem precondition is: <code>two key hashcode is the same</code>; <code>mappingFunction corresponds to a put operation</code>. Combined with our seata usage scenario, the mappingFunction corresponds to <code>DataSourceProxy::new</code>, suggesting that the put operation may be triggered in the DataSourceProxy's constructor method</p>
+<p>! <a href="https://p1-juejin.byteimg.com/tos-cn-i-k3u1fbpfcp/00d8e13f71644c63b3bbb58c93b30e0c~tplv-k3u1fbpfcp-watermark.image" target="_blank" rel="noopener noreferrer">image.png</a></p>
+<div class="language-java codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_biex"><pre tabindex="0" class="prism-code language-java codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><span class="token-line" style="color:#393A34"><span class="token class-name">Execute</span><span class="token plain"> </span><span class="token constant" style="co [...]
+<p>2, What is the <code>AOP proxy data source</code> and <code>native data source</code> stated in step 1? Look at the following diagram
+! <a href="https://p3-juejin.byteimg.com/tos-cn-i-k3u1fbpfcp/3579631f58df4d17bfcd6f28ccc3fd79~tplv-k3u1fbpfcp-watermark.image" target="_blank" rel="noopener noreferrer">image.png</a></p>
+<p>3, the above also said to produce this problem there is a condition <code>two key hashcode the same</code>, but I see that these two data source objects are not overriding the <code>hashcode</code> method, so by definition, these two objects must be different hashcode. After looking at the ConcurrentHashMap problem again, I feel that the statement <code>two keys have the same hashcode</code> is not correct, and <code>two keys will generate hash conflict</code> is more reasonable, whic [...]
+<div class="language-java codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_biex"><pre tabindex="0" class="prism-code language-java codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><span class="token-line" style="color:#393A34"><span class="token keyword" style="color:#00009f">public</span><span class="token plain"> </span><span class="token k [...]
+<ol>
+<li>To make it easier to reproduce the problem, we rewrite the <code>Num#hashCode</code> method to ensure that the constructor input is the hashcode value.</li>
+<li>create a ConcurrentHashMap object, initialCapacity is 8, sizeCtl calculated value is 16, that is, the default length of the array in the map is 16</li>
+<li>create object <code>n1</code>, the input parameter is 3, that is, the hashcode is 3, the calculation of its corresponding array subscript 3</li>
+<li>create object <code>n2</code>, the input parameter is 19, that is, the hashcode is 19, calculate its corresponding array subscript is 3, at this time we can think of <code>n1 and n2 hash conflict</code>.</li>
+<li>create object <code>n3</code> with input 20, i.e., hashcode 20, and its corresponding array subscript is 4.</li>
+<li>execute <code>map.computeIfAbsent(n1, k1 -> map.computeIfAbsent(n3, k2 -> 200))</code>, the programme exits normally: <code>Because there is no hash conflict between n1 and n3, the programme terminates normally</code>.</li>
+<li>Execute <code>map.computeIfAbsent(n1, k1 -> map.computeIfAbsent(n2, k2 -> 200))</code>, the programme exits normally: <code> because n1 and n2 have a hash conflict, so it is in a dead loop</code>.</li>
+</ol>
+<p>4、During the initialisation of the object, hasn't <code>SeataDataSourceBeanPostProcessor</code> already initialised the corresponding data source proxy of the object? Why the corresponding data source proxy is still created in <code>SeataAutoDataSourceProxyAdvice</code>?</p>
+<ol>
+<li>First of all, the <code>SeataDataSourceBeanPostProcessor</code> execution period is later than the creation of the AOP proxy object, so when executing the <code>SeataDataSourceBeanPostProcessor</code> related methods, the <code>SeataAutoDataSourceBeanPostProcessor</code> method is executed. SeataAutoDataSourceProxyAdvice<code>should actually take effect when the</code>SeataDataSourceBeanPostProcessor` related methods are executed.</li>
+<li>when adding elements to the map in <code>SeataDataSourceBeanPostProcessor</code>, the key is <code>AOP proxy datasource</code>; in <code>SeataAutoDataSourceProxyAdvice</code>, the key is <code>native datasource</code>, so the key is not the same as <code>invocation.getThis()</code>, so the key is not the same. `, so the key is not the same</li>
+</ol>
+<p>! <a href="https://p6-juejin.byteimg.com/tos-cn-i-k3u1fbpfcp/747b664a0b6c4f58843947576dd0856e~tplv-k3u1fbpfcp-watermark.image" target="_blank" rel="noopener noreferrer">image.png</a></p>
+<p>5, there is another problem, <code>SeataAutoDataSourceProxyAdvic#invoke</code> method does not filter <code>toString, hashCode</code> and other methods, the proxy object created by cglib will override these methods by default, if these methods of the proxy object are triggered when putting elements into the map. If these methods are triggered when putting elements into the map, the proxy object will re-enter the <code>SeataAutoDataSourceProxyAdvic#invoke</code> cut until the thread st [...]
+<h1>Summary of the problem</h1>
+<ol>
+<li>in two key will produce hash conflict, will trigger <code>ConcurrentHashMap#computeIfAbsent</code> BUG, the performance of this BUG is to make the current thread into a dead loop</li>
+<li>business feedback, the problem is occasional, occasional for two reasons: first, the application is a multi-node deployment, but only one node on the line triggered the BUG (hashcode conflict), so only when the request hits this node may trigger the BUG; second, because each restart object address (hashcode) are not sure, so not triggered after every app restart, but if once triggered, the node will always have this problem. Having a thread that keeps dying and blocking other threads [...]
+<li>when encountering this problem, from the perspective of the whole problem, it is indeed a deadlock, because the dead loop thread occupant lock has not been released, resulting in other threads operating on the map is BLOCKED!</li>
+<li>essentially because <code>ConcurrentHashMap#computeIfAbsent method may trigger a bug</code>, and seata's usage scenario just triggered the bug.</li>
+<li>The following demo is actually a complete simulation of what happens when something goes wrong online, as follows:</li>
+</ol>
+<div class="language-java codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_biex"><pre tabindex="0" class="prism-code language-java codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><span class="token-line" style="color:#393A34"><span class="token keyword" style="color:#00009f">public</span><span class="token plain"> </span><span class="token k [...]
+<p>! <a href="https://p6-juejin.byteimg.com/tos-cn-i-k3u1fbpfcp/d6134c6498fa49c4a68b2745ba0895e3~tplv-k3u1fbpfcp-watermark.image" target="_blank" rel="noopener noreferrer">image.png</a></p>
+<h3 class="anchor anchorWithStickyNavbar_LWe7" id="solving-the-problem">Solving the problem<a href="#solving-the-problem" class="hash-link" aria-label="Direct link to Solving the problem" title="Direct link to Solving the problem"></a></h3>
+<p>The problem can be solved in two ways:</p>
+<ol>
+<li>business changes: P6DataSource and DynamicDataSource do not need to be proxied, directly proxy P6DataSource can be, DynamicDataSource does not need to be declared as a bean; or through the excludes property excludes P6DataSource, so that there is no duplicate proxy problem. There will be no problem of duplicate proxies</li>
+<li>Seata refinement: improve the logic related to data source proxy</li>
+</ol>
+<h5 class="anchor anchorWithStickyNavbar_LWe7" id="business-changes">Business changes<a href="#business-changes" class="hash-link" aria-label="Direct link to Business changes" title="Direct link to Business changes"></a></h5>
+<ol>
+<li>Data source related configuration can be changed to the following:</li>
+</ol>
+<div class="language-java codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_biex"><pre tabindex="0" class="prism-code language-java codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><span class="token-line" style="color:#393A34"><span class="token annotation punctuation" style="color:#393A34">@Primary</span><span class="token plain"></span><br> [...]
+<ol start="2">
+<li>Or leave the current data source configuration unchanged and add the excludes property</li>
+</ol>
+<div class="language-java codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_biex"><pre tabindex="0" class="prism-code language-java codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><span class="token-line" style="color:#393A34"><span class="token annotation punctuation" style="color:#393A34">@EnableAutoDataSourceProxy</span><span class="token [...]
+<h5 class="anchor anchorWithStickyNavbar_LWe7" id="seata-refinement">Seata refinement<a href="#seata-refinement" class="hash-link" aria-label="Direct link to Seata refinement" title="Direct link to Seata refinement"></a></h5>
+<ol>
+<li><code>ConcurrentHashMap#computeIfAbsent</code> method is changed to double check as follows:</li>
+</ol>
+<div class="language-java codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_biex"><pre tabindex="0" class="prism-code language-java codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><span class="token-line" style="color:#393A34"><span class="token class-name">SeataDataSourceProxy</span><span class="token plain"> dsProxy </span><span class="toke [...]
+<p>I wanted to change the <code>CollectionUtils#computeIfAbsent</code> method directly, and the feedback from the group was that this might cause the data source to be created multiple times, which is indeed a problem: as follows</p>
+<div class="language-java codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_biex"><pre tabindex="0" class="prism-code language-java codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><span class="token-line" style="color:#393A34"><span class="token keyword" style="color:#00009f">public</span><span class="token plain"> </span><span class="token k [...]
+<ol start="2">
+<li>Add some filtering to the SeataAutoDataSourceProxyAdvice cutout logic</li>
+</ol>
+<div class="language-java codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_biex"><pre tabindex="0" class="prism-code language-java codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><span class="token-line" style="color:#393A34"><span class="token class-name">Method</span><span class="token plain"> m </span><span class="token operator" style="c [...]
+<h3 class="anchor anchorWithStickyNavbar_LWe7" id="legacy-issues">Legacy issues<a href="#legacy-issues" class="hash-link" aria-label="Direct link to Legacy issues" title="Direct link to Legacy issues"></a></h3>
+<p>In the corresponding methods of <code>SeataDataSourceBeanPostProcessor</code> and <code>SeataAutoDataSourceProxyAdvice</code>, the keys corresponding to initialising the <code>seata datasource proxy</code> into the map are fundamentally different, the <code>The key in</code>SeataDataSourceBeanPostProcessor<code>is the</code>AOP proxy data source<code>; the key in </code>SeataAutoDataSourceProxyAdvice<code>is the native object, which results in the unnecessary creation of the</code>sea [...]
+<p>What is the best suggestion for this problem? Is it possible to specify an order for <code>SeataDataSourceBeanPostProcessor</code> to take effect before the AOP proxy object is created?</p>
+<h1>Link to original article</h1>
+<p><a href="https://juejin.cn/post/6939041336964153352/" target="_blank" rel="noopener noreferrer">https://juejin.cn/post/6939041336964153352/</a></p></div><footer class="row docusaurus-mt-lg"></footer></article><article class="margin-bottom--xl" itemprop="blogPost" itemscope="" itemtype="https://schema.org/BlogPosting"><meta itemprop="description" content=""Just getting started with Seata and don't know enough about its modules?"><header><h2 class="title_f1Hy" itemprop="headli [...]
<p>"Just getting started with Seata and don't know enough about its modules? <br>
Want to dive into the Seata source code, but haven't done so yet? <br>
Want to find out what your application is doing "on the sly" during startup after integrating Seata? <br>
@@ -1027,54 +1136,7 @@ classes in the netty module are not "netty", and the RPC classes in th
<p><img decoding="async" loading="lazy" src="https://gitee.com/objcoding/md-picture/raw/master/img/20200711213204.png" alt="" class="img_ev3q"></p>
<h1>Author Bio</h1>
<p>Zhang Chenghui, currently working in Ant Group, loves to share technology, author of WeChat public number "Backend Advanced", technical blog (<a href="https://objcoding.com/" target="_blank" rel="noopener noreferrer">https://objcoding.com/</a>) blogger, Seata Contributor, GitHub
-ID: objcoding.</p></div><footer class="row docusaurus-mt-lg"></footer></article><article class="margin-bottom--xl" itemprop="blogPost" itemscope="" itemtype="https://schema.org/BlogPosting"><meta itemprop="description" content="[Distributed Transaction Seata Source Code Interpretation I] Server-side startup process"><meta itemprop="keywords" content="fescar,seata,distributed transaction"><header><h2 class="title_f1Hy" itemprop="headline"><a itemprop="url" href="/blog/seata-sourcecode-ser [...]
-<h3 class="anchor anchorWithStickyNavbar_LWe7" id="core-points-for-implementing-distributed-transactions">Core points for implementing distributed transactions:<a href="#core-points-for-implementing-distributed-transactions" class="hash-link" aria-label="Direct link to Core points for implementing distributed transactions:" title="Direct link to Core points for implementing distributed transactions:"></a></h3>
-<ol>
-<li>transaction persistence, the various states of the transaction at the various state of the transaction participants need to be persistent, when the instance is down in order to roll back or commit the transaction based on the persistent data to achieve the ultimate consistency</li>
-<li>Timing on the timeout transaction processing (continue to try to commit or rollback), that is, through the retry mechanism to achieve the ultimate consistency of the transaction</li>
-<li>cross-service instance propagation of distributed transactions, when distributed transactions across multiple instances need to achieve transaction propagation, generally need to adapt to different rpc frameworks.</li>
-<li>transaction isolation level: most distributed transactions for performance, the default isolation level is read uncommitted</li>
-<li>idempotency: for XA or seata's AT such distributed transactions, have been implemented by default idempotency, and TCC, Saga interface level implementation of distributed transactions are still required to implement their own business developers to achieve idempotency.</li>
-</ol>
-<p>This article introduces the source code of seata-server from the point of view of the startup process of seata-server, the startup flow chart is as follows:</p>
-<p>! [Insert image description here](<a href="https://img-blog.csdnimg.cn/20200726213919467.jpg?x-oss-process=image/watermark,type_ZmFuZ3poZW5naGVpdGk,shadow_10" target="_blank" rel="noopener noreferrer">https://img-blog.csdnimg.cn/20200726213919467.jpg?x-oss-process=image/watermark,type_ZmFuZ3poZW5naGVpdGk,shadow_10</a>, text_aHR0cHM6Ly9ibG9nLmNzZG4ubmV0L3dlaXhpbl80NTE0NTg0OA==,size_16,colour_FFFFFF,t_70)</p>
-<h4 class="anchor anchorWithStickyNavbar_LWe7" id="1-startup-class-server">1. Startup class Server<a href="#1-startup-class-server" class="hash-link" aria-label="Direct link to 1. Startup class Server" title="Direct link to 1. Startup class Server"></a></h4>
-<p>The entry class for seata-server is in the Server class with the following source code:</p>
-<div class="language-java codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_biex"><pre tabindex="0" class="prism-code language-java codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><span class="token-line" style="color:#393A34"><span class="token keyword" style="color:#00009f">public</span><span class="token plain"> </span><span class="token k [...]
-<h4 class="anchor anchorWithStickyNavbar_LWe7" id="2-parsing-configuration">2. Parsing Configuration<a href="#2-parsing-configuration" class="hash-link" aria-label="Direct link to 2. Parsing Configuration" title="Direct link to 2. Parsing Configuration"></a></h4>
-<p>The implementation code for parameter parsing is in the ParameterParser class, the init method source code is as follows:</p>
-<div class="language-java codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_biex"><pre tabindex="0" class="prism-code language-java codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><span class="token-line" style="color:#393A34"><span class="token keyword" style="color:#00009f">private</span><span class="token plain"> </span><span class="token [...]
-<p>The first call to ConfigurationFactory.getInstance() in the ParameterParser's init method initialises a singleton Configuration object, which is responsible for initialising all other configuration parameter information. From the Seata Server side of the source code we can see two configuration files file.conf, registry.conf. So what is the difference between these two configuration files, both files are required? We continue to look at the code.</p>
-<p>ConfigurationFactory.getInstance method is actually to get a singleton object, the core is in the buildConfiguration method, but before the buidlConfiguration method, there is a static code block of the ConfigurationFactory class will be executed first.</p>
-<div class="language-Java language-java codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_biex"><pre tabindex="0" class="prism-code language-java codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><span class="token-line" style="color:#393A34"><span class="token comment" style="color:#999988;font-style:italic">// Get the singleton object for Con [...]
-<p>The static block in ConfigurationFactory reads configuration information from registry.conf. The conf configuration file is mandatory, the registry.conf configuration file specifies the source for other detailed configurations, the current configuration source supports file, zk, apollo, nacos, etcd3, etc. So file.conf is not required, only when the configuration source is set to the file type will read the contents of the file.conf file.</p>
-<p>Next buildConfiguration in ConfigurationFactory is to load more configuration items based on the configuration source set in registry.conf.</p>
-<div class="language-Java language-java codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_biex"><pre tabindex="0" class="prism-code language-java codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><span class="token-line" style="color:#393A34"><span class="token keyword" style="color:#00009f">private</span><span class="token plain"> </span><span [...]
-<h4 class="anchor anchorWithStickyNavbar_LWe7" id="3-initialisation-of-uuidgenerator">3. Initialisation of UUIDGenerator<a href="#3-initialisation-of-uuidgenerator" class="hash-link" aria-label="Direct link to 3. Initialisation of UUIDGenerator" title="Direct link to 3. Initialisation of UUIDGenerator"></a></h4>
-<p>The UUIDGenertor initialisation receives a serverNode parameter, the UUIDGenertor currently uses the snowflake algorithm to generate the unique Id, this serverNode is used to ensure that the unique ids generated by multiple seata-server instances are not duplicated.</p>
-<div class="language-java codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_biex"><pre tabindex="0" class="prism-code language-java codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><span class="token-line" style="color:#393A34"><span class="token keyword" style="color:#00009f">public</span><span class="token plain"> </span><span class="token k [...]
-<p>UUIDGenerator is a wrapper around IdWorker, the core implementation logic for the unique id is in the IdWoker class, and IdWorker is a snowflake algorithm implementation. The IdWorker in this case is again a single instance</p>
-<div class="language-java codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_biex"><pre tabindex="0" class="prism-code language-java codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><span class="token-line" style="color:#393A34"><span class="token keyword" style="color:#00009f">public</span><span class="token plain"> </span><span class="token k [...]
-<h4 class="anchor anchorWithStickyNavbar_LWe7" id="4-sessionholder-initialisation">4. SessionHolder initialisation<a href="#4-sessionholder-initialisation" class="hash-link" aria-label="Direct link to 4. SessionHolder initialisation" title="Direct link to 4. SessionHolder initialisation"></a></h4>
-<p>SessionHolder is responsible for session persistence, a session object corresponds to a transaction, there are two kinds of transaction: GlobalSession and BranchSession.
-SessionHolder supports two types of persistence: file and db, of which db supports cluster mode and is recommended to use db. The four most important fields in SessionHolder are as follows:</p>
-<div class="language-java codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_biex"><pre tabindex="0" class="prism-code language-java codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><span class="token-line" style="color:#393A34"><span class="token comment" style="color:#999988;font-style:italic">// ROOT_SESSION_MANAGER is used to get all the Se [...]
-<p>SessionHolder init method</p>
-<div class="language-java codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_biex"><pre tabindex="0" class="prism-code language-java codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><span class="token-line" style="color:#393A34"><span class="token keyword" style="color:#00009f">private</span><span class="token plain"> </span><span class="token [...]
-<p>The four SessionManagers in the SessionHolder are all instances of the class DataBaseSessionManager, but they pass different parameters to the constructor, so take a look at the definition of DataBaseSessionManager:</p>
-<div class="language-java codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_biex"><pre tabindex="0" class="prism-code language-java codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><span class="token-line" style="color:#393A34"><span class="token keyword" style="color:#00009f">public</span><span class="token plain"> </span><span class="token c [...]
-<h4 class="anchor anchorWithStickyNavbar_LWe7" id="5-initialise-defaultcoordinator">5. Initialise DefaultCoordinator<a href="#5-initialise-defaultcoordinator" class="hash-link" aria-label="Direct link to 5. Initialise DefaultCoordinator" title="Direct link to 5. Initialise DefaultCoordinator"></a></h4>
-<p>The DefaultCoordinator is the core of the transaction coordinator, e.g., opening, committing, and rolling back global transactions, registering, committing, and rolling back branch transactions are all coordinated by the DefaultCoordinator.The DefaultCoordinato communicate with remote TMs and RMs through the RpcServer to achieve branch transactions such as commit and rollback. DefaultCoordinato communicates with remote TMs and RMs through the RpcServer to achieve branch transactions.</p>
-<div class="language-java codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_biex"><pre tabindex="0" class="prism-code language-java codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><span class="token-line" style="color:#393A34"><span class="token keyword" style="color:#00009f">public</span><span class="token plain"> </span><span class="token c [...]
-<h4 class="anchor anchorWithStickyNavbar_LWe7" id="6-initialising-nettyremotingserver">6. Initialising NettyRemotingServer<a href="#6-initialising-nettyremotingserver" class="hash-link" aria-label="Direct link to 6. Initialising NettyRemotingServer" title="Direct link to 6. Initialising NettyRemotingServer"></a></h4>
-<p>NettyRemotingServer is a simplified version of Rpc server based on Netty implementation, NettyRemotingServer initialisation does two main things:</p>
-<ol>
-<li><strong>registerProcessor</strong>: registers the Processor that communicates with the Client.</li>
-<li><strong>super.init()</strong>: the super.init() method is responsible for initialising Netty and registering the IP port of the current instance with the registry</li>
-</ol>
-<div class="language-java codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_biex"><pre tabindex="0" class="prism-code language-java codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><span class="token-line" style="color:#393A34"><span class="token keyword" style="color:#00009f">public</span><span class="token plain"> </span><span class="token k [...]
-<p>In NettyRemotingServer there is a call to the init method of the base class AbstractNettyRemotingServer with the following code:</p>
-<div class="language-Java language-java codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_biex"><pre tabindex="0" class="prism-code language-java codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><span class="token-line" style="color:#393A34"><span class="token keyword" style="color:#00009f">public</span><span class="token plain"> </span><span [...]
+ID: objcoding.</p></div><footer class="row docusaurus-mt-lg"></footer></article><nav class="pagination-nav" aria-label="Blog list page navigation"><a class="pagination-nav__link pagination-nav__link--prev" href="/blog/page/2"><div class="pagination-nav__label">Newer Entries</div></a><a class="pagination-nav__link pagination-nav__link--next" href="/blog/page/4"><div class="pagination-nav__label">Older Entries</div></a></nav></main></div></div></div><footer class="footer"><div class="conta [...]
<div class="fs-12">
<div class="center-div">
<span>Apache Seata (incubating) is an effort undergoing incubation at The Apache Software Foundation (ASF), sponsored by the Apache Incubator. Incubation is required of all newly accepted projects until a further review indicates that the infrastructure, communications, and decision making process have stabilized in a manner consistent with other successful ASF projects. While incubation status is not necessarily a reflection of the completeness or stability of the [...]
diff --git a/blog/page/4/index.html b/blog/page/4/index.html
index 1e399154540..c2e0acb7887 100644
--- a/blog/page/4/index.html
+++ b/blog/page/4/index.html
@@ -11,11 +11,58 @@
<meta name="aes-config" content="pid=xux-opensource&user_type=101&uid=&username=&dim10=seata"><link rel="stylesheet" href="/assets/css/styles.9644caf2.css">
-<script src="/assets/js/runtime~main.bf98ee01.js" defer="defer"></script>
-<script src="/assets/js/main.8371dd70.js" defer="defer"></script>
+<script src="/assets/js/runtime~main.762ed5c0.js" defer="defer"></script>
+<script src="/assets/js/main.aeea7339.js" defer="defer"></script>
</head>
<body class="navigation-with-keyboard">
-<script>!function(){function t(t){document.documentElement.setAttribute("data-theme",t)}var e=function(){try{return new URLSearchParams(window.location.search).get("docusaurus-theme")}catch(t){}}()||function(){try{return localStorage.getItem("theme")}catch(t){}}();t(null!==e?e:"light")}(),function(){try{const c=new URLSearchParams(window.location.search).entries();for(var[t,e]of c)if(t.startsWith("docusaurus-data-")){var a=t.replace("docusaurus-data-","data-");document.documentElement.se [...]
+<script>!function(){function t(t){document.documentElement.setAttribute("data-theme",t)}var e=function(){try{return new URLSearchParams(window.location.search).get("docusaurus-theme")}catch(t){}}()||function(){try{return localStorage.getItem("theme")}catch(t){}}();t(null!==e?e:"light")}(),function(){try{const c=new URLSearchParams(window.location.search).entries();for(var[t,e]of c)if(t.startsWith("docusaurus-data-")){var a=t.replace("docusaurus-data-","data-");document.documentElement.se [...]
+<h3 class="anchor anchorWithStickyNavbar_LWe7" id="core-points-for-implementing-distributed-transactions">Core points for implementing distributed transactions:<a href="#core-points-for-implementing-distributed-transactions" class="hash-link" aria-label="Direct link to Core points for implementing distributed transactions:" title="Direct link to Core points for implementing distributed transactions:"></a></h3>
+<ol>
+<li>transaction persistence, the various states of the transaction at the various state of the transaction participants need to be persistent, when the instance is down in order to roll back or commit the transaction based on the persistent data to achieve the ultimate consistency</li>
+<li>Timing on the timeout transaction processing (continue to try to commit or rollback), that is, through the retry mechanism to achieve the ultimate consistency of the transaction</li>
+<li>cross-service instance propagation of distributed transactions, when distributed transactions across multiple instances need to achieve transaction propagation, generally need to adapt to different rpc frameworks.</li>
+<li>transaction isolation level: most distributed transactions for performance, the default isolation level is read uncommitted</li>
+<li>idempotency: for XA or seata's AT such distributed transactions, have been implemented by default idempotency, and TCC, Saga interface level implementation of distributed transactions are still required to implement their own business developers to achieve idempotency.</li>
+</ol>
+<p>This article introduces the source code of seata-server from the point of view of the startup process of seata-server, the startup flow chart is as follows:</p>
+<p>! [Insert image description here](<a href="https://img-blog.csdnimg.cn/20200726213919467.jpg?x-oss-process=image/watermark,type_ZmFuZ3poZW5naGVpdGk,shadow_10" target="_blank" rel="noopener noreferrer">https://img-blog.csdnimg.cn/20200726213919467.jpg?x-oss-process=image/watermark,type_ZmFuZ3poZW5naGVpdGk,shadow_10</a>, text_aHR0cHM6Ly9ibG9nLmNzZG4ubmV0L3dlaXhpbl80NTE0NTg0OA==,size_16,colour_FFFFFF,t_70)</p>
+<h4 class="anchor anchorWithStickyNavbar_LWe7" id="1-startup-class-server">1. Startup class Server<a href="#1-startup-class-server" class="hash-link" aria-label="Direct link to 1. Startup class Server" title="Direct link to 1. Startup class Server"></a></h4>
+<p>The entry class for seata-server is in the Server class with the following source code:</p>
+<div class="language-java codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_biex"><pre tabindex="0" class="prism-code language-java codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><span class="token-line" style="color:#393A34"><span class="token keyword" style="color:#00009f">public</span><span class="token plain"> </span><span class="token k [...]
+<h4 class="anchor anchorWithStickyNavbar_LWe7" id="2-parsing-configuration">2. Parsing Configuration<a href="#2-parsing-configuration" class="hash-link" aria-label="Direct link to 2. Parsing Configuration" title="Direct link to 2. Parsing Configuration"></a></h4>
+<p>The implementation code for parameter parsing is in the ParameterParser class, the init method source code is as follows:</p>
+<div class="language-java codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_biex"><pre tabindex="0" class="prism-code language-java codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><span class="token-line" style="color:#393A34"><span class="token keyword" style="color:#00009f">private</span><span class="token plain"> </span><span class="token [...]
+<p>The first call to ConfigurationFactory.getInstance() in the ParameterParser's init method initialises a singleton Configuration object, which is responsible for initialising all other configuration parameter information. From the Seata Server side of the source code we can see two configuration files file.conf, registry.conf. So what is the difference between these two configuration files, both files are required? We continue to look at the code.</p>
+<p>ConfigurationFactory.getInstance method is actually to get a singleton object, the core is in the buildConfiguration method, but before the buidlConfiguration method, there is a static code block of the ConfigurationFactory class will be executed first.</p>
+<div class="language-Java language-java codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_biex"><pre tabindex="0" class="prism-code language-java codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><span class="token-line" style="color:#393A34"><span class="token comment" style="color:#999988;font-style:italic">// Get the singleton object for Con [...]
+<p>The static block in ConfigurationFactory reads configuration information from registry.conf. The conf configuration file is mandatory, the registry.conf configuration file specifies the source for other detailed configurations, the current configuration source supports file, zk, apollo, nacos, etcd3, etc. So file.conf is not required, only when the configuration source is set to the file type will read the contents of the file.conf file.</p>
+<p>Next buildConfiguration in ConfigurationFactory is to load more configuration items based on the configuration source set in registry.conf.</p>
+<div class="language-Java language-java codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_biex"><pre tabindex="0" class="prism-code language-java codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><span class="token-line" style="color:#393A34"><span class="token keyword" style="color:#00009f">private</span><span class="token plain"> </span><span [...]
+<h4 class="anchor anchorWithStickyNavbar_LWe7" id="3-initialisation-of-uuidgenerator">3. Initialisation of UUIDGenerator<a href="#3-initialisation-of-uuidgenerator" class="hash-link" aria-label="Direct link to 3. Initialisation of UUIDGenerator" title="Direct link to 3. Initialisation of UUIDGenerator"></a></h4>
+<p>The UUIDGenertor initialisation receives a serverNode parameter, the UUIDGenertor currently uses the snowflake algorithm to generate the unique Id, this serverNode is used to ensure that the unique ids generated by multiple seata-server instances are not duplicated.</p>
+<div class="language-java codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_biex"><pre tabindex="0" class="prism-code language-java codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><span class="token-line" style="color:#393A34"><span class="token keyword" style="color:#00009f">public</span><span class="token plain"> </span><span class="token k [...]
+<p>UUIDGenerator is a wrapper around IdWorker, the core implementation logic for the unique id is in the IdWoker class, and IdWorker is a snowflake algorithm implementation. The IdWorker in this case is again a single instance</p>
+<div class="language-java codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_biex"><pre tabindex="0" class="prism-code language-java codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><span class="token-line" style="color:#393A34"><span class="token keyword" style="color:#00009f">public</span><span class="token plain"> </span><span class="token k [...]
+<h4 class="anchor anchorWithStickyNavbar_LWe7" id="4-sessionholder-initialisation">4. SessionHolder initialisation<a href="#4-sessionholder-initialisation" class="hash-link" aria-label="Direct link to 4. SessionHolder initialisation" title="Direct link to 4. SessionHolder initialisation"></a></h4>
+<p>SessionHolder is responsible for session persistence, a session object corresponds to a transaction, there are two kinds of transaction: GlobalSession and BranchSession.
+SessionHolder supports two types of persistence: file and db, of which db supports cluster mode and is recommended to use db. The four most important fields in SessionHolder are as follows:</p>
+<div class="language-java codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_biex"><pre tabindex="0" class="prism-code language-java codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><span class="token-line" style="color:#393A34"><span class="token comment" style="color:#999988;font-style:italic">// ROOT_SESSION_MANAGER is used to get all the Se [...]
+<p>SessionHolder init method</p>
+<div class="language-java codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_biex"><pre tabindex="0" class="prism-code language-java codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><span class="token-line" style="color:#393A34"><span class="token keyword" style="color:#00009f">private</span><span class="token plain"> </span><span class="token [...]
+<p>The four SessionManagers in the SessionHolder are all instances of the class DataBaseSessionManager, but they pass different parameters to the constructor, so take a look at the definition of DataBaseSessionManager:</p>
+<div class="language-java codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_biex"><pre tabindex="0" class="prism-code language-java codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><span class="token-line" style="color:#393A34"><span class="token keyword" style="color:#00009f">public</span><span class="token plain"> </span><span class="token c [...]
+<h4 class="anchor anchorWithStickyNavbar_LWe7" id="5-initialise-defaultcoordinator">5. Initialise DefaultCoordinator<a href="#5-initialise-defaultcoordinator" class="hash-link" aria-label="Direct link to 5. Initialise DefaultCoordinator" title="Direct link to 5. Initialise DefaultCoordinator"></a></h4>
+<p>The DefaultCoordinator is the core of the transaction coordinator, e.g., opening, committing, and rolling back global transactions, registering, committing, and rolling back branch transactions are all coordinated by the DefaultCoordinator.The DefaultCoordinato communicate with remote TMs and RMs through the RpcServer to achieve branch transactions such as commit and rollback. DefaultCoordinato communicates with remote TMs and RMs through the RpcServer to achieve branch transactions.</p>
+<div class="language-java codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_biex"><pre tabindex="0" class="prism-code language-java codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><span class="token-line" style="color:#393A34"><span class="token keyword" style="color:#00009f">public</span><span class="token plain"> </span><span class="token c [...]
+<h4 class="anchor anchorWithStickyNavbar_LWe7" id="6-initialising-nettyremotingserver">6. Initialising NettyRemotingServer<a href="#6-initialising-nettyremotingserver" class="hash-link" aria-label="Direct link to 6. Initialising NettyRemotingServer" title="Direct link to 6. Initialising NettyRemotingServer"></a></h4>
+<p>NettyRemotingServer is a simplified version of Rpc server based on Netty implementation, NettyRemotingServer initialisation does two main things:</p>
+<ol>
+<li><strong>registerProcessor</strong>: registers the Processor that communicates with the Client.</li>
+<li><strong>super.init()</strong>: the super.init() method is responsible for initialising Netty and registering the IP port of the current instance with the registry</li>
+</ol>
+<div class="language-java codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_biex"><pre tabindex="0" class="prism-code language-java codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><span class="token-line" style="color:#393A34"><span class="token keyword" style="color:#00009f">public</span><span class="token plain"> </span><span class="token k [...]
+<p>In NettyRemotingServer there is a call to the init method of the base class AbstractNettyRemotingServer with the following code:</p>
+<div class="language-Java language-java codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_biex"><pre tabindex="0" class="prism-code language-java codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><span class="token-line" style="color:#393A34"><span class="token keyword" style="color:#00009f">public</span><span class="token plain"> </span><span [...]
<p>The 1.2.0 version of Seata has released a new transaction mode: XA mode, which supports the XA protocol.</p>
<p>Here, we will interpret this new feature in depth from three aspects:</p>
<ul>
@@ -778,94 +825,7 @@
<p><a href="https://nacos.io/zh-cn/index.html" target="_blank" rel="noopener noreferrer">nacos website</a></p>
<p><a href="http://dubbo.apache.org/en-us/" target="_blank" rel="noopener noreferrer">dubbo website</a></p>
<p><a href="https://seata.apache.org/zh-cn/" target="_blank" rel="noopener noreferrer">seata official website</a></p>
-<p><a href="https://www.docker.com/" target="_blank" rel="noopener noreferrer">docker official website</a></p></div><footer class="row docusaurus-mt-lg"></footer></article><article class="margin-bottom--xl" itemprop="blogPost" itemscope="" itemtype="https://schema.org/BlogPosting"><meta itemprop="description" content="This article explains how Seata adapts to different dynamic configuration subscriptions and implements degradation functionality with support for multiple configuration cen [...]
-<p>So how do the multiple configuration centres supported by Seata adapt to different dynamic configuration subscriptions and how do they achieve degradation? Here is a detailed explanation from the source code level.</p>
-<h1>Dynamic Configuration Subscriptions</h1>
-<p>The Seata Configuration Centre has a listener baseline interface, which has an abstract method and default method, as follows:</p>
-<p>io.seata.config.ConfigurationChangeListener</p>
-<p><img decoding="async" loading="lazy" src="https://gitee.com/objcoding/md-picture/raw/master/img/20191216212442.png" alt="" class="img_ev3q"></p>
-<p>This listener baseline interface has two main implementation types:</p>
-<ol>
-<li>implementation of the registration of configuration subscription event listener: for the implementation of a variety of functions of dynamic configuration subscription, such as GlobalTransactionalInterceptor implements ConfigurationChangeListener, according to the dynamic configuration subscription to the dynamic degradation of the implementation of the function;</li>
-<li>the implementation of the configuration centre dynamic subscription function and adaptation: for the file type default configuration centre that currently does not have dynamic subscription function, you can implement the benchmark interface to achieve dynamic configuration subscription function; for the blocking subscription needs to start another thread to execute, then you can implement the benchmark interface for adaptation, you can also reuse the thread pool of the benchmark int [...]
-</ol>
-<h2 class="anchor anchorWithStickyNavbar_LWe7" id="nacos-dynamic-subscription-implementation">Nacos Dynamic Subscription Implementation<a href="#nacos-dynamic-subscription-implementation" class="hash-link" aria-label="Direct link to Nacos Dynamic Subscription Implementation" title="Direct link to Nacos Dynamic Subscription Implementation"></a></h2>
-<p>Nacos has its own internal implementation of the listener, so it directly inherits its internal abstract listener, AbstractSharedListener, which is implemented as follows:</p>
-<p><img decoding="async" loading="lazy" src="https://gitee.com/objcoding/md-picture/raw/master/img/20191223212237.png" alt="" class="img_ev3q"></p>
-<p>As above.</p>
-<ul>
-<li>dataId: configuration attribute for the subscription;</li>
-<li>listener: configures the subscription event listener, which is used to use the incoming listener as a wrapper to perform the actual change logic.</li>
-</ul>
-<p>It's worth mentioning that nacos doesn't use ConfigurationChangeListener to implement its own listener configuration, on the one hand, because Nacos itself already has a listener subscription function, so it doesn't need to implement it; on the other hand, because nacos is a non-blocking subscription, it doesn't need to reuse the ConfigurationChangeListener's thread pool, i.e., no adaptation is needed.</p>
-<p>Add the subscription:</p>
-<p><img decoding="async" loading="lazy" src="https://gitee.com/objcoding/md-picture/raw/master/img/20191223213347.png" alt="" class="img_ev3q"></p>
-<p>The logic of adding a subscription to a dataId in Nacos Configuration Centre is very simple, create a NacosListener with the dataId and a listener, call the configService#addListener method, and use the NacosListener as a listener for the dataId, and then the dataId can be dynamically configured for subscription. Dynamic Configuration Subscription.</p>
-<h2 class="anchor anchorWithStickyNavbar_LWe7" id="file-dynamic-subscription-implementation">file Dynamic subscription implementation<a href="#file-dynamic-subscription-implementation" class="hash-link" aria-label="Direct link to file Dynamic subscription implementation" title="Direct link to file Dynamic subscription implementation"></a></h2>
-<p>Take its implementation class FileListener as an example, its implementation logic is as follows:</p>
-<p><img decoding="async" loading="lazy" src="https://gitee.com/objcoding/md-picture/raw/master/img/20191215151642.png" alt="" class="img_ev3q"></p>
-<p>As above.</p>
-<ul>
-<li>
-<p>dataId: configuration attribute for the subscription;</p>
-</li>
-<li>
-<p>listener: the configuration subscription event listener, used as a wrapper for the incoming listener to perform the real change logic, it is important to note that ** this listener and FileListener also implement the ConfigurationChangeListener interface, except that FileListener is used to provide dynamic configuration subscription to the file, while listener is used to execute configuration subscription events**;</p>
-</li>
-<li>
-<p>executor: a thread pool used for processing configuration change logic, used in the ConfigurationChangeListener#onProcessEvent method.</p>
-</li>
-</ul>
-<p>The implementation of the <strong>FileListener#onChangeEvent method gives the file the ability to subscribe to dynamic configurations</strong> with the following logic:</p>
-<p>It loops indefinitely to get the current value of the subscribed configuration property, fetches the old value from the cache, determines if there is a change, and executes the logic of the external incoming listener if there is a change.</p>
-<p>ConfigurationChangeEvent The event class used to save configuration changes, it has the following member properties:</p>
-<p><img decoding="async" loading="lazy" src="https://gitee.com/objcoding/md-picture/raw/master/img/20191215175232.png" alt="" class="img_ev3q"></p>
-<p>How does the getConfig method sense changes to the file configuration? We click into it and find that it ends up with the following logic:</p>
-<p><img decoding="async" loading="lazy" src="https://gitee.com/objcoding/md-picture/raw/master/img/20191215162713.png" alt="" class="img_ev3q"></p>
-<p>We see that it creates a future class, wraps it in a Runnable and puts it into the thread pool to execute asynchronously, and then calls the get method to block the retrieval of the value, so let's move on:</p>
-<p><img decoding="async" loading="lazy" src="https://gitee.com/objcoding/md-picture/raw/master/img/20191215170908.png" alt="" class="img_ev3q"></p>
-<p>allowDynamicRefresh: configure switch for dynamic refresh;</p>
-<p>targetFileLastModified: time cache of the last change to the file.</p>
-<p>The above logic:</p>
-<p>Get the tempLastModified value of the last update of the file, then compare it with the targetFileLastModified value, if tempLastModified > targetFileLastModified, it means that the configuration has been changed in the meantime. instance is reloaded, replacing the old fileConfig so that later operations can get the latest configuration values.</p>
-<p>The logic for adding a configuration property listener is as follows:</p>
-<p><img decoding="async" loading="lazy" src="https://gitee.com/objcoding/md-picture/raw/master/img/20191215161103.png" alt="" class="img_ev3q"></p>
-<p>configListenersMap is a configuration listener cache for FileConfiguration with the following data structure:</p>
-<div class="language-java codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_biex"><pre tabindex="0" class="prism-code language-java codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><span class="token-line" style="color:#393A34"><span class="token class-name">ConcurrentMap</span><span class="token operator" style="color:#393A34"><</span><spa [...]
-<p>As you can see from the data structure, each configuration property can be associated with multiple event listeners.</p>
-<p>Eventually the onProcessEvent method is executed, which is the default method in the listener's base interface, and it calls the onChangeEvent method, which means that it will eventually call the implementation in the FileListener.</p>
-<h1>Dynamic Degradation</h1>
-<p>With the above dynamic configuration subscription functionality, we only need to implement the ConfigurationChangeListener listener to do all kinds of functionality. Currently, Seata only has dynamic degradation functionality for dynamic configuration subscription.</p>
-<p>In the article 「<a href="https://mp.weixin.qq.com/s/n9MHk47zSsFQmV-gBq_P1A" target="_blank" rel="noopener noreferrer">Seata AT mode startup source code analysis</a>」, it is said that in the project of Spring integration with Seata, when AT mode is started, it will use the GlobalTransactionalInterceptor replaces the methods annotated with GlobalTransactional and GlobalLock. GlobalTransactionalInterceptor implements MethodInterceptor, which will eventually execute the invoker method, so [...]
-<ul>
-<li>Add a member variable to GlobalTransactionalInterceptor:</li>
-</ul>
-<div class="language-java codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_biex"><pre tabindex="0" class="prism-code language-java codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><span class="token-line" style="color:#393A34"><span class="token keyword" style="color:#00009f">private</span><span class="token plain"> </span><span class="token [...]
-<p>Initialise the assignment in the constructor:</p>
-<p><img decoding="async" loading="lazy" src="https://gitee.com/objcoding/md-picture/raw/master/img/20191215173221.png" alt="" class="img_ev3q"></p>
-<p>ConfigurationKeys.DISABLE_GLOBAL_TRANSACTION (service.disableGlobalTransaction) This parameter currently has two functions:</p>
-<ol>
-<li>to determine whether to enable global transactions at startup;</li>
-<li>to decide whether or not to demote a global transaction after it has been enabled.</li>
-</ol>
-<ul>
-<li>Implement ConfigurationChangeListener:</li>
-</ul>
-<p><img decoding="async" loading="lazy" src="https://gitee.com/objcoding/md-picture/raw/master/img/20191215173358.png" alt="" class="img_ev3q"></p>
-<p>The logic here is simple, it is to determine whether the listening event belongs to the ConfigurationKeys.DISABLE_GLOBAL_TRANSACTION configuration attribute, if so, directly update the disable value.</p>
-<ul>
-<li>Next, do something in GlobalTransactionalInterceptor#invoke</li>
-</ul>
-<p><img decoding="async" loading="lazy" src="https://gitee.com/objcoding/md-picture/raw/master/img/20191215174155.png" alt="" class="img_ev3q"></p>
-<p>As above, when disable = true, no global transaction with global lock is performed.</p>
-<ul>
-<li>Configuration Centre Subscription Degradation Listener</li>
-</ul>
-<p>io.seata.spring.annotation.GlobalTransactionScanner#wrapIfNecessary</p>
-<p><img decoding="async" loading="lazy" src="https://gitee.com/objcoding/md-picture/raw/master/img/20191215174409.png" alt="" class="img_ev3q"></p>
-<p>The current Configuration Centre will subscribe to the demotion event listener during wrap logic in Spring AOP.</p>
-<h1>Author Bio</h1>
-<p>Zhang Chenghui, currently working in the technology platform department of Zhongtong Technology Information Centre as a Java engineer, mainly responsible for the development of Zhongtong messaging platform and all-links pressure testing project, love to share technology, WeChat public number "back-end advanced" author, technology blog (<a href="https://objcoding.com/" target="_blank" rel="noopener noreferrer">https://objcoding.com/</a>) Blogger, Seata Contributor, GitHub ID: [...]
+<p><a href="https://www.docker.com/" target="_blank" rel="noopener noreferrer">docker official website</a></p></div><footer class="row docusaurus-mt-lg"></footer></article><nav class="pagination-nav" aria-label="Blog list page navigation"><a class="pagination-nav__link pagination-nav__link--prev" href="/blog/page/3"><div class="pagination-nav__label">Newer Entries</div></a><a class="pagination-nav__link pagination-nav__link--next" href="/blog/page/5"><div class="pagination-nav__label">Ol [...]
<div class="fs-12">
<div class="center-div">
<span>Apache Seata (incubating) is an effort undergoing incubation at The Apache Software Foundation (ASF), sponsored by the Apache Incubator. Incubation is required of all newly accepted projects until a further review indicates that the infrastructure, communications, and decision making process have stabilized in a manner consistent with other successful ASF projects. While incubation status is not necessarily a reflection of the completeness or stability of the [...]
diff --git a/blog/page/5/index.html b/blog/page/5/index.html
index 8f30b4349da..cc213cecb01 100644
--- a/blog/page/5/index.html
+++ b/blog/page/5/index.html
@@ -11,11 +11,98 @@
<meta name="aes-config" content="pid=xux-opensource&user_type=101&uid=&username=&dim10=seata"><link rel="stylesheet" href="/assets/css/styles.9644caf2.css">
-<script src="/assets/js/runtime~main.bf98ee01.js" defer="defer"></script>
-<script src="/assets/js/main.8371dd70.js" defer="defer"></script>
+<script src="/assets/js/runtime~main.762ed5c0.js" defer="defer"></script>
+<script src="/assets/js/main.aeea7339.js" defer="defer"></script>
</head>
<body class="navigation-with-keyboard">
-<script>!function(){function t(t){document.documentElement.setAttribute("data-theme",t)}var e=function(){try{return new URLSearchParams(window.location.search).get("docusaurus-theme")}catch(t){}}()||function(){try{return localStorage.getItem("theme")}catch(t){}}();t(null!==e?e:"light")}(),function(){try{const c=new URLSearchParams(window.location.search).entries();for(var[t,e]of c)if(t.startsWith("docusaurus-data-")){var a=t.replace("docusaurus-data-","data-");document.documentElement.se [...]
+<script>!function(){function t(t){document.documentElement.setAttribute("data-theme",t)}var e=function(){try{return new URLSearchParams(window.location.search).get("docusaurus-theme")}catch(t){}}()||function(){try{return localStorage.getItem("theme")}catch(t){}}();t(null!==e?e:"light")}(),function(){try{const c=new URLSearchParams(window.location.search).entries();for(var[t,e]of c)if(t.startsWith("docusaurus-data-")){var a=t.replace("docusaurus-data-","data-");document.documentElement.se [...]
+<p>So how do the multiple configuration centres supported by Seata adapt to different dynamic configuration subscriptions and how do they achieve degradation? Here is a detailed explanation from the source code level.</p>
+<h1>Dynamic Configuration Subscriptions</h1>
+<p>The Seata Configuration Centre has a listener baseline interface, which has an abstract method and default method, as follows:</p>
+<p>io.seata.config.ConfigurationChangeListener</p>
+<p><img decoding="async" loading="lazy" src="https://gitee.com/objcoding/md-picture/raw/master/img/20191216212442.png" alt="" class="img_ev3q"></p>
+<p>This listener baseline interface has two main implementation types:</p>
+<ol>
+<li>implementation of the registration of configuration subscription event listener: for the implementation of a variety of functions of dynamic configuration subscription, such as GlobalTransactionalInterceptor implements ConfigurationChangeListener, according to the dynamic configuration subscription to the dynamic degradation of the implementation of the function;</li>
+<li>the implementation of the configuration centre dynamic subscription function and adaptation: for the file type default configuration centre that currently does not have dynamic subscription function, you can implement the benchmark interface to achieve dynamic configuration subscription function; for the blocking subscription needs to start another thread to execute, then you can implement the benchmark interface for adaptation, you can also reuse the thread pool of the benchmark int [...]
+</ol>
+<h2 class="anchor anchorWithStickyNavbar_LWe7" id="nacos-dynamic-subscription-implementation">Nacos Dynamic Subscription Implementation<a href="#nacos-dynamic-subscription-implementation" class="hash-link" aria-label="Direct link to Nacos Dynamic Subscription Implementation" title="Direct link to Nacos Dynamic Subscription Implementation"></a></h2>
+<p>Nacos has its own internal implementation of the listener, so it directly inherits its internal abstract listener, AbstractSharedListener, which is implemented as follows:</p>
+<p><img decoding="async" loading="lazy" src="https://gitee.com/objcoding/md-picture/raw/master/img/20191223212237.png" alt="" class="img_ev3q"></p>
+<p>As above.</p>
+<ul>
+<li>dataId: configuration attribute for the subscription;</li>
+<li>listener: configures the subscription event listener, which is used to use the incoming listener as a wrapper to perform the actual change logic.</li>
+</ul>
+<p>It's worth mentioning that nacos doesn't use ConfigurationChangeListener to implement its own listener configuration, on the one hand, because Nacos itself already has a listener subscription function, so it doesn't need to implement it; on the other hand, because nacos is a non-blocking subscription, it doesn't need to reuse the ConfigurationChangeListener's thread pool, i.e., no adaptation is needed.</p>
+<p>Add the subscription:</p>
+<p><img decoding="async" loading="lazy" src="https://gitee.com/objcoding/md-picture/raw/master/img/20191223213347.png" alt="" class="img_ev3q"></p>
+<p>The logic of adding a subscription to a dataId in Nacos Configuration Centre is very simple, create a NacosListener with the dataId and a listener, call the configService#addListener method, and use the NacosListener as a listener for the dataId, and then the dataId can be dynamically configured for subscription. Dynamic Configuration Subscription.</p>
+<h2 class="anchor anchorWithStickyNavbar_LWe7" id="file-dynamic-subscription-implementation">file Dynamic subscription implementation<a href="#file-dynamic-subscription-implementation" class="hash-link" aria-label="Direct link to file Dynamic subscription implementation" title="Direct link to file Dynamic subscription implementation"></a></h2>
+<p>Take its implementation class FileListener as an example, its implementation logic is as follows:</p>
+<p><img decoding="async" loading="lazy" src="https://gitee.com/objcoding/md-picture/raw/master/img/20191215151642.png" alt="" class="img_ev3q"></p>
+<p>As above.</p>
+<ul>
+<li>
+<p>dataId: configuration attribute for the subscription;</p>
+</li>
+<li>
+<p>listener: the configuration subscription event listener, used as a wrapper for the incoming listener to perform the real change logic, it is important to note that ** this listener and FileListener also implement the ConfigurationChangeListener interface, except that FileListener is used to provide dynamic configuration subscription to the file, while listener is used to execute configuration subscription events**;</p>
+</li>
+<li>
+<p>executor: a thread pool used for processing configuration change logic, used in the ConfigurationChangeListener#onProcessEvent method.</p>
+</li>
+</ul>
+<p>The implementation of the <strong>FileListener#onChangeEvent method gives the file the ability to subscribe to dynamic configurations</strong> with the following logic:</p>
+<p>It loops indefinitely to get the current value of the subscribed configuration property, fetches the old value from the cache, determines if there is a change, and executes the logic of the external incoming listener if there is a change.</p>
+<p>ConfigurationChangeEvent The event class used to save configuration changes, it has the following member properties:</p>
+<p><img decoding="async" loading="lazy" src="https://gitee.com/objcoding/md-picture/raw/master/img/20191215175232.png" alt="" class="img_ev3q"></p>
+<p>How does the getConfig method sense changes to the file configuration? We click into it and find that it ends up with the following logic:</p>
+<p><img decoding="async" loading="lazy" src="https://gitee.com/objcoding/md-picture/raw/master/img/20191215162713.png" alt="" class="img_ev3q"></p>
+<p>We see that it creates a future class, wraps it in a Runnable and puts it into the thread pool to execute asynchronously, and then calls the get method to block the retrieval of the value, so let's move on:</p>
+<p><img decoding="async" loading="lazy" src="https://gitee.com/objcoding/md-picture/raw/master/img/20191215170908.png" alt="" class="img_ev3q"></p>
+<p>allowDynamicRefresh: configure switch for dynamic refresh;</p>
+<p>targetFileLastModified: time cache of the last change to the file.</p>
+<p>The above logic:</p>
+<p>Get the tempLastModified value of the last update of the file, then compare it with the targetFileLastModified value, if tempLastModified > targetFileLastModified, it means that the configuration has been changed in the meantime. instance is reloaded, replacing the old fileConfig so that later operations can get the latest configuration values.</p>
+<p>The logic for adding a configuration property listener is as follows:</p>
+<p><img decoding="async" loading="lazy" src="https://gitee.com/objcoding/md-picture/raw/master/img/20191215161103.png" alt="" class="img_ev3q"></p>
+<p>configListenersMap is a configuration listener cache for FileConfiguration with the following data structure:</p>
+<div class="language-java codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_biex"><pre tabindex="0" class="prism-code language-java codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><span class="token-line" style="color:#393A34"><span class="token class-name">ConcurrentMap</span><span class="token operator" style="color:#393A34"><</span><spa [...]
+<p>As you can see from the data structure, each configuration property can be associated with multiple event listeners.</p>
+<p>Eventually the onProcessEvent method is executed, which is the default method in the listener's base interface, and it calls the onChangeEvent method, which means that it will eventually call the implementation in the FileListener.</p>
+<h1>Dynamic Degradation</h1>
+<p>With the above dynamic configuration subscription functionality, we only need to implement the ConfigurationChangeListener listener to do all kinds of functionality. Currently, Seata only has dynamic degradation functionality for dynamic configuration subscription.</p>
+<p>In the article 「<a href="https://mp.weixin.qq.com/s/n9MHk47zSsFQmV-gBq_P1A" target="_blank" rel="noopener noreferrer">Seata AT mode startup source code analysis</a>」, it is said that in the project of Spring integration with Seata, when AT mode is started, it will use the GlobalTransactionalInterceptor replaces the methods annotated with GlobalTransactional and GlobalLock. GlobalTransactionalInterceptor implements MethodInterceptor, which will eventually execute the invoker method, so [...]
+<ul>
+<li>Add a member variable to GlobalTransactionalInterceptor:</li>
+</ul>
+<div class="language-java codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_biex"><pre tabindex="0" class="prism-code language-java codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><span class="token-line" style="color:#393A34"><span class="token keyword" style="color:#00009f">private</span><span class="token plain"> </span><span class="token [...]
+<p>Initialise the assignment in the constructor:</p>
+<p><img decoding="async" loading="lazy" src="https://gitee.com/objcoding/md-picture/raw/master/img/20191215173221.png" alt="" class="img_ev3q"></p>
+<p>ConfigurationKeys.DISABLE_GLOBAL_TRANSACTION (service.disableGlobalTransaction) This parameter currently has two functions:</p>
+<ol>
+<li>to determine whether to enable global transactions at startup;</li>
+<li>to decide whether or not to demote a global transaction after it has been enabled.</li>
+</ol>
+<ul>
+<li>Implement ConfigurationChangeListener:</li>
+</ul>
+<p><img decoding="async" loading="lazy" src="https://gitee.com/objcoding/md-picture/raw/master/img/20191215173358.png" alt="" class="img_ev3q"></p>
+<p>The logic here is simple, it is to determine whether the listening event belongs to the ConfigurationKeys.DISABLE_GLOBAL_TRANSACTION configuration attribute, if so, directly update the disable value.</p>
+<ul>
+<li>Next, do something in GlobalTransactionalInterceptor#invoke</li>
+</ul>
+<p><img decoding="async" loading="lazy" src="https://gitee.com/objcoding/md-picture/raw/master/img/20191215174155.png" alt="" class="img_ev3q"></p>
+<p>As above, when disable = true, no global transaction with global lock is performed.</p>
+<ul>
+<li>Configuration Centre Subscription Degradation Listener</li>
+</ul>
+<p>io.seata.spring.annotation.GlobalTransactionScanner#wrapIfNecessary</p>
+<p><img decoding="async" loading="lazy" src="https://gitee.com/objcoding/md-picture/raw/master/img/20191215174409.png" alt="" class="img_ev3q"></p>
+<p>The current Configuration Centre will subscribe to the demotion event listener during wrap logic in Spring AOP.</p>
+<h1>Author Bio</h1>
+<p>Zhang Chenghui, currently working in the technology platform department of Zhongtong Technology Information Centre as a Java engineer, mainly responsible for the development of Zhongtong messaging platform and all-links pressure testing project, love to share technology, WeChat public number "back-end advanced" author, technology blog (<a href="https://objcoding.com/" target="_blank" rel="noopener noreferrer">https://objcoding.com/</a>) Blogger, Seata Contributor, GitHub ID: [...]
<h1>Configuration Centre Property Loading</h1>
<p>In Seata Configuration Centre, there are two default configuration files:</p>
<p>! <a href="https://gitee.com/objcoding/md-picture/raw/master/img/20191211193041.png" target="_blank" rel="noopener noreferrer"></a></p>
@@ -754,154 +841,7 @@
</ul>
<a name="3X7vO"></a>
<h2 class="anchor anchorWithStickyNavbar_LWe7" id="related-links-mentioned-in-the-article">Related Links Mentioned in the Article<a href="#related-links-mentioned-in-the-article" class="hash-link" aria-label="Direct link to Related Links Mentioned in the Article" title="Direct link to Related Links Mentioned in the Article"></a></h2>
-<p>[1]<a href="https://github.com/aphyr/dist-sagas/blob/master/sagas.pdf" target="_blank" rel="noopener noreferrer">https://github.com/aphyr/dist-sagas/blob/master/sagas.pdf</a><br>[2]<a href="http://microservices.io/patterns/data/saga.html" target="_blank" rel="noopener noreferrer">http://microservices.io/patterns/data/saga.html</a><br>[3]<a href="https://github.com/eclipse/microprofile-sandbox/tree/master/proposals/0009-LRA" target="_blank" rel="noopener noreferrer">Microprofile 的 LRA< [...]
-<br>This article is based on the topic of "Distributed Transaction Seata and its Three Patterns" shared at SOFA Meetup#3 on 11 August in Guangzhou, focusing on the background and theoretical foundation of distributed transaction, as well as the principle of Seata distributed transaction and the implementation of distributed transaction in three patterns (AT, TCC, and Saga).</p>
-<p>The video and PPT are at the end of this article.</p>
-<p><img decoding="async" loading="lazy" alt="3 Distributed Transaction Seata Three Modes Explained-Eiyuan.jpg" src="/assets/images/1-59eeb2c64e493e827495e0417125db43.jpeg" width="746" height="420" class="img_ev3q"></p>
-<a name="Ad95d"></a>
-<h2 class="anchor anchorWithStickyNavbar_LWe7" id="i-background-of-the-emergence-of-distributed-transactions">I. Background of the emergence of distributed transactions<a href="#i-background-of-the-emergence-of-distributed-transactions" class="hash-link" aria-label="Direct link to I. Background of the emergence of distributed transactions" title="Direct link to I. Background of the emergence of distributed transactions"></a></h2>
-<a name="Q2ayF"></a>
-<h3 class="anchor anchorWithStickyNavbar_LWe7" id="11-distributed-architecture-evolution---horizontal-splitting-of-database">1.1 Distributed Architecture Evolution - Horizontal Splitting of Database<a href="#11-distributed-architecture-evolution---horizontal-splitting-of-database" class="hash-link" aria-label="Direct link to 1.1 Distributed Architecture Evolution - Horizontal Splitting of Database" title="Direct link to 1.1 Distributed Architecture Evolution - Horizontal Splitting of Dat [...]
-<p>AntGold's business database was initially a single database with a single table, but with the rapid development of the business data scale, the data volume is getting bigger and bigger, and the single database with a single table is gradually becoming a bottleneck. So we split the database horizontally, splitting the original single database and single table into database slices.</p>
-<p>As shown in the figure below, after splitting the database and table, the original write operation that can be completed on a database may be across multiple databases, which gives rise to cross-database transaction problems.</p>
-<p><img decoding="async" loading="lazy" alt="image.png" src="/assets/images/2-e3a8a7b0f1e093d70faf16a548dd6742.png" width="325" height="214" class="img_ev3q"></p>
-<a name="WBQbC"></a>
-<h3 class="anchor anchorWithStickyNavbar_LWe7" id="12-distributed-architecture-evolution---business-service-splitting">1.2 Distributed Architecture Evolution - Business Service Splitting<a href="#12-distributed-architecture-evolution---business-service-splitting" class="hash-link" aria-label="Direct link to 1.2 Distributed Architecture Evolution - Business Service Splitting" title="Direct link to 1.2 Distributed Architecture Evolution - Business Service Splitting"></a></h3>
-<p>In the early stage of business development, the single business system architecture of "one piece of cake" can meet the basic business needs. However, with the rapid development of the business, the system's access and business complexity are growing rapidly, single-system architecture has gradually become the bottleneck of business development, to solve the problem of high coupling and scalability of the business system demand is becoming stronger and stronger.</p>
-<p>As shown in the figure below, Ant Financial Services splits the single business system into multiple business systems in accordance with the design principles of Service Oriented Architecture (SOA), which reduces the coupling between the systems and enables different business systems to focus on their own business, which is more conducive to the development of the business and the scaling of the system capacity.</p>
-<p><img decoding="async" loading="lazy" alt="image.png" src="/assets/images/3-548d85e1cdfbab71650a542d5de5d10a.png" width="557" height="277" class="img_ev3q"></p>
-<p>After the business system is split according to services, a complete business often needs to call multiple services, how to ensure data consistency between multiple services becomes a difficult problem.</p>
-<a name="3oIxE"></a>
-<h2 class="anchor anchorWithStickyNavbar_LWe7" id="ii-theoretical-foundation-of-distributed-transaction">II. Theoretical foundation of distributed transaction<a href="#ii-theoretical-foundation-of-distributed-transaction" class="hash-link" aria-label="Direct link to II. Theoretical foundation of distributed transaction" title="Direct link to II. Theoretical foundation of distributed transaction"></a></h2>
-<a name="akRiW"></a>
-<h3 class="anchor anchorWithStickyNavbar_LWe7" id="21-two-stage-commit-protocols">2.1 Two-stage commit protocols<a href="#21-two-stage-commit-protocols" class="hash-link" aria-label="Direct link to 2.1 Two-stage commit protocols" title="Direct link to 2.1 Two-stage commit protocols"></a></h3>
-<p><img decoding="async" loading="lazy" alt="16_16_18__08_13_2019.jpg" src="/assets/images/4-5933efe8b07271b941670f74b7322a1f.jpeg" width="746" height="419" class="img_ev3q"></p>
-<p>Two phase commit protocol: transaction manager coordinates resource manager in two phases, the first phase prepares resources, that is, reserve the resources needed for the transaction, if every resource manager resource reservation succeeds, the second phase resource commit is performed, otherwise the coordinated resource manager rolls back the resources.</p>
-<a name="8tfKI"></a>
-<h3 class="anchor anchorWithStickyNavbar_LWe7" id="22-tcc">2.2 TCC<a href="#22-tcc" class="hash-link" aria-label="Direct link to 2.2 TCC" title="Direct link to 2.2 TCC"></a></h3>
-<p><img decoding="async" loading="lazy" alt="16_16_51__08_13_2019.jpg" src="/assets/images/5-79c36a571b40ceb0119e48100150675b.jpeg" width="746" height="416" class="img_ev3q"></p>
-<p>TCC (Try-Confirm-Cancel) is actually a two-phase commit protocol for servitisation, business developers need to implement these three service interfaces, the first phase of the service is choreographed by the business code to call the Try interface for resource reservation, the Try interface for all participants is successful, the transaction manager will commit the transaction and call the Confirm interface for each participant The transaction manager will commit the transaction and [...]
-<a name="IXxpF"></a>
-<h3 class="anchor anchorWithStickyNavbar_LWe7" id="23-saga">2.3 Saga<a href="#23-saga" class="hash-link" aria-label="Direct link to 2.3 Saga" title="Direct link to 2.3 Saga"></a></h3>
-<p><img decoding="async" loading="lazy" alt="3 Distributed Transactions Seata Three Patterns Explained - Yi Yuan-9.jpg" src="/assets/images/6-9d33493d97af453a8450f0739fa60a0f.jpeg" width="746" height="420" class="img_ev3q"></p>
-<p>Saga is a compensation protocol. In Saga mode, there are multiple participants within a distributed transaction, and each participant is an offsetting compensation service that requires the user to implement its forward and reverse rollback operations according to the business scenario.</p>
-<p>During the execution of a distributed transaction, the forward operations of each participant are executed sequentially, and if all forward operations are executed successfully, the distributed transaction commits. If any of the forward operations fails, the distributed transaction backs out and performs a reverse rollback on the previous participants, rolling back the committed participants and returning the distributed transaction to its initial state.</p>
-<p>Saga theory is from the paper Sagas published by Hector & Kenneth in 1987.<br>
-<br>Saga Positive Service and Compensation Service also need to be implemented by business developers.</p>
-<a name="fZPaN"></a>
-<h2 class="anchor anchorWithStickyNavbar_LWe7" id="iii-seata-and-its-three-patterns-explained-in-detail">III. Seata and its three patterns explained in detail<a href="#iii-seata-and-its-three-patterns-explained-in-detail" class="hash-link" aria-label="Direct link to III. Seata and its three patterns explained in detail" title="Direct link to III. Seata and its three patterns explained in detail"></a></h2>
-<a name="IgVM7"></a>
-<h3 class="anchor anchorWithStickyNavbar_LWe7" id="31-distributed-transaction-seata-introduction">3.1 Distributed transaction Seata introduction<a href="#31-distributed-transaction-seata-introduction" class="hash-link" aria-label="Direct link to 3.1 Distributed transaction Seata introduction" title="Direct link to 3.1 Distributed transaction Seata introduction"></a></h3>
-<p>Seata (Simple Extensible Autonomous Transaction Architecture) is a distributed transaction solution jointly open-sourced by Ant Financial Services and Alibaba in January 2019.Seata has been open-sourced for about half a year, and currently has more than 11,000 stars. Seata has been open source for about half a year, and now has more than 11,000 stars and a very active community. We warmly welcome you to participate in the Seata community construction, together will Seata become the op [...]
-<p>Seata: <a href="https://github.com/apache/incubator-seata" target="_blank" rel="noopener noreferrer">https://</a>[github.com/apache/incubator-seata](<a href="https://github.com/apache/incubator" target="_blank" rel="noopener noreferrer">https://github.com/apache/incubator</a> -seata)<br>
-<br><img decoding="async" loading="lazy" alt="image.png" src="/assets/images/7-409b712dba10afe30f485ec206d0240f.png" width="584" height="142" class="img_ev3q"></p>
-<a name="zyy0l"></a>
-<h3 class="anchor anchorWithStickyNavbar_LWe7" id="32-distributed-transactions-seata-product-module">3.2 Distributed Transactions Seata Product Module<a href="#32-distributed-transactions-seata-product-module" class="hash-link" aria-label="Direct link to 3.2 Distributed Transactions Seata Product Module" title="Direct link to 3.2 Distributed Transactions Seata Product Module"></a></h3>
-<p>As shown in the figure below, there are three major modules in Seata, namely TM, RM and TC. TM and RM are integrated with the business system as clients of Seata, and TC is deployed independently as the server of Seata.</p>
-<p>TC is deployed independently as a Seata server. <a href="/assets/files/8-1e7e5bd472714f2a5eaf932b449942b2.png" target="_blank">image.png</a></p>
-<p>The execution flow of a distributed transaction in Seata:</p>
-<ul>
-<li>TM opens distributed transaction (TM registers global transaction record with TC);</li>
-<li>According to the business scenario, arrange the resources in the transaction such as database and service (RM reports the resource readiness status to TC);</li>
-<li>TM ends the distributed transaction, and the transaction phase ends (TM notifies TC to commit/rollback the distributed transaction);</li>
-<li>TC aggregates the transaction information and decides whether the distributed transaction should be committed or rolled back;</li>
-<li>TC notifies all RMs to commit/rollback resources, transaction phase 2 ends;</li>
-</ul>
-<a name="1QKqI"></a>
-<h3 class="anchor anchorWithStickyNavbar_LWe7" id="33-distributed-transactions-seata-solution">3.3 Distributed Transactions Seata Solution<a href="#33-distributed-transactions-seata-solution" class="hash-link" aria-label="Direct link to 3.3 Distributed Transactions Seata Solution" title="Direct link to 3.3 Distributed Transactions Seata Solution"></a></h3>
-<p>Seata has four distributed transaction solutions, AT mode, TCC mode, Saga mode and XA mode.</p>
-<p><img decoding="async" loading="lazy" alt="15_49_23__08_13_2019.jpg" src="/assets/images/9-92fbc62876258a48b6778d72eaab6af6.jpeg" width="746" height="385" class="img_ev3q"><br></p>
-<a name="784n4"></a>
-<h4 class="anchor anchorWithStickyNavbar_LWe7" id="231-at-mode">2.3.1 AT Mode<a href="#231-at-mode" class="hash-link" aria-label="Direct link to 2.3.1 AT Mode" title="Direct link to 2.3.1 AT Mode"></a></h4>
-<p>In January, Seata open sourced AT Mode, a non-intrusive distributed transaction solution. In AT mode, users only need to focus on their own "business SQL", the user's "business SQL" as a phase, Seata framework will automatically generate the transaction of the two-phase commit and rollback operations.</p>
-<p><img decoding="async" loading="lazy" alt="image.png" src="/assets/images/10-c19d842e385a2e54cc4b838e11642851.png" width="521" height="238" class="img_ev3q"><br></p>
-<a name="Acfeo"></a>
-<h5 class="anchor anchorWithStickyNavbar_LWe7" id="how-the-at-model-is-non-intrusive-to-business-">How the AT model is non-intrusive to business :<a href="#how-the-at-model-is-non-intrusive-to-business-" class="hash-link" aria-label="Direct link to How the AT model is non-intrusive to business :" title="Direct link to How the AT model is non-intrusive to business :"></a></h5>
-<ul>
-<li>Phase I:</li>
-</ul>
-<p>In phase 1, Seata intercepts the "business SQL", first parses the semantics of the SQL, finds the business data to be updated by the "business SQL", and then saves it as a "before image" before updating the business data. Before the business data is updated, it will save it as "before image", then execute "business SQL" to update the business data, and after the business data is updated, it will save it as "after image", and [...]
-<p>This ensures the atomicity of a phase of operations. <a href="/assets/files/11-b62ee2dfd6ab6e9094d2b51451b41cdd.png" target="_blank">image3.png</a></p>
-<ul>
-<li>Second-phase commit:</li>
-</ul>
-<p>If the second phase is a commit, since the "business SQL" has already been committed to the database in the first phase, the Seata framework only needs to delete the snapshot data and row locks saved in the first phase to complete the data cleanup.</p>
-<p><img decoding="async" loading="lazy" alt="image 4.png" src="/assets/images/12-fb7571a44266fa4692599f2907e93125.png" width="480" height="206" class="img_ev3q"></p>
-<ul>
-<li>Phase 2 rollback:</li>
-</ul>
-<p>If the second phase is a rollback, Seata needs to rollback the "business SQL" that has been executed in the first phase to restore the business data. The way to rollback is to use "before image" to restore the business data; however, before restoring, we must first verify the dirty writing, compare the "current business data in the database" and the "after image", if the two data are not in the same state, then we will use the "after image& [...]
-<p><img decoding="async" loading="lazy" alt="image 5.png" src="/assets/images/13-67b42e8743563de3117194847e4119de.png" width="463" height="317" class="img_ev3q"></p>
-<p>AT mode one phase, two phase commit and rollback are automatically generated by Seata framework, user only need to write "business SQL", then can easily access distributed transaction, AT mode is a kind of distributed transaction solution without any intrusion to business.</p>
-<a name="FnD1S"></a>
-<h4 class="anchor anchorWithStickyNavbar_LWe7" id="232-tcc-mode">2.3.2 TCC Mode<a href="#232-tcc-mode" class="hash-link" aria-label="Direct link to 2.3.2 TCC Mode" title="Direct link to 2.3.2 TCC Mode"></a></h4>
-<p>In March 2019, Seata open-sourced the TCC pattern, which is contributed by Ant Gold. the TCC pattern requires users to implement Try, Confirm and Cancel operations according to their business scenarios; the transaction initiator executes the Try method in the first stage, the Confirm method in the second-stage commit, and the Cancel method in the second-stage rollback.</p>
-<p>The transaction initiator performs Try in the first stage, Confirm in the second stage, and Cancel in the second stage. <a href="/assets/files/14-bd8bfbb4c59f42028ab03a8c409b1c73.png" target="_blank">image 6.png</a></p>
-<p>TCC Three method descriptions:</p>
-<ul>
-<li>Try: detection and reservation of resources;</li>
-<li>Confirm: the execution of the business operation submitted; require Try success Confirm must be successful;</li>
-<li>Cancel: the release of the reserved resources;</li>
-</ul>
-<p><strong>Ant Gold's practical experience in TCC</strong><br>**<br><img decoding="async" loading="lazy" alt="16_48_02__08_13_2019.jpg" src="/assets/images/15-02cfa1203b468d38c80caa594a7644f7.jpeg" width="746" height="414" class="img_ev3q"></p>
-<p><strong>1 TCC Design - Business model is designed in 2 phases:</strong></p>
-<p>The most important thing for users to consider when accessing TCC is how to split their business model into two phases.</p>
-<p>Take the "debit" scenario as an example, before accessing TCC, the debit of account A can be completed with a single SQL for updating the account balance; however, after accessing TCC, the user needs to consider how to split the original one-step debit operation into two phases and implement it into three methods, and to ensure that the first-phase Try will be successful and the second-phase Confirm will be successful if Try is successful. If Try succeeds in the first stage, [...]
-<p><img decoding="async" loading="lazy" alt="image 7.png" src="/assets/images/16-e07ff8c531571c0ef2887d9dc8b4c83f.png" width="588" height="265" class="img_ev3q"></p>
-<p>As shown above, the</p>
-<p>Try method as a one-stage preparation method needs to do resource checking and reservation. In the deduction scenario, what Try has to do is to check whether the account balance is sufficient and reserve funds for transfer, and the way to reserve is to freeze the transfer funds of account A. After the execution of the Try method, although the balance of account A is still 100, but $30 of it has been frozen and cannot be used by other transactions.</p>
-<p>The second stage, the Confirm method, performs the real debit operation; Confirm will use the funds frozen in the Try stage to perform the debit operation; after the Confirm method is executed, the $30 frozen in the first stage has been deducted from account A, and the balance of account A becomes $70.</p>
-<p>If the second stage is a rollback, you need to release the $30 frozen in the first stage of Try in the Cancel method, so that account A is back to the initial state, and all $100 is available.</p>
-<p>The most important thing for users to access TCC mode is to consider how to split the business model into 2 phases, implement it into 3 methods of TCC, and ensure that Try succeeds and Confirm succeeds. Compared to AT mode, TCC mode is somewhat intrusive to the business code, but TCC mode does not have the global line locks of AT mode, and the performance of TCC will be much higher than AT mode.</p>
-<p><strong>2 TCC Design - Allow Null Rollback:</strong><br>**<br><img decoding="async" loading="lazy" alt="16_51_44__08_13_2019.jpg" src="/assets/images/17-b2c8866f3bee9d7eacf27c0e02f0ef68.jpeg" width="746" height="414" class="img_ev3q"></p>
-<p>The Cancel interface needs to be designed to allow null rollbacks. When the Try interface is not received due to packet loss, the transaction manager triggers a rollback, which triggers the Cancel interface, which needs to return to the success of the rollback when it finds that there is no corresponding transaction xid or primary key during the execution of Cancel. If the transaction service manager thinks it has been rolled back, otherwise it will keep retrying, and Cancel has no co [...]
-<p><strong>3 TCC Design - Anti-Suspension Control:</strong><br>**<br><img decoding="async" loading="lazy" alt="16_51_56__08_13_2019.jpg" src="/assets/images/18-3cfd6186d46d6c1cf79f4b5aea91aea0.jpeg" width="746" height="416" class="img_ev3q"></p>
-<p>The implication of the suspension is that the Cancel is executed before the Try interface, which occurs because the Try times out due to network congestion, the transaction manager generates a rollback that triggers the Cancel interface, and the Try interface call is eventually received, but the Cancel arrives before the Try. According to the previous logic of allowing empty rollback, the rollback will return successfully, the transaction manager thinks the transaction has been rolled [...]
-<p><strong>4 TCC Design - Power Control:</strong><br>**<br><img decoding="async" loading="lazy" alt="16_52_07__08_13_2019.jpg" src="/assets/images/19-cbc9396d9760ae9eee6ef163c21e8034.jpeg" width="746" height="415" class="img_ev3q"></p>
-<p>Idempotence means that for the same system, using the same conditions, a single request and repeated multiple requests have the same impact on system resources. Because network jitter or congestion may timeout, transaction manager will retry operation on resources, so it is very likely that a business operation will be called repeatedly, in order not to occupy resources many times because of repeated calls, it is necessary to control idempotency when designing the service, usually we [...]
-<a name="dsMch"></a>
-<h4 class="anchor anchorWithStickyNavbar_LWe7" id="233-saga-patterns">2.3.3 Saga Patterns<a href="#233-saga-patterns" class="hash-link" aria-label="Direct link to 2.3.3 Saga Patterns" title="Direct link to 2.3.3 Saga Patterns"></a></h4>
-<p>Saga mode is Seata's upcoming open source solution for long transactions, which will be mainly contributed by Ant Gold. In Saga mode, there are multiple participants within a distributed transaction, and each participant is an offsetting compensation service that requires users to implement its forward and reverse rollback operations according to business scenarios.</p>
-<p>During the execution of a distributed transaction, the forward operations of each participant are executed sequentially, and if all forward operations are executed successfully, the distributed transaction commits. If any of the forward operations fails, the distributed transaction will go back and execute the reverse rollback operations of the previous participants to roll back the committed participants and bring the distributed transaction back to the initial state.</p>
-<p><img decoding="async" loading="lazy" alt="image 8.png" src="/assets/images/20-7a8ab27e616b4987792c11ff82ac900d.png" width="360" height="359" class="img_ev3q"></p>
-<p>Saga Pattern Distributed transactions are usually event-driven and executed asynchronously between the various participants, Saga Pattern is a long transaction solution.</p>
-<p><strong>1 Saga pattern usage scenario</strong><br>**<br><img decoding="async" loading="lazy" alt="16_44_58__08_13_2019.jpg" src="/assets/images/21-cb2c15b7cda9ba7e3870b03efb42b0f7.jpeg" width="746" height="416" class="img_ev3q"></p>
-<p>Saga pattern is suitable for business systems with long business processes and the need to ensure the final consistency of transactions. Saga pattern commits local transactions at one stage, and performance can be guaranteed in the case of lock-free and long processes.</p>
-<p>Transaction participants may be services from other companies or legacy systems that cannot be transformed and provide the interfaces required by TCC, and can use the Saga pattern.</p>
-<p>The advantages of the Saga pattern are:</p>
-<ul>
-<li>One-stage commit of local database transactions, lock-free, high performance;</li>
-<li>Participants can use transaction-driven asynchronous execution, high throughput;</li>
-<li>The compensation service is the "reverse" of the forward service, which is easy to understand and implement;</li>
-</ul>
-<p>Disadvantages: The Saga pattern does not guarantee isolation because the local database transaction has already been committed in the first phase and no "reservation" action has been performed. Later we will talk about the lack of isolation of the countermeasures. <br><strong>2 Saga implementation based on a state machine engine</strong>* <br><strong>2 Saga implementation based on a state machine engine</strong>* <br>**3</p>
-<p><img decoding="async" loading="lazy" alt="17_13_19__08_13_2019.jpg" src="/assets/images/22-d2bafd9570e63096283bb8cad41a0f43.png" width="1222" height="646" class="img_ev3q"></p>
-<p>Currently there are generally two types of Saga implementations, one is achieved through event-driven architecture, and the other is based on annotations plus interceptors to intercept the business of the positive service implementation.Seata is currently implemented using an event-driven mechanism, Seata implements a state machine, which can orchestrate the call flow of the service and the compensation service of the positive service, generating a state diagram defined by a json file [...]
-<p><strong>3 State Machine Engine Principles</strong><br></p>
-<p><img decoding="async" loading="lazy" alt="16_45_32__08_13_2019.jpg" src="/assets/images/23-1d09ccedb0eb9f45ddda46963f6a9f12.png" width="1240" height="647" class="img_ev3q"></p>
-<p>The basic principle of this state machine engine is that it is based on an event-driven architecture, where each step is executed asynchronously, and steps flow through an event queue between steps, <br>greatly improving system throughput. Transaction logs are recorded at the time of execution of each step for use when rolling back in the event of an exception. Transaction logs are recorded in the database where the business tables are located to improve performance.</p>
-<p>**4 State Machine Engine Design</p>
-<p><img decoding="async" loading="lazy" alt="16_45_46__08_13_2019.jpg" src="/assets/images/24-15fdd730a55833c61ceb860ada0f871b.jpeg" width="746" height="411" class="img_ev3q"></p>
-<p>The state machine engine is divided into a three-tier architecture design, the bottom layer is the "event-driven" layer, the implementation of the EventBus and the consumption of events in the thread pool, is a Pub-Sub architecture. The second layer is the "process controller" layer, which implements a minimalist process engine framework that drives an "empty" process execution. node does, it just executes the process method of each node and then executes [...]
-<p><strong>5 The Saga Service Design Experience</strong></p>
-<p>Similar to TCC, Saga's forward and reverse services need to follow the following design principles:</p>
-<p><strong>1) Saga Service Design - Allow Null Compensation</strong><br>**<br><img decoding="async" loading="lazy" alt="16_52_22__08_13_2019.jpg" src="/assets/images/25-2cae6395619166a3c23e698ac2306f8b.jpeg" width="746" height="415" class="img_ev3q"></p>
-<p><strong>2) Saga Service Design - Anti-Suspension Control</strong><br>**<br><img decoding="async" loading="lazy" alt="16_52_52__08_13_2019.jpg" src="/assets/images/26-ead26d36857d8ae91dbb16ff72873653.jpeg" width="746" height="417" class="img_ev3q"></p>
-<p><strong>3) Saga Service Design - Power Control</strong><br>**<br><img decoding="async" loading="lazy" alt="3 Distributed Transactions Seata Three Patterns Explained - Yi Yuan-31.jpg" src="/assets/images/27-11883ffbfbca7e56a3a5984f3e0c3fe6.jpeg" width="746" height="420" class="img_ev3q"></p>
-<p><strong>4) Saga Design - Custom Transaction Recovery Strategies</strong><br>**<br><img decoding="async" loading="lazy" alt="16_53_07__08_13_2019.jpg" src="/assets/images/28-73c6b9cfb082be166cb84a9381b81c0f.jpeg" width="746" height="414" class="img_ev3q"></p>
-<p>As mentioned earlier, the Saga pattern does not guarantee transaction isolation, and dirty writes can occur in extreme cases. For example, in the case of a distributed transaction is not committed, the data of the previous service was modified, and the service behind the anomaly needs to be rolled back, may not be able to compensate for the operation due to the data of the previous service was modified. One way to deal with this situation is to "retry" and continue forward t [...]
-<p>Since Saga does not guarantee isolation, we need to achieve the principle of "long money rather than short money" in business design. Long money refers to the situation when there is a mistake and the money is too much from our point of view, and the money is too little, because if the money is too long, we can refund the money to the customer, but if it is too short, the money may not be recovered, which means that in the business design, we must give priority to "roll [...]
-<p><strong>6 Annotation and Interceptor Based Saga Implementation</strong><br>**<br><img decoding="async" loading="lazy" alt="17_13_37__08_13_2019.jpg" src="/assets/images/29-3d3a00510ed54a37763e1558f7343789.jpeg" width="746" height="416" class="img_ev3q"></p>
-<p>There is another implementation of Saga that is based on annotations + interceptors, which Seata does not currently implement. You can look at the pseudo-code above to understand it, the @SagaCompensable annotation is defined on the one method, and the compensation method used to define the one method is the compensateOne method. Then the @SagaTransactional annotation is defined on the processA method of the business process code, which starts a Saga distributed transaction, intercept [...]
-<p>**7 Comparison of Advantages and Disadvantages of the Two Saga Implementations</p>
-<p>The following table compares the advantages and disadvantages of the two Saga implementations:</p>
-<p><img decoding="async" loading="lazy" alt="17_13_49__08_13_2019.jpg" src="/assets/images/30-990cbb972417453d06119316c2c1bc7e.jpeg" width="746" height="415" class="img_ev3q"></p>
-<p>The biggest advantage of the state machine engine is that it can be executed asynchronously through an event-driven approach to improve system throughput, service scheduling requirements can be achieved, and in the absence of isolation in the Saga model, there can be an additional "retry forward" strategy to recover from things. The biggest advantage of annotations and interceptors is that they are easy to develop and low cost to learn.</p>
-<a name="Gpkrf"></a>
-<h2 class="anchor anchorWithStickyNavbar_LWe7" id="summary">Summary<a href="#summary" class="hash-link" aria-label="Direct link to Summary" title="Direct link to Summary"></a></h2>
-<p>This article first reviewed the background and theoretical basis of distributed transactions, and then focused on the principles of Seata distributed transactions and three patterns (AT, TCC, Saga) of distributed transaction implementation.</p>
-<p>Seata's positioning is a full-scenario solution for distributed transactions, and in the future there will also be XA mode of distributed transaction implementation, each mode has its own application scenarios, AT mode is a non-intrusive distributed transaction solution for scenes that do not want to transform the business, with almost zero learning cost. TCC mode is a high-performance distributed transaction solution for core systems and other scenes that have a high demand for [...]
-<p>The video review and PPT of this sharing can be viewed at: [<a href="https://tech.antfin.com/community/activities/779/review%5D(" target="_blank" rel="noopener noreferrer">https://tech.antfin.com/community/activities/779/review](</a><a href="https://tech.antfin.com/community/activities/779/" target="_blank" rel="noopener noreferrer">https://tech.antfin.com/community/activities/779/</a> review)</p></div><footer class="row docusaurus-mt-lg"></footer></article><nav class="pagination-nav" [...]
+<p>[1]<a href="https://github.com/aphyr/dist-sagas/blob/master/sagas.pdf" target="_blank" rel="noopener noreferrer">https://github.com/aphyr/dist-sagas/blob/master/sagas.pdf</a><br>[2]<a href="http://microservices.io/patterns/data/saga.html" target="_blank" rel="noopener noreferrer">http://microservices.io/patterns/data/saga.html</a><br>[3]<a href="https://github.com/eclipse/microprofile-sandbox/tree/master/proposals/0009-LRA" target="_blank" rel="noopener noreferrer">Microprofile 的 LRA< [...]
<div class="fs-12">
<div class="center-div">
<span>Apache Seata (incubating) is an effort undergoing incubation at The Apache Software Foundation (ASF), sponsored by the Apache Incubator. Incubation is required of all newly accepted projects until a further review indicates that the infrastructure, communications, and decision making process have stabilized in a manner consistent with other successful ASF projects. While incubation status is not necessarily a reflection of the completeness or stability of the [...]
diff --git a/blog/page/6/index.html b/blog/page/6/index.html
index 9b6f93db5b1..0edb76f220a 100644
--- a/blog/page/6/index.html
+++ b/blog/page/6/index.html
@@ -11,11 +11,158 @@
<meta name="aes-config" content="pid=xux-opensource&user_type=101&uid=&username=&dim10=seata"><link rel="stylesheet" href="/assets/css/styles.9644caf2.css">
-<script src="/assets/js/runtime~main.bf98ee01.js" defer="defer"></script>
-<script src="/assets/js/main.8371dd70.js" defer="defer"></script>
+<script src="/assets/js/runtime~main.762ed5c0.js" defer="defer"></script>
+<script src="/assets/js/main.aeea7339.js" defer="defer"></script>
</head>
<body class="navigation-with-keyboard">
-<script>!function(){function t(t){document.documentElement.setAttribute("data-theme",t)}var e=function(){try{return new URLSearchParams(window.location.search).get("docusaurus-theme")}catch(t){}}()||function(){try{return localStorage.getItem("theme")}catch(t){}}();t(null!==e?e:"light")}(),function(){try{const c=new URLSearchParams(window.location.search).entries();for(var[t,e]of c)if(t.startsWith("docusaurus-data-")){var a=t.replace("docusaurus-data-","data-");document.documentElement.se [...]
+<script>!function(){function t(t){document.documentElement.setAttribute("data-theme",t)}var e=function(){try{return new URLSearchParams(window.location.search).get("docusaurus-theme")}catch(t){}}()||function(){try{return localStorage.getItem("theme")}catch(t){}}();t(null!==e?e:"light")}(),function(){try{const c=new URLSearchParams(window.location.search).entries();for(var[t,e]of c)if(t.startsWith("docusaurus-data-")){var a=t.replace("docusaurus-data-","data-");document.documentElement.se [...]
+<br>This article is based on the topic of "Distributed Transaction Seata and its Three Patterns" shared at SOFA Meetup#3 on 11 August in Guangzhou, focusing on the background and theoretical foundation of distributed transaction, as well as the principle of Seata distributed transaction and the implementation of distributed transaction in three patterns (AT, TCC, and Saga).</p>
+<p>The video and PPT are at the end of this article.</p>
+<p><img decoding="async" loading="lazy" alt="3 Distributed Transaction Seata Three Modes Explained-Eiyuan.jpg" src="/assets/images/1-59eeb2c64e493e827495e0417125db43.jpeg" width="746" height="420" class="img_ev3q"></p>
+<a name="Ad95d"></a>
+<h2 class="anchor anchorWithStickyNavbar_LWe7" id="i-background-of-the-emergence-of-distributed-transactions">I. Background of the emergence of distributed transactions<a href="#i-background-of-the-emergence-of-distributed-transactions" class="hash-link" aria-label="Direct link to I. Background of the emergence of distributed transactions" title="Direct link to I. Background of the emergence of distributed transactions"></a></h2>
+<a name="Q2ayF"></a>
+<h3 class="anchor anchorWithStickyNavbar_LWe7" id="11-distributed-architecture-evolution---horizontal-splitting-of-database">1.1 Distributed Architecture Evolution - Horizontal Splitting of Database<a href="#11-distributed-architecture-evolution---horizontal-splitting-of-database" class="hash-link" aria-label="Direct link to 1.1 Distributed Architecture Evolution - Horizontal Splitting of Database" title="Direct link to 1.1 Distributed Architecture Evolution - Horizontal Splitting of Dat [...]
+<p>AntGold's business database was initially a single database with a single table, but with the rapid development of the business data scale, the data volume is getting bigger and bigger, and the single database with a single table is gradually becoming a bottleneck. So we split the database horizontally, splitting the original single database and single table into database slices.</p>
+<p>As shown in the figure below, after splitting the database and table, the original write operation that can be completed on a database may be across multiple databases, which gives rise to cross-database transaction problems.</p>
+<p><img decoding="async" loading="lazy" alt="image.png" src="/assets/images/2-e3a8a7b0f1e093d70faf16a548dd6742.png" width="325" height="214" class="img_ev3q"></p>
+<a name="WBQbC"></a>
+<h3 class="anchor anchorWithStickyNavbar_LWe7" id="12-distributed-architecture-evolution---business-service-splitting">1.2 Distributed Architecture Evolution - Business Service Splitting<a href="#12-distributed-architecture-evolution---business-service-splitting" class="hash-link" aria-label="Direct link to 1.2 Distributed Architecture Evolution - Business Service Splitting" title="Direct link to 1.2 Distributed Architecture Evolution - Business Service Splitting"></a></h3>
+<p>In the early stage of business development, the single business system architecture of "one piece of cake" can meet the basic business needs. However, with the rapid development of the business, the system's access and business complexity are growing rapidly, single-system architecture has gradually become the bottleneck of business development, to solve the problem of high coupling and scalability of the business system demand is becoming stronger and stronger.</p>
+<p>As shown in the figure below, Ant Financial Services splits the single business system into multiple business systems in accordance with the design principles of Service Oriented Architecture (SOA), which reduces the coupling between the systems and enables different business systems to focus on their own business, which is more conducive to the development of the business and the scaling of the system capacity.</p>
+<p><img decoding="async" loading="lazy" alt="image.png" src="/assets/images/3-548d85e1cdfbab71650a542d5de5d10a.png" width="557" height="277" class="img_ev3q"></p>
+<p>After the business system is split according to services, a complete business often needs to call multiple services, how to ensure data consistency between multiple services becomes a difficult problem.</p>
+<a name="3oIxE"></a>
+<h2 class="anchor anchorWithStickyNavbar_LWe7" id="ii-theoretical-foundation-of-distributed-transaction">II. Theoretical foundation of distributed transaction<a href="#ii-theoretical-foundation-of-distributed-transaction" class="hash-link" aria-label="Direct link to II. Theoretical foundation of distributed transaction" title="Direct link to II. Theoretical foundation of distributed transaction"></a></h2>
+<a name="akRiW"></a>
+<h3 class="anchor anchorWithStickyNavbar_LWe7" id="21-two-stage-commit-protocols">2.1 Two-stage commit protocols<a href="#21-two-stage-commit-protocols" class="hash-link" aria-label="Direct link to 2.1 Two-stage commit protocols" title="Direct link to 2.1 Two-stage commit protocols"></a></h3>
+<p><img decoding="async" loading="lazy" alt="16_16_18__08_13_2019.jpg" src="/assets/images/4-5933efe8b07271b941670f74b7322a1f.jpeg" width="746" height="419" class="img_ev3q"></p>
+<p>Two phase commit protocol: transaction manager coordinates resource manager in two phases, the first phase prepares resources, that is, reserve the resources needed for the transaction, if every resource manager resource reservation succeeds, the second phase resource commit is performed, otherwise the coordinated resource manager rolls back the resources.</p>
+<a name="8tfKI"></a>
+<h3 class="anchor anchorWithStickyNavbar_LWe7" id="22-tcc">2.2 TCC<a href="#22-tcc" class="hash-link" aria-label="Direct link to 2.2 TCC" title="Direct link to 2.2 TCC"></a></h3>
+<p><img decoding="async" loading="lazy" alt="16_16_51__08_13_2019.jpg" src="/assets/images/5-79c36a571b40ceb0119e48100150675b.jpeg" width="746" height="416" class="img_ev3q"></p>
+<p>TCC (Try-Confirm-Cancel) is actually a two-phase commit protocol for servitisation, business developers need to implement these three service interfaces, the first phase of the service is choreographed by the business code to call the Try interface for resource reservation, the Try interface for all participants is successful, the transaction manager will commit the transaction and call the Confirm interface for each participant The transaction manager will commit the transaction and [...]
+<a name="IXxpF"></a>
+<h3 class="anchor anchorWithStickyNavbar_LWe7" id="23-saga">2.3 Saga<a href="#23-saga" class="hash-link" aria-label="Direct link to 2.3 Saga" title="Direct link to 2.3 Saga"></a></h3>
+<p><img decoding="async" loading="lazy" alt="3 Distributed Transactions Seata Three Patterns Explained - Yi Yuan-9.jpg" src="/assets/images/6-9d33493d97af453a8450f0739fa60a0f.jpeg" width="746" height="420" class="img_ev3q"></p>
+<p>Saga is a compensation protocol. In Saga mode, there are multiple participants within a distributed transaction, and each participant is an offsetting compensation service that requires the user to implement its forward and reverse rollback operations according to the business scenario.</p>
+<p>During the execution of a distributed transaction, the forward operations of each participant are executed sequentially, and if all forward operations are executed successfully, the distributed transaction commits. If any of the forward operations fails, the distributed transaction backs out and performs a reverse rollback on the previous participants, rolling back the committed participants and returning the distributed transaction to its initial state.</p>
+<p>Saga theory is from the paper Sagas published by Hector & Kenneth in 1987.<br>
+<br>Saga Positive Service and Compensation Service also need to be implemented by business developers.</p>
+<a name="fZPaN"></a>
+<h2 class="anchor anchorWithStickyNavbar_LWe7" id="iii-seata-and-its-three-patterns-explained-in-detail">III. Seata and its three patterns explained in detail<a href="#iii-seata-and-its-three-patterns-explained-in-detail" class="hash-link" aria-label="Direct link to III. Seata and its three patterns explained in detail" title="Direct link to III. Seata and its three patterns explained in detail"></a></h2>
+<a name="IgVM7"></a>
+<h3 class="anchor anchorWithStickyNavbar_LWe7" id="31-distributed-transaction-seata-introduction">3.1 Distributed transaction Seata introduction<a href="#31-distributed-transaction-seata-introduction" class="hash-link" aria-label="Direct link to 3.1 Distributed transaction Seata introduction" title="Direct link to 3.1 Distributed transaction Seata introduction"></a></h3>
+<p>Seata (Simple Extensible Autonomous Transaction Architecture) is a distributed transaction solution jointly open-sourced by Ant Financial Services and Alibaba in January 2019.Seata has been open-sourced for about half a year, and currently has more than 11,000 stars. Seata has been open source for about half a year, and now has more than 11,000 stars and a very active community. We warmly welcome you to participate in the Seata community construction, together will Seata become the op [...]
+<p>Seata: <a href="https://github.com/apache/incubator-seata" target="_blank" rel="noopener noreferrer">https://</a>[github.com/apache/incubator-seata](<a href="https://github.com/apache/incubator" target="_blank" rel="noopener noreferrer">https://github.com/apache/incubator</a> -seata)<br>
+<br><img decoding="async" loading="lazy" alt="image.png" src="/assets/images/7-409b712dba10afe30f485ec206d0240f.png" width="584" height="142" class="img_ev3q"></p>
+<a name="zyy0l"></a>
+<h3 class="anchor anchorWithStickyNavbar_LWe7" id="32-distributed-transactions-seata-product-module">3.2 Distributed Transactions Seata Product Module<a href="#32-distributed-transactions-seata-product-module" class="hash-link" aria-label="Direct link to 3.2 Distributed Transactions Seata Product Module" title="Direct link to 3.2 Distributed Transactions Seata Product Module"></a></h3>
+<p>As shown in the figure below, there are three major modules in Seata, namely TM, RM and TC. TM and RM are integrated with the business system as clients of Seata, and TC is deployed independently as the server of Seata.</p>
+<p>TC is deployed independently as a Seata server. <a href="/assets/files/8-1e7e5bd472714f2a5eaf932b449942b2.png" target="_blank">image.png</a></p>
+<p>The execution flow of a distributed transaction in Seata:</p>
+<ul>
+<li>TM opens distributed transaction (TM registers global transaction record with TC);</li>
+<li>According to the business scenario, arrange the resources in the transaction such as database and service (RM reports the resource readiness status to TC);</li>
+<li>TM ends the distributed transaction, and the transaction phase ends (TM notifies TC to commit/rollback the distributed transaction);</li>
+<li>TC aggregates the transaction information and decides whether the distributed transaction should be committed or rolled back;</li>
+<li>TC notifies all RMs to commit/rollback resources, transaction phase 2 ends;</li>
+</ul>
+<a name="1QKqI"></a>
+<h3 class="anchor anchorWithStickyNavbar_LWe7" id="33-distributed-transactions-seata-solution">3.3 Distributed Transactions Seata Solution<a href="#33-distributed-transactions-seata-solution" class="hash-link" aria-label="Direct link to 3.3 Distributed Transactions Seata Solution" title="Direct link to 3.3 Distributed Transactions Seata Solution"></a></h3>
+<p>Seata has four distributed transaction solutions, AT mode, TCC mode, Saga mode and XA mode.</p>
+<p><img decoding="async" loading="lazy" alt="15_49_23__08_13_2019.jpg" src="/assets/images/9-92fbc62876258a48b6778d72eaab6af6.jpeg" width="746" height="385" class="img_ev3q"><br></p>
+<a name="784n4"></a>
+<h4 class="anchor anchorWithStickyNavbar_LWe7" id="231-at-mode">2.3.1 AT Mode<a href="#231-at-mode" class="hash-link" aria-label="Direct link to 2.3.1 AT Mode" title="Direct link to 2.3.1 AT Mode"></a></h4>
+<p>In January, Seata open sourced AT Mode, a non-intrusive distributed transaction solution. In AT mode, users only need to focus on their own "business SQL", the user's "business SQL" as a phase, Seata framework will automatically generate the transaction of the two-phase commit and rollback operations.</p>
+<p><img decoding="async" loading="lazy" alt="image.png" src="/assets/images/10-c19d842e385a2e54cc4b838e11642851.png" width="521" height="238" class="img_ev3q"><br></p>
+<a name="Acfeo"></a>
+<h5 class="anchor anchorWithStickyNavbar_LWe7" id="how-the-at-model-is-non-intrusive-to-business-">How the AT model is non-intrusive to business :<a href="#how-the-at-model-is-non-intrusive-to-business-" class="hash-link" aria-label="Direct link to How the AT model is non-intrusive to business :" title="Direct link to How the AT model is non-intrusive to business :"></a></h5>
+<ul>
+<li>Phase I:</li>
+</ul>
+<p>In phase 1, Seata intercepts the "business SQL", first parses the semantics of the SQL, finds the business data to be updated by the "business SQL", and then saves it as a "before image" before updating the business data. Before the business data is updated, it will save it as "before image", then execute "business SQL" to update the business data, and after the business data is updated, it will save it as "after image", and [...]
+<p>This ensures the atomicity of a phase of operations. <a href="/assets/files/11-b62ee2dfd6ab6e9094d2b51451b41cdd.png" target="_blank">image3.png</a></p>
+<ul>
+<li>Second-phase commit:</li>
+</ul>
+<p>If the second phase is a commit, since the "business SQL" has already been committed to the database in the first phase, the Seata framework only needs to delete the snapshot data and row locks saved in the first phase to complete the data cleanup.</p>
+<p><img decoding="async" loading="lazy" alt="image 4.png" src="/assets/images/12-fb7571a44266fa4692599f2907e93125.png" width="480" height="206" class="img_ev3q"></p>
+<ul>
+<li>Phase 2 rollback:</li>
+</ul>
+<p>If the second phase is a rollback, Seata needs to rollback the "business SQL" that has been executed in the first phase to restore the business data. The way to rollback is to use "before image" to restore the business data; however, before restoring, we must first verify the dirty writing, compare the "current business data in the database" and the "after image", if the two data are not in the same state, then we will use the "after image& [...]
+<p><img decoding="async" loading="lazy" alt="image 5.png" src="/assets/images/13-67b42e8743563de3117194847e4119de.png" width="463" height="317" class="img_ev3q"></p>
+<p>AT mode one phase, two phase commit and rollback are automatically generated by Seata framework, user only need to write "business SQL", then can easily access distributed transaction, AT mode is a kind of distributed transaction solution without any intrusion to business.</p>
+<a name="FnD1S"></a>
+<h4 class="anchor anchorWithStickyNavbar_LWe7" id="232-tcc-mode">2.3.2 TCC Mode<a href="#232-tcc-mode" class="hash-link" aria-label="Direct link to 2.3.2 TCC Mode" title="Direct link to 2.3.2 TCC Mode"></a></h4>
+<p>In March 2019, Seata open-sourced the TCC pattern, which is contributed by Ant Gold. the TCC pattern requires users to implement Try, Confirm and Cancel operations according to their business scenarios; the transaction initiator executes the Try method in the first stage, the Confirm method in the second-stage commit, and the Cancel method in the second-stage rollback.</p>
+<p>The transaction initiator performs Try in the first stage, Confirm in the second stage, and Cancel in the second stage. <a href="/assets/files/14-bd8bfbb4c59f42028ab03a8c409b1c73.png" target="_blank">image 6.png</a></p>
+<p>TCC Three method descriptions:</p>
+<ul>
+<li>Try: detection and reservation of resources;</li>
+<li>Confirm: the execution of the business operation submitted; require Try success Confirm must be successful;</li>
+<li>Cancel: the release of the reserved resources;</li>
+</ul>
+<p><strong>Ant Gold's practical experience in TCC</strong><br>**<br><img decoding="async" loading="lazy" alt="16_48_02__08_13_2019.jpg" src="/assets/images/15-02cfa1203b468d38c80caa594a7644f7.jpeg" width="746" height="414" class="img_ev3q"></p>
+<p><strong>1 TCC Design - Business model is designed in 2 phases:</strong></p>
+<p>The most important thing for users to consider when accessing TCC is how to split their business model into two phases.</p>
+<p>Take the "debit" scenario as an example, before accessing TCC, the debit of account A can be completed with a single SQL for updating the account balance; however, after accessing TCC, the user needs to consider how to split the original one-step debit operation into two phases and implement it into three methods, and to ensure that the first-phase Try will be successful and the second-phase Confirm will be successful if Try is successful. If Try succeeds in the first stage, [...]
+<p><img decoding="async" loading="lazy" alt="image 7.png" src="/assets/images/16-e07ff8c531571c0ef2887d9dc8b4c83f.png" width="588" height="265" class="img_ev3q"></p>
+<p>As shown above, the</p>
+<p>Try method as a one-stage preparation method needs to do resource checking and reservation. In the deduction scenario, what Try has to do is to check whether the account balance is sufficient and reserve funds for transfer, and the way to reserve is to freeze the transfer funds of account A. After the execution of the Try method, although the balance of account A is still 100, but $30 of it has been frozen and cannot be used by other transactions.</p>
+<p>The second stage, the Confirm method, performs the real debit operation; Confirm will use the funds frozen in the Try stage to perform the debit operation; after the Confirm method is executed, the $30 frozen in the first stage has been deducted from account A, and the balance of account A becomes $70.</p>
+<p>If the second stage is a rollback, you need to release the $30 frozen in the first stage of Try in the Cancel method, so that account A is back to the initial state, and all $100 is available.</p>
+<p>The most important thing for users to access TCC mode is to consider how to split the business model into 2 phases, implement it into 3 methods of TCC, and ensure that Try succeeds and Confirm succeeds. Compared to AT mode, TCC mode is somewhat intrusive to the business code, but TCC mode does not have the global line locks of AT mode, and the performance of TCC will be much higher than AT mode.</p>
+<p><strong>2 TCC Design - Allow Null Rollback:</strong><br>**<br><img decoding="async" loading="lazy" alt="16_51_44__08_13_2019.jpg" src="/assets/images/17-b2c8866f3bee9d7eacf27c0e02f0ef68.jpeg" width="746" height="414" class="img_ev3q"></p>
+<p>The Cancel interface needs to be designed to allow null rollbacks. When the Try interface is not received due to packet loss, the transaction manager triggers a rollback, which triggers the Cancel interface, which needs to return to the success of the rollback when it finds that there is no corresponding transaction xid or primary key during the execution of Cancel. If the transaction service manager thinks it has been rolled back, otherwise it will keep retrying, and Cancel has no co [...]
+<p><strong>3 TCC Design - Anti-Suspension Control:</strong><br>**<br><img decoding="async" loading="lazy" alt="16_51_56__08_13_2019.jpg" src="/assets/images/18-3cfd6186d46d6c1cf79f4b5aea91aea0.jpeg" width="746" height="416" class="img_ev3q"></p>
+<p>The implication of the suspension is that the Cancel is executed before the Try interface, which occurs because the Try times out due to network congestion, the transaction manager generates a rollback that triggers the Cancel interface, and the Try interface call is eventually received, but the Cancel arrives before the Try. According to the previous logic of allowing empty rollback, the rollback will return successfully, the transaction manager thinks the transaction has been rolled [...]
+<p><strong>4 TCC Design - Power Control:</strong><br>**<br><img decoding="async" loading="lazy" alt="16_52_07__08_13_2019.jpg" src="/assets/images/19-cbc9396d9760ae9eee6ef163c21e8034.jpeg" width="746" height="415" class="img_ev3q"></p>
+<p>Idempotence means that for the same system, using the same conditions, a single request and repeated multiple requests have the same impact on system resources. Because network jitter or congestion may timeout, transaction manager will retry operation on resources, so it is very likely that a business operation will be called repeatedly, in order not to occupy resources many times because of repeated calls, it is necessary to control idempotency when designing the service, usually we [...]
+<a name="dsMch"></a>
+<h4 class="anchor anchorWithStickyNavbar_LWe7" id="233-saga-patterns">2.3.3 Saga Patterns<a href="#233-saga-patterns" class="hash-link" aria-label="Direct link to 2.3.3 Saga Patterns" title="Direct link to 2.3.3 Saga Patterns"></a></h4>
+<p>Saga mode is Seata's upcoming open source solution for long transactions, which will be mainly contributed by Ant Gold. In Saga mode, there are multiple participants within a distributed transaction, and each participant is an offsetting compensation service that requires users to implement its forward and reverse rollback operations according to business scenarios.</p>
+<p>During the execution of a distributed transaction, the forward operations of each participant are executed sequentially, and if all forward operations are executed successfully, the distributed transaction commits. If any of the forward operations fails, the distributed transaction will go back and execute the reverse rollback operations of the previous participants to roll back the committed participants and bring the distributed transaction back to the initial state.</p>
+<p><img decoding="async" loading="lazy" alt="image 8.png" src="/assets/images/20-7a8ab27e616b4987792c11ff82ac900d.png" width="360" height="359" class="img_ev3q"></p>
+<p>Saga Pattern Distributed transactions are usually event-driven and executed asynchronously between the various participants, Saga Pattern is a long transaction solution.</p>
+<p><strong>1 Saga pattern usage scenario</strong><br>**<br><img decoding="async" loading="lazy" alt="16_44_58__08_13_2019.jpg" src="/assets/images/21-cb2c15b7cda9ba7e3870b03efb42b0f7.jpeg" width="746" height="416" class="img_ev3q"></p>
+<p>Saga pattern is suitable for business systems with long business processes and the need to ensure the final consistency of transactions. Saga pattern commits local transactions at one stage, and performance can be guaranteed in the case of lock-free and long processes.</p>
+<p>Transaction participants may be services from other companies or legacy systems that cannot be transformed and provide the interfaces required by TCC, and can use the Saga pattern.</p>
+<p>The advantages of the Saga pattern are:</p>
+<ul>
+<li>One-stage commit of local database transactions, lock-free, high performance;</li>
+<li>Participants can use transaction-driven asynchronous execution, high throughput;</li>
+<li>The compensation service is the "reverse" of the forward service, which is easy to understand and implement;</li>
+</ul>
+<p>Disadvantages: The Saga pattern does not guarantee isolation because the local database transaction has already been committed in the first phase and no "reservation" action has been performed. Later we will talk about the lack of isolation of the countermeasures. <br><strong>2 Saga implementation based on a state machine engine</strong>* <br><strong>2 Saga implementation based on a state machine engine</strong>* <br>**3</p>
+<p><img decoding="async" loading="lazy" alt="17_13_19__08_13_2019.jpg" src="/assets/images/22-d2bafd9570e63096283bb8cad41a0f43.png" width="1222" height="646" class="img_ev3q"></p>
+<p>Currently there are generally two types of Saga implementations, one is achieved through event-driven architecture, and the other is based on annotations plus interceptors to intercept the business of the positive service implementation.Seata is currently implemented using an event-driven mechanism, Seata implements a state machine, which can orchestrate the call flow of the service and the compensation service of the positive service, generating a state diagram defined by a json file [...]
+<p><strong>3 State Machine Engine Principles</strong><br></p>
+<p><img decoding="async" loading="lazy" alt="16_45_32__08_13_2019.jpg" src="/assets/images/23-1d09ccedb0eb9f45ddda46963f6a9f12.png" width="1240" height="647" class="img_ev3q"></p>
+<p>The basic principle of this state machine engine is that it is based on an event-driven architecture, where each step is executed asynchronously, and steps flow through an event queue between steps, <br>greatly improving system throughput. Transaction logs are recorded at the time of execution of each step for use when rolling back in the event of an exception. Transaction logs are recorded in the database where the business tables are located to improve performance.</p>
+<p>**4 State Machine Engine Design</p>
+<p><img decoding="async" loading="lazy" alt="16_45_46__08_13_2019.jpg" src="/assets/images/24-15fdd730a55833c61ceb860ada0f871b.jpeg" width="746" height="411" class="img_ev3q"></p>
+<p>The state machine engine is divided into a three-tier architecture design, the bottom layer is the "event-driven" layer, the implementation of the EventBus and the consumption of events in the thread pool, is a Pub-Sub architecture. The second layer is the "process controller" layer, which implements a minimalist process engine framework that drives an "empty" process execution. node does, it just executes the process method of each node and then executes [...]
+<p><strong>5 The Saga Service Design Experience</strong></p>
+<p>Similar to TCC, Saga's forward and reverse services need to follow the following design principles:</p>
+<p><strong>1) Saga Service Design - Allow Null Compensation</strong><br>**<br><img decoding="async" loading="lazy" alt="16_52_22__08_13_2019.jpg" src="/assets/images/25-2cae6395619166a3c23e698ac2306f8b.jpeg" width="746" height="415" class="img_ev3q"></p>
+<p><strong>2) Saga Service Design - Anti-Suspension Control</strong><br>**<br><img decoding="async" loading="lazy" alt="16_52_52__08_13_2019.jpg" src="/assets/images/26-ead26d36857d8ae91dbb16ff72873653.jpeg" width="746" height="417" class="img_ev3q"></p>
+<p><strong>3) Saga Service Design - Power Control</strong><br>**<br><img decoding="async" loading="lazy" alt="3 Distributed Transactions Seata Three Patterns Explained - Yi Yuan-31.jpg" src="/assets/images/27-11883ffbfbca7e56a3a5984f3e0c3fe6.jpeg" width="746" height="420" class="img_ev3q"></p>
+<p><strong>4) Saga Design - Custom Transaction Recovery Strategies</strong><br>**<br><img decoding="async" loading="lazy" alt="16_53_07__08_13_2019.jpg" src="/assets/images/28-73c6b9cfb082be166cb84a9381b81c0f.jpeg" width="746" height="414" class="img_ev3q"></p>
+<p>As mentioned earlier, the Saga pattern does not guarantee transaction isolation, and dirty writes can occur in extreme cases. For example, in the case of a distributed transaction is not committed, the data of the previous service was modified, and the service behind the anomaly needs to be rolled back, may not be able to compensate for the operation due to the data of the previous service was modified. One way to deal with this situation is to "retry" and continue forward t [...]
+<p>Since Saga does not guarantee isolation, we need to achieve the principle of "long money rather than short money" in business design. Long money refers to the situation when there is a mistake and the money is too much from our point of view, and the money is too little, because if the money is too long, we can refund the money to the customer, but if it is too short, the money may not be recovered, which means that in the business design, we must give priority to "roll [...]
+<p><strong>6 Annotation and Interceptor Based Saga Implementation</strong><br>**<br><img decoding="async" loading="lazy" alt="17_13_37__08_13_2019.jpg" src="/assets/images/29-3d3a00510ed54a37763e1558f7343789.jpeg" width="746" height="416" class="img_ev3q"></p>
+<p>There is another implementation of Saga that is based on annotations + interceptors, which Seata does not currently implement. You can look at the pseudo-code above to understand it, the @SagaCompensable annotation is defined on the one method, and the compensation method used to define the one method is the compensateOne method. Then the @SagaTransactional annotation is defined on the processA method of the business process code, which starts a Saga distributed transaction, intercept [...]
+<p>**7 Comparison of Advantages and Disadvantages of the Two Saga Implementations</p>
+<p>The following table compares the advantages and disadvantages of the two Saga implementations:</p>
+<p><img decoding="async" loading="lazy" alt="17_13_49__08_13_2019.jpg" src="/assets/images/30-990cbb972417453d06119316c2c1bc7e.jpeg" width="746" height="415" class="img_ev3q"></p>
+<p>The biggest advantage of the state machine engine is that it can be executed asynchronously through an event-driven approach to improve system throughput, service scheduling requirements can be achieved, and in the absence of isolation in the Saga model, there can be an additional "retry forward" strategy to recover from things. The biggest advantage of annotations and interceptors is that they are easy to develop and low cost to learn.</p>
+<a name="Gpkrf"></a>
+<h2 class="anchor anchorWithStickyNavbar_LWe7" id="summary">Summary<a href="#summary" class="hash-link" aria-label="Direct link to Summary" title="Direct link to Summary"></a></h2>
+<p>This article first reviewed the background and theoretical basis of distributed transactions, and then focused on the principles of Seata distributed transactions and three patterns (AT, TCC, Saga) of distributed transaction implementation.</p>
+<p>Seata's positioning is a full-scenario solution for distributed transactions, and in the future there will also be XA mode of distributed transaction implementation, each mode has its own application scenarios, AT mode is a non-intrusive distributed transaction solution for scenes that do not want to transform the business, with almost zero learning cost. TCC mode is a high-performance distributed transaction solution for core systems and other scenes that have a high demand for [...]
+<p>The video review and PPT of this sharing can be viewed at: [<a href="https://tech.antfin.com/community/activities/779/review%5D(" target="_blank" rel="noopener noreferrer">https://tech.antfin.com/community/activities/779/review](</a><a href="https://tech.antfin.com/community/activities/779/" target="_blank" rel="noopener noreferrer">https://tech.antfin.com/community/activities/779/</a> review)</p></div><footer class="row docusaurus-mt-lg"></footer></article><article class="margin-bott [...]
<p>At the beginning of this year, Ali open source a distributed transaction middleware, initially named Fescar, later renamed Seata, in the beginning of its open source, I know it must be fire, because this is an open source project to solve the pain points, Seata began to rush to the business of non-intrusive and high-performance direction to go, which is exactly the solution to the problem of distributed transactions of the urgent needs of us. Because several companies have stayed with [...]
<h1>What are the solutions for distributed transaction resolution?</h1>
<p>Currently distributed transaction solutions mainly have no invasion of business and invasive solutions, no invasive solutions are mainly based on the database XA protocol two-part submission (2PC) scheme, its advantage is no invasion of business code, but its shortcomings are also very obvious: the database must be required to support the XA protocol, and because of the characteristics of the XA protocol itself, it will result in a long period of time without the release of transactio [...]
@@ -823,99 +970,7 @@ dubbo-storage-service.xml</p>
<ul>
<li>seata: <a href="https://github.com/apache/incubator-seata/" target="_blank" rel="noopener noreferrer">https://github.com/apache/incubator-seata/</a></li>
<li>seata-samples : <a href="https://github.com/apache/incubator-seata-samples" target="_blank" rel="noopener noreferrer">https://github.com/apache/incubator-seata-samples</a></li>
-</ul></div><footer class="row docusaurus-mt-lg"></footer></article><article class="margin-bottom--xl" itemprop="blogPost" itemscope="" itemtype="https://schema.org/BlogPosting"><meta itemprop="description" content="Fescar has been released for a while, and distributed transactions have always been a highly focused area in the industry. Fescar received nearly 5000 stars within a month of its release, indicating its popularity. Of course, before Fescar, there were already relatively mature [...]
-<h1>Project Address</h1>
-<p>Fescar: <a href="https://github.com/alibaba/fescar" target="_blank" rel="noopener noreferrer">https://github.com/alibaba/fescar</a></p>
-<p>The code discussed in this blog post is from the 0.1.2-SNAPSHOT version of Fescar. As Fescar evolves, the project structure and module implementations might change significantly.</p>
-<h1>Fescar's TXC Model</h1>
-<p><img decoding="async" loading="lazy" src="/assets/images/c45496461bca15ecd522e497d98ba954f95-4483e7e2aab41db92fd1ee606abf0cf5.jpg" width="764" height="416" class="img_ev3q"></p>
-<p>The above image is an official schematic of the TXC model created by Fescar. The quality of visuals produced by large companies is indeed impressive. From the schematic, we can see the overall implementation of TXC. TXC is implemented through three components, as depicted in the three dark yellow sections in the image, with the following roles:</p>
-<ol>
-<li>TM: Global Transaction Manager, which starts the Fescar distributed transaction on the server side and sends the global transaction to the TC (Transaction Coordinator) for management.</li>
-<li>TC: Transaction Coordinator, which controls the global transaction's commit or rollback. This component requires independent deployment and maintenance, currently only supporting a single-machine version. Future iterations plan to include a clustered version.</li>
-<li>RM: Resource Manager, mainly responsible for reporting branch transactions and managing local transactions.</li>
-</ol>
-<p>A brief description of its implementation process: The initiating service starts a global transaction and registers it with the TC. When calling a cooperating service, the branch transaction of the cooperating service completes the first phase of transaction commit or rollback and generates an undo_log for transaction rollback, then registers the current cooperating service with the TC and reports its transaction status, merging it into the global transaction of the same business. If [...]
-<p>The goal of this blog post is to delve into the code details and explore how its basic ideas are implemented. We will first outline the role of each module from the project's structure, then investigate the entire distributed transaction implementation process using the official examples.</p>
-<h1>Project Structure Analysis</h1>
-<p>After pulling the project and opening it with an IDE, the directory structure is as follows. Let's take a look at the implementation of each module:</p>
-<p><img decoding="async" loading="lazy" src="/assets/images/a88cf147f489f913886ef1785d94183bf09-675292f77733fca39c09b525924847ad.jpg" width="705" height="363" class="img_ev3q"></p>
-<ul>
-<li>common: Common components, providing commonly used utility classes, static variables, extension mechanism class loaders, and defining global exceptions, etc.</li>
-<li>config: Configuration loading and parsing module, providing basic interfaces for configuration. Currently, only file configuration is implemented, with plans for implementations of configuration centers like Nacos.</li>
-<li>core: The core module mainly encapsulating RPC-related content for communication between TM, RM, and TC.</li>
-<li>dubbo: The Dubbo module mainly adapts the Dubbo communication framework, using Dubbo's filter mechanism to pass global transaction information to branches.</li>
-<li>examples: A simple example module that we will explore to understand the implementation.</li>
-<li>rm-datasource: The resource management module, a core module that proxies some JDBC classes to parse SQL, generate rollback logs, and coordinate local transactions. Personally, I think naming this module "core" would be more appropriate.</li>
-<li>server: The TC component, mainly coordinating and managing global transactions, responsible for committing or rolling back global transactions, and maintaining global locks.</li>
-<li>spring: The module integrated with Spring, mainly consisting of AOP logic, serving as the entry point for the entire distributed transaction, and the breakthrough point for studying Fescar.</li>
-<li>tm: The global transaction management module, managing the boundaries of global transactions, and controlling the initiation and rollback points of global transactions.</li>
-</ul>
-<h1>Viewing the Effects through the [examples] Module</h1>
-<p>First, start the TC (Server) module, and start the main method directly. The default server port is 8091.</p>
-<p>Second, go to the examples module and configure the configuration files for the order, business, account, and storage services, mainly the MySQL data source and Zookeeper connection address. Note that the default Dubbo Zookeeper registry dependency is missing, and starting it will throw a class not found exception. Add the following dependency:</p>
-<div class="language-xml codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_biex"><pre tabindex="0" class="prism-code language-xml codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><span class="token-line" style="color:#393A34"><span class="token tag punctuation" style="color:#393A34"><</span><span class="token tag" style="color:#00009f">depe [...]
-<p>Third, place a breakpoint at the simulated exception in BusinessServiceImpl. Start OrderServiceImpl, StorageServiceImpl, AccountServiceImpl, and BusinessServiceImpl services one by one. After hitting the breakpoint, check the account_tbl table in the database; the amount has been reduced by 400 yuan, to 599 yuan. Then, release the breakpoint to trigger the simulated exception in the BusinessServiceImpl module. The global transaction rolls back, and the account_tbl table amount returns [...]
-<p>As shown above, we have experienced the control capability of Fescar transactions. Next, let's look at how it controls transactions in detail.</p>
-<h1>Analysis of Fescar Transaction Process</h1>
-<h2 class="anchor anchorWithStickyNavbar_LWe7" id="first-analyze-the-configuration-file">First, Analyze the Configuration File<a href="#first-analyze-the-configuration-file" class="hash-link" aria-label="Direct link to First, Analyze the Configuration File" title="Direct link to First, Analyze the Configuration File"></a></h2>
-<p>This is a golden rule: to integrate any technology or framework, the configuration file is definitely a breakthrough point. From the above example, we learned that the configuration file in the example module configured an instance of a global transaction scanner, as follows:</p>
-<div class="language-xml codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_biex"><pre tabindex="0" class="prism-code language-xml codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><span class="token-line" style="color:#393A34"><span class="token tag punctuation" style="color:#393A34"><</span><span class="token tag" style="color:#00009f">bean [...]
-<p>This instance scans all instances when the project starts. The specific implementation can be found in the [spring] module, and methods marked with the @GlobalTransactional annotation are woven into the logic of GlobalTransactionalInterceptor's invoke method. When the application starts, instances of TM (TmRpcClient) and RM (RmRpcClient) are initialized, connecting the service with the TC (Transaction Coordinator). Going further involves the TransactionalTemplate class in the TM [...]
-<h2 class="anchor anchorWithStickyNavbar_LWe7" id="tm-module-starts-global-transactions">[TM] Module Starts Global Transactions<a href="#tm-module-starts-global-transactions" class="hash-link" aria-label="Direct link to [TM] Module Starts Global Transactions" title="Direct link to [TM] Module Starts Global Transactions"></a></h2>
-<p>The opening, committing, and rolling back of global transactions are encapsulated in the TransactionalTemplate. The code is as follows:</p>
-<div class="language-java codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_biex"><pre tabindex="0" class="prism-code language-java codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><span class="token-line" style="color:#393A34"><span class="token plain" style="display:inline-block"></span><br></span><span class="token-line" style="color:#393A3 [...]
-<p>The more detailed implementation in the [TM] module is divided into two classes, as follows:</p>
-<p>DefaultGlobalTransaction: Responsible for the specific actions of starting, committing, and rolling back global transactions.</p>
-<p>DefaultTransactionManager: Responsible for using TmRpcClient to send commands to the TC control center, such as starting a global transaction (GlobalBeginRequest), committing (GlobalCommitRequest), rolling back (GlobalRollbackRequest), and querying status (GlobalStatusRequest).</p>
-<p>The above are the core contents of the TM module. After the TM module completes the global transaction start, we then look at how the global transaction ID, xid, is passed and how the RM component intervenes.</p>
-<h2 class="anchor anchorWithStickyNavbar_LWe7" id="passing-global-transaction-xid-with-dubbo">Passing Global Transaction xid with [dubbo]<a href="#passing-global-transaction-xid-with-dubbo" class="hash-link" aria-label="Direct link to Passing Global Transaction xid with [dubbo]" title="Direct link to Passing Global Transaction xid with [dubbo]"></a></h2>
-<p>First is the transmission of xid. Currently, the transmission in a microservice architecture implemented with the Dubbo framework has been realized. It is also easy to implement for others like Spring Cloud and Motan. By using the filter mechanism that general RPC communication frameworks have, xid is passed from the initiating node of the global transaction to the service's subordinate nodes. After being received by the subordinate nodes, it is bound to the current thread contex [...]
-<div class="language-java codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_biex"><pre tabindex="0" class="prism-code language-java codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><span class="token-line" style="color:#393A34"><span class="token annotation punctuation" style="color:#393A34">@Activate</span><span class="token punctuation" styl [...]
-<p>When rpcXid is not null, it is added to the ContextCore of RootContext. Let's delve into this a bit. ContextCore is an extensible interface, and the default implementation is ThreadLocalContextCore, which maintains the current xid based on ThreadLocal. Fescar provides an extensible mechanism implemented in the [common] module. Through a custom class loader, EnhancedServiceLoader, it loads the service classes that need to be extended. By adding the @LoadLevel annotation with a hig [...]
-<h2 class="anchor anchorWithStickyNavbar_LWe7" id="intervention-of-local-resource-management-in-the-rm-module">Intervention of Local Resource Management in the [RM] Module<a href="#intervention-of-local-resource-management-in-the-rm-module" class="hash-link" aria-label="Direct link to Intervention of Local Resource Management in the [RM] Module" title="Direct link to Intervention of Local Resource Management in the [RM] Module"></a></h2>
-<p>Fescar implements proxy classes for local transaction-related interfaces through a proxy mechanism, such as DataSourceProxy, ConnectionProxy, and StatementProxy. This can be seen in the configuration file, indicating that to use Fescar distributed transactions, the proxy data source provided by Fescar must be configured. For example:</p>
-<p><img decoding="async" loading="lazy" src="/assets/images/af317255c71a5c1bf46f7140387acf365f8-89383a2f18f6ee0c38517552ef7c838b.jpg" width="960" height="382" class="img_ev3q"></p>
-<p>After configuring the proxy data source, starting from DataSourceProxy, we can freely control all local operations on the database. From the xid transmission above, we know that the xid is saved in RootContext. Now, look at the following code to see it clearly:</p>
-<p>First, look at a piece of code from StatementProxy:</p>
-<p><img decoding="async" loading="lazy" src="/assets/images/17896deea47b9aee518812b039c39101d8f-17aee47c7b0181e494847cd605377176.jpg" width="916" height="512" class="img_ev3q"></p>
-<p>Then, look at the code in ExecuteTemplate:</p>
-<p><img decoding="async" loading="lazy" src="/assets/images/04488a2745a5d564498462ed64c506174d2-f982f1865728c70f4e9dc802a6f70c54.jpg" width="960" height="625" class="img_ev3q"></p>
-<p>Similar to the transaction management template class TransactionalTemplate in the [TM] module, the crucial logic proxy here is encapsulated in the ExecuteTemplate template class. By overriding Statement with StatementProxy implementation, the execute logic of ExecuteTemplate is called when the original JDBC executeUpdate method is executed. Before the SQL is actually executed, it checks whether the current context in RootContext contains xid, i.e., whether it is a global distributed t [...]
-<p><img decoding="async" loading="lazy" src="/assets/images/bb9a2f07054f19bc21adc332671de4f7b75-0b10f570ec26e2246b4d02e607fb42f9.jpg" width="945" height="419" class="img_ev3q"></p>
-<h3 class="anchor anchorWithStickyNavbar_LWe7" id="plainexecutor">PlainExecutor:<a href="#plainexecutor" class="hash-link" aria-label="Direct link to PlainExecutor:" title="Direct link to PlainExecutor:"></a></h3>
-<p>The native JDBC interface implementation, without any processing, is used for ordinary select queries in global transactions.</p>
-<h3 class="anchor anchorWithStickyNavbar_LWe7" id="updateexecutor-deleteexecutor-insertexecutor">UpdateExecutor, DeleteExecutor, InsertExecutor:<a href="#updateexecutor-deleteexecutor-insertexecutor" class="hash-link" aria-label="Direct link to UpdateExecutor, DeleteExecutor, InsertExecutor:" title="Direct link to UpdateExecutor, DeleteExecutor, InsertExecutor:"></a></h3>
-<p>The three DML (Data Manipulation Language) executors for updating, deleting, and inserting, mainly analyze the SQL statements before and after execution and implement the following two abstract interface methods:</p>
-<div class="language-java codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_biex"><pre tabindex="0" class="prism-code language-java codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><span class="token-line" style="color:#393A34"><span class="token keyword" style="color:#00009f">protected</span><span class="token plain"> </span><span class="toke [...]
-<p>During this process, the undo_log for rollback operation is generated by analyzing the SQL, and the log is currently saved in MySQL, sharing the same transaction with the business SQL operation. The table structure is as follows:</p>
-<p><img decoding="async" loading="lazy" src="/assets/images/fd5c423815d3b84bdbc70d7efeb9cd16757-8fed493519894148d20b0102af49138a.jpg" width="731" height="332" class="img_ev3q"></p>
-<p>The rollback_info column contains the detailed information of the undo_log, which is of type longblob. The structure is as follows:</p>
-<div class="language-json codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_biex"><pre tabindex="0" class="prism-code language-json codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><span class="token-line" style="color:#393A34"><span class="token plain">{</span><br></span><span class="token-line" style="color:#393A34"><span class="token plain" [...]
-<p>Here is an example of an update operation. The undo_log records very detailed information. It associates the branch ID with the global transaction xid, records the table name, the operation field names, and the records before and after the SQL execution. For instance, this record shows table name = storage_tbl, before SQL execution ID = 10, count = 100, after SQL execution ID = 10, count = 98. If the entire global transaction fails and needs to be rolled back, it can generate the foll [...]
-<div class="language-sql codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_biex"><pre tabindex="0" class="prism-code language-sql codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><span class="token-line" style="color:#393A34"><span class="token keyword" style="color:#00009f">update</span><span class="token plain"> storage_tbl </span><span clas [...]
-<h3 class="anchor anchorWithStickyNavbar_LWe7" id="selectforupdateexecutor">SelectForUpdateExecutor:<a href="#selectforupdateexecutor" class="hash-link" aria-label="Direct link to SelectForUpdateExecutor:" title="Direct link to SelectForUpdateExecutor:"></a></h3>
-<p>In Fescar's AT mode, the default isolation level above the local transaction is read uncommitted. However, through the SelectForUpdateExecutor, it can support the read committed isolation level. The code is as follows:</p>
-<div class="language-java codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_biex"><pre tabindex="0" class="prism-code language-java codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><span class="token-line" style="color:#393A34"><span class="token annotation punctuation" style="color:#393A34">@Override</span><span class="token plain"></span><br [...]
-<p>The key code is as follows:</p>
-<div class="language-java codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_biex"><pre tabindex="0" class="prism-code language-java codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><span class="token-line" style="color:#393A34"><span class="token class-name">TableRecords</span><span class="token plain"> selectPKRows </span><span class="token o [...]
-<p>By operating on the selectPKRows table records, lockKeys are obtained, and then it checks with the TC controller to see if they are globally locked. If they are locked, it retries until the lock is released and then returns the query result.</p>
-<h2 class="anchor anchorWithStickyNavbar_LWe7" id="registration-and-reporting-of-branch-transactions">Registration and Reporting of Branch Transactions<a href="#registration-and-reporting-of-branch-transactions" class="hash-link" aria-label="Direct link to Registration and Reporting of Branch Transactions" title="Direct link to Registration and Reporting of Branch Transactions"></a></h2>
-<p>Before the local transaction is committed, Fescar registers and reports information related to the branch transaction. This can be seen in the commit part of the ConnectionProxy class code:</p>
-<div class="language-java codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_biex"><pre tabindex="0" class="prism-code language-java codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><span class="token-line" style="color:#393A34"><span class="token annotation punctuation" style="color:#393A34">@Override</span><span class="token plain"></span><br [...]
-<p>From this code, we can see that it first checks whether it is a global transaction. If it is not, it commits directly. If it is, it first registers the branch transaction with the TC controller. For write isolation, it involves obtaining global locks on the TC side. Then, it saves the undo_log used for rollback operations and finally commits the local transaction. Lastly, it reports the transaction status to the TC controller. At this point, the first phase of the local transaction is [...]
-<h2 class="anchor anchorWithStickyNavbar_LWe7" id="coordinating-the-global-transaction-with-the-server-module">Coordinating the Global Transaction with the [server] Module<a href="#coordinating-the-global-transaction-with-the-server-module" class="hash-link" aria-label="Direct link to Coordinating the Global Transaction with the [server] Module" title="Direct link to Coordinating the Global Transaction with the [server] Module"></a></h2>
-<p>For the server module, we can focus on the DefaultCoordinator class. This is the default implementation of the AbstractTCInboundHandler controller handler. It mainly implements interfaces for starting, committing, rolling back, querying the status of global transactions, registering branch transactions, reporting, and checking locks, such as:</p>
-<p><img decoding="async" loading="lazy" src="/assets/images/3da6fd82debb9470eb4a5feb1eecac6d6a2-b042b32322c41b9cbe7563f9ccfdcf87.jpg" width="756" height="426" class="img_ev3q"></p>
-<p>Returning to the TransactionalTemplate at the beginning, if the entire distributed transaction fails and needs to be rolled back, TM first initiates a rollback instruction to TC. After TC receives it and parses the request, it is routed to the doGlobalRollback method of the default controller class. The code executed on the TC controller side is as follows:</p>
-<div class="language-java codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_biex"><pre tabindex="0" class="prism-code language-java codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><span class="token-line" style="color:#393A34"><span class="token annotation punctuation" style="color:#393A34">@Override</span><span class="token plain"></span><br [...]
-<p>As seen from the above code, during rollback, each branch transaction is iterated from the global transaction session, and then each branch transaction is notified to rollback. When the branch service receives the request, it is first routed to the doBranchRollback method in RMHandlerAT, and then the branchRollback method in RM is called. The code is as follows:</p>
-<div class="language-java codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_biex"><pre tabindex="0" class="prism-code language-java codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><span class="token-line" style="color:#393A34"><span class="token annotation punctuation" style="color:#393A34">@Override</span><span class="token plain"></span><br [...]
-<p>On the RM branch transaction side, the UndoLogManager's undo method is ultimately executed. It retrieves the rollback log from the database using xid and branchId to complete the data rollback operation. The entire process is completed synchronously. If the global transaction is successful, TC will have a similar coordination process as mentioned above, but it will be asynchronous, clearing the undo_log related to the global transaction. At this point, the two-phase commit or rol [...]
-<h1>Conclusion</h1>
-<p>If you've made it this far, thank you very much for patiently taking the time to learn amidst your busy schedule. I believe the time spent was worthwhile. By thoroughly reading and understanding this article, you likely have a comprehensive understanding of the main flow of Fescar's implementation. This article took approximately one person-day from conception to completion. During this process, I also gained a deeper understanding of Fescar's implementation. Due to spa [...]
-<h3 class="anchor anchorWithStickyNavbar_LWe7" id="about-the-author">About the Author:<a href="#about-the-author" class="hash-link" aria-label="Direct link to About the Author:" title="Direct link to About the Author:"></a></h3>
-<p>Chen Kailing joined Kaijing Technology in May 2016. Formerly a senior developer and project manager, currently the head of the Architecture & Operations Department of Kaijing Technology's R&D Center. PMP project management certification, Alibaba Cloud MVP. Enthusiastic about open source, having open-sourced several popular projects. Passionate about sharing technical insights, and author of the independent blog KL Blog (<a href="http://www.kailing.pub/" target="_blank" re [...]
+</ul></div><footer class="row docusaurus-mt-lg"></footer></article><nav class="pagination-nav" aria-label="Blog list page navigation"><a class="pagination-nav__link pagination-nav__link--prev" href="/blog/page/5"><div class="pagination-nav__label">Newer Entries</div></a><a class="pagination-nav__link pagination-nav__link--next" href="/blog/page/7"><div class="pagination-nav__label">Older Entries</div></a></nav></main></div></div></div><footer class="footer"><div class="container containe [...]
<div class="fs-12">
<div class="center-div">
<span>Apache Seata (incubating) is an effort undergoing incubation at The Apache Software Foundation (ASF), sponsored by the Apache Incubator. Incubation is required of all newly accepted projects until a further review indicates that the infrastructure, communications, and decision making process have stabilized in a manner consistent with other successful ASF projects. While incubation status is not necessarily a reflection of the completeness or stability of the [...]
diff --git a/blog/page/7/index.html b/blog/page/7/index.html
index 6b49029bb2e..a48e6a12138 100644
--- a/blog/page/7/index.html
+++ b/blog/page/7/index.html
@@ -11,11 +11,103 @@
<meta name="aes-config" content="pid=xux-opensource&user_type=101&uid=&username=&dim10=seata"><link rel="stylesheet" href="/assets/css/styles.9644caf2.css">
-<script src="/assets/js/runtime~main.bf98ee01.js" defer="defer"></script>
-<script src="/assets/js/main.8371dd70.js" defer="defer"></script>
+<script src="/assets/js/runtime~main.762ed5c0.js" defer="defer"></script>
+<script src="/assets/js/main.aeea7339.js" defer="defer"></script>
</head>
<body class="navigation-with-keyboard">
-<script>!function(){function t(t){document.documentElement.setAttribute("data-theme",t)}var e=function(){try{return new URLSearchParams(window.location.search).get("docusaurus-theme")}catch(t){}}()||function(){try{return localStorage.getItem("theme")}catch(t){}}();t(null!==e?e:"light")}(),function(){try{const c=new URLSearchParams(window.location.search).entries();for(var[t,e]of c)if(t.startsWith("docusaurus-data-")){var a=t.replace("docusaurus-data-","data-");document.documentElement.se [...]
+<script>!function(){function t(t){document.documentElement.setAttribute("data-theme",t)}var e=function(){try{return new URLSearchParams(window.location.search).get("docusaurus-theme")}catch(t){}}()||function(){try{return localStorage.getItem("theme")}catch(t){}}();t(null!==e?e:"light")}(),function(){try{const c=new URLSearchParams(window.location.search).entries();for(var[t,e]of c)if(t.startsWith("docusaurus-data-")){var a=t.replace("docusaurus-data-","data-");document.documentElement.se [...]
+<h1>Project Address</h1>
+<p>Fescar: <a href="https://github.com/alibaba/fescar" target="_blank" rel="noopener noreferrer">https://github.com/alibaba/fescar</a></p>
+<p>The code discussed in this blog post is from the 0.1.2-SNAPSHOT version of Fescar. As Fescar evolves, the project structure and module implementations might change significantly.</p>
+<h1>Fescar's TXC Model</h1>
+<p><img decoding="async" loading="lazy" src="/assets/images/c45496461bca15ecd522e497d98ba954f95-4483e7e2aab41db92fd1ee606abf0cf5.jpg" width="764" height="416" class="img_ev3q"></p>
+<p>The above image is an official schematic of the TXC model created by Fescar. The quality of visuals produced by large companies is indeed impressive. From the schematic, we can see the overall implementation of TXC. TXC is implemented through three components, as depicted in the three dark yellow sections in the image, with the following roles:</p>
+<ol>
+<li>TM: Global Transaction Manager, which starts the Fescar distributed transaction on the server side and sends the global transaction to the TC (Transaction Coordinator) for management.</li>
+<li>TC: Transaction Coordinator, which controls the global transaction's commit or rollback. This component requires independent deployment and maintenance, currently only supporting a single-machine version. Future iterations plan to include a clustered version.</li>
+<li>RM: Resource Manager, mainly responsible for reporting branch transactions and managing local transactions.</li>
+</ol>
+<p>A brief description of its implementation process: The initiating service starts a global transaction and registers it with the TC. When calling a cooperating service, the branch transaction of the cooperating service completes the first phase of transaction commit or rollback and generates an undo_log for transaction rollback, then registers the current cooperating service with the TC and reports its transaction status, merging it into the global transaction of the same business. If [...]
+<p>The goal of this blog post is to delve into the code details and explore how its basic ideas are implemented. We will first outline the role of each module from the project's structure, then investigate the entire distributed transaction implementation process using the official examples.</p>
+<h1>Project Structure Analysis</h1>
+<p>After pulling the project and opening it with an IDE, the directory structure is as follows. Let's take a look at the implementation of each module:</p>
+<p><img decoding="async" loading="lazy" src="/assets/images/a88cf147f489f913886ef1785d94183bf09-675292f77733fca39c09b525924847ad.jpg" width="705" height="363" class="img_ev3q"></p>
+<ul>
+<li>common: Common components, providing commonly used utility classes, static variables, extension mechanism class loaders, and defining global exceptions, etc.</li>
+<li>config: Configuration loading and parsing module, providing basic interfaces for configuration. Currently, only file configuration is implemented, with plans for implementations of configuration centers like Nacos.</li>
+<li>core: The core module mainly encapsulating RPC-related content for communication between TM, RM, and TC.</li>
+<li>dubbo: The Dubbo module mainly adapts the Dubbo communication framework, using Dubbo's filter mechanism to pass global transaction information to branches.</li>
+<li>examples: A simple example module that we will explore to understand the implementation.</li>
+<li>rm-datasource: The resource management module, a core module that proxies some JDBC classes to parse SQL, generate rollback logs, and coordinate local transactions. Personally, I think naming this module "core" would be more appropriate.</li>
+<li>server: The TC component, mainly coordinating and managing global transactions, responsible for committing or rolling back global transactions, and maintaining global locks.</li>
+<li>spring: The module integrated with Spring, mainly consisting of AOP logic, serving as the entry point for the entire distributed transaction, and the breakthrough point for studying Fescar.</li>
+<li>tm: The global transaction management module, managing the boundaries of global transactions, and controlling the initiation and rollback points of global transactions.</li>
+</ul>
+<h1>Viewing the Effects through the [examples] Module</h1>
+<p>First, start the TC (Server) module, and start the main method directly. The default server port is 8091.</p>
+<p>Second, go to the examples module and configure the configuration files for the order, business, account, and storage services, mainly the MySQL data source and Zookeeper connection address. Note that the default Dubbo Zookeeper registry dependency is missing, and starting it will throw a class not found exception. Add the following dependency:</p>
+<div class="language-xml codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_biex"><pre tabindex="0" class="prism-code language-xml codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><span class="token-line" style="color:#393A34"><span class="token tag punctuation" style="color:#393A34"><</span><span class="token tag" style="color:#00009f">depe [...]
+<p>Third, place a breakpoint at the simulated exception in BusinessServiceImpl. Start OrderServiceImpl, StorageServiceImpl, AccountServiceImpl, and BusinessServiceImpl services one by one. After hitting the breakpoint, check the account_tbl table in the database; the amount has been reduced by 400 yuan, to 599 yuan. Then, release the breakpoint to trigger the simulated exception in the BusinessServiceImpl module. The global transaction rolls back, and the account_tbl table amount returns [...]
+<p>As shown above, we have experienced the control capability of Fescar transactions. Next, let's look at how it controls transactions in detail.</p>
+<h1>Analysis of Fescar Transaction Process</h1>
+<h2 class="anchor anchorWithStickyNavbar_LWe7" id="first-analyze-the-configuration-file">First, Analyze the Configuration File<a href="#first-analyze-the-configuration-file" class="hash-link" aria-label="Direct link to First, Analyze the Configuration File" title="Direct link to First, Analyze the Configuration File"></a></h2>
+<p>This is a golden rule: to integrate any technology or framework, the configuration file is definitely a breakthrough point. From the above example, we learned that the configuration file in the example module configured an instance of a global transaction scanner, as follows:</p>
+<div class="language-xml codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_biex"><pre tabindex="0" class="prism-code language-xml codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><span class="token-line" style="color:#393A34"><span class="token tag punctuation" style="color:#393A34"><</span><span class="token tag" style="color:#00009f">bean [...]
+<p>This instance scans all instances when the project starts. The specific implementation can be found in the [spring] module, and methods marked with the @GlobalTransactional annotation are woven into the logic of GlobalTransactionalInterceptor's invoke method. When the application starts, instances of TM (TmRpcClient) and RM (RmRpcClient) are initialized, connecting the service with the TC (Transaction Coordinator). Going further involves the TransactionalTemplate class in the TM [...]
+<h2 class="anchor anchorWithStickyNavbar_LWe7" id="tm-module-starts-global-transactions">[TM] Module Starts Global Transactions<a href="#tm-module-starts-global-transactions" class="hash-link" aria-label="Direct link to [TM] Module Starts Global Transactions" title="Direct link to [TM] Module Starts Global Transactions"></a></h2>
+<p>The opening, committing, and rolling back of global transactions are encapsulated in the TransactionalTemplate. The code is as follows:</p>
+<div class="language-java codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_biex"><pre tabindex="0" class="prism-code language-java codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><span class="token-line" style="color:#393A34"><span class="token plain" style="display:inline-block"></span><br></span><span class="token-line" style="color:#393A3 [...]
+<p>The more detailed implementation in the [TM] module is divided into two classes, as follows:</p>
+<p>DefaultGlobalTransaction: Responsible for the specific actions of starting, committing, and rolling back global transactions.</p>
+<p>DefaultTransactionManager: Responsible for using TmRpcClient to send commands to the TC control center, such as starting a global transaction (GlobalBeginRequest), committing (GlobalCommitRequest), rolling back (GlobalRollbackRequest), and querying status (GlobalStatusRequest).</p>
+<p>The above are the core contents of the TM module. After the TM module completes the global transaction start, we then look at how the global transaction ID, xid, is passed and how the RM component intervenes.</p>
+<h2 class="anchor anchorWithStickyNavbar_LWe7" id="passing-global-transaction-xid-with-dubbo">Passing Global Transaction xid with [dubbo]<a href="#passing-global-transaction-xid-with-dubbo" class="hash-link" aria-label="Direct link to Passing Global Transaction xid with [dubbo]" title="Direct link to Passing Global Transaction xid with [dubbo]"></a></h2>
+<p>First is the transmission of xid. Currently, the transmission in a microservice architecture implemented with the Dubbo framework has been realized. It is also easy to implement for others like Spring Cloud and Motan. By using the filter mechanism that general RPC communication frameworks have, xid is passed from the initiating node of the global transaction to the service's subordinate nodes. After being received by the subordinate nodes, it is bound to the current thread contex [...]
+<div class="language-java codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_biex"><pre tabindex="0" class="prism-code language-java codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><span class="token-line" style="color:#393A34"><span class="token annotation punctuation" style="color:#393A34">@Activate</span><span class="token punctuation" styl [...]
+<p>When rpcXid is not null, it is added to the ContextCore of RootContext. Let's delve into this a bit. ContextCore is an extensible interface, and the default implementation is ThreadLocalContextCore, which maintains the current xid based on ThreadLocal. Fescar provides an extensible mechanism implemented in the [common] module. Through a custom class loader, EnhancedServiceLoader, it loads the service classes that need to be extended. By adding the @LoadLevel annotation with a hig [...]
+<h2 class="anchor anchorWithStickyNavbar_LWe7" id="intervention-of-local-resource-management-in-the-rm-module">Intervention of Local Resource Management in the [RM] Module<a href="#intervention-of-local-resource-management-in-the-rm-module" class="hash-link" aria-label="Direct link to Intervention of Local Resource Management in the [RM] Module" title="Direct link to Intervention of Local Resource Management in the [RM] Module"></a></h2>
+<p>Fescar implements proxy classes for local transaction-related interfaces through a proxy mechanism, such as DataSourceProxy, ConnectionProxy, and StatementProxy. This can be seen in the configuration file, indicating that to use Fescar distributed transactions, the proxy data source provided by Fescar must be configured. For example:</p>
+<p><img decoding="async" loading="lazy" src="/assets/images/af317255c71a5c1bf46f7140387acf365f8-89383a2f18f6ee0c38517552ef7c838b.jpg" width="960" height="382" class="img_ev3q"></p>
+<p>After configuring the proxy data source, starting from DataSourceProxy, we can freely control all local operations on the database. From the xid transmission above, we know that the xid is saved in RootContext. Now, look at the following code to see it clearly:</p>
+<p>First, look at a piece of code from StatementProxy:</p>
+<p><img decoding="async" loading="lazy" src="/assets/images/17896deea47b9aee518812b039c39101d8f-17aee47c7b0181e494847cd605377176.jpg" width="916" height="512" class="img_ev3q"></p>
+<p>Then, look at the code in ExecuteTemplate:</p>
+<p><img decoding="async" loading="lazy" src="/assets/images/04488a2745a5d564498462ed64c506174d2-f982f1865728c70f4e9dc802a6f70c54.jpg" width="960" height="625" class="img_ev3q"></p>
+<p>Similar to the transaction management template class TransactionalTemplate in the [TM] module, the crucial logic proxy here is encapsulated in the ExecuteTemplate template class. By overriding Statement with StatementProxy implementation, the execute logic of ExecuteTemplate is called when the original JDBC executeUpdate method is executed. Before the SQL is actually executed, it checks whether the current context in RootContext contains xid, i.e., whether it is a global distributed t [...]
+<p><img decoding="async" loading="lazy" src="/assets/images/bb9a2f07054f19bc21adc332671de4f7b75-0b10f570ec26e2246b4d02e607fb42f9.jpg" width="945" height="419" class="img_ev3q"></p>
+<h3 class="anchor anchorWithStickyNavbar_LWe7" id="plainexecutor">PlainExecutor:<a href="#plainexecutor" class="hash-link" aria-label="Direct link to PlainExecutor:" title="Direct link to PlainExecutor:"></a></h3>
+<p>The native JDBC interface implementation, without any processing, is used for ordinary select queries in global transactions.</p>
+<h3 class="anchor anchorWithStickyNavbar_LWe7" id="updateexecutor-deleteexecutor-insertexecutor">UpdateExecutor, DeleteExecutor, InsertExecutor:<a href="#updateexecutor-deleteexecutor-insertexecutor" class="hash-link" aria-label="Direct link to UpdateExecutor, DeleteExecutor, InsertExecutor:" title="Direct link to UpdateExecutor, DeleteExecutor, InsertExecutor:"></a></h3>
+<p>The three DML (Data Manipulation Language) executors for updating, deleting, and inserting, mainly analyze the SQL statements before and after execution and implement the following two abstract interface methods:</p>
+<div class="language-java codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_biex"><pre tabindex="0" class="prism-code language-java codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><span class="token-line" style="color:#393A34"><span class="token keyword" style="color:#00009f">protected</span><span class="token plain"> </span><span class="toke [...]
+<p>During this process, the undo_log for rollback operation is generated by analyzing the SQL, and the log is currently saved in MySQL, sharing the same transaction with the business SQL operation. The table structure is as follows:</p>
+<p><img decoding="async" loading="lazy" src="/assets/images/fd5c423815d3b84bdbc70d7efeb9cd16757-8fed493519894148d20b0102af49138a.jpg" width="731" height="332" class="img_ev3q"></p>
+<p>The rollback_info column contains the detailed information of the undo_log, which is of type longblob. The structure is as follows:</p>
+<div class="language-json codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_biex"><pre tabindex="0" class="prism-code language-json codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><span class="token-line" style="color:#393A34"><span class="token plain">{</span><br></span><span class="token-line" style="color:#393A34"><span class="token plain" [...]
+<p>Here is an example of an update operation. The undo_log records very detailed information. It associates the branch ID with the global transaction xid, records the table name, the operation field names, and the records before and after the SQL execution. For instance, this record shows table name = storage_tbl, before SQL execution ID = 10, count = 100, after SQL execution ID = 10, count = 98. If the entire global transaction fails and needs to be rolled back, it can generate the foll [...]
+<div class="language-sql codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_biex"><pre tabindex="0" class="prism-code language-sql codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><span class="token-line" style="color:#393A34"><span class="token keyword" style="color:#00009f">update</span><span class="token plain"> storage_tbl </span><span clas [...]
+<h3 class="anchor anchorWithStickyNavbar_LWe7" id="selectforupdateexecutor">SelectForUpdateExecutor:<a href="#selectforupdateexecutor" class="hash-link" aria-label="Direct link to SelectForUpdateExecutor:" title="Direct link to SelectForUpdateExecutor:"></a></h3>
+<p>In Fescar's AT mode, the default isolation level above the local transaction is read uncommitted. However, through the SelectForUpdateExecutor, it can support the read committed isolation level. The code is as follows:</p>
+<div class="language-java codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_biex"><pre tabindex="0" class="prism-code language-java codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><span class="token-line" style="color:#393A34"><span class="token annotation punctuation" style="color:#393A34">@Override</span><span class="token plain"></span><br [...]
+<p>The key code is as follows:</p>
+<div class="language-java codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_biex"><pre tabindex="0" class="prism-code language-java codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><span class="token-line" style="color:#393A34"><span class="token class-name">TableRecords</span><span class="token plain"> selectPKRows </span><span class="token o [...]
+<p>By operating on the selectPKRows table records, lockKeys are obtained, and then it checks with the TC controller to see if they are globally locked. If they are locked, it retries until the lock is released and then returns the query result.</p>
+<h2 class="anchor anchorWithStickyNavbar_LWe7" id="registration-and-reporting-of-branch-transactions">Registration and Reporting of Branch Transactions<a href="#registration-and-reporting-of-branch-transactions" class="hash-link" aria-label="Direct link to Registration and Reporting of Branch Transactions" title="Direct link to Registration and Reporting of Branch Transactions"></a></h2>
+<p>Before the local transaction is committed, Fescar registers and reports information related to the branch transaction. This can be seen in the commit part of the ConnectionProxy class code:</p>
+<div class="language-java codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_biex"><pre tabindex="0" class="prism-code language-java codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><span class="token-line" style="color:#393A34"><span class="token annotation punctuation" style="color:#393A34">@Override</span><span class="token plain"></span><br [...]
+<p>From this code, we can see that it first checks whether it is a global transaction. If it is not, it commits directly. If it is, it first registers the branch transaction with the TC controller. For write isolation, it involves obtaining global locks on the TC side. Then, it saves the undo_log used for rollback operations and finally commits the local transaction. Lastly, it reports the transaction status to the TC controller. At this point, the first phase of the local transaction is [...]
+<h2 class="anchor anchorWithStickyNavbar_LWe7" id="coordinating-the-global-transaction-with-the-server-module">Coordinating the Global Transaction with the [server] Module<a href="#coordinating-the-global-transaction-with-the-server-module" class="hash-link" aria-label="Direct link to Coordinating the Global Transaction with the [server] Module" title="Direct link to Coordinating the Global Transaction with the [server] Module"></a></h2>
+<p>For the server module, we can focus on the DefaultCoordinator class. This is the default implementation of the AbstractTCInboundHandler controller handler. It mainly implements interfaces for starting, committing, rolling back, querying the status of global transactions, registering branch transactions, reporting, and checking locks, such as:</p>
+<p><img decoding="async" loading="lazy" src="/assets/images/3da6fd82debb9470eb4a5feb1eecac6d6a2-b042b32322c41b9cbe7563f9ccfdcf87.jpg" width="756" height="426" class="img_ev3q"></p>
+<p>Returning to the TransactionalTemplate at the beginning, if the entire distributed transaction fails and needs to be rolled back, TM first initiates a rollback instruction to TC. After TC receives it and parses the request, it is routed to the doGlobalRollback method of the default controller class. The code executed on the TC controller side is as follows:</p>
+<div class="language-java codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_biex"><pre tabindex="0" class="prism-code language-java codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><span class="token-line" style="color:#393A34"><span class="token annotation punctuation" style="color:#393A34">@Override</span><span class="token plain"></span><br [...]
+<p>As seen from the above code, during rollback, each branch transaction is iterated from the global transaction session, and then each branch transaction is notified to rollback. When the branch service receives the request, it is first routed to the doBranchRollback method in RMHandlerAT, and then the branchRollback method in RM is called. The code is as follows:</p>
+<div class="language-java codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_biex"><pre tabindex="0" class="prism-code language-java codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><span class="token-line" style="color:#393A34"><span class="token annotation punctuation" style="color:#393A34">@Override</span><span class="token plain"></span><br [...]
+<p>On the RM branch transaction side, the UndoLogManager's undo method is ultimately executed. It retrieves the rollback log from the database using xid and branchId to complete the data rollback operation. The entire process is completed synchronously. If the global transaction is successful, TC will have a similar coordination process as mentioned above, but it will be asynchronous, clearing the undo_log related to the global transaction. At this point, the two-phase commit or rol [...]
+<h1>Conclusion</h1>
+<p>If you've made it this far, thank you very much for patiently taking the time to learn amidst your busy schedule. I believe the time spent was worthwhile. By thoroughly reading and understanding this article, you likely have a comprehensive understanding of the main flow of Fescar's implementation. This article took approximately one person-day from conception to completion. During this process, I also gained a deeper understanding of Fescar's implementation. Due to spa [...]
+<h3 class="anchor anchorWithStickyNavbar_LWe7" id="about-the-author">About the Author:<a href="#about-the-author" class="hash-link" aria-label="Direct link to About the Author:" title="Direct link to About the Author:"></a></h3>
+<p>Chen Kailing joined Kaijing Technology in May 2016. Formerly a senior developer and project manager, currently the head of the Architecture & Operations Department of Kaijing Technology's R&D Center. PMP project management certification, Alibaba Cloud MVP. Enthusiastic about open source, having open-sourced several popular projects. Passionate about sharing technical insights, and author of the independent blog KL Blog (<a href="http://www.kailing.pub/" target="_blank" re [...]
<ul>
<li>One phase prepare behavior</li>
<li>Two phase commit or rollback behavior</li>
diff --git a/blog/quick-start-use-seata-and-dubbo-services/index.html b/blog/quick-start-use-seata-and-dubbo-services/index.html
index 2a4c9d56bcc..13ef54ab0ef 100644
--- a/blog/quick-start-use-seata-and-dubbo-services/index.html
+++ b/blog/quick-start-use-seata-and-dubbo-services/index.html
@@ -11,11 +11,11 @@
<meta name="aes-config" content="pid=xux-opensource&user_type=101&uid=&username=&dim10=seata"><link rel="stylesheet" href="/assets/css/styles.9644caf2.css">
-<script src="/assets/js/runtime~main.bf98ee01.js" defer="defer"></script>
-<script src="/assets/js/main.8371dd70.js" defer="defer"></script>
+<script src="/assets/js/runtime~main.762ed5c0.js" defer="defer"></script>
+<script src="/assets/js/main.aeea7339.js" defer="defer"></script>
</head>
<body class="navigation-with-keyboard">
-<script>!function(){function t(t){document.documentElement.setAttribute("data-theme",t)}var e=function(){try{return new URLSearchParams(window.location.search).get("docusaurus-theme")}catch(t){}}()||function(){try{return localStorage.getItem("theme")}catch(t){}}();t(null!==e?e:"light")}(),function(){try{const c=new URLSearchParams(window.location.search).entries();for(var[t,e]of c)if(t.startsWith("docusaurus-data-")){var a=t.replace("docusaurus-data-","data-");document.documentElement.se [...]
+<script>!function(){function t(t){document.documentElement.setAttribute("data-theme",t)}var e=function(){try{return new URLSearchParams(window.location.search).get("docusaurus-theme")}catch(t){}}()||function(){try{return localStorage.getItem("theme")}catch(t){}}();t(null!==e?e:"light")}(),function(){try{const c=new URLSearchParams(window.location.search).entries();for(var[t,e]of c)if(t.startsWith("docusaurus-data-")){var a=t.replace("docusaurus-data-","data-");document.documentElement.se [...]
<p>A business logic for user purchasing commodities. The whole business logic is powered by 3 microservices:</p>
<ul>
<li>Storage service: deduct storage count on given commodity.</li>
diff --git a/blog/rss.xml b/blog/rss.xml
index 463b65aa6ec..cb6a951be36 100644
--- a/blog/rss.xml
+++ b/blog/rss.xml
@@ -4,7 +4,7 @@
<title>Apache Seata Blog</title>
<link>https://seata.apache.org/blog</link>
<description>Apache Seata Blog</description>
- <lastBuildDate>Tue, 26 Nov 2024 03:53:20 GMT</lastBuildDate>
+ <lastBuildDate>Fri, 13 Dec 2024 16:25:48 GMT</lastBuildDate>
<docs>https://validator.w3.org/feed/docs/rss2.html</docs>
<generator>https://github.com/jpmonette/feed</generator>
<language>en</language>
@@ -12,10 +12,62 @@
<title><![CDATA[seata-namingserver]]></title>
<link>https://seata.apache.org/blog/seata-namingserver</link>
<guid>https://seata.apache.org/blog/seata-namingserver</guid>
- <pubDate>Tue, 26 Nov 2024 03:53:20 GMT</pubDate>
+ <pubDate>Fri, 13 Dec 2024 16:25:48 GMT</pubDate>
<description><![CDATA[Placeholder. DO NOT DELETE.]]></description>
<content:encoded><![CDATA[<p>Placeholder. DO NOT DELETE.</p>]]></content:encoded>
</item>
+ <item>
+ <title><![CDATA[Go Language Client Communication with Seata Server]]></title>
+ <link>https://seata.apache.org/blog/seata-grpc-client</link>
+ <guid>https://seata.apache.org/blog/seata-grpc-client</guid>
+ <pubDate>Sat, 30 Nov 2024 00:00:00 GMT</pubDate>
+ <description><![CDATA[This article takes Go language as an example to demonstrate Seata's multi-language client communication capabilities.]]></description>
+ <content:encoded><![CDATA[<p>With the merge of PR <a href="https://github.com/apache/incubator-seata/pull/6754" target="_blank" rel="noopener noreferrer">https://github.com/apache/incubator-seata/pull/6754</a>, Seata Server is now capable of recognizing and processing Grpc requests. This means that any language client, by simply including the proto files, can communicate with the Seata Server deployed on the JVM, thereby achieving the full process of distributed transactions.</p>
+<p>Below is a demonstration of this process using Go language as an example.</p>
+<h1>Environment Preparation</h1>
+<p>Goland 2024.2</p>
+<p>Idea 2024.3</p>
+<p>JDK 1.8</p>
+<p>Go 1.23.3</p>
+<p>Seata 2.3.0-SNAPSHOT</p>
+<p>libprotoc 3.21.0</p>
+<h1>Operation Process</h1>
+<h2 class="anchor anchorWithStickyNavbar_LWe7" id="deploy-and-start-seata-server">Deploy and Start Seata Server<a href="https://seata.apache.org/blog/seata-grpc-client#deploy-and-start-seata-server" class="hash-link" aria-label="Direct link to Deploy and Start Seata Server" title="Direct link to Deploy and Start Seata Server"></a></h2>
+<p>Run org.apache.seata.server.ServerApplication#main as shown below:</p>
+<p><img decoding="async" loading="lazy" alt="2024121301.png" src="https://seata.apache.org/assets/images/2024121301-4613ead894d7510e65d88296eb86e297.png" width="2560" height="1504" class="img_ev3q"></p>
+<h2 class="anchor anchorWithStickyNavbar_LWe7" id="proto-file-import">Proto File Import<a href="https://seata.apache.org/blog/seata-grpc-client#proto-file-import" class="hash-link" aria-label="Direct link to Proto File Import" title="Direct link to Proto File Import"></a></h2>
+<p>Import the necessary proto files for the transaction process in the Go project, including various transaction request and response proto files and the proto files for initiating RPC. As shown below:</p>
+<p><img decoding="async" loading="lazy" alt="2024121302.png" src="https://seata.apache.org/assets/images/2024121302-39625f525d6da1bbc7ad4509c94718eb.png" width="2560" height="1504" class="img_ev3q"></p>
+<h2 class="anchor anchorWithStickyNavbar_LWe7" id="grpc-file-generation">Grpc File Generation<a href="https://seata.apache.org/blog/seata-grpc-client#grpc-file-generation" class="hash-link" aria-label="Direct link to Grpc File Generation" title="Direct link to Grpc File Generation"></a></h2>
+<p>In the directory where the proto files were imported in the previous step, execute the command:</p>
+<div class="language-shell codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_biex"><pre tabindex="0" class="prism-code language-shell codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><span class="token-line" style="color:#393A34"><span class="token plain">protoc --go_out=. --go-grpc_out=. .\*.proto</span><br></span></code></pre><div class="but [...]
+<p>After execution, the grpc code will be generated as shown below:</p>
+<p><img decoding="async" loading="lazy" alt="2024121303.png" src="https://seata.apache.org/assets/images/2024121303-bad6bb1db830335d72e2037ea7dbf4de.png" width="2560" height="1504" class="img_ev3q"></p>
+<h2 class="anchor anchorWithStickyNavbar_LWe7" id="grpc-invocation">Grpc Invocation<a href="https://seata.apache.org/blog/seata-grpc-client#grpc-invocation" class="hash-link" aria-label="Direct link to Grpc Invocation" title="Direct link to Grpc Invocation"></a></h2>
+<p>Complete a distributed transaction process in main.go and print the response from Seata Server. The code is as follows:</p>
+<div class="language-go codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_biex"><pre tabindex="0" class="prism-code language-go codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><span class="token-line" style="color:#393A34"><span class="token keyword" style="color:#00009f">func</span><span class="token plain"> </span><span class="token functio [...]
+<p>After running, the Seata Server console prints as follows:</p>
+<p><img decoding="async" loading="lazy" alt="2024121304.png" src="https://seata.apache.org/assets/images/2024121304-fcc9119043d66143a841d2008ef136f5.png" width="2560" height="1504" class="img_ev3q"></p>
+<p>The Go client console prints as follows:</p>
+<p><img decoding="async" loading="lazy" alt="2024121305.png" src="https://seata.apache.org/assets/images/2024121305-327ecb450c5fd7f7fc636165421972b2.png" width="2560" height="1504" class="img_ev3q"></p>
+<h1>Implementation Principle</h1>
+<h2 class="anchor anchorWithStickyNavbar_LWe7" id="proto-design">Proto Design<a href="https://seata.apache.org/blog/seata-grpc-client#proto-design" class="hash-link" aria-label="Direct link to Proto Design" title="Direct link to Proto Design"></a></h2>
+<p>To achieve communication with multi-language grpc clients, Seata Server defines grpcMessage.proto, which defines the GrpcMessageProto that assembles various Seata Message objects and the bidirectional stream interface sendRequest for assembling Seata communication requests. Seata Server uses grpcMessage.proto as a medium to achieve communication with multi-language clients.</p>
+<div class="language-proto codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_biex"><pre tabindex="0" class="prism-code language-proto codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><span class="token-line" style="color:#393A34"><span class="token plain">syntax = "proto3";</span><br></span><span class="token-line" style="color:#393A34"><span [...]
+<p>In addition, GrpcSerializer is defined, adapting to Seata's serialization SPI system, which is used to achieve the mutual conversion of protobuf byte streams and Seata message objects.</p>
+<h2 class="anchor anchorWithStickyNavbar_LWe7" id="grpc-protocol-recognition">Grpc Protocol Recognition<a href="https://seata.apache.org/blog/seata-grpc-client#grpc-protocol-recognition" class="hash-link" aria-label="Direct link to Grpc Protocol Recognition" title="Direct link to Grpc Protocol Recognition"></a></h2>
+<p>Seata Server implements ProtocolDetectHandler and ProtocolDetector. ProtocolDetectHandler, as a ByteToMessageDecoder, will traverse the ProtocolDetector list when receiving a message to find a ProtocolDetector that can recognize the current message. ProtocolDetector distinguishes Seata protocols, Http1.1 protocols, and Http2 protocols through recognizing magic numbers. Once recognized, the ChannelHandler capable of handling the protocol is added to the current Channel's Pipeline.</p>
+<p><img decoding="async" loading="lazy" alt="2024121306.jpeg" src="https://seata.apache.org/assets/images/2024121306-5568d956a86d67c43e4d76837dd5c8b8.jpeg" width="1904" height="1657" class="img_ev3q"></p>
+<h2 class="anchor anchorWithStickyNavbar_LWe7" id="grpc-request-sending-and-processing">Grpc Request Sending and Processing<a href="https://seata.apache.org/blog/seata-grpc-client#grpc-request-sending-and-processing" class="hash-link" aria-label="Direct link to Grpc Request Sending and Processing" title="Direct link to Grpc Request Sending and Processing"></a></h2>
+<p>Seata Server implements GrpcEncoder and GrpcDecoder. GrpcEncoder is responsible for converting Seata's RpcMessage into GrpcMessageProto recognizable by grpc native clients, filling the header with status, contentType, and other protocol headers for communication with grpc native clients. GrpcEncoder also adapts to grpc protocol specifications, writing the compression bit, length, and message body in the order specified by the grpc protocol into the channel.</p>
+<p>GrpcDecoder is responsible for processing requests from grpc native clients. Since grpc clients implement request batching in the underlying transmission through a queue flush, GrpcDecoder is also responsible for unpacking a batch of requests. Finally, GrpcDecoder converts the protobuf byte stream into one or more RpcMessages and passes them to the Seata request processor.</p>
+<h2 class="anchor anchorWithStickyNavbar_LWe7" id="grpc-connection-establishment-and-management">Grpc Connection Establishment and Management<a href="https://seata.apache.org/blog/seata-grpc-client#grpc-connection-establishment-and-management" class="hash-link" aria-label="Direct link to Grpc Connection Establishment and Management" title="Direct link to Grpc Connection Establishment and Management"></a></h2>
+<p>On the server side, simply configure a ProtocolDetectHandler to complete the recognition and establishment of various types of connections.</p>
+<div class="language-java codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_biex"><pre tabindex="0" class="prism-code language-java codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><span class="token-line" style="color:#393A34"><span class="token annotation punctuation" style="color:#393A34">@Override</span><span class="token plain"></span><br [...]
+<p>On the client side, when obtaining a Channel, if the current communication method is Grpc, an Http2MultiStreamChannel is obtained as the parent Channel, and grpc-related handlers are added to this Channel.</p>
+<div class="language-java codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_biex"><pre tabindex="0" class="prism-code language-java codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><span class="token-line" style="color:#393A34"><span class="token keyword" style="color:#00009f">if</span><span class="token plain"> </span><span class="token punct [...]
+<p>Please note that due to network issues, the parsing of the above links was unsuccessful. If you need the content of the parsed web pages, please check the legality of the web page links and try again. If you do not need the parsing of these links, the question can be answered normally.</p>]]></content:encoded>
+ </item>
<item>
<title><![CDATA[Seata Raft Configuration Center]]></title>
<link>https://seata.apache.org/blog/seata-raft-config-center</link>
@@ -1558,122 +1610,5 @@ Page splits are unfriendly to I/O, requiring the creation of new data pages, cop
<h3 class="anchor anchorWithStickyNavbar_LWe7" id="peroration">peroration<a href="https://seata.apache.org/blog/seata-feature-undo-log-compress#peroration" class="hash-link" aria-label="Direct link to peroration" title="Direct link to peroration"></a></h3>
<p>By compressing undo_log, Seata can further improve its performance when processing large amounts of data at the framework level. At the same time, it also provides the corresponding switch and relatively reasonable default value, which is convenient for users to use out of the box, but also convenient for users to adjust according to actual needs, so that the corresponding function is more suitable for the actual use scenario.</p>]]></content:encoded>
</item>
- <item>
- <title><![CDATA[Seata Deadlock Issue Caused by ConcurrentHashMap]]></title>
- <link>https://seata.apache.org/blog/seata-dsproxy-deadlock</link>
- <guid>https://seata.apache.org/blog/seata-dsproxy-deadlock</guid>
- <pubDate>Sat, 13 Mar 2021 00:00:00 GMT</pubDate>
- <description><![CDATA[This article primarily discusses an online issue, a Seata dynamic data source proxy deadlock caused by a ConcurrentHashMap bug.]]></description>
- <content:encoded><![CDATA[<ol>
-<li>seata version: 1.4.0, but all versions below 1.4 also have this problem.</li>
-<li>Problem description: In a global transaction, a pure query operation on a branch transaction suddenly gets stuck without any feedback (logs/exceptions) until the RPC timeout on the consumer side</li>
-</ol>
-<p>! <a href="https://p3-juejin.byteimg.com/tos-cn-i-k3u1fbpfcp/03a7f737b56e45b4b74e662033ec74f6~tplv-k3u1fbpfcp-watermark.image" target="_blank" rel="noopener noreferrer">image.png</a></p>
-<h1>Problem Troubleshooting</h1>
-<ol>
-<li>The whole process is in a global transaction, the consumer and provider can be seen as two branches of the global transaction, consumer --> provider.</li>
-<li>the consumer first executes some local logic, and then sends an RPC request to the provider to make sure that the consumer has sent the request and the provider has received it.</li>
-<li>the provider first prints a log, and then executes a pure query SQL, if the SQL is executed properly, it will print the log, but the current phenomenon is that only the log before the execution of the SQL is printed, and no SQL-related logs are printed. Find DBA to check the SQL log, and found that the SQL is not executed.</li>
-<li>Determined that the operation is only a pure query operation under the global transaction, before the operation, the overall process of the global transaction is completely normal.</li>
-<li>In fact, the phenomenon here has been very obvious, but at that time the idea did not change over, has been concerned about the query SQL, always thinking that even if the query timeout and other reasons should be thrown exceptions ah, should not be nothing. DBA can not find the query record, that is not to say that the SQL may not have been executed ah, but in the execution of the SQL before the problem, such as the agent?</li>
-<li>With the help of arthas's watch command, there is no output. The first log output means that the method must have been executed, and the delay in outputting the result means that the current request is stuck, why is it stuck?</li>
-<li>With arthas's thread command <code>thread -b</code>, <code>thread -n</code>, is to find out the current busiest thread. This works very well, there is a thread CPU usage <code>92%</code>, and because of this thread caused the other 20 or so Dubbo threads <code>BLOCKED</code>. The stack information is as follows</li>
-<li>Analysing the stack information, we can clearly find the interface related to seata, which is probably related to seata's data source proxy; at the same time, we found that the thread with the highest CPU usage is stuck in the <code>ConcurrentHashMap#computeIfAbsent</code> method. Is there a bug in the <code>ConcurrentHashMap#computeIfAbsent</code> method?</li>
-<li>By now, we don't know the exact cause of the problem, but it should have something to do with seata's data source proxy, and we need to analyse both the business code and the seata code to find out why.</li>
-</ol>
-<p>! <a href="https://p1-juejin.byteimg.com/tos-cn-i-k3u1fbpfcp/faac0be0982e45a7a43b335e8f8b44bf~tplv-k3u1fbpfcp-watermark.image" target="_blank" rel="noopener noreferrer">image.png</a></p>
-<h2 class="anchor anchorWithStickyNavbar_LWe7" id="problem-analysis">Problem analysis<a href="https://seata.apache.org/blog/seata-dsproxy-deadlock#problem-analysis" class="hash-link" aria-label="Direct link to Problem analysis" title="Direct link to Problem analysis"></a></h2>
-<h3 class="anchor anchorWithStickyNavbar_LWe7" id="concurrenthashmapcomputeifabsent">ConcurrentHashMap##computeIfAbsent<a href="https://seata.apache.org/blog/seata-dsproxy-deadlock#concurrenthashmapcomputeifabsent" class="hash-link" aria-label="Direct link to ConcurrentHashMap##computeIfAbsent" title="Direct link to ConcurrentHashMap##computeIfAbsent"></a></h3>
-<p>This method does have the potential for problems: if two keys have the same hascode, and the computeIfAbsent operation is performed in the corresponding mappingFunction, it will lead to a dead loop, refer to this article for specific analysis: <a href="https://juejin.cn/post/" target="_blank" rel="noopener noreferrer">https://juejin.cn/post/</a> 6844904191077384200</p>
-<h3 class="anchor anchorWithStickyNavbar_LWe7" id="seata-data-source-autoproxy">Seata data source autoproxy<a href="https://seata.apache.org/blog/seata-dsproxy-deadlock#seata-data-source-autoproxy" class="hash-link" aria-label="Direct link to Seata data source autoproxy" title="Direct link to Seata data source autoproxy"></a></h3>
-<p>Related content has been analysed before, let's focus on the following core classes:</p>
-<ol>
-<li>SeataDataSourceBeanPostProcessor</li>
-<li>SeataAutoDataSourceProxyAdvice</li>
-<li>DataSourceProxyHolder</li>
-</ol>
-<h5 class="anchor anchorWithStickyNavbar_LWe7" id="seatadatasourcebeanpostprocessor">SeataDataSourceBeanPostProcessor<a href="https://seata.apache.org/blog/seata-dsproxy-deadlock#seatadatasourcebeanpostprocessor" class="hash-link" aria-label="Direct link to SeataDataSourceBeanPostProcessor" title="Direct link to SeataDataSourceBeanPostProcessor"></a></h5>
-<p>The <code>SeataDataSourceBeanPostProcessor</code> is a <code>BeanPostProcessor</code> implementation class that creates a <code>seataAutoDataSourceProxyDataSource</code> for the data source configured by the business side in the <code>postProcessAfterInitialization</code> method (i.e., after the bean is initialised). proxy data source</p>
-<div class="language-java codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_biex"><pre tabindex="0" class="prism-code language-java codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><span class="token-line" style="color:#393A34"><span class="token keyword" style="color:#00009f">public</span><span class="token plain"> </span><span class="token k [...]
-<h5 class="anchor anchorWithStickyNavbar_LWe7" id="seataautodatasourceproxyadvice">SeataAutoDataSourceProxyAdvice<a href="https://seata.apache.org/blog/seata-dsproxy-deadlock#seataautodatasourceproxyadvice" class="hash-link" aria-label="Direct link to SeataAutoDataSourceProxyAdvice" title="Direct link to SeataAutoDataSourceProxyAdvice"></a></h5>
-<p><code>SeataAutoDataSourceProxyAdvice</code> is a MethodInterceptor, <code>SeataAutoDataSourceProxyCreator</code> in seata creates a dynamic proxy object for <code>Bean</code> of type <code>DataSource</code>, the proxy logic is the <code>SeataAutoDataSourceProxyAdvice#invoke</code> logic. That is: when executing the relevant methods of the <code>DataSourceAOPProxyAdvice</code>, it will go through its <code>invoke</code> method, and in the <code>invoke</code> method, it will find the co [...]
-<div class="language-java codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_biex"><pre tabindex="0" class="prism-code language-java codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><span class="token-line" style="color:#393A34"><span class="token keyword" style="color:#00009f">public</span><span class="token plain"> </span><span class="token k [...]
-<h5 class="anchor anchorWithStickyNavbar_LWe7" id="datasourceproxyholder">DataSourceProxyHolder<a href="https://seata.apache.org/blog/seata-dsproxy-deadlock#datasourceproxyholder" class="hash-link" aria-label="Direct link to DataSourceProxyHolder" title="Direct link to DataSourceProxyHolder"></a></h5>
-<p>The process is clear to us, now there is a question, how to maintain the relationship between <code>native data source</code> and <code>seata proxy data source</code>? It is maintained by <code>DataSourceProxyHolder</code>, which is a singleton object that maintains the relationship between the two through a ConcurrentHashMap: <code>native data source</code> as key --> <code>seata proxy data source</code> as value.</p>
-<div class="language-java codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_biex"><pre tabindex="0" class="prism-code language-java codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><span class="token-line" style="color:#393A34"><span class="token keyword" style="color:#00009f">public</span><span class="token plain"> </span><span class="token k [...]
-<h3 class="anchor anchorWithStickyNavbar_LWe7" id="client-data-source-configuration">Client data source configuration<a href="https://seata.apache.org/blog/seata-dsproxy-deadlock#client-data-source-configuration" class="hash-link" aria-label="Direct link to Client data source configuration" title="Direct link to Client data source configuration"></a></h3>
-<ol>
-<li>Two data sources are configured: <code>DynamicDataSource</code>, <code>P6DataSource</code>, <code>P6DataSource</code>, <code>P6DataSource</code> and <code>P6DataSource</code>.</li>
-<li><code>P6DataSource</code> can be seen as a wrapper for <code>DynamicDataSource</code>. 3.</li>
-<li>Let's not worry about whether this configuration makes sense or not, now we just analyse the problem purely based on this data source configuration.</li>
-</ol>
-<div class="language-java codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_biex"><pre tabindex="0" class="prism-code language-java codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><span class="token-line" style="color:#393A34"><span class="token annotation punctuation" style="color:#393A34">@Qualifier</span><span class="token punctuation" sty [...]
-<h3 class="anchor anchorWithStickyNavbar_LWe7" id="analyse-the-process">Analyse the process<a href="https://seata.apache.org/blog/seata-dsproxy-deadlock#analyse-the-process" class="hash-link" aria-label="Direct link to Analyse the process" title="Direct link to Analyse the process"></a></h3>
-<p><code>Assuming that by now everyone is aware of the problems that may arise from ConcurrentHashMap#computeIfAbsent</code>, it is known that this problem has now arisen, and in combination with the stack information, we can see roughly where this problem has arisen.</p>
-<p>1, <code>ConcurrentHashMap#computeIfAbsent</code> will produce this problem precondition is: <code>two key hashcode is the same</code>; <code>mappingFunction corresponds to a put operation</code>. Combined with our seata usage scenario, the mappingFunction corresponds to <code>DataSourceProxy::new</code>, suggesting that the put operation may be triggered in the DataSourceProxy's constructor method</p>
-<p>! <a href="https://p1-juejin.byteimg.com/tos-cn-i-k3u1fbpfcp/00d8e13f71644c63b3bbb58c93b30e0c~tplv-k3u1fbpfcp-watermark.image" target="_blank" rel="noopener noreferrer">image.png</a></p>
-<div class="language-java codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_biex"><pre tabindex="0" class="prism-code language-java codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><span class="token-line" style="color:#393A34"><span class="token class-name">Execute</span><span class="token plain"> </span><span class="token constant" style="co [...]
-<p>2, What is the <code>AOP proxy data source</code> and <code>native data source</code> stated in step 1? Look at the following diagram
-! <a href="https://p3-juejin.byteimg.com/tos-cn-i-k3u1fbpfcp/3579631f58df4d17bfcd6f28ccc3fd79~tplv-k3u1fbpfcp-watermark.image" target="_blank" rel="noopener noreferrer">image.png</a></p>
-<p>3, the above also said to produce this problem there is a condition <code>two key hashcode the same</code>, but I see that these two data source objects are not overriding the <code>hashcode</code> method, so by definition, these two objects must be different hashcode. After looking at the ConcurrentHashMap problem again, I feel that the statement <code>two keys have the same hashcode</code> is not correct, and <code>two keys will generate hash conflict</code> is more reasonable, whic [...]
-<div class="language-java codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_biex"><pre tabindex="0" class="prism-code language-java codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><span class="token-line" style="color:#393A34"><span class="token keyword" style="color:#00009f">public</span><span class="token plain"> </span><span class="token k [...]
-<ol>
-<li>To make it easier to reproduce the problem, we rewrite the <code>Num#hashCode</code> method to ensure that the constructor input is the hashcode value.</li>
-<li>create a ConcurrentHashMap object, initialCapacity is 8, sizeCtl calculated value is 16, that is, the default length of the array in the map is 16</li>
-<li>create object <code>n1</code>, the input parameter is 3, that is, the hashcode is 3, the calculation of its corresponding array subscript 3</li>
-<li>create object <code>n2</code>, the input parameter is 19, that is, the hashcode is 19, calculate its corresponding array subscript is 3, at this time we can think of <code>n1 and n2 hash conflict</code>.</li>
-<li>create object <code>n3</code> with input 20, i.e., hashcode 20, and its corresponding array subscript is 4.</li>
-<li>execute <code>map.computeIfAbsent(n1, k1 -> map.computeIfAbsent(n3, k2 -> 200))</code>, the programme exits normally: <code>Because there is no hash conflict between n1 and n3, the programme terminates normally</code>.</li>
-<li>Execute <code>map.computeIfAbsent(n1, k1 -> map.computeIfAbsent(n2, k2 -> 200))</code>, the programme exits normally: <code> because n1 and n2 have a hash conflict, so it is in a dead loop</code>.</li>
-</ol>
-<p>4、During the initialisation of the object, hasn't <code>SeataDataSourceBeanPostProcessor</code> already initialised the corresponding data source proxy of the object? Why the corresponding data source proxy is still created in <code>SeataAutoDataSourceProxyAdvice</code>?</p>
-<ol>
-<li>First of all, the <code>SeataDataSourceBeanPostProcessor</code> execution period is later than the creation of the AOP proxy object, so when executing the <code>SeataDataSourceBeanPostProcessor</code> related methods, the <code>SeataAutoDataSourceBeanPostProcessor</code> method is executed. SeataAutoDataSourceProxyAdvice<code>should actually take effect when the</code>SeataDataSourceBeanPostProcessor` related methods are executed.</li>
-<li>when adding elements to the map in <code>SeataDataSourceBeanPostProcessor</code>, the key is <code>AOP proxy datasource</code>; in <code>SeataAutoDataSourceProxyAdvice</code>, the key is <code>native datasource</code>, so the key is not the same as <code>invocation.getThis()</code>, so the key is not the same. `, so the key is not the same</li>
-</ol>
-<p>! <a href="https://p6-juejin.byteimg.com/tos-cn-i-k3u1fbpfcp/747b664a0b6c4f58843947576dd0856e~tplv-k3u1fbpfcp-watermark.image" target="_blank" rel="noopener noreferrer">image.png</a></p>
-<p>5, there is another problem, <code>SeataAutoDataSourceProxyAdvic#invoke</code> method does not filter <code>toString, hashCode</code> and other methods, the proxy object created by cglib will override these methods by default, if these methods of the proxy object are triggered when putting elements into the map. If these methods are triggered when putting elements into the map, the proxy object will re-enter the <code>SeataAutoDataSourceProxyAdvic#invoke</code> cut until the thread st [...]
-<h1>Summary of the problem</h1>
-<ol>
-<li>in two key will produce hash conflict, will trigger <code>ConcurrentHashMap#computeIfAbsent</code> BUG, the performance of this BUG is to make the current thread into a dead loop</li>
-<li>business feedback, the problem is occasional, occasional for two reasons: first, the application is a multi-node deployment, but only one node on the line triggered the BUG (hashcode conflict), so only when the request hits this node may trigger the BUG; second, because each restart object address (hashcode) are not sure, so not triggered after every app restart, but if once triggered, the node will always have this problem. Having a thread that keeps dying and blocking other threads [...]
-<li>when encountering this problem, from the perspective of the whole problem, it is indeed a deadlock, because the dead loop thread occupant lock has not been released, resulting in other threads operating on the map is BLOCKED!</li>
-<li>essentially because <code>ConcurrentHashMap#computeIfAbsent method may trigger a bug</code>, and seata's usage scenario just triggered the bug.</li>
-<li>The following demo is actually a complete simulation of what happens when something goes wrong online, as follows:</li>
-</ol>
-<div class="language-java codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_biex"><pre tabindex="0" class="prism-code language-java codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><span class="token-line" style="color:#393A34"><span class="token keyword" style="color:#00009f">public</span><span class="token plain"> </span><span class="token k [...]
-<p>! <a href="https://p6-juejin.byteimg.com/tos-cn-i-k3u1fbpfcp/d6134c6498fa49c4a68b2745ba0895e3~tplv-k3u1fbpfcp-watermark.image" target="_blank" rel="noopener noreferrer">image.png</a></p>
-<h3 class="anchor anchorWithStickyNavbar_LWe7" id="solving-the-problem">Solving the problem<a href="https://seata.apache.org/blog/seata-dsproxy-deadlock#solving-the-problem" class="hash-link" aria-label="Direct link to Solving the problem" title="Direct link to Solving the problem"></a></h3>
-<p>The problem can be solved in two ways:</p>
-<ol>
-<li>business changes: P6DataSource and DynamicDataSource do not need to be proxied, directly proxy P6DataSource can be, DynamicDataSource does not need to be declared as a bean; or through the excludes property excludes P6DataSource, so that there is no duplicate proxy problem. There will be no problem of duplicate proxies</li>
-<li>Seata refinement: improve the logic related to data source proxy</li>
-</ol>
-<h5 class="anchor anchorWithStickyNavbar_LWe7" id="business-changes">Business changes<a href="https://seata.apache.org/blog/seata-dsproxy-deadlock#business-changes" class="hash-link" aria-label="Direct link to Business changes" title="Direct link to Business changes"></a></h5>
-<ol>
-<li>Data source related configuration can be changed to the following:</li>
-</ol>
-<div class="language-java codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_biex"><pre tabindex="0" class="prism-code language-java codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><span class="token-line" style="color:#393A34"><span class="token annotation punctuation" style="color:#393A34">@Primary</span><span class="token plain"></span><br> [...]
-<ol start="2">
-<li>Or leave the current data source configuration unchanged and add the excludes property</li>
-</ol>
-<div class="language-java codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_biex"><pre tabindex="0" class="prism-code language-java codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><span class="token-line" style="color:#393A34"><span class="token annotation punctuation" style="color:#393A34">@EnableAutoDataSourceProxy</span><span class="token [...]
-<h5 class="anchor anchorWithStickyNavbar_LWe7" id="seata-refinement">Seata refinement<a href="https://seata.apache.org/blog/seata-dsproxy-deadlock#seata-refinement" class="hash-link" aria-label="Direct link to Seata refinement" title="Direct link to Seata refinement"></a></h5>
-<ol>
-<li><code>ConcurrentHashMap#computeIfAbsent</code> method is changed to double check as follows:</li>
-</ol>
-<div class="language-java codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_biex"><pre tabindex="0" class="prism-code language-java codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><span class="token-line" style="color:#393A34"><span class="token class-name">SeataDataSourceProxy</span><span class="token plain"> dsProxy </span><span class="toke [...]
-<p>I wanted to change the <code>CollectionUtils#computeIfAbsent</code> method directly, and the feedback from the group was that this might cause the data source to be created multiple times, which is indeed a problem: as follows</p>
-<div class="language-java codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_biex"><pre tabindex="0" class="prism-code language-java codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><span class="token-line" style="color:#393A34"><span class="token keyword" style="color:#00009f">public</span><span class="token plain"> </span><span class="token k [...]
-<ol start="2">
-<li>Add some filtering to the SeataAutoDataSourceProxyAdvice cutout logic</li>
-</ol>
-<div class="language-java codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_biex"><pre tabindex="0" class="prism-code language-java codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><span class="token-line" style="color:#393A34"><span class="token class-name">Method</span><span class="token plain"> m </span><span class="token operator" style="c [...]
-<h3 class="anchor anchorWithStickyNavbar_LWe7" id="legacy-issues">Legacy issues<a href="https://seata.apache.org/blog/seata-dsproxy-deadlock#legacy-issues" class="hash-link" aria-label="Direct link to Legacy issues" title="Direct link to Legacy issues"></a></h3>
-<p>In the corresponding methods of <code>SeataDataSourceBeanPostProcessor</code> and <code>SeataAutoDataSourceProxyAdvice</code>, the keys corresponding to initialising the <code>seata datasource proxy</code> into the map are fundamentally different, the <code>The key in</code>SeataDataSourceBeanPostProcessor<code>is the</code>AOP proxy data source<code>; the key in </code>SeataAutoDataSourceProxyAdvice<code>is the native object, which results in the unnecessary creation of the</code>sea [...]
-<p>What is the best suggestion for this problem? Is it possible to specify an order for <code>SeataDataSourceBeanPostProcessor</code> to take effect before the AOP proxy object is created?</p>
-<h1>Link to original article</h1>
-<p><a href="https://juejin.cn/post/6939041336964153352/" target="_blank" rel="noopener noreferrer">https://juejin.cn/post/6939041336964153352/</a></p>]]></content:encoded>
- </item>
</channel>
</rss>
\ No newline at end of file
diff --git a/blog/seata-1.5.2/index.html b/blog/seata-1.5.2/index.html
index 7aab6094d77..1f560ae0d49 100644
--- a/blog/seata-1.5.2/index.html
+++ b/blog/seata-1.5.2/index.html
@@ -11,11 +11,11 @@
<meta name="aes-config" content="pid=xux-opensource&user_type=101&uid=&username=&dim10=seata"><link rel="stylesheet" href="/assets/css/styles.9644caf2.css">
-<script src="/assets/js/runtime~main.bf98ee01.js" defer="defer"></script>
-<script src="/assets/js/main.8371dd70.js" defer="defer"></script>
+<script src="/assets/js/runtime~main.762ed5c0.js" defer="defer"></script>
+<script src="/assets/js/main.aeea7339.js" defer="defer"></script>
</head>
<body class="navigation-with-keyboard">
-<script>!function(){function t(t){document.documentElement.setAttribute("data-theme",t)}var e=function(){try{return new URLSearchParams(window.location.search).get("docusaurus-theme")}catch(t){}}()||function(){try{return localStorage.getItem("theme")}catch(t){}}();t(null!==e?e:"light")}(),function(){try{const c=new URLSearchParams(window.location.search).entries();for(var[t,e]of c)if(t.startsWith("docusaurus-data-")){var a=t.replace("docusaurus-data-","data-");document.documentElement.se [...]
+<script>!function(){function t(t){document.documentElement.setAttribute("data-theme",t)}var e=function(){try{return new URLSearchParams(window.location.search).get("docusaurus-theme")}catch(t){}}()||function(){try{return localStorage.getItem("theme")}catch(t){}}();t(null!==e?e:"light")}(),function(){try{const c=new URLSearchParams(window.location.search).entries();for(var[t,e]of c)if(t.startsWith("docusaurus-data-")){var a=t.replace("docusaurus-data-","data-");document.documentElement.se [...]
<p>Seata is an open-source distributed transaction solution that provides high-performance and easy-to-use distributed transaction services.</p>
<p><strong>seata-server Download Links:</strong></p>
<p><a href="https://github.com/apache/incubator-seata/archive/v1.5.2.zip" target="_blank" rel="noopener noreferrer">source</a> |
diff --git a/blog/seata-1.6.0/index.html b/blog/seata-1.6.0/index.html
index 44b1bf89e70..ea2df372def 100644
--- a/blog/seata-1.6.0/index.html
+++ b/blog/seata-1.6.0/index.html
@@ -11,11 +11,11 @@
<meta name="aes-config" content="pid=xux-opensource&user_type=101&uid=&username=&dim10=seata"><link rel="stylesheet" href="/assets/css/styles.9644caf2.css">
-<script src="/assets/js/runtime~main.bf98ee01.js" defer="defer"></script>
-<script src="/assets/js/main.8371dd70.js" defer="defer"></script>
+<script src="/assets/js/runtime~main.762ed5c0.js" defer="defer"></script>
+<script src="/assets/js/main.aeea7339.js" defer="defer"></script>
</head>
<body class="navigation-with-keyboard">
-<script>!function(){function t(t){document.documentElement.setAttribute("data-theme",t)}var e=function(){try{return new URLSearchParams(window.location.search).get("docusaurus-theme")}catch(t){}}()||function(){try{return localStorage.getItem("theme")}catch(t){}}();t(null!==e?e:"light")}(),function(){try{const c=new URLSearchParams(window.location.search).entries();for(var[t,e]of c)if(t.startsWith("docusaurus-data-")){var a=t.replace("docusaurus-data-","data-");document.documentElement.se [...]
+<script>!function(){function t(t){document.documentElement.setAttribute("data-theme",t)}var e=function(){try{return new URLSearchParams(window.location.search).get("docusaurus-theme")}catch(t){}}()||function(){try{return localStorage.getItem("theme")}catch(t){}}();t(null!==e?e:"light")}(),function(){try{const c=new URLSearchParams(window.location.search).entries();for(var[t,e]of c)if(t.startsWith("docusaurus-data-")){var a=t.replace("docusaurus-data-","data-");document.documentElement.se [...]
<p>Seata is an open-source distributed transaction solution that provides high performance and easy-to-use distributed transaction services.</p>
<p><strong>Download Links for seata-server:</strong></p>
<p><a href="https://github.com/apache/incubator-seata/archive/v1.6.0.zip" target="_blank" rel="noopener noreferrer">source</a> |
diff --git a/blog/seata-analysis-UUID-generator/index.html b/blog/seata-analysis-UUID-generator/index.html
index e55fd144510..0db8f498c1b 100644
--- a/blog/seata-analysis-UUID-generator/index.html
+++ b/blog/seata-analysis-UUID-generator/index.html
@@ -11,11 +11,11 @@
<meta name="aes-config" content="pid=xux-opensource&user_type=101&uid=&username=&dim10=seata"><link rel="stylesheet" href="/assets/css/styles.9644caf2.css">
-<script src="/assets/js/runtime~main.bf98ee01.js" defer="defer"></script>
-<script src="/assets/js/main.8371dd70.js" defer="defer"></script>
+<script src="/assets/js/runtime~main.762ed5c0.js" defer="defer"></script>
+<script src="/assets/js/main.aeea7339.js" defer="defer"></script>
</head>
<body class="navigation-with-keyboard">
-<script>!function(){function t(t){document.documentElement.setAttribute("data-theme",t)}var e=function(){try{return new URLSearchParams(window.location.search).get("docusaurus-theme")}catch(t){}}()||function(){try{return localStorage.getItem("theme")}catch(t){}}();t(null!==e?e:"light")}(),function(){try{const c=new URLSearchParams(window.location.search).entries();for(var[t,e]of c)if(t.startsWith("docusaurus-data-")){var a=t.replace("docusaurus-data-","data-");document.documentElement.se [...]
+<script>!function(){function t(t){document.documentElement.setAttribute("data-theme",t)}var e=function(){try{return new URLSearchParams(window.location.search).get("docusaurus-theme")}catch(t){}}()||function(){try{return localStorage.getItem("theme")}catch(t){}}();t(null!==e?e:"light")}(),function(){try{const c=new URLSearchParams(window.location.search).entries();for(var[t,e]of c)if(t.startsWith("docusaurus-data-")){var a=t.replace("docusaurus-data-","data-");document.documentElement.se [...]
<p>High performance is self-explanatory, and global uniqueness is crucial to prevent confusion between different global transactions or branch transactions. Additionally, trend incrementation is valuable for users employing databases as the storage tool for TC clusters, as it can reduce the frequency of data page splits, thereby minimizing database IO pressure (the <code>branch_table</code> table uses the branch transaction ID as the primary key).</p>
<p>In the older version of Seata (prior to 1.4), the implementation of this generator was based on the standard version of the Snowflake algorithm. The standard Snowflake algorithm has been well-documented online, so we won't delve into it here. If you're unfamiliar with it, consider referring to existing resources before continuing with this article.</p>
<p>Here, we discuss some drawbacks of the standard Snowflake algorithm:</p>
diff --git a/blog/seata-analysis-config-modular/index.html b/blog/seata-analysis-config-modular/index.html
index 998260cfafa..fcc2cd37110 100644
--- a/blog/seata-analysis-config-modular/index.html
+++ b/blog/seata-analysis-config-modular/index.html
@@ -11,11 +11,11 @@
<meta name="aes-config" content="pid=xux-opensource&user_type=101&uid=&username=&dim10=seata"><link rel="stylesheet" href="/assets/css/styles.9644caf2.css">
-<script src="/assets/js/runtime~main.bf98ee01.js" defer="defer"></script>
-<script src="/assets/js/main.8371dd70.js" defer="defer"></script>
+<script src="/assets/js/runtime~main.762ed5c0.js" defer="defer"></script>
+<script src="/assets/js/main.aeea7339.js" defer="defer"></script>
</head>
<body class="navigation-with-keyboard">
-<script>!function(){function t(t){document.documentElement.setAttribute("data-theme",t)}var e=function(){try{return new URLSearchParams(window.location.search).get("docusaurus-theme")}catch(t){}}()||function(){try{return localStorage.getItem("theme")}catch(t){}}();t(null!==e?e:"light")}(),function(){try{const c=new URLSearchParams(window.location.search).entries();for(var[t,e]of c)if(t.startsWith("docusaurus-data-")){var a=t.replace("docusaurus-data-","data-");document.documentElement.se [...]
+<script>!function(){function t(t){document.documentElement.setAttribute("data-theme",t)}var e=function(){try{return new URLSearchParams(window.location.search).get("docusaurus-theme")}catch(t){}}()||function(){try{return localStorage.getItem("theme")}catch(t){}}();t(null!==e?e:"light")}(),function(){try{const c=new URLSearchParams(window.location.search).entries();for(var[t,e]of c)if(t.startsWith("docusaurus-data-")){var a=t.replace("docusaurus-data-","data-");document.documentElement.se [...]
<p>According to the classification defined by <a href="https://www.iteye.com/blog/javatar-949527" target="_blank" rel="noopener noreferrer">experts</a>, configurations can be categorized into three types: environment configuration, descriptive configuration, and extension configuration.</p>
<ul>
<li>Environment configuration: Typically consists of discrete simple values like parameters for component startup, often in key-value pair format.</li>
diff --git a/blog/seata-analysis-core-modular/index.html b/blog/seata-analysis-core-modular/index.html
index c91ffa20eb1..3495eec7206 100644
--- a/blog/seata-analysis-core-modular/index.html
+++ b/blog/seata-analysis-core-modular/index.html
@@ -11,18 +11,18 @@
<meta name="aes-config" content="pid=xux-opensource&user_type=101&uid=&username=&dim10=seata"><link rel="stylesheet" href="/assets/css/styles.9644caf2.css">
-<script src="/assets/js/runtime~main.bf98ee01.js" defer="defer"></script>
-<script src="/assets/js/main.8371dd70.js" defer="defer"></script>
+<script src="/assets/js/runtime~main.762ed5c0.js" defer="defer"></script>
+<script src="/assets/js/main.aeea7339.js" defer="defer"></script>
</head>
<body class="navigation-with-keyboard">
-<script>!function(){function t(t){document.documentElement.setAttribute("data-theme",t)}var e=function(){try{return new URLSearchParams(window.location.search).get("docusaurus-theme")}catch(t){}}()||function(){try{return localStorage.getItem("theme")}catch(t){}}();t(null!==e?e:"light")}(),function(){try{const c=new URLSearchParams(window.location.search).entries();for(var[t,e]of c)if(t.startsWith("docusaurus-data-")){var a=t.replace("docusaurus-data-","data-");document.documentElement.se [...]
+<script>!function(){function t(t){document.documentElement.setAttribute("data-theme",t)}var e=function(){try{return new URLSearchParams(window.location.search).get("docusaurus-theme")}catch(t){}}()||function(){try{return localStorage.getItem("theme")}catch(t){}}();t(null!==e?e:"light")}(),function(){try{const c=new URLSearchParams(window.location.search).entries();for(var[t,e]of c)if(t.startsWith("docusaurus-data-")){var a=t.replace("docusaurus-data-","data-");document.documentElement.se [...]
<p>The core module defines the types and states of transactions, common behaviors, protocols, and message models for communication between clients and servers, as well as exception handling methods, compilation, compression types, configuration information names, environment context, etc. It also encapsulates RPC based on Netty for use by both clients and servers.</p>
<p>Let's analyze the main functional classes of the core module according to the package order:</p>
<p><img decoding="async" loading="lazy" src="https://img-blog.csdnimg.cn/20191223162313317.png" alt="Image Description" class="img_ev3q"></p>
<p>codec: Defines a codec factory class, which provides a method to find the corresponding processing class based on the serialization type. It also provides an interface class Codec with two abstract methods:</p>
<div class="language-java codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_biex"><pre tabindex="0" class="prism-code language-java codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><span class="token-line" style="color:#393A34"><span class="token generics punctuation" style="color:#393A34"><</span><span class="token generics class-name">T</ [...]
<div class="language-java codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_biex"><pre tabindex="0" class="prism-code language-java codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><span class="token-line" style="color:#393A34"><span class="token generics punctuation" style="color:#393A34"><</span><span class="token generics class-name">T</ [...]
-<h2 class="anchor anchorWithStickyNavbar_LWe7" id="1-codec-module">1. codec Module<a href="#1-codec-module" class="hash-link" aria-label="Direct link to 1. codec Module" title="Direct link to 1. codec Module">