You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@bifromq.apache.org by vi...@apache.org on 2026/01/12 05:42:53 UTC

(bifromq-sites) 03/04: chore: remove i18n configuration and redundant files

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

visoar pushed a commit to branch clean-rebuild
in repository https://gitbox.apache.org/repos/asf/bifromq-sites.git

commit b8810118c871b7f0527d3a688125748736c59f40
Author: Visoar <vi...@gmail.com>
AuthorDate: Mon Jan 12 13:31:31 2026 +0800

    chore: remove i18n configuration and redundant files
---
 docusaurus.config.ts                               | 169 +++----
 i18n/zh-Hans/code.json                             | 420 ----------------
 .../2023-07-07-bifromq-opensource-pr.md            |  46 --
 .../2023-09-04-bifromq-auth-plugin.mdx             |  83 ----
 .../2023-09-06-bifromq-architecture-overview.md    |  92 ----
 .../2023-10-24-bifromq-standardcluster.mdx         |  71 ---
 .../2023-12-01-bifromq-high-availability.mdx       | 198 --------
 ...-12-04-bifromq-topic-subscription-mechanism.mdx | 102 ----
 .../2024-03-14-bifromq-3.0.0.mdx                   |  27 -
 .../docusaurus-plugin-content-blog/authors.yml     |  12 -
 .../bifromq-architecture-1.png                     | Bin 51941 -> 0 bytes
 .../bifromq-architecture-2-1.png                   | Bin 26786 -> 0 bytes
 .../bifromq-architecture-2-2.png                   | Bin 27408 -> 0 bytes
 .../bifromq-architecture-3.png                     | Bin 19799 -> 0 bytes
 .../BifroMQ-API-Service.png                        | Bin 350572 -> 0 bytes
 .../BifroMQ-Dist-SubCluster.png                    | Bin 533111 -> 0 bytes
 .../BifroMQ-Inbox-LoadBasedSplitter.png            | Bin 364430 -> 0 bytes
 .../BifroMQ-Inbox-SubCluster.png                   | Bin 537105 -> 0 bytes
 .../BifroMQ-StandardCluster.png                    | Bin 667253 -> 0 bytes
 .../BifroMQ-AutoEviction.png                       | Bin 124674 -> 0 bytes
 .../BifroMQ-BrainSplit.png                         | Bin 127572 -> 0 bytes
 .../BifroMQ-Domain.png                             | Bin 254695 -> 0 bytes
 .../BifroMQ-DynamicConfig.png                      | Bin 189016 -> 0 bytes
 .../BifroMQ-IndependentWorkload.png                | Bin 231896 -> 0 bytes
 .../BifroMQ-Join.png                               | Bin 247578 -> 0 bytes
 .../BifroMQ-LeaderBalance.png                      | Bin 140611 -> 0 bytes
 .../BifroMQ-RPCCluster.png                         | Bin 167199 -> 0 bytes
 .../BifroMQ-RangeBalancer.png                      | Bin 139785 -> 0 bytes
 .../BifroMQ-RangeLeaderBalancer.png                | Bin 213408 -> 0 bytes
 .../BifroMQ-RangeSplit.png                         | Bin 104011 -> 0 bytes
 .../BifroMQ-RangeSplitBalancer.png                 | Bin 214477 -> 0 bytes
 .../BifroMQ-RecoveryBalancer.png                   | Bin 173261 -> 0 bytes
 .../BifroMQ-ReplicaCntBalancer.png                 | Bin 262251 -> 0 bytes
 .../DistService.png                                | Bin 250095 -> 0 bytes
 .../MQTT_Topic_TopicFilter.png                     | Bin 292209 -> 0 bytes
 .../OnePass.png                                    | Bin 257990 -> 0 bytes
 .../TopicExpansionSet.png                          | Bin 793506 -> 0 bytes
 .../docusaurus-plugin-content-blog/options.json    |  14 -
 .../docusaurus-plugin-content-docs/current.json    |  66 ---
 .../current/01_get_started/1_quick_install.md      |  13 -
 .../current/01_get_started/2_quick_verify.md       |  30 --
 .../current/01_get_started/3_faq.md                |  44 --
 .../current/01_get_started/_category_.json         |   8 -
 .../current/01_get_started/images/newconn.jpg      | Bin 312148 -> 0 bytes
 .../current/01_get_started/images/publish.jpg      | Bin 298876 -> 0 bytes
 .../current/01_get_started/images/subscribe.jpg    | Bin 211030 -> 0 bytes
 .../current/01_get_started/intro.md                |  43 --
 .../current/02_installation/1_docker.md            |  35 --
 .../current/02_installation/2_linux.md             |  16 -
 .../current/02_installation/3_windows.md           |  17 -
 .../02_installation/4_install_from_source.md       |  32 --
 .../current/02_installation/5_config_migration.md  |   8 -
 .../current/02_installation/6_nodes_on_k8s.md      |  32 --
 .../current/02_installation/_category_.json        |   8 -
 .../current/02_installation/intro.md               |  39 --
 .../current/04_cluster/1_standardcluster.md        |  69 ---
 .../current/04_cluster/2_high_availability.md      |  68 ---
 .../current/04_cluster/3_upgrade.md                |  86 ----
 .../current/04_cluster/_category_.json             |   8 -
 .../04_cluster/images/IndependentWorkload.png      | Bin 231896 -> 0 bytes
 .../current/04_cluster/intro.md                    |  34 --
 .../current/05_user_guide/1_basic/1_connect.md     |  20 -
 .../current/05_user_guide/1_basic/2_pubsub.md      |  39 --
 .../current/05_user_guide/1_basic/3_shared_sub.md  |  21 -
 .../current/05_user_guide/1_basic/_category_.json  |   8 -
 .../1_basic/images/pub-sub-pattern.png             | Bin 372353 -> 0 bytes
 .../1_basic/images/shared-subscription.png         | Bin 489533 -> 0 bytes
 .../current/05_user_guide/1_basic/intro.md         |  17 -
 .../05_user_guide/2_integration/1_integration.md   |  26 -
 .../05_user_guide/2_integration/_category_.json    |   8 -
 .../2_integration/images/bifromqapproach.jpg       | Bin 133675 -> 0 bytes
 .../2_integration/images/commonapproach.jpg        | Bin 129120 -> 0 bytes
 .../2_integration/images/integration.png           | Bin 300130 -> 0 bytes
 .../current/05_user_guide/2_integration/intro.md   |  56 ---
 .../current/05_user_guide/3_api/1_api_reference.md | 127 -----
 .../current/05_user_guide/3_api/_category_.json    |   8 -
 .../05_user_guide/3_api/images/API-Arch.png        | Bin 25560 -> 0 bytes
 .../current/05_user_guide/3_api/intro.md           |  15 -
 .../current/05_user_guide/_category_.json          |   8 -
 .../current/05_user_guide/intro.md                 |  19 -
 .../current/06_plugin/1_auth_provider.md           | 386 ---------------
 .../current/06_plugin/2_event_collector.md         |  42 --
 .../current/06_plugin/3_resource_throttler.md      | 135 -----
 .../4_setting_provider/1_tenantsetting.md          |  49 --
 .../06_plugin/4_setting_provider/_category_.json   |   8 -
 .../current/06_plugin/4_setting_provider/intro.md  | 123 -----
 .../current/06_plugin/5_plugin_practice.md         |  73 ---
 .../current/06_plugin/_category_.json              |   8 -
 .../current/06_plugin/intro.md                     |  66 ---
 .../01_configuration/1_config_file_manual.md       | 116 -----
 .../01_configuration/2_bifromq_sys_props.md        |  54 --
 .../01_configuration/3_configs_print.md            |  88 ----
 .../01_configuration/_category_.json               |   8 -
 .../07_admin_guide/01_configuration/intro.md       |  11 -
 .../07_admin_guide/02_tuning/1_os_tuning_linux.md  |  58 ---
 .../07_admin_guide/02_tuning/_category_.json       |   8 -
 .../current/07_admin_guide/02_tuning/intro.md      |  29 --
 .../07_admin_guide/03_observability/01_logging.md  |  18 -
 .../07_admin_guide/03_observability/03_events.md   |  21 -
 .../03_observability/_category_.json               |   8 -
 .../07_admin_guide/03_observability/intro.md       |   7 -
 .../03_observability/metrics/_category_.json       |   8 -
 .../03_observability/metrics/intro.md              |  21 -
 .../03_observability/metrics/tenantmetrics.md      |  60 ---
 .../07_admin_guide/04_security/_category_.json     |   8 -
 .../current/07_admin_guide/04_security/intro.md    |  25 -
 .../current/07_admin_guide/_category_.json         |   8 -
 .../current/07_admin_guide/intro.md                |   7 -
 .../current/98_mqtt_best_practices/1_spec.md       |  11 -
 .../current/98_mqtt_best_practices/2_about_mqtt.md |  64 ---
 .../98_mqtt_best_practices/3_mqtt_parameters.md    |  49 --
 .../98_mqtt_best_practices/4_topicfilter_design.md |  32 --
 .../current/98_mqtt_best_practices/_category_.json |   8 -
 .../current/999_bifromq_inside.md                  |  18 -
 .../version-1.0.x.json                             | 130 -----
 .../version-1.0.x/00_Readme.md                     |  29 --
 .../version-1.0.x/01_intro/_category_.json         |   8 -
 .../version-1.0.x/01_intro/features_list.md        |  15 -
 .../02_get_started/1_quick_install.md              |  15 -
 .../version-1.0.x/02_get_started/2_connect_to.md   |  35 --
 .../version-1.0.x/02_get_started/_category_.json   |   8 -
 .../03_deploy/11_build_from_source.md              |  33 --
 .../03_deploy/1_deploy_with_docker.md              |  19 -
 .../version-1.0.x/03_deploy/21_cluster.md          |   9 -
 .../03_deploy/2_deploy_on_linux_mac.md             |  19 -
 .../version-1.0.x/03_deploy/3_deploy_on_windows.md |  20 -
 .../version-1.0.x/03_deploy/_category_.json        |   8 -
 .../04_configuration/1_configs_introduction.md     |  22 -
 .../04_configuration/2_file_configs_manual.md      | 414 ----------------
 .../04_configuration/3_performance_tuning_linux.md |  57 ---
 .../version-1.0.x/04_configuration/_category_.json |   8 -
 .../05_user_guide/1_connect/1_connect.md           |  22 -
 .../05_user_guide/1_connect/2_pubsub.md            |  41 --
 .../05_user_guide/1_connect/3_shared_sub.md        |  18 -
 .../05_user_guide/1_connect/_category_.json        |   8 -
 .../1_connect/images/pub-sub-pattern.png           | Bin 372353 -> 0 bytes
 .../1_connect/images/shared-subscription.png       | Bin 489533 -> 0 bytes
 .../05_user_guide/2_integration/1_integration.md   |  50 --
 .../05_user_guide/2_integration/_category_.json    |   8 -
 .../2_integration/images/integration.png           | Bin 300130 -> 0 bytes
 .../version-1.0.x/05_user_guide/3_API/1_api.md     |   7 -
 .../05_user_guide/3_API/_category_.json            |   8 -
 .../version-1.0.x/05_user_guide/_category_.json    |   8 -
 .../version-1.0.x/06_plugin/1_plugin.md            |  33 --
 .../version-1.0.x/06_plugin/2_auth_provider.md     | 161 ------
 .../version-1.0.x/06_plugin/3_event_collector.md   |  29 --
 .../version-1.0.x/06_plugin/4_setting_provider.md  |  28 --
 .../version-1.0.x/06_plugin/5_plugin_practice.md   |  53 --
 .../version-1.0.x/06_plugin/_category_.json        |   8 -
 .../version-1.0.x/07_operations/1_tls.md           |  18 -
 .../07_operations/2_high_availability.md           |   8 -
 .../07_operations/4_logs_observable.md             |  53 --
 .../version-1.0.x/07_operations/_category_.json    |   8 -
 .../08_best_practices/1_mqtt_parameters.md         |  40 --
 .../08_best_practices/2_topicfilter.md             |  20 -
 .../08_best_practices/_category_.json              |   8 -
 .../version-1.0.x/09_faq/1_bifromq.md              |  46 --
 .../version-1.0.x/09_faq/2_mqtt.md                 |  44 --
 .../version-1.0.x/09_faq/_category_.json           |   8 -
 .../version-1.0.x/21_mqtt/1_mqtt.md                |   9 -
 .../version-1.0.x/21_mqtt/_category_.json          |   8 -
 .../version-1.0.x/999_bifromq_inside.md            |  26 -
 .../version-1.0.x/99_test_report/1_test_report.md  | 416 ----------------
 .../version-1.0.x/99_test_report/_category_.json   |   8 -
 .../images/false_100_100_qos2_p1024_50mps/cpu.png  | Bin 144277 -> 0 bytes
 .../images/false_100_100_qos2_p1024_50mps/max.png  | Bin 416879 -> 0 bytes
 .../images/false_100_100_qos2_p1024_50mps/mean.png | Bin 396636 -> 0 bytes
 .../images/false_100_100_qos2_p1024_50mps/p99.png  | Bin 412952 -> 0 bytes
 .../images/false_100_100_qos2_p1024_50mps/qps.png  | Bin 387965 -> 0 bytes
 .../images/false_100_100_qos2_p32_50mps/cpu.png    | Bin 139366 -> 0 bytes
 .../images/false_100_100_qos2_p32_50mps/max.png    | Bin 426670 -> 0 bytes
 .../images/false_100_100_qos2_p32_50mps/mean.png   | Bin 403274 -> 0 bytes
 .../images/false_100_100_qos2_p32_50mps/p99.png    | Bin 402431 -> 0 bytes
 .../images/false_100_100_qos2_p32_50mps/qps.png    | Bin 399376 -> 0 bytes
 .../images/false_10k_10k_qos0_p1024_1mps/cpu.png   | Bin 181523 -> 0 bytes
 .../images/false_10k_10k_qos0_p1024_1mps/max.png   | Bin 412355 -> 0 bytes
 .../images/false_10k_10k_qos0_p1024_1mps/mean.png  | Bin 409719 -> 0 bytes
 .../images/false_10k_10k_qos0_p1024_1mps/p99.png   | Bin 407114 -> 0 bytes
 .../images/false_10k_10k_qos0_p1024_1mps/qps.png   | Bin 380534 -> 0 bytes
 .../images/false_10k_10k_qos0_p32_1mps/cpu.png     | Bin 151179 -> 0 bytes
 .../images/false_10k_10k_qos0_p32_1mps/max.png     | Bin 418104 -> 0 bytes
 .../images/false_10k_10k_qos0_p32_1mps/mean.png    | Bin 438550 -> 0 bytes
 .../images/false_10k_10k_qos0_p32_1mps/p99.png     | Bin 406292 -> 0 bytes
 .../images/false_10k_10k_qos0_p32_1mps/qps.png     | Bin 406159 -> 0 bytes
 .../images/false_10k_10k_qos1_p1024_1mps/cpu.png   | Bin 150383 -> 0 bytes
 .../images/false_10k_10k_qos1_p1024_1mps/max.png   | Bin 407178 -> 0 bytes
 .../images/false_10k_10k_qos1_p1024_1mps/mean.png  | Bin 408757 -> 0 bytes
 .../images/false_10k_10k_qos1_p1024_1mps/p99.png   | Bin 417178 -> 0 bytes
 .../images/false_10k_10k_qos1_p1024_1mps/qps.png   | Bin 388185 -> 0 bytes
 .../images/false_10k_10k_qos1_p32_1mps/cpu.png     | Bin 148967 -> 0 bytes
 .../images/false_10k_10k_qos1_p32_1mps/max.png     | Bin 435242 -> 0 bytes
 .../images/false_10k_10k_qos1_p32_1mps/mean.png    | Bin 413195 -> 0 bytes
 .../images/false_10k_10k_qos1_p32_1mps/p99.png     | Bin 409118 -> 0 bytes
 .../images/false_10k_10k_qos1_p32_1mps/qps.png     | Bin 386007 -> 0 bytes
 .../images/false_300_300_qos0_p1024_50mps/cpu.png  | Bin 140668 -> 0 bytes
 .../images/false_300_300_qos0_p1024_50mps/max.png  | Bin 426909 -> 0 bytes
 .../images/false_300_300_qos0_p1024_50mps/mean.png | Bin 403434 -> 0 bytes
 .../images/false_300_300_qos0_p1024_50mps/p99.png  | Bin 411867 -> 0 bytes
 .../images/false_300_300_qos0_p1024_50mps/qps.png  | Bin 384525 -> 0 bytes
 .../images/false_300_300_qos0_p32_50mps/cpu.png    | Bin 148995 -> 0 bytes
 .../images/false_300_300_qos0_p32_50mps/max.png    | Bin 418782 -> 0 bytes
 .../images/false_300_300_qos0_p32_50mps/mean.png   | Bin 385679 -> 0 bytes
 .../images/false_300_300_qos0_p32_50mps/p99.png    | Bin 398392 -> 0 bytes
 .../images/false_300_300_qos0_p32_50mps/qps.png    | Bin 380337 -> 0 bytes
 .../images/false_300_300_qos1_p1024_50mps/cpu.png  | Bin 153160 -> 0 bytes
 .../images/false_300_300_qos1_p1024_50mps/max.png  | Bin 430127 -> 0 bytes
 .../images/false_300_300_qos1_p1024_50mps/mean.png | Bin 418826 -> 0 bytes
 .../images/false_300_300_qos1_p1024_50mps/p99.png  | Bin 427629 -> 0 bytes
 .../images/false_300_300_qos1_p1024_50mps/qps.png  | Bin 413791 -> 0 bytes
 .../images/false_300_300_qos1_p32_50mps/cpu.png    | Bin 148886 -> 0 bytes
 .../images/false_300_300_qos1_p32_50mps/max.png    | Bin 426848 -> 0 bytes
 .../images/false_300_300_qos1_p32_50mps/mean.png   | Bin 402307 -> 0 bytes
 .../images/false_300_300_qos1_p32_50mps/p99.png    | Bin 402363 -> 0 bytes
 .../images/false_300_300_qos1_p32_50mps/qps.png    | Bin 382995 -> 0 bytes
 .../images/false_7k_7k_qos2_p1024_1mps/cpu.png     | Bin 153038 -> 0 bytes
 .../images/false_7k_7k_qos2_p1024_1mps/max.png     | Bin 443946 -> 0 bytes
 .../images/false_7k_7k_qos2_p1024_1mps/mean.png    | Bin 419643 -> 0 bytes
 .../images/false_7k_7k_qos2_p1024_1mps/p99.png     | Bin 420809 -> 0 bytes
 .../images/false_7k_7k_qos2_p1024_1mps/qps.png     | Bin 395388 -> 0 bytes
 .../images/false_7k_7k_qos2_p32_1mps/cpu.png       | Bin 157115 -> 0 bytes
 .../images/false_7k_7k_qos2_p32_1mps/max.png       | Bin 456877 -> 0 bytes
 .../images/false_7k_7k_qos2_p32_1mps/mean.png      | Bin 403394 -> 0 bytes
 .../images/false_7k_7k_qos2_p32_1mps/p99.png       | Bin 416945 -> 0 bytes
 .../images/false_7k_7k_qos2_p32_1mps/qps.png       | Bin 386818 -> 0 bytes
 .../share_false_40k_400_qos2_p1024_1mps/max.png    | Bin 75466 -> 0 bytes
 .../share_false_40k_400_qos2_p1024_1mps/mean.png   | Bin 62199 -> 0 bytes
 .../share_false_40k_400_qos2_p1024_1mps/p99.png    | Bin 63289 -> 0 bytes
 .../share_false_40k_400_qos2_p1024_1mps/qps.png    | Bin 50674 -> 0 bytes
 .../share_true_40k_400_qos2_p1024_1mps/max.png     | Bin 57071 -> 0 bytes
 .../share_true_40k_400_qos2_p1024_1mps/mean.png    | Bin 51961 -> 0 bytes
 .../share_true_40k_400_qos2_p1024_1mps/p99.png     | Bin 53321 -> 0 bytes
 .../share_true_40k_400_qos2_p1024_1mps/qps.png     | Bin 45945 -> 0 bytes
 .../images/true_1.2k_1.2k_qos2_p32_50mps/max.png   | Bin 88918 -> 0 bytes
 .../images/true_1.2k_1.2k_qos2_p32_50mps/mean.png  | Bin 61882 -> 0 bytes
 .../images/true_1.2k_1.2k_qos2_p32_50mps/p99.png   | Bin 67304 -> 0 bytes
 .../images/true_1.2k_1.2k_qos2_p32_50mps/qps.png   | Bin 56660 -> 0 bytes
 .../images/true_100k_100k_qos0_p1024_1mps/max.png  | Bin 63090 -> 0 bytes
 .../images/true_100k_100k_qos0_p1024_1mps/mean.png | Bin 46664 -> 0 bytes
 .../images/true_100k_100k_qos0_p1024_1mps/p99.png  | Bin 50996 -> 0 bytes
 .../images/true_100k_100k_qos0_p1024_1mps/qps.png  | Bin 48492 -> 0 bytes
 .../images/true_100k_100k_qos1_p1024_1mps/max.png  | Bin 406074 -> 0 bytes
 .../images/true_100k_100k_qos1_p1024_1mps/mean.png | Bin 400883 -> 0 bytes
 .../images/true_100k_100k_qos1_p1024_1mps/p99.png  | Bin 389508 -> 0 bytes
 .../images/true_100k_100k_qos1_p1024_1mps/qps.png  | Bin 408365 -> 0 bytes
 .../images/true_1_1k_qos1_p32_1mps/max.png         | Bin 381584 -> 0 bytes
 .../images/true_1_1k_qos1_p32_1mps/mean.png        | Bin 385563 -> 0 bytes
 .../images/true_1_1k_qos1_p32_1mps/p99.png         | Bin 374742 -> 0 bytes
 .../images/true_1_1k_qos1_p32_1mps/qps.png         | Bin 399221 -> 0 bytes
 .../images/true_2k_2k_qos1_p32_50mps/max.png       | Bin 69588 -> 0 bytes
 .../images/true_2k_2k_qos1_p32_50mps/mean.png      | Bin 58016 -> 0 bytes
 .../images/true_2k_2k_qos1_p32_50mps/p99.png       | Bin 66032 -> 0 bytes
 .../images/true_2k_2k_qos1_p32_50mps/qps.png       | Bin 59386 -> 0 bytes
 .../images/true_4k_4k_qos0_p32_50mps/max.png       | Bin 67266 -> 0 bytes
 .../images/true_4k_4k_qos0_p32_50mps/mean.png      | Bin 48735 -> 0 bytes
 .../images/true_4k_4k_qos0_p32_50mps/p99.png       | Bin 48530 -> 0 bytes
 .../images/true_4k_4k_qos0_p32_50mps/qps.png       | Bin 46111 -> 0 bytes
 .../images/true_50k_50k_qos2_p1024_1mps/max.png    | Bin 502302 -> 0 bytes
 .../images/true_50k_50k_qos2_p1024_1mps/mean.png   | Bin 469489 -> 0 bytes
 .../images/true_50k_50k_qos2_p1024_1mps/p99.png    | Bin 486299 -> 0 bytes
 .../images/true_50k_50k_qos2_p1024_1mps/qps.png    | Bin 418971 -> 0 bytes
 .../version-2.0.0/00_Readme.md                     |  29 --
 .../version-2.0.0/01_intro/_category_.json         |   8 -
 .../version-2.0.0/01_intro/features_list.md        |  15 -
 .../02_get_started/1_quick_install.md              |  15 -
 .../version-2.0.0/02_get_started/2_connect_to.md   |  35 --
 .../version-2.0.0/02_get_started/_category_.json   |   8 -
 .../03_deploy/11_build_from_source.md              |  33 --
 .../03_deploy/1_deploy_with_docker.md              |  38 --
 .../version-2.0.0/03_deploy/21_cluster.md          |  49 --
 .../03_deploy/2_deploy_on_linux_mac.md             |  19 -
 .../version-2.0.0/03_deploy/3_deploy_on_windows.md |  20 -
 .../version-2.0.0/03_deploy/_category_.json        |   8 -
 .../04_configuration/1_configs_introduction.md     |  22 -
 .../04_configuration/2_file_configs_manual.md      | 354 -------------
 .../04_configuration/3_performance_tuning_linux.md |  57 ---
 .../version-2.0.0/04_configuration/_category_.json |   8 -
 .../05_user_guide/1_connect/1_connect.md           |  22 -
 .../05_user_guide/1_connect/2_pubsub.md            |  41 --
 .../05_user_guide/1_connect/3_shared_sub.md        |  18 -
 .../05_user_guide/1_connect/_category_.json        |   8 -
 .../1_connect/images/pub-sub-pattern.png           | Bin 372353 -> 0 bytes
 .../1_connect/images/shared-subscription.png       | Bin 489533 -> 0 bytes
 .../05_user_guide/2_integration/1_integration.md   |  50 --
 .../05_user_guide/2_integration/_category_.json    |   8 -
 .../2_integration/images/integration.png           | Bin 300130 -> 0 bytes
 .../version-2.0.0/05_user_guide/3_API/1_api.md     |  89 ----
 .../05_user_guide/3_API/_category_.json            |   8 -
 .../05_user_guide/3_API/images/API-Arch.png        | Bin 25560 -> 0 bytes
 .../version-2.0.0/05_user_guide/_category_.json    |   8 -
 .../version-2.0.0/06_plugin/1_plugin.md            |  33 --
 .../version-2.0.0/06_plugin/2_auth_provider.md     | 161 ------
 .../version-2.0.0/06_plugin/3_event_collector.md   |  29 --
 .../version-2.0.0/06_plugin/4_setting_provider.md  |  28 --
 .../version-2.0.0/06_plugin/5_plugin_practice.md   |  53 --
 .../version-2.0.0/06_plugin/_category_.json        |   8 -
 .../version-2.0.0/07_operations/1_tls.md           |  18 -
 .../07_operations/2_high_availability.md           | 147 ------
 .../07_operations/4_logs_observable.md             |  53 --
 .../version-2.0.0/07_operations/5_api_service.md   |   8 -
 .../version-2.0.0/07_operations/_category_.json    |   8 -
 .../08_best_practices/1_mqtt_parameters.md         |  40 --
 .../08_best_practices/2_topicfilter.md             |  20 -
 .../08_best_practices/_category_.json              |   8 -
 .../version-2.0.0/09_faq/1_bifromq.md              |  46 --
 .../version-2.0.0/09_faq/2_mqtt.md                 |  44 --
 .../version-2.0.0/09_faq/_category_.json           |   8 -
 .../version-2.0.0/21_mqtt/1_mqtt.md                |   9 -
 .../version-2.0.0/21_mqtt/_category_.json          |   8 -
 .../version-2.0.0/999_bifromq_inside.md            |  26 -
 .../version-2.0.0/99_test_report/1_test_report.md  | 542 --------------------
 .../version-2.0.0/99_test_report/_category_.json   |   8 -
 .../images/conn-tcp-1M-5K_1n_false/conn.png        | Bin 154938 -> 0 bytes
 .../images/conn-tcp-1M-5K_1n_false/cpu.png         | Bin 141598 -> 0 bytes
 .../images/conn-tcp-1M-5K_1n_false/mem.png         | Bin 169402 -> 0 bytes
 .../images/conn-tcp-1M-5K_1n_true/conn.png         | Bin 143183 -> 0 bytes
 .../images/conn-tcp-1M-5K_1n_true/cpu.png          | Bin 144699 -> 0 bytes
 .../images/conn-tcp-1M-5K_1n_true/mem.png          | Bin 156081 -> 0 bytes
 .../false_15k_15k_qos0_p256_1mps_1n_1v/cpu.png     | Bin 123666 -> 0 bytes
 .../false_15k_15k_qos0_p256_1mps_1n_1v/max.png     | Bin 464098 -> 0 bytes
 .../false_15k_15k_qos0_p256_1mps_1n_1v/mean.png    | Bin 428201 -> 0 bytes
 .../false_15k_15k_qos0_p256_1mps_1n_1v/mem.png     | Bin 172684 -> 0 bytes
 .../false_15k_15k_qos0_p256_1mps_1n_1v/p99.png     | Bin 454402 -> 0 bytes
 .../false_15k_15k_qos0_p256_1mps_1n_1v/qps.png     | Bin 385090 -> 0 bytes
 .../false_15k_15k_qos0_p256_1mps_1n_1v/result.html |  72 ---
 .../false_15k_15k_qos0_p256_1mps_3n_3v/cpu.png     | Bin 162013 -> 0 bytes
 .../false_15k_15k_qos0_p256_1mps_3n_3v/max.png     | Bin 433171 -> 0 bytes
 .../false_15k_15k_qos0_p256_1mps_3n_3v/mean.png    | Bin 424642 -> 0 bytes
 .../false_15k_15k_qos0_p256_1mps_3n_3v/mem.png     | Bin 226554 -> 0 bytes
 .../false_15k_15k_qos0_p256_1mps_3n_3v/p99.png     | Bin 419426 -> 0 bytes
 .../false_15k_15k_qos0_p256_1mps_3n_3v/qps.png     | Bin 394889 -> 0 bytes
 .../false_15k_15k_qos0_p256_1mps_3n_3v/result.html |  72 ---
 .../false_15k_15k_qos1_p256_1mps_1n_1v/cpu.png     | Bin 154553 -> 0 bytes
 .../false_15k_15k_qos1_p256_1mps_1n_1v/max.png     | Bin 500700 -> 0 bytes
 .../false_15k_15k_qos1_p256_1mps_1n_1v/mean.png    | Bin 476241 -> 0 bytes
 .../false_15k_15k_qos1_p256_1mps_1n_1v/mem.png     | Bin 160913 -> 0 bytes
 .../false_15k_15k_qos1_p256_1mps_1n_1v/p99.png     | Bin 495851 -> 0 bytes
 .../false_15k_15k_qos1_p256_1mps_1n_1v/qps.png     | Bin 395368 -> 0 bytes
 .../false_15k_15k_qos1_p256_1mps_1n_1v/result.html |  72 ---
 .../false_15k_15k_qos1_p256_1mps_3n_3v/cpu.png     | Bin 166060 -> 0 bytes
 .../false_15k_15k_qos1_p256_1mps_3n_3v/max.png     | Bin 447771 -> 0 bytes
 .../false_15k_15k_qos1_p256_1mps_3n_3v/mean.png    | Bin 441286 -> 0 bytes
 .../false_15k_15k_qos1_p256_1mps_3n_3v/mem.png     | Bin 238005 -> 0 bytes
 .../false_15k_15k_qos1_p256_1mps_3n_3v/p99.png     | Bin 425698 -> 0 bytes
 .../false_15k_15k_qos1_p256_1mps_3n_3v/qps.png     | Bin 393608 -> 0 bytes
 .../false_15k_15k_qos1_p256_1mps_3n_3v/result.html |  72 ---
 .../false_300_300_qos0_p32_50mps_1n_1v/cpu.png     | Bin 152154 -> 0 bytes
 .../false_300_300_qos0_p32_50mps_1n_1v/max.png     | Bin 452335 -> 0 bytes
 .../false_300_300_qos0_p32_50mps_1n_1v/mean.png    | Bin 426291 -> 0 bytes
 .../false_300_300_qos0_p32_50mps_1n_1v/mem.png     | Bin 181177 -> 0 bytes
 .../false_300_300_qos0_p32_50mps_1n_1v/p99.png     | Bin 447715 -> 0 bytes
 .../false_300_300_qos0_p32_50mps_1n_1v/qps.png     | Bin 380611 -> 0 bytes
 .../false_300_300_qos0_p32_50mps_1n_1v/result.html |  72 ---
 .../false_300_300_qos0_p32_50mps_3n_3v/cpu.png     | Bin 158592 -> 0 bytes
 .../false_300_300_qos0_p32_50mps_3n_3v/max.png     | Bin 417698 -> 0 bytes
 .../false_300_300_qos0_p32_50mps_3n_3v/mean.png    | Bin 406755 -> 0 bytes
 .../false_300_300_qos0_p32_50mps_3n_3v/mem.png     | Bin 246060 -> 0 bytes
 .../false_300_300_qos0_p32_50mps_3n_3v/p99.png     | Bin 411946 -> 0 bytes
 .../false_300_300_qos0_p32_50mps_3n_3v/qps.png     | Bin 377671 -> 0 bytes
 .../false_300_300_qos0_p32_50mps_3n_3v/result.html |  72 ---
 .../false_300_300_qos1_p32_50mps_1n_1v/cpu.png     | Bin 152994 -> 0 bytes
 .../false_300_300_qos1_p32_50mps_1n_1v/max.png     | Bin 461409 -> 0 bytes
 .../false_300_300_qos1_p32_50mps_1n_1v/mean.png    | Bin 445612 -> 0 bytes
 .../false_300_300_qos1_p32_50mps_1n_1v/mem.png     | Bin 178475 -> 0 bytes
 .../false_300_300_qos1_p32_50mps_1n_1v/p99.png     | Bin 449759 -> 0 bytes
 .../false_300_300_qos1_p32_50mps_1n_1v/qps.png     | Bin 369940 -> 0 bytes
 .../false_300_300_qos1_p32_50mps_1n_1v/result.html |  72 ---
 .../false_300_300_qos1_p32_50mps_3n_3v/cpu.png     | Bin 154735 -> 0 bytes
 .../false_300_300_qos1_p32_50mps_3n_3v/max.png     | Bin 426501 -> 0 bytes
 .../false_300_300_qos1_p32_50mps_3n_3v/mean.png    | Bin 409864 -> 0 bytes
 .../false_300_300_qos1_p32_50mps_3n_3v/mem.png     | Bin 225135 -> 0 bytes
 .../false_300_300_qos1_p32_50mps_3n_3v/p99.png     | Bin 420962 -> 0 bytes
 .../false_300_300_qos1_p32_50mps_3n_3v/qps.png     | Bin 375985 -> 0 bytes
 .../false_300_300_qos1_p32_50mps_3n_3v/result.html |  72 ---
 .../false_30k_30k_qos0_p256_1mps_3n_1v/cpu.png     | Bin 135552 -> 0 bytes
 .../false_30k_30k_qos0_p256_1mps_3n_1v/max.png     | Bin 454618 -> 0 bytes
 .../false_30k_30k_qos0_p256_1mps_3n_1v/mean.png    | Bin 443931 -> 0 bytes
 .../false_30k_30k_qos0_p256_1mps_3n_1v/mem.png     | Bin 180545 -> 0 bytes
 .../false_30k_30k_qos0_p256_1mps_3n_1v/p99.png     | Bin 430081 -> 0 bytes
 .../false_30k_30k_qos0_p256_1mps_3n_1v/qps.png     | Bin 405348 -> 0 bytes
 .../false_30k_30k_qos0_p256_1mps_3n_1v/result.html |  72 ---
 .../false_30k_30k_qos1_p256_1mps_3n_1v/cpu.png     | Bin 138119 -> 0 bytes
 .../false_30k_30k_qos1_p256_1mps_3n_1v/max.png     | Bin 481261 -> 0 bytes
 .../false_30k_30k_qos1_p256_1mps_3n_1v/mean.png    | Bin 465053 -> 0 bytes
 .../false_30k_30k_qos1_p256_1mps_3n_1v/mem.png     | Bin 206858 -> 0 bytes
 .../false_30k_30k_qos1_p256_1mps_3n_1v/p99.png     | Bin 472582 -> 0 bytes
 .../false_30k_30k_qos1_p256_1mps_3n_1v/qps.png     | Bin 407011 -> 0 bytes
 .../false_30k_30k_qos1_p256_1mps_3n_1v/result.html |  72 ---
 .../cpu.png                                        | Bin 179202 -> 0 bytes
 .../max.png                                        | Bin 457779 -> 0 bytes
 .../mean.png                                       | Bin 431350 -> 0 bytes
 .../mem.png                                        | Bin 223359 -> 0 bytes
 .../p99.png                                        | Bin 444413 -> 0 bytes
 .../qps.png                                        | Bin 451442 -> 0 bytes
 .../result.html                                    |  72 ---
 .../false_900_900_qos0_p32_50mps_3n_1v/cpu.png     | Bin 166447 -> 0 bytes
 .../false_900_900_qos0_p32_50mps_3n_1v/max.png     | Bin 464196 -> 0 bytes
 .../false_900_900_qos0_p32_50mps_3n_1v/mean.png    | Bin 410328 -> 0 bytes
 .../false_900_900_qos0_p32_50mps_3n_1v/mem.png     | Bin 230296 -> 0 bytes
 .../false_900_900_qos0_p32_50mps_3n_1v/p99.png     | Bin 408459 -> 0 bytes
 .../false_900_900_qos0_p32_50mps_3n_1v/qps.png     | Bin 376167 -> 0 bytes
 .../false_900_900_qos0_p32_50mps_3n_1v/result.html |  72 ---
 .../false_900_900_qos1_p32_50mps_3n_1v/cpu.png     | Bin 170995 -> 0 bytes
 .../false_900_900_qos1_p32_50mps_3n_1v/max.png     | Bin 402701 -> 0 bytes
 .../false_900_900_qos1_p32_50mps_3n_1v/mean.png    | Bin 424613 -> 0 bytes
 .../false_900_900_qos1_p32_50mps_3n_1v/mem.png     | Bin 241244 -> 0 bytes
 .../false_900_900_qos1_p32_50mps_3n_1v/p99.png     | Bin 419898 -> 0 bytes
 .../false_900_900_qos1_p32_50mps_3n_1v/qps.png     | Bin 371677 -> 0 bytes
 .../false_900_900_qos1_p32_50mps_3n_1v/result.html |  72 ---
 .../fanout_true_1_100000_qos0_p256_1mps_1n/cpu.png | Bin 172016 -> 0 bytes
 .../fanout_true_1_100000_qos0_p256_1mps_1n/max.png | Bin 406028 -> 0 bytes
 .../mean.png                                       | Bin 388088 -> 0 bytes
 .../fanout_true_1_100000_qos0_p256_1mps_1n/mem.png | Bin 168983 -> 0 bytes
 .../fanout_true_1_100000_qos0_p256_1mps_1n/p99.png | Bin 383266 -> 0 bytes
 .../fanout_true_1_100000_qos0_p256_1mps_1n/qps.png | Bin 424697 -> 0 bytes
 .../result.html                                    |  72 ---
 .../fanout_true_1_100000_qos1_p256_1mps_1n/cpu.png | Bin 128184 -> 0 bytes
 .../fanout_true_1_100000_qos1_p256_1mps_1n/max.png | Bin 424440 -> 0 bytes
 .../mean.png                                       | Bin 418194 -> 0 bytes
 .../fanout_true_1_100000_qos1_p256_1mps_1n/mem.png | Bin 166324 -> 0 bytes
 .../fanout_true_1_100000_qos1_p256_1mps_1n/p99.png | Bin 423369 -> 0 bytes
 .../fanout_true_1_100000_qos1_p256_1mps_1n/qps.png | Bin 430108 -> 0 bytes
 .../result.html                                    |  72 ---
 .../fanout_true_1_200000_qos1_p256_1mps_3n/cpu.png | Bin 162031 -> 0 bytes
 .../fanout_true_1_200000_qos1_p256_1mps_3n/max.png | Bin 395786 -> 0 bytes
 .../mean.png                                       | Bin 392969 -> 0 bytes
 .../fanout_true_1_200000_qos1_p256_1mps_3n/mem.png | Bin 204377 -> 0 bytes
 .../fanout_true_1_200000_qos1_p256_1mps_3n/p99.png | Bin 397443 -> 0 bytes
 .../fanout_true_1_200000_qos1_p256_1mps_3n/qps.png | Bin 370716 -> 0 bytes
 .../result.html                                    |  72 ---
 .../fanout_true_1_300000_qos0_p256_1mps_3n/cpu.png | Bin 158505 -> 0 bytes
 .../fanout_true_1_300000_qos0_p256_1mps_3n/max.png | Bin 397019 -> 0 bytes
 .../mean.png                                       | Bin 394834 -> 0 bytes
 .../fanout_true_1_300000_qos0_p256_1mps_3n/mem.png | Bin 207535 -> 0 bytes
 .../fanout_true_1_300000_qos0_p256_1mps_3n/p99.png | Bin 389659 -> 0 bytes
 .../fanout_true_1_300000_qos0_p256_1mps_3n/qps.png | Bin 391466 -> 0 bytes
 .../result.html                                    |  72 ---
 .../share_true_100k_1000_qos0_p256_1mps_1n/cpu.png | Bin 153585 -> 0 bytes
 .../share_true_100k_1000_qos0_p256_1mps_1n/max.png | Bin 444477 -> 0 bytes
 .../mean.png                                       | Bin 408732 -> 0 bytes
 .../share_true_100k_1000_qos0_p256_1mps_1n/mem.png | Bin 153019 -> 0 bytes
 .../share_true_100k_1000_qos0_p256_1mps_1n/p99.png | Bin 415750 -> 0 bytes
 .../share_true_100k_1000_qos0_p256_1mps_1n/qps.png | Bin 373232 -> 0 bytes
 .../result.html                                    |  72 ---
 .../share_true_100k_1000_qos1_p256_1mps_1n/cpu.png | Bin 163185 -> 0 bytes
 .../share_true_100k_1000_qos1_p256_1mps_1n/max.png | Bin 475347 -> 0 bytes
 .../mean.png                                       | Bin 461658 -> 0 bytes
 .../share_true_100k_1000_qos1_p256_1mps_1n/mem.png | Bin 162004 -> 0 bytes
 .../share_true_100k_1000_qos1_p256_1mps_1n/p99.png | Bin 433140 -> 0 bytes
 .../share_true_100k_1000_qos1_p256_1mps_1n/qps.png | Bin 365089 -> 0 bytes
 .../result.html                                    |  72 ---
 .../share_true_200k_2000_qos1_p256_1mps_3n/cpu.png | Bin 156053 -> 0 bytes
 .../share_true_200k_2000_qos1_p256_1mps_3n/max.png | Bin 433168 -> 0 bytes
 .../mean.png                                       | Bin 431424 -> 0 bytes
 .../share_true_200k_2000_qos1_p256_1mps_3n/mem.png | Bin 203666 -> 0 bytes
 .../share_true_200k_2000_qos1_p256_1mps_3n/p99.png | Bin 431871 -> 0 bytes
 .../share_true_200k_2000_qos1_p256_1mps_3n/qps.png | Bin 358857 -> 0 bytes
 .../result.html                                    |  72 ---
 .../share_true_300k_3000_qos0_p256_1mps_3n/cpu.png | Bin 140421 -> 0 bytes
 .../share_true_300k_3000_qos0_p256_1mps_3n/max.png | Bin 422790 -> 0 bytes
 .../mean.png                                       | Bin 393642 -> 0 bytes
 .../share_true_300k_3000_qos0_p256_1mps_3n/mem.png | Bin 194556 -> 0 bytes
 .../share_true_300k_3000_qos0_p256_1mps_3n/p99.png | Bin 392244 -> 0 bytes
 .../share_true_300k_3000_qos0_p256_1mps_3n/qps.png | Bin 368275 -> 0 bytes
 .../result.html                                    |  72 ---
 .../true_100k_100k_qos0_p256_1mps_1n/cpu.png       | Bin 165031 -> 0 bytes
 .../true_100k_100k_qos0_p256_1mps_1n/max.png       | Bin 450775 -> 0 bytes
 .../true_100k_100k_qos0_p256_1mps_1n/mean.png      | Bin 425118 -> 0 bytes
 .../true_100k_100k_qos0_p256_1mps_1n/mem.png       | Bin 153881 -> 0 bytes
 .../true_100k_100k_qos0_p256_1mps_1n/p99.png       | Bin 419483 -> 0 bytes
 .../true_100k_100k_qos0_p256_1mps_1n/qps.png       | Bin 378326 -> 0 bytes
 .../true_100k_100k_qos0_p256_1mps_1n/result.html   |  72 ---
 .../true_100k_100k_qos1_p256_1mps_1n/cpu.png       | Bin 128096 -> 0 bytes
 .../true_100k_100k_qos1_p256_1mps_1n/max.png       | Bin 500804 -> 0 bytes
 .../true_100k_100k_qos1_p256_1mps_1n/mean.png      | Bin 514095 -> 0 bytes
 .../true_100k_100k_qos1_p256_1mps_1n/mem.png       | Bin 149756 -> 0 bytes
 .../true_100k_100k_qos1_p256_1mps_1n/p99.png       | Bin 501140 -> 0 bytes
 .../true_100k_100k_qos1_p256_1mps_1n/qps.png       | Bin 398965 -> 0 bytes
 .../true_100k_100k_qos1_p256_1mps_1n/result.html   |  72 ---
 .../images/true_2k_2k_qos0_p32_100mps_1n/cpu.png   | Bin 130674 -> 0 bytes
 .../images/true_2k_2k_qos0_p32_100mps_1n/max.png   | Bin 419834 -> 0 bytes
 .../images/true_2k_2k_qos0_p32_100mps_1n/mean.png  | Bin 400016 -> 0 bytes
 .../images/true_2k_2k_qos0_p32_100mps_1n/mem.png   | Bin 150831 -> 0 bytes
 .../images/true_2k_2k_qos0_p32_100mps_1n/p99.png   | Bin 387414 -> 0 bytes
 .../images/true_2k_2k_qos0_p32_100mps_1n/qps.png   | Bin 358720 -> 0 bytes
 .../true_2k_2k_qos0_p32_100mps_1n/result.html      |  72 ---
 .../images/true_2k_2k_qos1_p32_100mps_1n/cpu.png   | Bin 145116 -> 0 bytes
 .../images/true_2k_2k_qos1_p32_100mps_1n/max.png   | Bin 472108 -> 0 bytes
 .../images/true_2k_2k_qos1_p32_100mps_1n/mean.png  | Bin 468209 -> 0 bytes
 .../images/true_2k_2k_qos1_p32_100mps_1n/mem.png   | Bin 150551 -> 0 bytes
 .../images/true_2k_2k_qos1_p32_100mps_1n/p99.png   | Bin 455661 -> 0 bytes
 .../images/true_2k_2k_qos1_p32_100mps_1n/qps.png   | Bin 385653 -> 0 bytes
 .../true_2k_2k_qos1_p32_100mps_1n/result.html      |  72 ---
 .../true_300k_300k_qos0_p256_1mps_3n/cpu.png       | Bin 133597 -> 0 bytes
 .../true_300k_300k_qos0_p256_1mps_3n/max.png       | Bin 460801 -> 0 bytes
 .../true_300k_300k_qos0_p256_1mps_3n/mean.png      | Bin 423561 -> 0 bytes
 .../true_300k_300k_qos0_p256_1mps_3n/mem.png       | Bin 196444 -> 0 bytes
 .../true_300k_300k_qos0_p256_1mps_3n/p99.png       | Bin 440019 -> 0 bytes
 .../true_300k_300k_qos0_p256_1mps_3n/qps.png       | Bin 399201 -> 0 bytes
 .../true_300k_300k_qos0_p256_1mps_3n/result.html   |  72 ---
 .../images/true_4k_4k_qos1_p32_100mps_3n/cpu.png   | Bin 152694 -> 0 bytes
 .../images/true_4k_4k_qos1_p32_100mps_3n/max.png   | Bin 447799 -> 0 bytes
 .../images/true_4k_4k_qos1_p32_100mps_3n/mean.png  | Bin 449679 -> 0 bytes
 .../images/true_4k_4k_qos1_p32_100mps_3n/mem.png   | Bin 184322 -> 0 bytes
 .../images/true_4k_4k_qos1_p32_100mps_3n/p99.png   | Bin 446368 -> 0 bytes
 .../images/true_4k_4k_qos1_p32_100mps_3n/qps.png   | Bin 424682 -> 0 bytes
 .../true_4k_4k_qos1_p32_100mps_3n/result.html      |  72 ---
 .../images/true_5k_5k_qos0_p32_100mps_3n/cpu.png   | Bin 142972 -> 0 bytes
 .../images/true_5k_5k_qos0_p32_100mps_3n/max.png   | Bin 434018 -> 0 bytes
 .../images/true_5k_5k_qos0_p32_100mps_3n/mean.png  | Bin 388755 -> 0 bytes
 .../images/true_5k_5k_qos0_p32_100mps_3n/mem.png   | Bin 185043 -> 0 bytes
 .../images/true_5k_5k_qos0_p32_100mps_3n/p99.png   | Bin 395682 -> 0 bytes
 .../images/true_5k_5k_qos0_p32_100mps_3n/qps.png   | Bin 398963 -> 0 bytes
 .../true_5k_5k_qos0_p32_100mps_3n/result.html      |  72 ---
 .../version-2.1.x/00_Readme.md                     |  29 --
 .../version-2.1.x/01_intro/_category_.json         |   8 -
 .../version-2.1.x/01_intro/features_list.md        |  15 -
 .../02_get_started/1_quick_install.md              |  15 -
 .../version-2.1.x/02_get_started/2_connect_to.md   |  35 --
 .../version-2.1.x/02_get_started/_category_.json   |   8 -
 .../03_deploy/11_build_from_source.md              |  33 --
 .../03_deploy/1_deploy_with_docker.md              |  38 --
 .../version-2.1.x/03_deploy/21_cluster.md          |  49 --
 .../03_deploy/2_deploy_on_linux_mac.md             |  19 -
 .../version-2.1.x/03_deploy/3_deploy_on_windows.md |  20 -
 .../version-2.1.x/03_deploy/_category_.json        |   8 -
 .../04_configuration/1_configs_introduction.md     |  22 -
 .../04_configuration/2_file_configs_manual.md      | 354 -------------
 .../04_configuration/3_performance_tuning_linux.md |  61 ---
 .../04_configuration/4_configs_print.md            |  92 ----
 .../version-2.1.x/04_configuration/_category_.json |   8 -
 .../05_user_guide/1_connect/1_connect.md           |  22 -
 .../05_user_guide/1_connect/2_pubsub.md            |  41 --
 .../05_user_guide/1_connect/3_shared_sub.md        |  18 -
 .../05_user_guide/1_connect/_category_.json        |   8 -
 .../1_connect/images/pub-sub-pattern.png           | Bin 372353 -> 0 bytes
 .../1_connect/images/shared-subscription.png       | Bin 489533 -> 0 bytes
 .../05_user_guide/2_integration/1_integration.md   |  50 --
 .../05_user_guide/2_integration/_category_.json    |   8 -
 .../2_integration/images/integration.png           | Bin 300130 -> 0 bytes
 .../version-2.1.x/05_user_guide/3_API/1_api.md     |  89 ----
 .../05_user_guide/3_API/_category_.json            |   8 -
 .../05_user_guide/3_API/images/API-Arch.png        | Bin 25560 -> 0 bytes
 .../version-2.1.x/05_user_guide/_category_.json    |   8 -
 .../version-2.1.x/06_plugin/1_plugin.md            |  33 --
 .../version-2.1.x/06_plugin/2_auth_provider.md     | 161 ------
 .../version-2.1.x/06_plugin/3_event_collector.md   |  29 --
 .../version-2.1.x/06_plugin/4_setting_provider.md  |  28 --
 .../version-2.1.x/06_plugin/5_plugin_practice.md   |  53 --
 .../version-2.1.x/06_plugin/_category_.json        |   8 -
 .../version-2.1.x/07_operations/1_tls.md           |  18 -
 .../07_operations/2_high_availability.md           | 147 ------
 .../07_operations/4_logs_observable.md             |  53 --
 .../version-2.1.x/07_operations/5_api_service.md   |   8 -
 .../version-2.1.x/07_operations/_category_.json    |   8 -
 .../08_best_practices/1_mqtt_parameters.md         |  40 --
 .../08_best_practices/2_topicfilter.md             |  20 -
 .../08_best_practices/_category_.json              |   8 -
 .../version-2.1.x/09_faq/1_bifromq.md              |  46 --
 .../version-2.1.x/09_faq/2_mqtt.md                 |  44 --
 .../version-2.1.x/09_faq/_category_.json           |   8 -
 .../version-2.1.x/21_mqtt/1_mqtt.md                |   9 -
 .../version-2.1.x/21_mqtt/_category_.json          |   8 -
 .../version-2.1.x/999_bifromq_inside.md            |  26 -
 .../version-2.1.x/99_test_report/1_test_report.md  | 542 --------------------
 .../version-2.1.x/99_test_report/_category_.json   |   8 -
 .../images/conn-tcp-1M-5K_1n_false/conn.png        | Bin 154938 -> 0 bytes
 .../images/conn-tcp-1M-5K_1n_false/cpu.png         | Bin 141598 -> 0 bytes
 .../images/conn-tcp-1M-5K_1n_false/mem.png         | Bin 169402 -> 0 bytes
 .../images/conn-tcp-1M-5K_1n_true/conn.png         | Bin 143183 -> 0 bytes
 .../images/conn-tcp-1M-5K_1n_true/cpu.png          | Bin 144699 -> 0 bytes
 .../images/conn-tcp-1M-5K_1n_true/mem.png          | Bin 156081 -> 0 bytes
 .../false_15k_15k_qos0_p256_1mps_1n_1v/cpu.png     | Bin 123666 -> 0 bytes
 .../false_15k_15k_qos0_p256_1mps_1n_1v/max.png     | Bin 464098 -> 0 bytes
 .../false_15k_15k_qos0_p256_1mps_1n_1v/mean.png    | Bin 428201 -> 0 bytes
 .../false_15k_15k_qos0_p256_1mps_1n_1v/mem.png     | Bin 172684 -> 0 bytes
 .../false_15k_15k_qos0_p256_1mps_1n_1v/p99.png     | Bin 454402 -> 0 bytes
 .../false_15k_15k_qos0_p256_1mps_1n_1v/qps.png     | Bin 385090 -> 0 bytes
 .../false_15k_15k_qos0_p256_1mps_1n_1v/result.html |  72 ---
 .../false_15k_15k_qos0_p256_1mps_3n_3v/cpu.png     | Bin 162013 -> 0 bytes
 .../false_15k_15k_qos0_p256_1mps_3n_3v/max.png     | Bin 433171 -> 0 bytes
 .../false_15k_15k_qos0_p256_1mps_3n_3v/mean.png    | Bin 424642 -> 0 bytes
 .../false_15k_15k_qos0_p256_1mps_3n_3v/mem.png     | Bin 226554 -> 0 bytes
 .../false_15k_15k_qos0_p256_1mps_3n_3v/p99.png     | Bin 419426 -> 0 bytes
 .../false_15k_15k_qos0_p256_1mps_3n_3v/qps.png     | Bin 394889 -> 0 bytes
 .../false_15k_15k_qos0_p256_1mps_3n_3v/result.html |  72 ---
 .../false_15k_15k_qos1_p256_1mps_1n_1v/cpu.png     | Bin 154553 -> 0 bytes
 .../false_15k_15k_qos1_p256_1mps_1n_1v/max.png     | Bin 500700 -> 0 bytes
 .../false_15k_15k_qos1_p256_1mps_1n_1v/mean.png    | Bin 476241 -> 0 bytes
 .../false_15k_15k_qos1_p256_1mps_1n_1v/mem.png     | Bin 160913 -> 0 bytes
 .../false_15k_15k_qos1_p256_1mps_1n_1v/p99.png     | Bin 495851 -> 0 bytes
 .../false_15k_15k_qos1_p256_1mps_1n_1v/qps.png     | Bin 395368 -> 0 bytes
 .../false_15k_15k_qos1_p256_1mps_1n_1v/result.html |  72 ---
 .../false_15k_15k_qos1_p256_1mps_3n_3v/cpu.png     | Bin 166060 -> 0 bytes
 .../false_15k_15k_qos1_p256_1mps_3n_3v/max.png     | Bin 447771 -> 0 bytes
 .../false_15k_15k_qos1_p256_1mps_3n_3v/mean.png    | Bin 441286 -> 0 bytes
 .../false_15k_15k_qos1_p256_1mps_3n_3v/mem.png     | Bin 238005 -> 0 bytes
 .../false_15k_15k_qos1_p256_1mps_3n_3v/p99.png     | Bin 425698 -> 0 bytes
 .../false_15k_15k_qos1_p256_1mps_3n_3v/qps.png     | Bin 393608 -> 0 bytes
 .../false_15k_15k_qos1_p256_1mps_3n_3v/result.html |  72 ---
 .../false_300_300_qos0_p32_50mps_1n_1v/cpu.png     | Bin 152154 -> 0 bytes
 .../false_300_300_qos0_p32_50mps_1n_1v/max.png     | Bin 452335 -> 0 bytes
 .../false_300_300_qos0_p32_50mps_1n_1v/mean.png    | Bin 426291 -> 0 bytes
 .../false_300_300_qos0_p32_50mps_1n_1v/mem.png     | Bin 181177 -> 0 bytes
 .../false_300_300_qos0_p32_50mps_1n_1v/p99.png     | Bin 447715 -> 0 bytes
 .../false_300_300_qos0_p32_50mps_1n_1v/qps.png     | Bin 380611 -> 0 bytes
 .../false_300_300_qos0_p32_50mps_1n_1v/result.html |  72 ---
 .../false_300_300_qos0_p32_50mps_3n_3v/cpu.png     | Bin 158592 -> 0 bytes
 .../false_300_300_qos0_p32_50mps_3n_3v/max.png     | Bin 417698 -> 0 bytes
 .../false_300_300_qos0_p32_50mps_3n_3v/mean.png    | Bin 406755 -> 0 bytes
 .../false_300_300_qos0_p32_50mps_3n_3v/mem.png     | Bin 246060 -> 0 bytes
 .../false_300_300_qos0_p32_50mps_3n_3v/p99.png     | Bin 411946 -> 0 bytes
 .../false_300_300_qos0_p32_50mps_3n_3v/qps.png     | Bin 377671 -> 0 bytes
 .../false_300_300_qos0_p32_50mps_3n_3v/result.html |  72 ---
 .../false_300_300_qos1_p32_50mps_1n_1v/cpu.png     | Bin 152994 -> 0 bytes
 .../false_300_300_qos1_p32_50mps_1n_1v/max.png     | Bin 461409 -> 0 bytes
 .../false_300_300_qos1_p32_50mps_1n_1v/mean.png    | Bin 445612 -> 0 bytes
 .../false_300_300_qos1_p32_50mps_1n_1v/mem.png     | Bin 178475 -> 0 bytes
 .../false_300_300_qos1_p32_50mps_1n_1v/p99.png     | Bin 449759 -> 0 bytes
 .../false_300_300_qos1_p32_50mps_1n_1v/qps.png     | Bin 369940 -> 0 bytes
 .../false_300_300_qos1_p32_50mps_1n_1v/result.html |  72 ---
 .../false_300_300_qos1_p32_50mps_3n_3v/cpu.png     | Bin 154735 -> 0 bytes
 .../false_300_300_qos1_p32_50mps_3n_3v/max.png     | Bin 426501 -> 0 bytes
 .../false_300_300_qos1_p32_50mps_3n_3v/mean.png    | Bin 409864 -> 0 bytes
 .../false_300_300_qos1_p32_50mps_3n_3v/mem.png     | Bin 225135 -> 0 bytes
 .../false_300_300_qos1_p32_50mps_3n_3v/p99.png     | Bin 420962 -> 0 bytes
 .../false_300_300_qos1_p32_50mps_3n_3v/qps.png     | Bin 375985 -> 0 bytes
 .../false_300_300_qos1_p32_50mps_3n_3v/result.html |  72 ---
 .../false_30k_30k_qos0_p256_1mps_3n_1v/cpu.png     | Bin 135552 -> 0 bytes
 .../false_30k_30k_qos0_p256_1mps_3n_1v/max.png     | Bin 454618 -> 0 bytes
 .../false_30k_30k_qos0_p256_1mps_3n_1v/mean.png    | Bin 443931 -> 0 bytes
 .../false_30k_30k_qos0_p256_1mps_3n_1v/mem.png     | Bin 180545 -> 0 bytes
 .../false_30k_30k_qos0_p256_1mps_3n_1v/p99.png     | Bin 430081 -> 0 bytes
 .../false_30k_30k_qos0_p256_1mps_3n_1v/qps.png     | Bin 405348 -> 0 bytes
 .../false_30k_30k_qos0_p256_1mps_3n_1v/result.html |  72 ---
 .../false_30k_30k_qos1_p256_1mps_3n_1v/cpu.png     | Bin 138119 -> 0 bytes
 .../false_30k_30k_qos1_p256_1mps_3n_1v/max.png     | Bin 481261 -> 0 bytes
 .../false_30k_30k_qos1_p256_1mps_3n_1v/mean.png    | Bin 465053 -> 0 bytes
 .../false_30k_30k_qos1_p256_1mps_3n_1v/mem.png     | Bin 206858 -> 0 bytes
 .../false_30k_30k_qos1_p256_1mps_3n_1v/p99.png     | Bin 472582 -> 0 bytes
 .../false_30k_30k_qos1_p256_1mps_3n_1v/qps.png     | Bin 407011 -> 0 bytes
 .../false_30k_30k_qos1_p256_1mps_3n_1v/result.html |  72 ---
 .../cpu.png                                        | Bin 179202 -> 0 bytes
 .../max.png                                        | Bin 457779 -> 0 bytes
 .../mean.png                                       | Bin 431350 -> 0 bytes
 .../mem.png                                        | Bin 223359 -> 0 bytes
 .../p99.png                                        | Bin 444413 -> 0 bytes
 .../qps.png                                        | Bin 451442 -> 0 bytes
 .../result.html                                    |  72 ---
 .../false_900_900_qos0_p32_50mps_3n_1v/cpu.png     | Bin 166447 -> 0 bytes
 .../false_900_900_qos0_p32_50mps_3n_1v/max.png     | Bin 464196 -> 0 bytes
 .../false_900_900_qos0_p32_50mps_3n_1v/mean.png    | Bin 410328 -> 0 bytes
 .../false_900_900_qos0_p32_50mps_3n_1v/mem.png     | Bin 230296 -> 0 bytes
 .../false_900_900_qos0_p32_50mps_3n_1v/p99.png     | Bin 408459 -> 0 bytes
 .../false_900_900_qos0_p32_50mps_3n_1v/qps.png     | Bin 376167 -> 0 bytes
 .../false_900_900_qos0_p32_50mps_3n_1v/result.html |  72 ---
 .../false_900_900_qos1_p32_50mps_3n_1v/cpu.png     | Bin 170995 -> 0 bytes
 .../false_900_900_qos1_p32_50mps_3n_1v/max.png     | Bin 402701 -> 0 bytes
 .../false_900_900_qos1_p32_50mps_3n_1v/mean.png    | Bin 424613 -> 0 bytes
 .../false_900_900_qos1_p32_50mps_3n_1v/mem.png     | Bin 241244 -> 0 bytes
 .../false_900_900_qos1_p32_50mps_3n_1v/p99.png     | Bin 419898 -> 0 bytes
 .../false_900_900_qos1_p32_50mps_3n_1v/qps.png     | Bin 371677 -> 0 bytes
 .../false_900_900_qos1_p32_50mps_3n_1v/result.html |  72 ---
 .../fanout_true_1_100000_qos0_p256_1mps_1n/cpu.png | Bin 172016 -> 0 bytes
 .../fanout_true_1_100000_qos0_p256_1mps_1n/max.png | Bin 406028 -> 0 bytes
 .../mean.png                                       | Bin 388088 -> 0 bytes
 .../fanout_true_1_100000_qos0_p256_1mps_1n/mem.png | Bin 168983 -> 0 bytes
 .../fanout_true_1_100000_qos0_p256_1mps_1n/p99.png | Bin 383266 -> 0 bytes
 .../fanout_true_1_100000_qos0_p256_1mps_1n/qps.png | Bin 424697 -> 0 bytes
 .../result.html                                    |  72 ---
 .../fanout_true_1_100000_qos1_p256_1mps_1n/cpu.png | Bin 128184 -> 0 bytes
 .../fanout_true_1_100000_qos1_p256_1mps_1n/max.png | Bin 424440 -> 0 bytes
 .../mean.png                                       | Bin 418194 -> 0 bytes
 .../fanout_true_1_100000_qos1_p256_1mps_1n/mem.png | Bin 166324 -> 0 bytes
 .../fanout_true_1_100000_qos1_p256_1mps_1n/p99.png | Bin 423369 -> 0 bytes
 .../fanout_true_1_100000_qos1_p256_1mps_1n/qps.png | Bin 430108 -> 0 bytes
 .../result.html                                    |  72 ---
 .../fanout_true_1_200000_qos1_p256_1mps_3n/cpu.png | Bin 162031 -> 0 bytes
 .../fanout_true_1_200000_qos1_p256_1mps_3n/max.png | Bin 395786 -> 0 bytes
 .../mean.png                                       | Bin 392969 -> 0 bytes
 .../fanout_true_1_200000_qos1_p256_1mps_3n/mem.png | Bin 204377 -> 0 bytes
 .../fanout_true_1_200000_qos1_p256_1mps_3n/p99.png | Bin 397443 -> 0 bytes
 .../fanout_true_1_200000_qos1_p256_1mps_3n/qps.png | Bin 370716 -> 0 bytes
 .../result.html                                    |  72 ---
 .../fanout_true_1_300000_qos0_p256_1mps_3n/cpu.png | Bin 158505 -> 0 bytes
 .../fanout_true_1_300000_qos0_p256_1mps_3n/max.png | Bin 397019 -> 0 bytes
 .../mean.png                                       | Bin 394834 -> 0 bytes
 .../fanout_true_1_300000_qos0_p256_1mps_3n/mem.png | Bin 207535 -> 0 bytes
 .../fanout_true_1_300000_qos0_p256_1mps_3n/p99.png | Bin 389659 -> 0 bytes
 .../fanout_true_1_300000_qos0_p256_1mps_3n/qps.png | Bin 391466 -> 0 bytes
 .../result.html                                    |  72 ---
 .../share_true_100k_1000_qos0_p256_1mps_1n/cpu.png | Bin 153585 -> 0 bytes
 .../share_true_100k_1000_qos0_p256_1mps_1n/max.png | Bin 444477 -> 0 bytes
 .../mean.png                                       | Bin 408732 -> 0 bytes
 .../share_true_100k_1000_qos0_p256_1mps_1n/mem.png | Bin 153019 -> 0 bytes
 .../share_true_100k_1000_qos0_p256_1mps_1n/p99.png | Bin 415750 -> 0 bytes
 .../share_true_100k_1000_qos0_p256_1mps_1n/qps.png | Bin 373232 -> 0 bytes
 .../result.html                                    |  72 ---
 .../share_true_100k_1000_qos1_p256_1mps_1n/cpu.png | Bin 163185 -> 0 bytes
 .../share_true_100k_1000_qos1_p256_1mps_1n/max.png | Bin 475347 -> 0 bytes
 .../mean.png                                       | Bin 461658 -> 0 bytes
 .../share_true_100k_1000_qos1_p256_1mps_1n/mem.png | Bin 162004 -> 0 bytes
 .../share_true_100k_1000_qos1_p256_1mps_1n/p99.png | Bin 433140 -> 0 bytes
 .../share_true_100k_1000_qos1_p256_1mps_1n/qps.png | Bin 365089 -> 0 bytes
 .../result.html                                    |  72 ---
 .../share_true_200k_2000_qos1_p256_1mps_3n/cpu.png | Bin 156053 -> 0 bytes
 .../share_true_200k_2000_qos1_p256_1mps_3n/max.png | Bin 433168 -> 0 bytes
 .../mean.png                                       | Bin 431424 -> 0 bytes
 .../share_true_200k_2000_qos1_p256_1mps_3n/mem.png | Bin 203666 -> 0 bytes
 .../share_true_200k_2000_qos1_p256_1mps_3n/p99.png | Bin 431871 -> 0 bytes
 .../share_true_200k_2000_qos1_p256_1mps_3n/qps.png | Bin 358857 -> 0 bytes
 .../result.html                                    |  72 ---
 .../share_true_300k_3000_qos0_p256_1mps_3n/cpu.png | Bin 140421 -> 0 bytes
 .../share_true_300k_3000_qos0_p256_1mps_3n/max.png | Bin 422790 -> 0 bytes
 .../mean.png                                       | Bin 393642 -> 0 bytes
 .../share_true_300k_3000_qos0_p256_1mps_3n/mem.png | Bin 194556 -> 0 bytes
 .../share_true_300k_3000_qos0_p256_1mps_3n/p99.png | Bin 392244 -> 0 bytes
 .../share_true_300k_3000_qos0_p256_1mps_3n/qps.png | Bin 368275 -> 0 bytes
 .../result.html                                    |  72 ---
 .../true_100k_100k_qos0_p256_1mps_1n/cpu.png       | Bin 165031 -> 0 bytes
 .../true_100k_100k_qos0_p256_1mps_1n/max.png       | Bin 450775 -> 0 bytes
 .../true_100k_100k_qos0_p256_1mps_1n/mean.png      | Bin 425118 -> 0 bytes
 .../true_100k_100k_qos0_p256_1mps_1n/mem.png       | Bin 153881 -> 0 bytes
 .../true_100k_100k_qos0_p256_1mps_1n/p99.png       | Bin 419483 -> 0 bytes
 .../true_100k_100k_qos0_p256_1mps_1n/qps.png       | Bin 378326 -> 0 bytes
 .../true_100k_100k_qos0_p256_1mps_1n/result.html   |  72 ---
 .../true_100k_100k_qos1_p256_1mps_1n/cpu.png       | Bin 128096 -> 0 bytes
 .../true_100k_100k_qos1_p256_1mps_1n/max.png       | Bin 500804 -> 0 bytes
 .../true_100k_100k_qos1_p256_1mps_1n/mean.png      | Bin 514095 -> 0 bytes
 .../true_100k_100k_qos1_p256_1mps_1n/mem.png       | Bin 149756 -> 0 bytes
 .../true_100k_100k_qos1_p256_1mps_1n/p99.png       | Bin 501140 -> 0 bytes
 .../true_100k_100k_qos1_p256_1mps_1n/qps.png       | Bin 398965 -> 0 bytes
 .../true_100k_100k_qos1_p256_1mps_1n/result.html   |  72 ---
 .../images/true_2k_2k_qos0_p32_100mps_1n/cpu.png   | Bin 130674 -> 0 bytes
 .../images/true_2k_2k_qos0_p32_100mps_1n/max.png   | Bin 419834 -> 0 bytes
 .../images/true_2k_2k_qos0_p32_100mps_1n/mean.png  | Bin 400016 -> 0 bytes
 .../images/true_2k_2k_qos0_p32_100mps_1n/mem.png   | Bin 150831 -> 0 bytes
 .../images/true_2k_2k_qos0_p32_100mps_1n/p99.png   | Bin 387414 -> 0 bytes
 .../images/true_2k_2k_qos0_p32_100mps_1n/qps.png   | Bin 358720 -> 0 bytes
 .../true_2k_2k_qos0_p32_100mps_1n/result.html      |  72 ---
 .../images/true_2k_2k_qos1_p32_100mps_1n/cpu.png   | Bin 145116 -> 0 bytes
 .../images/true_2k_2k_qos1_p32_100mps_1n/max.png   | Bin 472108 -> 0 bytes
 .../images/true_2k_2k_qos1_p32_100mps_1n/mean.png  | Bin 468209 -> 0 bytes
 .../images/true_2k_2k_qos1_p32_100mps_1n/mem.png   | Bin 150551 -> 0 bytes
 .../images/true_2k_2k_qos1_p32_100mps_1n/p99.png   | Bin 455661 -> 0 bytes
 .../images/true_2k_2k_qos1_p32_100mps_1n/qps.png   | Bin 385653 -> 0 bytes
 .../true_2k_2k_qos1_p32_100mps_1n/result.html      |  72 ---
 .../true_300k_300k_qos0_p256_1mps_3n/cpu.png       | Bin 133597 -> 0 bytes
 .../true_300k_300k_qos0_p256_1mps_3n/max.png       | Bin 460801 -> 0 bytes
 .../true_300k_300k_qos0_p256_1mps_3n/mean.png      | Bin 423561 -> 0 bytes
 .../true_300k_300k_qos0_p256_1mps_3n/mem.png       | Bin 196444 -> 0 bytes
 .../true_300k_300k_qos0_p256_1mps_3n/p99.png       | Bin 440019 -> 0 bytes
 .../true_300k_300k_qos0_p256_1mps_3n/qps.png       | Bin 399201 -> 0 bytes
 .../true_300k_300k_qos0_p256_1mps_3n/result.html   |  72 ---
 .../images/true_4k_4k_qos1_p32_100mps_3n/cpu.png   | Bin 152694 -> 0 bytes
 .../images/true_4k_4k_qos1_p32_100mps_3n/max.png   | Bin 447799 -> 0 bytes
 .../images/true_4k_4k_qos1_p32_100mps_3n/mean.png  | Bin 449679 -> 0 bytes
 .../images/true_4k_4k_qos1_p32_100mps_3n/mem.png   | Bin 184322 -> 0 bytes
 .../images/true_4k_4k_qos1_p32_100mps_3n/p99.png   | Bin 446368 -> 0 bytes
 .../images/true_4k_4k_qos1_p32_100mps_3n/qps.png   | Bin 424682 -> 0 bytes
 .../true_4k_4k_qos1_p32_100mps_3n/result.html      |  72 ---
 .../images/true_5k_5k_qos0_p32_100mps_3n/cpu.png   | Bin 142972 -> 0 bytes
 .../images/true_5k_5k_qos0_p32_100mps_3n/max.png   | Bin 434018 -> 0 bytes
 .../images/true_5k_5k_qos0_p32_100mps_3n/mean.png  | Bin 388755 -> 0 bytes
 .../images/true_5k_5k_qos0_p32_100mps_3n/mem.png   | Bin 185043 -> 0 bytes
 .../images/true_5k_5k_qos0_p32_100mps_3n/p99.png   | Bin 395682 -> 0 bytes
 .../images/true_5k_5k_qos0_p32_100mps_3n/qps.png   | Bin 398963 -> 0 bytes
 .../true_5k_5k_qos0_p32_100mps_3n/result.html      |  72 ---
 .../01_get_started/1_quick_install.md              |  13 -
 .../version-3.0.x/01_get_started/2_quick_verify.md |  30 --
 .../version-3.0.x/01_get_started/3_faq.md          |  44 --
 .../version-3.0.x/01_get_started/_category_.json   |   8 -
 .../01_get_started/images/newconn.jpg              | Bin 312148 -> 0 bytes
 .../01_get_started/images/publish.jpg              | Bin 298876 -> 0 bytes
 .../01_get_started/images/subscribe.jpg            | Bin 211030 -> 0 bytes
 .../version-3.0.x/01_get_started/intro.md          |  43 --
 .../version-3.0.x/02_installation/1_docker.md      |  35 --
 .../version-3.0.x/02_installation/2_linux.md       |  16 -
 .../version-3.0.x/02_installation/3_windows.md     |  17 -
 .../02_installation/4_install_from_source.md       |  32 --
 .../02_installation/5_config_migration.md          |   8 -
 .../02_installation/6_nodes_on_k8s.md              |  32 --
 .../version-3.0.x/02_installation/_category_.json  |   8 -
 .../version-3.0.x/02_installation/intro.md         |  39 --
 .../version-3.0.x/04_cluster/1_standardcluster.md  |  65 ---
 .../04_cluster/2_high_availability.md              | 107 ----
 .../version-3.0.x/04_cluster/_category_.json       |   8 -
 .../04_cluster/images/IndependentWorkload.png      | Bin 231896 -> 0 bytes
 .../version-3.0.x/04_cluster/intro.md              |  34 --
 .../05_user_guide/1_basic/1_connect.md             |  20 -
 .../05_user_guide/1_basic/2_pubsub.md              |  39 --
 .../05_user_guide/1_basic/3_shared_sub.md          |  21 -
 .../05_user_guide/1_basic/_category_.json          |   8 -
 .../1_basic/images/pub-sub-pattern.png             | Bin 372353 -> 0 bytes
 .../1_basic/images/shared-subscription.png         | Bin 489533 -> 0 bytes
 .../version-3.0.x/05_user_guide/1_basic/intro.md   |  17 -
 .../05_user_guide/2_integration/1_integration.md   |  26 -
 .../05_user_guide/2_integration/_category_.json    |   8 -
 .../2_integration/images/bifromqapproach.jpg       | Bin 133675 -> 0 bytes
 .../2_integration/images/commonapproach.jpg        | Bin 129120 -> 0 bytes
 .../2_integration/images/integration.png           | Bin 300130 -> 0 bytes
 .../05_user_guide/2_integration/intro.md           |  56 ---
 .../05_user_guide/3_api/1_api_reference.md         | 114 -----
 .../05_user_guide/3_api/_category_.json            |   8 -
 .../05_user_guide/3_api/images/API-Arch.png        | Bin 25560 -> 0 bytes
 .../version-3.0.x/05_user_guide/3_api/intro.md     |  15 -
 .../version-3.0.x/05_user_guide/_category_.json    |   8 -
 .../version-3.0.x/05_user_guide/intro.md           |  19 -
 .../version-3.0.x/06_plugin/1_auth_provider.md     | 386 ---------------
 .../version-3.0.x/06_plugin/2_event_collector.md   |  42 --
 .../06_plugin/3_resource_throttler.md              | 135 -----
 .../4_setting_provider/1_tenantsetting.md          |  49 --
 .../06_plugin/4_setting_provider/_category_.json   |   8 -
 .../06_plugin/4_setting_provider/intro.md          | 123 -----
 .../version-3.0.x/06_plugin/5_plugin_practice.md   |  44 --
 .../version-3.0.x/06_plugin/_category_.json        |   8 -
 .../version-3.0.x/06_plugin/intro.md               |  69 ---
 .../01_configuration/1_config_file_manual.md       | 114 -----
 .../01_configuration/2_bifromq_sys_props.md        |  49 --
 .../01_configuration/3_configs_print.md            |  89 ----
 .../01_configuration/_category_.json               |   8 -
 .../07_admin_guide/01_configuration/intro.md       |  11 -
 .../07_admin_guide/02_tuning/1_os_tuning_linux.md  |  58 ---
 .../07_admin_guide/02_tuning/_category_.json       |   8 -
 .../07_admin_guide/02_tuning/intro.md              |  29 --
 .../07_admin_guide/03_observability/01_logging.md  |  18 -
 .../07_admin_guide/03_observability/03_events.md   |  21 -
 .../03_observability/_category_.json               |   8 -
 .../07_admin_guide/03_observability/intro.md       |   7 -
 .../03_observability/metrics/_category_.json       |   8 -
 .../03_observability/metrics/intro.md              |  21 -
 .../03_observability/metrics/tenantmetrics.md      |  60 ---
 .../07_admin_guide/04_security/_category_.json     |   8 -
 .../07_admin_guide/04_security/intro.md            |  25 -
 .../version-3.0.x/07_admin_guide/_category_.json   |   8 -
 .../version-3.0.x/07_admin_guide/intro.md          |   7 -
 .../version-3.0.x/98_mqtt_best_practices/1_spec.md |  11 -
 .../98_mqtt_best_practices/2_about_mqtt.md         |  45 --
 .../98_mqtt_best_practices/3_mqtt_parameters.md    |  45 --
 .../98_mqtt_best_practices/4_topicfilter_design.md |  18 -
 .../98_mqtt_best_practices/_category_.json         |   8 -
 .../version-3.0.x/999_bifromq_inside.md            |  18 -
 .../version-3.0.x/99_test_report/1_test_report.md  | 546 ---------------------
 .../version-3.0.x/99_test_report/_category_.json   |   8 -
 .../images/conn-tcp-1M-5K_1n_false/conn.png        | Bin 130636 -> 0 bytes
 .../images/conn-tcp-1M-5K_1n_false/cpu.png         | Bin 144018 -> 0 bytes
 .../images/conn-tcp-1M-5K_1n_false/mem.png         | Bin 155271 -> 0 bytes
 .../images/conn-tcp-1M-5K_1n_true/conn.png         | Bin 126893 -> 0 bytes
 .../images/conn-tcp-1M-5K_1n_true/cpu.png          | Bin 138613 -> 0 bytes
 .../images/conn-tcp-1M-5K_1n_true/mem.png          | Bin 144605 -> 0 bytes
 .../false_15k_15k_qos0_p256_1mps_1n_1v/cpu.png     | Bin 124423 -> 0 bytes
 .../false_15k_15k_qos0_p256_1mps_1n_1v/max.png     | Bin 481936 -> 0 bytes
 .../false_15k_15k_qos0_p256_1mps_1n_1v/mean.png    | Bin 442098 -> 0 bytes
 .../false_15k_15k_qos0_p256_1mps_1n_1v/mem.png     | Bin 165294 -> 0 bytes
 .../false_15k_15k_qos0_p256_1mps_1n_1v/p99.png     | Bin 467389 -> 0 bytes
 .../false_15k_15k_qos0_p256_1mps_1n_1v/qps.png     | Bin 367528 -> 0 bytes
 .../false_15k_15k_qos0_p256_1mps_1n_1v/result.html |  72 ---
 .../false_15k_15k_qos0_p256_1mps_3n_3v/cpu.png     | Bin 163949 -> 0 bytes
 .../false_15k_15k_qos0_p256_1mps_3n_3v/max.png     | Bin 457564 -> 0 bytes
 .../false_15k_15k_qos0_p256_1mps_3n_3v/mean.png    | Bin 428277 -> 0 bytes
 .../false_15k_15k_qos0_p256_1mps_3n_3v/mem.png     | Bin 194051 -> 0 bytes
 .../false_15k_15k_qos0_p256_1mps_3n_3v/p99.png     | Bin 450467 -> 0 bytes
 .../false_15k_15k_qos0_p256_1mps_3n_3v/qps.png     | Bin 362831 -> 0 bytes
 .../false_15k_15k_qos0_p256_1mps_3n_3v/result.html |  72 ---
 .../false_15k_15k_qos1_p256_1mps_1n_1v/cpu.png     | Bin 124342 -> 0 bytes
 .../false_15k_15k_qos1_p256_1mps_1n_1v/max.png     | Bin 493335 -> 0 bytes
 .../false_15k_15k_qos1_p256_1mps_1n_1v/mean.png    | Bin 449111 -> 0 bytes
 .../false_15k_15k_qos1_p256_1mps_1n_1v/mem.png     | Bin 160513 -> 0 bytes
 .../false_15k_15k_qos1_p256_1mps_1n_1v/p99.png     | Bin 449313 -> 0 bytes
 .../false_15k_15k_qos1_p256_1mps_1n_1v/qps.png     | Bin 365110 -> 0 bytes
 .../false_15k_15k_qos1_p256_1mps_1n_1v/result.html |  72 ---
 .../false_15k_15k_qos1_p256_1mps_3n_3v/cpu.png     | Bin 161174 -> 0 bytes
 .../false_15k_15k_qos1_p256_1mps_3n_3v/max.png     | Bin 448325 -> 0 bytes
 .../false_15k_15k_qos1_p256_1mps_3n_3v/mean.png    | Bin 421273 -> 0 bytes
 .../false_15k_15k_qos1_p256_1mps_3n_3v/mem.png     | Bin 231691 -> 0 bytes
 .../false_15k_15k_qos1_p256_1mps_3n_3v/p99.png     | Bin 448784 -> 0 bytes
 .../false_15k_15k_qos1_p256_1mps_3n_3v/qps.png     | Bin 369465 -> 0 bytes
 .../false_15k_15k_qos1_p256_1mps_3n_3v/result.html |  72 ---
 .../false_300_300_qos0_p32_50mps_1n_1v/cpu.png     | Bin 148546 -> 0 bytes
 .../false_300_300_qos0_p32_50mps_1n_1v/max.png     | Bin 423727 -> 0 bytes
 .../false_300_300_qos0_p32_50mps_1n_1v/mean.png    | Bin 406039 -> 0 bytes
 .../false_300_300_qos0_p32_50mps_1n_1v/mem.png     | Bin 180041 -> 0 bytes
 .../false_300_300_qos0_p32_50mps_1n_1v/p99.png     | Bin 430647 -> 0 bytes
 .../false_300_300_qos0_p32_50mps_1n_1v/qps.png     | Bin 356304 -> 0 bytes
 .../false_300_300_qos0_p32_50mps_1n_1v/result.html |  72 ---
 .../false_300_300_qos0_p32_50mps_3n_3v/cpu.png     | Bin 167043 -> 0 bytes
 .../false_300_300_qos0_p32_50mps_3n_3v/max.png     | Bin 468320 -> 0 bytes
 .../false_300_300_qos0_p32_50mps_3n_3v/mean.png    | Bin 427972 -> 0 bytes
 .../false_300_300_qos0_p32_50mps_3n_3v/mem.png     | Bin 224126 -> 0 bytes
 .../false_300_300_qos0_p32_50mps_3n_3v/p99.png     | Bin 476371 -> 0 bytes
 .../false_300_300_qos0_p32_50mps_3n_3v/qps.png     | Bin 365025 -> 0 bytes
 .../false_300_300_qos0_p32_50mps_3n_3v/result.html |  72 ---
 .../false_300_300_qos1_p32_50mps_1n_1v/cpu.png     | Bin 153309 -> 0 bytes
 .../false_300_300_qos1_p32_50mps_1n_1v/max.png     | Bin 523514 -> 0 bytes
 .../false_300_300_qos1_p32_50mps_1n_1v/mean.png    | Bin 494252 -> 0 bytes
 .../false_300_300_qos1_p32_50mps_1n_1v/mem.png     | Bin 177374 -> 0 bytes
 .../false_300_300_qos1_p32_50mps_1n_1v/p99.png     | Bin 518860 -> 0 bytes
 .../false_300_300_qos1_p32_50mps_1n_1v/qps.png     | Bin 384807 -> 0 bytes
 .../false_300_300_qos1_p32_50mps_1n_1v/result.html |  72 ---
 .../false_300_300_qos1_p32_50mps_3n_3v/cpu.png     | Bin 171693 -> 0 bytes
 .../false_300_300_qos1_p32_50mps_3n_3v/max.png     | Bin 484093 -> 0 bytes
 .../false_300_300_qos1_p32_50mps_3n_3v/mean.png    | Bin 432840 -> 0 bytes
 .../false_300_300_qos1_p32_50mps_3n_3v/mem.png     | Bin 235274 -> 0 bytes
 .../false_300_300_qos1_p32_50mps_3n_3v/p99.png     | Bin 453165 -> 0 bytes
 .../false_300_300_qos1_p32_50mps_3n_3v/qps.png     | Bin 367206 -> 0 bytes
 .../false_300_300_qos1_p32_50mps_3n_3v/result.html |  72 ---
 .../false_30k_30k_qos0_p256_1mps_3n_1v/cpu.png     | Bin 156205 -> 0 bytes
 .../false_30k_30k_qos0_p256_1mps_3n_1v/max.png     | Bin 447493 -> 0 bytes
 .../false_30k_30k_qos0_p256_1mps_3n_1v/mean.png    | Bin 455117 -> 0 bytes
 .../false_30k_30k_qos0_p256_1mps_3n_1v/mem.png     | Bin 221544 -> 0 bytes
 .../false_30k_30k_qos0_p256_1mps_3n_1v/p99.png     | Bin 446752 -> 0 bytes
 .../false_30k_30k_qos0_p256_1mps_3n_1v/qps.png     | Bin 374810 -> 0 bytes
 .../false_30k_30k_qos0_p256_1mps_3n_1v/result.html |  72 ---
 .../false_30k_30k_qos1_p256_1mps_3n_1v/cpu.png     | Bin 164699 -> 0 bytes
 .../false_30k_30k_qos1_p256_1mps_3n_1v/max.png     | Bin 480417 -> 0 bytes
 .../false_30k_30k_qos1_p256_1mps_3n_1v/mean.png    | Bin 458004 -> 0 bytes
 .../false_30k_30k_qos1_p256_1mps_3n_1v/mem.png     | Bin 217174 -> 0 bytes
 .../false_30k_30k_qos1_p256_1mps_3n_1v/p99.png     | Bin 434707 -> 0 bytes
 .../false_30k_30k_qos1_p256_1mps_3n_1v/qps.png     | Bin 372192 -> 0 bytes
 .../false_30k_30k_qos1_p256_1mps_3n_1v/result.html |  72 ---
 .../cpu.png                                        | Bin 156485 -> 0 bytes
 .../max.png                                        | Bin 392463 -> 0 bytes
 .../mean.png                                       | Bin 366103 -> 0 bytes
 .../mem.png                                        | Bin 230360 -> 0 bytes
 .../p99.png                                        | Bin 364874 -> 0 bytes
 .../qps.png                                        | Bin 396099 -> 0 bytes
 .../result.html                                    |  72 ---
 .../false_900_900_qos0_p32_50mps_3n_1v/cpu.png     | Bin 147359 -> 0 bytes
 .../false_900_900_qos0_p32_50mps_3n_1v/max.png     | Bin 415245 -> 0 bytes
 .../false_900_900_qos0_p32_50mps_3n_1v/mean.png    | Bin 424401 -> 0 bytes
 .../false_900_900_qos0_p32_50mps_3n_1v/mem.png     | Bin 247714 -> 0 bytes
 .../false_900_900_qos0_p32_50mps_3n_1v/p99.png     | Bin 427135 -> 0 bytes
 .../false_900_900_qos0_p32_50mps_3n_1v/qps.png     | Bin 341558 -> 0 bytes
 .../false_900_900_qos0_p32_50mps_3n_1v/result.html |  72 ---
 .../false_900_900_qos1_p32_50mps_3n_1v/cpu.png     | Bin 129250 -> 0 bytes
 .../false_900_900_qos1_p32_50mps_3n_1v/max.png     | Bin 432010 -> 0 bytes
 .../false_900_900_qos1_p32_50mps_3n_1v/mean.png    | Bin 433489 -> 0 bytes
 .../false_900_900_qos1_p32_50mps_3n_1v/mem.png     | Bin 235924 -> 0 bytes
 .../false_900_900_qos1_p32_50mps_3n_1v/p99.png     | Bin 431310 -> 0 bytes
 .../false_900_900_qos1_p32_50mps_3n_1v/qps.png     | Bin 359146 -> 0 bytes
 .../false_900_900_qos1_p32_50mps_3n_1v/result.html |  72 ---
 .../fanout_true_1_100000_qos0_p256_1mps_1n/cpu.png | Bin 138421 -> 0 bytes
 .../fanout_true_1_100000_qos0_p256_1mps_1n/max.png | Bin 482712 -> 0 bytes
 .../mean.png                                       | Bin 413584 -> 0 bytes
 .../fanout_true_1_100000_qos0_p256_1mps_1n/mem.png | Bin 186253 -> 0 bytes
 .../fanout_true_1_100000_qos0_p256_1mps_1n/p99.png | Bin 411878 -> 0 bytes
 .../fanout_true_1_100000_qos0_p256_1mps_1n/qps.png | Bin 389245 -> 0 bytes
 .../result.html                                    |  72 ---
 .../fanout_true_1_100000_qos1_p256_1mps_1n/cpu.png | Bin 138421 -> 0 bytes
 .../fanout_true_1_100000_qos1_p256_1mps_1n/max.png | Bin 482712 -> 0 bytes
 .../mean.png                                       | Bin 413584 -> 0 bytes
 .../fanout_true_1_100000_qos1_p256_1mps_1n/mem.png | Bin 186253 -> 0 bytes
 .../fanout_true_1_100000_qos1_p256_1mps_1n/p99.png | Bin 411878 -> 0 bytes
 .../fanout_true_1_100000_qos1_p256_1mps_1n/qps.png | Bin 389245 -> 0 bytes
 .../result.html                                    |  72 ---
 .../fanout_true_1_200000_qos1_p256_1mps_3n/cpu.png | Bin 174708 -> 0 bytes
 .../fanout_true_1_200000_qos1_p256_1mps_3n/max.png | Bin 463804 -> 0 bytes
 .../mean.png                                       | Bin 491642 -> 0 bytes
 .../fanout_true_1_200000_qos1_p256_1mps_3n/mem.png | Bin 210477 -> 0 bytes
 .../fanout_true_1_200000_qos1_p256_1mps_3n/p99.png | Bin 476914 -> 0 bytes
 .../fanout_true_1_200000_qos1_p256_1mps_3n/qps.png | Bin 392552 -> 0 bytes
 .../result.html                                    |  72 ---
 .../fanout_true_1_300000_qos0_p256_1mps_3n/cpu.png | Bin 168359 -> 0 bytes
 .../fanout_true_1_300000_qos0_p256_1mps_3n/max.png | Bin 425551 -> 0 bytes
 .../mean.png                                       | Bin 416007 -> 0 bytes
 .../fanout_true_1_300000_qos0_p256_1mps_3n/mem.png | Bin 208450 -> 0 bytes
 .../fanout_true_1_300000_qos0_p256_1mps_3n/p99.png | Bin 397548 -> 0 bytes
 .../fanout_true_1_300000_qos0_p256_1mps_3n/qps.png | Bin 397553 -> 0 bytes
 .../result.html                                    |  72 ---
 .../share_true_100k_1000_qos0_p256_1mps_1n/cpu.png | Bin 127396 -> 0 bytes
 .../share_true_100k_1000_qos0_p256_1mps_1n/max.png | Bin 468560 -> 0 bytes
 .../mean.png                                       | Bin 422977 -> 0 bytes
 .../share_true_100k_1000_qos0_p256_1mps_1n/mem.png | Bin 132604 -> 0 bytes
 .../share_true_100k_1000_qos0_p256_1mps_1n/p99.png | Bin 406178 -> 0 bytes
 .../share_true_100k_1000_qos0_p256_1mps_1n/qps.png | Bin 382632 -> 0 bytes
 .../result.html                                    |  72 ---
 .../share_true_100k_1000_qos1_p256_1mps_1n/cpu.png | Bin 127592 -> 0 bytes
 .../share_true_100k_1000_qos1_p256_1mps_1n/max.png | Bin 499702 -> 0 bytes
 .../mean.png                                       | Bin 459028 -> 0 bytes
 .../share_true_100k_1000_qos1_p256_1mps_1n/mem.png | Bin 131975 -> 0 bytes
 .../share_true_100k_1000_qos1_p256_1mps_1n/p99.png | Bin 477290 -> 0 bytes
 .../share_true_100k_1000_qos1_p256_1mps_1n/qps.png | Bin 391096 -> 0 bytes
 .../result.html                                    |  72 ---
 .../share_true_200k_2000_qos1_p256_1mps_3n/cpu.png | Bin 147805 -> 0 bytes
 .../share_true_200k_2000_qos1_p256_1mps_3n/max.png | Bin 476120 -> 0 bytes
 .../mean.png                                       | Bin 502200 -> 0 bytes
 .../share_true_200k_2000_qos1_p256_1mps_3n/mem.png | Bin 194208 -> 0 bytes
 .../share_true_200k_2000_qos1_p256_1mps_3n/p99.png | Bin 453390 -> 0 bytes
 .../share_true_200k_2000_qos1_p256_1mps_3n/qps.png | Bin 381698 -> 0 bytes
 .../result.html                                    |  72 ---
 .../share_true_300k_3000_qos0_p256_1mps_3n/cpu.png | Bin 138421 -> 0 bytes
 .../share_true_300k_3000_qos0_p256_1mps_3n/max.png | Bin 482712 -> 0 bytes
 .../mean.png                                       | Bin 413584 -> 0 bytes
 .../share_true_300k_3000_qos0_p256_1mps_3n/mem.png | Bin 186253 -> 0 bytes
 .../share_true_300k_3000_qos0_p256_1mps_3n/p99.png | Bin 411878 -> 0 bytes
 .../share_true_300k_3000_qos0_p256_1mps_3n/qps.png | Bin 389245 -> 0 bytes
 .../result.html                                    |  72 ---
 .../true_1.5k_1.5k_qos1_p32_100mps_1n/cpu.png      | Bin 128543 -> 0 bytes
 .../true_1.5k_1.5k_qos1_p32_100mps_1n/max.png      | Bin 519155 -> 0 bytes
 .../true_1.5k_1.5k_qos1_p32_100mps_1n/mean.png     | Bin 453879 -> 0 bytes
 .../true_1.5k_1.5k_qos1_p32_100mps_1n/mem.png      | Bin 135557 -> 0 bytes
 .../true_1.5k_1.5k_qos1_p32_100mps_1n/p99.png      | Bin 503262 -> 0 bytes
 .../true_1.5k_1.5k_qos1_p32_100mps_1n/qps.png      | Bin 393079 -> 0 bytes
 .../true_1.5k_1.5k_qos1_p32_100mps_1n/result.html  |  72 ---
 .../true_100k_100k_qos0_p256_1mps_1n/cpu.png       | Bin 136092 -> 0 bytes
 .../true_100k_100k_qos0_p256_1mps_1n/max.png       | Bin 456324 -> 0 bytes
 .../true_100k_100k_qos0_p256_1mps_1n/mean.png      | Bin 426233 -> 0 bytes
 .../true_100k_100k_qos0_p256_1mps_1n/mem.png       | Bin 138886 -> 0 bytes
 .../true_100k_100k_qos0_p256_1mps_1n/p99.png       | Bin 427125 -> 0 bytes
 .../true_100k_100k_qos0_p256_1mps_1n/qps.png       | Bin 399792 -> 0 bytes
 .../true_100k_100k_qos0_p256_1mps_1n/result.html   |  72 ---
 .../true_100k_100k_qos1_p256_1mps_1n/cpu.png       | Bin 108749 -> 0 bytes
 .../true_100k_100k_qos1_p256_1mps_1n/max.png       | Bin 532626 -> 0 bytes
 .../true_100k_100k_qos1_p256_1mps_1n/mean.png      | Bin 541320 -> 0 bytes
 .../true_100k_100k_qos1_p256_1mps_1n/mem.png       | Bin 139607 -> 0 bytes
 .../true_100k_100k_qos1_p256_1mps_1n/p99.png       | Bin 529164 -> 0 bytes
 .../true_100k_100k_qos1_p256_1mps_1n/qps.png       | Bin 414141 -> 0 bytes
 .../true_100k_100k_qos1_p256_1mps_1n/result.html   |  72 ---
 .../true_200k_200k_qos1_p256_1mps_3n/cpu.png       | Bin 144086 -> 0 bytes
 .../true_200k_200k_qos1_p256_1mps_3n/mem.png       | Bin 210516 -> 0 bytes
 .../true_200k_200k_qos1_p256_1mps_3n/result.html   |  72 ---
 .../true_250k_250k_qos0_p256_1mps_3n/cpu.png       | Bin 141368 -> 0 bytes
 .../true_250k_250k_qos0_p256_1mps_3n/max.png       | Bin 511336 -> 0 bytes
 .../true_250k_250k_qos0_p256_1mps_3n/mean.png      | Bin 441334 -> 0 bytes
 .../true_250k_250k_qos0_p256_1mps_3n/mem.png       | Bin 182460 -> 0 bytes
 .../true_250k_250k_qos0_p256_1mps_3n/p99.png       | Bin 439309 -> 0 bytes
 .../true_250k_250k_qos0_p256_1mps_3n/qps.png       | Bin 410246 -> 0 bytes
 .../true_250k_250k_qos0_p256_1mps_3n/result.html   |  72 ---
 .../images/true_2k_2k_qos0_p32_100mps_1n/cpu.png   | Bin 128590 -> 0 bytes
 .../images/true_2k_2k_qos0_p32_100mps_1n/max.png   | Bin 331258 -> 0 bytes
 .../images/true_2k_2k_qos0_p32_100mps_1n/mean.png  | Bin 341395 -> 0 bytes
 .../images/true_2k_2k_qos0_p32_100mps_1n/mem.png   | Bin 126026 -> 0 bytes
 .../images/true_2k_2k_qos0_p32_100mps_1n/p99.png   | Bin 339018 -> 0 bytes
 .../images/true_2k_2k_qos0_p32_100mps_1n/qps.png   | Bin 291957 -> 0 bytes
 .../true_2k_2k_qos0_p32_100mps_1n/result.html      |  72 ---
 .../images/true_4k_4k_qos1_p32_100mps_3n/cpu.png   | Bin 148154 -> 0 bytes
 .../images/true_4k_4k_qos1_p32_100mps_3n/max.png   | Bin 375398 -> 0 bytes
 .../images/true_4k_4k_qos1_p32_100mps_3n/mean.png  | Bin 353213 -> 0 bytes
 .../images/true_4k_4k_qos1_p32_100mps_3n/mem.png   | Bin 183773 -> 0 bytes
 .../images/true_4k_4k_qos1_p32_100mps_3n/p99.png   | Bin 347844 -> 0 bytes
 .../images/true_4k_4k_qos1_p32_100mps_3n/qps.png   | Bin 289837 -> 0 bytes
 .../true_4k_4k_qos1_p32_100mps_3n/result.html      |  72 ---
 .../images/true_5k_5k_qos0_p32_100mps_3n/cpu.png   | Bin 158592 -> 0 bytes
 .../images/true_5k_5k_qos0_p32_100mps_3n/max.png   | Bin 348310 -> 0 bytes
 .../images/true_5k_5k_qos0_p32_100mps_3n/mean.png  | Bin 327563 -> 0 bytes
 .../images/true_5k_5k_qos0_p32_100mps_3n/mem.png   | Bin 196465 -> 0 bytes
 .../images/true_5k_5k_qos0_p32_100mps_3n/p99.png   | Bin 323008 -> 0 bytes
 .../images/true_5k_5k_qos0_p32_100mps_3n/qps.png   | Bin 296054 -> 0 bytes
 .../true_5k_5k_qos0_p32_100mps_3n/result.html      |  72 ---
 .../01_get_started/1_quick_install.md              |  13 -
 .../version-3.1.x/01_get_started/2_quick_verify.md |  30 --
 .../version-3.1.x/01_get_started/3_faq.md          |  44 --
 .../version-3.1.x/01_get_started/_category_.json   |   8 -
 .../01_get_started/images/newconn.jpg              | Bin 312148 -> 0 bytes
 .../01_get_started/images/publish.jpg              | Bin 298876 -> 0 bytes
 .../01_get_started/images/subscribe.jpg            | Bin 211030 -> 0 bytes
 .../version-3.1.x/01_get_started/intro.md          |  43 --
 .../version-3.1.x/02_installation/1_docker.md      |  35 --
 .../version-3.1.x/02_installation/2_linux.md       |  16 -
 .../version-3.1.x/02_installation/3_windows.md     |  17 -
 .../02_installation/4_install_from_source.md       |  32 --
 .../02_installation/5_config_migration.md          |   8 -
 .../02_installation/6_nodes_on_k8s.md              |  32 --
 .../version-3.1.x/02_installation/_category_.json  |   8 -
 .../version-3.1.x/02_installation/intro.md         |  39 --
 .../version-3.1.x/04_cluster/1_standardcluster.md  |  65 ---
 .../04_cluster/2_high_availability.md              | 107 ----
 .../version-3.1.x/04_cluster/_category_.json       |   8 -
 .../04_cluster/images/IndependentWorkload.png      | Bin 231896 -> 0 bytes
 .../version-3.1.x/04_cluster/intro.md              |  34 --
 .../05_user_guide/1_basic/1_connect.md             |  20 -
 .../05_user_guide/1_basic/2_pubsub.md              |  39 --
 .../05_user_guide/1_basic/3_shared_sub.md          |  21 -
 .../05_user_guide/1_basic/_category_.json          |   8 -
 .../1_basic/images/pub-sub-pattern.png             | Bin 372353 -> 0 bytes
 .../1_basic/images/shared-subscription.png         | Bin 489533 -> 0 bytes
 .../version-3.1.x/05_user_guide/1_basic/intro.md   |  17 -
 .../05_user_guide/2_integration/1_integration.md   |  26 -
 .../05_user_guide/2_integration/_category_.json    |   8 -
 .../2_integration/images/bifromqapproach.jpg       | Bin 133675 -> 0 bytes
 .../2_integration/images/commonapproach.jpg        | Bin 129120 -> 0 bytes
 .../2_integration/images/integration.png           | Bin 300130 -> 0 bytes
 .../05_user_guide/2_integration/intro.md           |  56 ---
 .../05_user_guide/3_api/1_api_reference.md         | 127 -----
 .../05_user_guide/3_api/_category_.json            |   8 -
 .../05_user_guide/3_api/images/API-Arch.png        | Bin 25560 -> 0 bytes
 .../version-3.1.x/05_user_guide/3_api/intro.md     |  15 -
 .../version-3.1.x/05_user_guide/_category_.json    |   8 -
 .../version-3.1.x/05_user_guide/intro.md           |  19 -
 .../version-3.1.x/06_plugin/1_auth_provider.md     | 386 ---------------
 .../version-3.1.x/06_plugin/2_event_collector.md   |  42 --
 .../06_plugin/3_resource_throttler.md              | 135 -----
 .../4_setting_provider/1_tenantsetting.md          |  49 --
 .../06_plugin/4_setting_provider/_category_.json   |   8 -
 .../06_plugin/4_setting_provider/intro.md          | 123 -----
 .../version-3.1.x/06_plugin/5_plugin_practice.md   |  43 --
 .../version-3.1.x/06_plugin/_category_.json        |   8 -
 .../version-3.1.x/06_plugin/intro.md               |  60 ---
 .../01_configuration/1_config_file_manual.md       | 114 -----
 .../01_configuration/2_bifromq_sys_props.md        |  54 --
 .../01_configuration/3_configs_print.md            |  89 ----
 .../01_configuration/_category_.json               |   8 -
 .../07_admin_guide/01_configuration/intro.md       |  11 -
 .../07_admin_guide/02_tuning/1_os_tuning_linux.md  |  58 ---
 .../07_admin_guide/02_tuning/_category_.json       |   8 -
 .../07_admin_guide/02_tuning/intro.md              |  29 --
 .../07_admin_guide/03_observability/01_logging.md  |  18 -
 .../07_admin_guide/03_observability/03_events.md   |  21 -
 .../03_observability/_category_.json               |   8 -
 .../07_admin_guide/03_observability/intro.md       |   7 -
 .../03_observability/metrics/_category_.json       |   8 -
 .../03_observability/metrics/intro.md              |  21 -
 .../03_observability/metrics/tenantmetrics.md      |  60 ---
 .../07_admin_guide/04_security/_category_.json     |   8 -
 .../07_admin_guide/04_security/intro.md            |  25 -
 .../version-3.1.x/07_admin_guide/_category_.json   |   8 -
 .../version-3.1.x/07_admin_guide/intro.md          |   7 -
 .../version-3.1.x/98_mqtt_best_practices/1_spec.md |  11 -
 .../98_mqtt_best_practices/2_about_mqtt.md         |  45 --
 .../98_mqtt_best_practices/3_mqtt_parameters.md    |  45 --
 .../98_mqtt_best_practices/4_topicfilter_design.md |  18 -
 .../98_mqtt_best_practices/_category_.json         |   8 -
 .../version-3.1.x/999_bifromq_inside.md            |  18 -
 .../version-3.1.x/99_test_report/1_test_report.md  | 546 ---------------------
 .../version-3.1.x/99_test_report/_category_.json   |   8 -
 .../images/conn-tcp-1M-5K_1n_false/conn.png        | Bin 130636 -> 0 bytes
 .../images/conn-tcp-1M-5K_1n_false/cpu.png         | Bin 144018 -> 0 bytes
 .../images/conn-tcp-1M-5K_1n_false/mem.png         | Bin 155271 -> 0 bytes
 .../images/conn-tcp-1M-5K_1n_true/conn.png         | Bin 126893 -> 0 bytes
 .../images/conn-tcp-1M-5K_1n_true/cpu.png          | Bin 138613 -> 0 bytes
 .../images/conn-tcp-1M-5K_1n_true/mem.png          | Bin 144605 -> 0 bytes
 .../false_15k_15k_qos0_p256_1mps_1n_1v/cpu.png     | Bin 124423 -> 0 bytes
 .../false_15k_15k_qos0_p256_1mps_1n_1v/max.png     | Bin 481936 -> 0 bytes
 .../false_15k_15k_qos0_p256_1mps_1n_1v/mean.png    | Bin 442098 -> 0 bytes
 .../false_15k_15k_qos0_p256_1mps_1n_1v/mem.png     | Bin 165294 -> 0 bytes
 .../false_15k_15k_qos0_p256_1mps_1n_1v/p99.png     | Bin 467389 -> 0 bytes
 .../false_15k_15k_qos0_p256_1mps_1n_1v/qps.png     | Bin 367528 -> 0 bytes
 .../false_15k_15k_qos0_p256_1mps_1n_1v/result.html |  72 ---
 .../false_15k_15k_qos0_p256_1mps_3n_3v/cpu.png     | Bin 163949 -> 0 bytes
 .../false_15k_15k_qos0_p256_1mps_3n_3v/max.png     | Bin 457564 -> 0 bytes
 .../false_15k_15k_qos0_p256_1mps_3n_3v/mean.png    | Bin 428277 -> 0 bytes
 .../false_15k_15k_qos0_p256_1mps_3n_3v/mem.png     | Bin 194051 -> 0 bytes
 .../false_15k_15k_qos0_p256_1mps_3n_3v/p99.png     | Bin 450467 -> 0 bytes
 .../false_15k_15k_qos0_p256_1mps_3n_3v/qps.png     | Bin 362831 -> 0 bytes
 .../false_15k_15k_qos0_p256_1mps_3n_3v/result.html |  72 ---
 .../false_15k_15k_qos1_p256_1mps_1n_1v/cpu.png     | Bin 124342 -> 0 bytes
 .../false_15k_15k_qos1_p256_1mps_1n_1v/max.png     | Bin 493335 -> 0 bytes
 .../false_15k_15k_qos1_p256_1mps_1n_1v/mean.png    | Bin 449111 -> 0 bytes
 .../false_15k_15k_qos1_p256_1mps_1n_1v/mem.png     | Bin 160513 -> 0 bytes
 .../false_15k_15k_qos1_p256_1mps_1n_1v/p99.png     | Bin 449313 -> 0 bytes
 .../false_15k_15k_qos1_p256_1mps_1n_1v/qps.png     | Bin 365110 -> 0 bytes
 .../false_15k_15k_qos1_p256_1mps_1n_1v/result.html |  72 ---
 .../false_15k_15k_qos1_p256_1mps_3n_3v/cpu.png     | Bin 161174 -> 0 bytes
 .../false_15k_15k_qos1_p256_1mps_3n_3v/max.png     | Bin 448325 -> 0 bytes
 .../false_15k_15k_qos1_p256_1mps_3n_3v/mean.png    | Bin 421273 -> 0 bytes
 .../false_15k_15k_qos1_p256_1mps_3n_3v/mem.png     | Bin 231691 -> 0 bytes
 .../false_15k_15k_qos1_p256_1mps_3n_3v/p99.png     | Bin 448784 -> 0 bytes
 .../false_15k_15k_qos1_p256_1mps_3n_3v/qps.png     | Bin 369465 -> 0 bytes
 .../false_15k_15k_qos1_p256_1mps_3n_3v/result.html |  72 ---
 .../false_300_300_qos0_p32_50mps_1n_1v/cpu.png     | Bin 148546 -> 0 bytes
 .../false_300_300_qos0_p32_50mps_1n_1v/max.png     | Bin 423727 -> 0 bytes
 .../false_300_300_qos0_p32_50mps_1n_1v/mean.png    | Bin 406039 -> 0 bytes
 .../false_300_300_qos0_p32_50mps_1n_1v/mem.png     | Bin 180041 -> 0 bytes
 .../false_300_300_qos0_p32_50mps_1n_1v/p99.png     | Bin 430647 -> 0 bytes
 .../false_300_300_qos0_p32_50mps_1n_1v/qps.png     | Bin 356304 -> 0 bytes
 .../false_300_300_qos0_p32_50mps_1n_1v/result.html |  72 ---
 .../false_300_300_qos0_p32_50mps_3n_3v/cpu.png     | Bin 167043 -> 0 bytes
 .../false_300_300_qos0_p32_50mps_3n_3v/max.png     | Bin 468320 -> 0 bytes
 .../false_300_300_qos0_p32_50mps_3n_3v/mean.png    | Bin 427972 -> 0 bytes
 .../false_300_300_qos0_p32_50mps_3n_3v/mem.png     | Bin 224126 -> 0 bytes
 .../false_300_300_qos0_p32_50mps_3n_3v/p99.png     | Bin 476371 -> 0 bytes
 .../false_300_300_qos0_p32_50mps_3n_3v/qps.png     | Bin 365025 -> 0 bytes
 .../false_300_300_qos0_p32_50mps_3n_3v/result.html |  72 ---
 .../false_300_300_qos1_p32_50mps_1n_1v/cpu.png     | Bin 153309 -> 0 bytes
 .../false_300_300_qos1_p32_50mps_1n_1v/max.png     | Bin 523514 -> 0 bytes
 .../false_300_300_qos1_p32_50mps_1n_1v/mean.png    | Bin 494252 -> 0 bytes
 .../false_300_300_qos1_p32_50mps_1n_1v/mem.png     | Bin 177374 -> 0 bytes
 .../false_300_300_qos1_p32_50mps_1n_1v/p99.png     | Bin 518860 -> 0 bytes
 .../false_300_300_qos1_p32_50mps_1n_1v/qps.png     | Bin 384807 -> 0 bytes
 .../false_300_300_qos1_p32_50mps_1n_1v/result.html |  72 ---
 .../false_300_300_qos1_p32_50mps_3n_3v/cpu.png     | Bin 171693 -> 0 bytes
 .../false_300_300_qos1_p32_50mps_3n_3v/max.png     | Bin 484093 -> 0 bytes
 .../false_300_300_qos1_p32_50mps_3n_3v/mean.png    | Bin 432840 -> 0 bytes
 .../false_300_300_qos1_p32_50mps_3n_3v/mem.png     | Bin 235274 -> 0 bytes
 .../false_300_300_qos1_p32_50mps_3n_3v/p99.png     | Bin 453165 -> 0 bytes
 .../false_300_300_qos1_p32_50mps_3n_3v/qps.png     | Bin 367206 -> 0 bytes
 .../false_300_300_qos1_p32_50mps_3n_3v/result.html |  72 ---
 .../false_30k_30k_qos0_p256_1mps_3n_1v/cpu.png     | Bin 156205 -> 0 bytes
 .../false_30k_30k_qos0_p256_1mps_3n_1v/max.png     | Bin 447493 -> 0 bytes
 .../false_30k_30k_qos0_p256_1mps_3n_1v/mean.png    | Bin 455117 -> 0 bytes
 .../false_30k_30k_qos0_p256_1mps_3n_1v/mem.png     | Bin 221544 -> 0 bytes
 .../false_30k_30k_qos0_p256_1mps_3n_1v/p99.png     | Bin 446752 -> 0 bytes
 .../false_30k_30k_qos0_p256_1mps_3n_1v/qps.png     | Bin 374810 -> 0 bytes
 .../false_30k_30k_qos0_p256_1mps_3n_1v/result.html |  72 ---
 .../false_30k_30k_qos1_p256_1mps_3n_1v/cpu.png     | Bin 164699 -> 0 bytes
 .../false_30k_30k_qos1_p256_1mps_3n_1v/max.png     | Bin 480417 -> 0 bytes
 .../false_30k_30k_qos1_p256_1mps_3n_1v/mean.png    | Bin 458004 -> 0 bytes
 .../false_30k_30k_qos1_p256_1mps_3n_1v/mem.png     | Bin 217174 -> 0 bytes
 .../false_30k_30k_qos1_p256_1mps_3n_1v/p99.png     | Bin 434707 -> 0 bytes
 .../false_30k_30k_qos1_p256_1mps_3n_1v/qps.png     | Bin 372192 -> 0 bytes
 .../false_30k_30k_qos1_p256_1mps_3n_1v/result.html |  72 ---
 .../cpu.png                                        | Bin 156485 -> 0 bytes
 .../max.png                                        | Bin 392463 -> 0 bytes
 .../mean.png                                       | Bin 366103 -> 0 bytes
 .../mem.png                                        | Bin 230360 -> 0 bytes
 .../p99.png                                        | Bin 364874 -> 0 bytes
 .../qps.png                                        | Bin 396099 -> 0 bytes
 .../result.html                                    |  72 ---
 .../false_900_900_qos0_p32_50mps_3n_1v/cpu.png     | Bin 147359 -> 0 bytes
 .../false_900_900_qos0_p32_50mps_3n_1v/max.png     | Bin 415245 -> 0 bytes
 .../false_900_900_qos0_p32_50mps_3n_1v/mean.png    | Bin 424401 -> 0 bytes
 .../false_900_900_qos0_p32_50mps_3n_1v/mem.png     | Bin 247714 -> 0 bytes
 .../false_900_900_qos0_p32_50mps_3n_1v/p99.png     | Bin 427135 -> 0 bytes
 .../false_900_900_qos0_p32_50mps_3n_1v/qps.png     | Bin 341558 -> 0 bytes
 .../false_900_900_qos0_p32_50mps_3n_1v/result.html |  72 ---
 .../false_900_900_qos1_p32_50mps_3n_1v/cpu.png     | Bin 129250 -> 0 bytes
 .../false_900_900_qos1_p32_50mps_3n_1v/max.png     | Bin 432010 -> 0 bytes
 .../false_900_900_qos1_p32_50mps_3n_1v/mean.png    | Bin 433489 -> 0 bytes
 .../false_900_900_qos1_p32_50mps_3n_1v/mem.png     | Bin 235924 -> 0 bytes
 .../false_900_900_qos1_p32_50mps_3n_1v/p99.png     | Bin 431310 -> 0 bytes
 .../false_900_900_qos1_p32_50mps_3n_1v/qps.png     | Bin 359146 -> 0 bytes
 .../false_900_900_qos1_p32_50mps_3n_1v/result.html |  72 ---
 .../fanout_true_1_100000_qos0_p256_1mps_1n/cpu.png | Bin 138421 -> 0 bytes
 .../fanout_true_1_100000_qos0_p256_1mps_1n/max.png | Bin 482712 -> 0 bytes
 .../mean.png                                       | Bin 413584 -> 0 bytes
 .../fanout_true_1_100000_qos0_p256_1mps_1n/mem.png | Bin 186253 -> 0 bytes
 .../fanout_true_1_100000_qos0_p256_1mps_1n/p99.png | Bin 411878 -> 0 bytes
 .../fanout_true_1_100000_qos0_p256_1mps_1n/qps.png | Bin 389245 -> 0 bytes
 .../result.html                                    |  72 ---
 .../fanout_true_1_100000_qos1_p256_1mps_1n/cpu.png | Bin 138421 -> 0 bytes
 .../fanout_true_1_100000_qos1_p256_1mps_1n/max.png | Bin 482712 -> 0 bytes
 .../mean.png                                       | Bin 413584 -> 0 bytes
 .../fanout_true_1_100000_qos1_p256_1mps_1n/mem.png | Bin 186253 -> 0 bytes
 .../fanout_true_1_100000_qos1_p256_1mps_1n/p99.png | Bin 411878 -> 0 bytes
 .../fanout_true_1_100000_qos1_p256_1mps_1n/qps.png | Bin 389245 -> 0 bytes
 .../result.html                                    |  72 ---
 .../fanout_true_1_200000_qos1_p256_1mps_3n/cpu.png | Bin 174708 -> 0 bytes
 .../fanout_true_1_200000_qos1_p256_1mps_3n/max.png | Bin 463804 -> 0 bytes
 .../mean.png                                       | Bin 491642 -> 0 bytes
 .../fanout_true_1_200000_qos1_p256_1mps_3n/mem.png | Bin 210477 -> 0 bytes
 .../fanout_true_1_200000_qos1_p256_1mps_3n/p99.png | Bin 476914 -> 0 bytes
 .../fanout_true_1_200000_qos1_p256_1mps_3n/qps.png | Bin 392552 -> 0 bytes
 .../result.html                                    |  72 ---
 .../fanout_true_1_300000_qos0_p256_1mps_3n/cpu.png | Bin 168359 -> 0 bytes
 .../fanout_true_1_300000_qos0_p256_1mps_3n/max.png | Bin 425551 -> 0 bytes
 .../mean.png                                       | Bin 416007 -> 0 bytes
 .../fanout_true_1_300000_qos0_p256_1mps_3n/mem.png | Bin 208450 -> 0 bytes
 .../fanout_true_1_300000_qos0_p256_1mps_3n/p99.png | Bin 397548 -> 0 bytes
 .../fanout_true_1_300000_qos0_p256_1mps_3n/qps.png | Bin 397553 -> 0 bytes
 .../result.html                                    |  72 ---
 .../share_true_100k_1000_qos0_p256_1mps_1n/cpu.png | Bin 127396 -> 0 bytes
 .../share_true_100k_1000_qos0_p256_1mps_1n/max.png | Bin 468560 -> 0 bytes
 .../mean.png                                       | Bin 422977 -> 0 bytes
 .../share_true_100k_1000_qos0_p256_1mps_1n/mem.png | Bin 132604 -> 0 bytes
 .../share_true_100k_1000_qos0_p256_1mps_1n/p99.png | Bin 406178 -> 0 bytes
 .../share_true_100k_1000_qos0_p256_1mps_1n/qps.png | Bin 382632 -> 0 bytes
 .../result.html                                    |  72 ---
 .../share_true_100k_1000_qos1_p256_1mps_1n/cpu.png | Bin 127592 -> 0 bytes
 .../share_true_100k_1000_qos1_p256_1mps_1n/max.png | Bin 499702 -> 0 bytes
 .../mean.png                                       | Bin 459028 -> 0 bytes
 .../share_true_100k_1000_qos1_p256_1mps_1n/mem.png | Bin 131975 -> 0 bytes
 .../share_true_100k_1000_qos1_p256_1mps_1n/p99.png | Bin 477290 -> 0 bytes
 .../share_true_100k_1000_qos1_p256_1mps_1n/qps.png | Bin 391096 -> 0 bytes
 .../result.html                                    |  72 ---
 .../share_true_200k_2000_qos1_p256_1mps_3n/cpu.png | Bin 147805 -> 0 bytes
 .../share_true_200k_2000_qos1_p256_1mps_3n/max.png | Bin 476120 -> 0 bytes
 .../mean.png                                       | Bin 502200 -> 0 bytes
 .../share_true_200k_2000_qos1_p256_1mps_3n/mem.png | Bin 194208 -> 0 bytes
 .../share_true_200k_2000_qos1_p256_1mps_3n/p99.png | Bin 453390 -> 0 bytes
 .../share_true_200k_2000_qos1_p256_1mps_3n/qps.png | Bin 381698 -> 0 bytes
 .../result.html                                    |  72 ---
 .../share_true_300k_3000_qos0_p256_1mps_3n/cpu.png | Bin 138421 -> 0 bytes
 .../share_true_300k_3000_qos0_p256_1mps_3n/max.png | Bin 482712 -> 0 bytes
 .../mean.png                                       | Bin 413584 -> 0 bytes
 .../share_true_300k_3000_qos0_p256_1mps_3n/mem.png | Bin 186253 -> 0 bytes
 .../share_true_300k_3000_qos0_p256_1mps_3n/p99.png | Bin 411878 -> 0 bytes
 .../share_true_300k_3000_qos0_p256_1mps_3n/qps.png | Bin 389245 -> 0 bytes
 .../result.html                                    |  72 ---
 .../true_1.5k_1.5k_qos1_p32_100mps_1n/cpu.png      | Bin 128543 -> 0 bytes
 .../true_1.5k_1.5k_qos1_p32_100mps_1n/max.png      | Bin 519155 -> 0 bytes
 .../true_1.5k_1.5k_qos1_p32_100mps_1n/mean.png     | Bin 453879 -> 0 bytes
 .../true_1.5k_1.5k_qos1_p32_100mps_1n/mem.png      | Bin 135557 -> 0 bytes
 .../true_1.5k_1.5k_qos1_p32_100mps_1n/p99.png      | Bin 503262 -> 0 bytes
 .../true_1.5k_1.5k_qos1_p32_100mps_1n/qps.png      | Bin 393079 -> 0 bytes
 .../true_1.5k_1.5k_qos1_p32_100mps_1n/result.html  |  72 ---
 .../true_100k_100k_qos0_p256_1mps_1n/cpu.png       | Bin 136092 -> 0 bytes
 .../true_100k_100k_qos0_p256_1mps_1n/max.png       | Bin 456324 -> 0 bytes
 .../true_100k_100k_qos0_p256_1mps_1n/mean.png      | Bin 426233 -> 0 bytes
 .../true_100k_100k_qos0_p256_1mps_1n/mem.png       | Bin 138886 -> 0 bytes
 .../true_100k_100k_qos0_p256_1mps_1n/p99.png       | Bin 427125 -> 0 bytes
 .../true_100k_100k_qos0_p256_1mps_1n/qps.png       | Bin 399792 -> 0 bytes
 .../true_100k_100k_qos0_p256_1mps_1n/result.html   |  72 ---
 .../true_100k_100k_qos1_p256_1mps_1n/cpu.png       | Bin 108749 -> 0 bytes
 .../true_100k_100k_qos1_p256_1mps_1n/max.png       | Bin 532626 -> 0 bytes
 .../true_100k_100k_qos1_p256_1mps_1n/mean.png      | Bin 541320 -> 0 bytes
 .../true_100k_100k_qos1_p256_1mps_1n/mem.png       | Bin 139607 -> 0 bytes
 .../true_100k_100k_qos1_p256_1mps_1n/p99.png       | Bin 529164 -> 0 bytes
 .../true_100k_100k_qos1_p256_1mps_1n/qps.png       | Bin 414141 -> 0 bytes
 .../true_100k_100k_qos1_p256_1mps_1n/result.html   |  72 ---
 .../true_200k_200k_qos1_p256_1mps_3n/cpu.png       | Bin 144086 -> 0 bytes
 .../true_200k_200k_qos1_p256_1mps_3n/mem.png       | Bin 210516 -> 0 bytes
 .../true_200k_200k_qos1_p256_1mps_3n/result.html   |  72 ---
 .../true_250k_250k_qos0_p256_1mps_3n/cpu.png       | Bin 141368 -> 0 bytes
 .../true_250k_250k_qos0_p256_1mps_3n/max.png       | Bin 511336 -> 0 bytes
 .../true_250k_250k_qos0_p256_1mps_3n/mean.png      | Bin 441334 -> 0 bytes
 .../true_250k_250k_qos0_p256_1mps_3n/mem.png       | Bin 182460 -> 0 bytes
 .../true_250k_250k_qos0_p256_1mps_3n/p99.png       | Bin 439309 -> 0 bytes
 .../true_250k_250k_qos0_p256_1mps_3n/qps.png       | Bin 410246 -> 0 bytes
 .../true_250k_250k_qos0_p256_1mps_3n/result.html   |  72 ---
 .../images/true_2k_2k_qos0_p32_100mps_1n/cpu.png   | Bin 128590 -> 0 bytes
 .../images/true_2k_2k_qos0_p32_100mps_1n/max.png   | Bin 331258 -> 0 bytes
 .../images/true_2k_2k_qos0_p32_100mps_1n/mean.png  | Bin 341395 -> 0 bytes
 .../images/true_2k_2k_qos0_p32_100mps_1n/mem.png   | Bin 126026 -> 0 bytes
 .../images/true_2k_2k_qos0_p32_100mps_1n/p99.png   | Bin 339018 -> 0 bytes
 .../images/true_2k_2k_qos0_p32_100mps_1n/qps.png   | Bin 291957 -> 0 bytes
 .../true_2k_2k_qos0_p32_100mps_1n/result.html      |  72 ---
 .../images/true_4k_4k_qos1_p32_100mps_3n/cpu.png   | Bin 148154 -> 0 bytes
 .../images/true_4k_4k_qos1_p32_100mps_3n/max.png   | Bin 375398 -> 0 bytes
 .../images/true_4k_4k_qos1_p32_100mps_3n/mean.png  | Bin 353213 -> 0 bytes
 .../images/true_4k_4k_qos1_p32_100mps_3n/mem.png   | Bin 183773 -> 0 bytes
 .../images/true_4k_4k_qos1_p32_100mps_3n/p99.png   | Bin 347844 -> 0 bytes
 .../images/true_4k_4k_qos1_p32_100mps_3n/qps.png   | Bin 289837 -> 0 bytes
 .../true_4k_4k_qos1_p32_100mps_3n/result.html      |  72 ---
 .../images/true_5k_5k_qos0_p32_100mps_3n/cpu.png   | Bin 158592 -> 0 bytes
 .../images/true_5k_5k_qos0_p32_100mps_3n/max.png   | Bin 348310 -> 0 bytes
 .../images/true_5k_5k_qos0_p32_100mps_3n/mean.png  | Bin 327563 -> 0 bytes
 .../images/true_5k_5k_qos0_p32_100mps_3n/mem.png   | Bin 196465 -> 0 bytes
 .../images/true_5k_5k_qos0_p32_100mps_3n/p99.png   | Bin 323008 -> 0 bytes
 .../images/true_5k_5k_qos0_p32_100mps_3n/qps.png   | Bin 296054 -> 0 bytes
 .../true_5k_5k_qos0_p32_100mps_3n/result.html      |  72 ---
 .../01_get_started/1_quick_install.md              |  13 -
 .../version-3.2.x/01_get_started/2_quick_verify.md |  30 --
 .../version-3.2.x/01_get_started/3_faq.md          |  44 --
 .../version-3.2.x/01_get_started/_category_.json   |   8 -
 .../01_get_started/images/newconn.jpg              | Bin 312148 -> 0 bytes
 .../01_get_started/images/publish.jpg              | Bin 298876 -> 0 bytes
 .../01_get_started/images/subscribe.jpg            | Bin 211030 -> 0 bytes
 .../version-3.2.x/01_get_started/intro.md          |  43 --
 .../version-3.2.x/02_installation/1_docker.md      |  35 --
 .../version-3.2.x/02_installation/2_linux.md       |  16 -
 .../version-3.2.x/02_installation/3_windows.md     |  17 -
 .../02_installation/4_install_from_source.md       |  32 --
 .../02_installation/5_config_migration.md          |   8 -
 .../02_installation/6_nodes_on_k8s.md              |  32 --
 .../version-3.2.x/02_installation/_category_.json  |   8 -
 .../version-3.2.x/02_installation/intro.md         |  39 --
 .../version-3.2.x/04_cluster/1_standardcluster.md  |  65 ---
 .../04_cluster/2_high_availability.md              | 107 ----
 .../version-3.2.x/04_cluster/_category_.json       |   8 -
 .../04_cluster/images/IndependentWorkload.png      | Bin 231896 -> 0 bytes
 .../version-3.2.x/04_cluster/intro.md              |  34 --
 .../05_user_guide/1_basic/1_connect.md             |  20 -
 .../05_user_guide/1_basic/2_pubsub.md              |  39 --
 .../05_user_guide/1_basic/3_shared_sub.md          |  21 -
 .../05_user_guide/1_basic/_category_.json          |   8 -
 .../1_basic/images/pub-sub-pattern.png             | Bin 372353 -> 0 bytes
 .../1_basic/images/shared-subscription.png         | Bin 489533 -> 0 bytes
 .../version-3.2.x/05_user_guide/1_basic/intro.md   |  17 -
 .../05_user_guide/2_integration/1_integration.md   |  26 -
 .../05_user_guide/2_integration/_category_.json    |   8 -
 .../2_integration/images/bifromqapproach.jpg       | Bin 133675 -> 0 bytes
 .../2_integration/images/commonapproach.jpg        | Bin 129120 -> 0 bytes
 .../2_integration/images/integration.png           | Bin 300130 -> 0 bytes
 .../05_user_guide/2_integration/intro.md           |  56 ---
 .../05_user_guide/3_api/1_api_reference.md         | 127 -----
 .../05_user_guide/3_api/_category_.json            |   8 -
 .../05_user_guide/3_api/images/API-Arch.png        | Bin 25560 -> 0 bytes
 .../version-3.2.x/05_user_guide/3_api/intro.md     |  15 -
 .../version-3.2.x/05_user_guide/_category_.json    |   8 -
 .../version-3.2.x/05_user_guide/intro.md           |  19 -
 .../version-3.2.x/06_plugin/1_auth_provider.md     | 386 ---------------
 .../version-3.2.x/06_plugin/2_event_collector.md   |  42 --
 .../06_plugin/3_resource_throttler.md              | 135 -----
 .../4_setting_provider/1_tenantsetting.md          |  49 --
 .../06_plugin/4_setting_provider/_category_.json   |   8 -
 .../06_plugin/4_setting_provider/intro.md          | 123 -----
 .../version-3.2.x/06_plugin/5_plugin_practice.md   |  73 ---
 .../version-3.2.x/06_plugin/_category_.json        |   8 -
 .../version-3.2.x/06_plugin/intro.md               |  61 ---
 .../01_configuration/1_config_file_manual.md       | 114 -----
 .../01_configuration/2_bifromq_sys_props.md        |  54 --
 .../01_configuration/3_configs_print.md            |  89 ----
 .../01_configuration/_category_.json               |   8 -
 .../07_admin_guide/01_configuration/intro.md       |  11 -
 .../07_admin_guide/02_tuning/1_os_tuning_linux.md  |  58 ---
 .../07_admin_guide/02_tuning/_category_.json       |   8 -
 .../07_admin_guide/02_tuning/intro.md              |  29 --
 .../07_admin_guide/03_observability/01_logging.md  |  18 -
 .../07_admin_guide/03_observability/03_events.md   |  21 -
 .../03_observability/_category_.json               |   8 -
 .../07_admin_guide/03_observability/intro.md       |   7 -
 .../03_observability/metrics/_category_.json       |   8 -
 .../03_observability/metrics/intro.md              |  21 -
 .../03_observability/metrics/tenantmetrics.md      |  60 ---
 .../07_admin_guide/04_security/_category_.json     |   8 -
 .../07_admin_guide/04_security/intro.md            |  25 -
 .../version-3.2.x/07_admin_guide/_category_.json   |   8 -
 .../version-3.2.x/07_admin_guide/intro.md          |   7 -
 .../version-3.2.x/98_mqtt_best_practices/1_spec.md |  11 -
 .../98_mqtt_best_practices/2_about_mqtt.md         |  45 --
 .../98_mqtt_best_practices/3_mqtt_parameters.md    |  45 --
 .../98_mqtt_best_practices/4_topicfilter_design.md |  18 -
 .../98_mqtt_best_practices/_category_.json         |   8 -
 .../version-3.2.x/999_bifromq_inside.md            |  18 -
 .../version-3.2.x/99_test_report/1_test_report.md  | 546 ---------------------
 .../version-3.2.x/99_test_report/_category_.json   |   8 -
 .../images/conn-tcp-1M-5K_1n_false/conn.png        | Bin 130636 -> 0 bytes
 .../images/conn-tcp-1M-5K_1n_false/cpu.png         | Bin 144018 -> 0 bytes
 .../images/conn-tcp-1M-5K_1n_false/mem.png         | Bin 155271 -> 0 bytes
 .../images/conn-tcp-1M-5K_1n_true/conn.png         | Bin 126893 -> 0 bytes
 .../images/conn-tcp-1M-5K_1n_true/cpu.png          | Bin 138613 -> 0 bytes
 .../images/conn-tcp-1M-5K_1n_true/mem.png          | Bin 144605 -> 0 bytes
 .../false_15k_15k_qos0_p256_1mps_1n_1v/cpu.png     | Bin 124423 -> 0 bytes
 .../false_15k_15k_qos0_p256_1mps_1n_1v/max.png     | Bin 481936 -> 0 bytes
 .../false_15k_15k_qos0_p256_1mps_1n_1v/mean.png    | Bin 442098 -> 0 bytes
 .../false_15k_15k_qos0_p256_1mps_1n_1v/mem.png     | Bin 165294 -> 0 bytes
 .../false_15k_15k_qos0_p256_1mps_1n_1v/p99.png     | Bin 467389 -> 0 bytes
 .../false_15k_15k_qos0_p256_1mps_1n_1v/qps.png     | Bin 367528 -> 0 bytes
 .../false_15k_15k_qos0_p256_1mps_1n_1v/result.html |  72 ---
 .../false_15k_15k_qos0_p256_1mps_3n_3v/cpu.png     | Bin 163949 -> 0 bytes
 .../false_15k_15k_qos0_p256_1mps_3n_3v/max.png     | Bin 457564 -> 0 bytes
 .../false_15k_15k_qos0_p256_1mps_3n_3v/mean.png    | Bin 428277 -> 0 bytes
 .../false_15k_15k_qos0_p256_1mps_3n_3v/mem.png     | Bin 194051 -> 0 bytes
 .../false_15k_15k_qos0_p256_1mps_3n_3v/p99.png     | Bin 450467 -> 0 bytes
 .../false_15k_15k_qos0_p256_1mps_3n_3v/qps.png     | Bin 362831 -> 0 bytes
 .../false_15k_15k_qos0_p256_1mps_3n_3v/result.html |  72 ---
 .../false_15k_15k_qos1_p256_1mps_1n_1v/cpu.png     | Bin 124342 -> 0 bytes
 .../false_15k_15k_qos1_p256_1mps_1n_1v/max.png     | Bin 493335 -> 0 bytes
 .../false_15k_15k_qos1_p256_1mps_1n_1v/mean.png    | Bin 449111 -> 0 bytes
 .../false_15k_15k_qos1_p256_1mps_1n_1v/mem.png     | Bin 160513 -> 0 bytes
 .../false_15k_15k_qos1_p256_1mps_1n_1v/p99.png     | Bin 449313 -> 0 bytes
 .../false_15k_15k_qos1_p256_1mps_1n_1v/qps.png     | Bin 365110 -> 0 bytes
 .../false_15k_15k_qos1_p256_1mps_1n_1v/result.html |  72 ---
 .../false_15k_15k_qos1_p256_1mps_3n_3v/cpu.png     | Bin 161174 -> 0 bytes
 .../false_15k_15k_qos1_p256_1mps_3n_3v/max.png     | Bin 448325 -> 0 bytes
 .../false_15k_15k_qos1_p256_1mps_3n_3v/mean.png    | Bin 421273 -> 0 bytes
 .../false_15k_15k_qos1_p256_1mps_3n_3v/mem.png     | Bin 231691 -> 0 bytes
 .../false_15k_15k_qos1_p256_1mps_3n_3v/p99.png     | Bin 448784 -> 0 bytes
 .../false_15k_15k_qos1_p256_1mps_3n_3v/qps.png     | Bin 369465 -> 0 bytes
 .../false_15k_15k_qos1_p256_1mps_3n_3v/result.html |  72 ---
 .../false_300_300_qos0_p32_50mps_1n_1v/cpu.png     | Bin 148546 -> 0 bytes
 .../false_300_300_qos0_p32_50mps_1n_1v/max.png     | Bin 423727 -> 0 bytes
 .../false_300_300_qos0_p32_50mps_1n_1v/mean.png    | Bin 406039 -> 0 bytes
 .../false_300_300_qos0_p32_50mps_1n_1v/mem.png     | Bin 180041 -> 0 bytes
 .../false_300_300_qos0_p32_50mps_1n_1v/p99.png     | Bin 430647 -> 0 bytes
 .../false_300_300_qos0_p32_50mps_1n_1v/qps.png     | Bin 356304 -> 0 bytes
 .../false_300_300_qos0_p32_50mps_1n_1v/result.html |  72 ---
 .../false_300_300_qos0_p32_50mps_3n_3v/cpu.png     | Bin 167043 -> 0 bytes
 .../false_300_300_qos0_p32_50mps_3n_3v/max.png     | Bin 468320 -> 0 bytes
 .../false_300_300_qos0_p32_50mps_3n_3v/mean.png    | Bin 427972 -> 0 bytes
 .../false_300_300_qos0_p32_50mps_3n_3v/mem.png     | Bin 224126 -> 0 bytes
 .../false_300_300_qos0_p32_50mps_3n_3v/p99.png     | Bin 476371 -> 0 bytes
 .../false_300_300_qos0_p32_50mps_3n_3v/qps.png     | Bin 365025 -> 0 bytes
 .../false_300_300_qos0_p32_50mps_3n_3v/result.html |  72 ---
 .../false_300_300_qos1_p32_50mps_1n_1v/cpu.png     | Bin 153309 -> 0 bytes
 .../false_300_300_qos1_p32_50mps_1n_1v/max.png     | Bin 523514 -> 0 bytes
 .../false_300_300_qos1_p32_50mps_1n_1v/mean.png    | Bin 494252 -> 0 bytes
 .../false_300_300_qos1_p32_50mps_1n_1v/mem.png     | Bin 177374 -> 0 bytes
 .../false_300_300_qos1_p32_50mps_1n_1v/p99.png     | Bin 518860 -> 0 bytes
 .../false_300_300_qos1_p32_50mps_1n_1v/qps.png     | Bin 384807 -> 0 bytes
 .../false_300_300_qos1_p32_50mps_1n_1v/result.html |  72 ---
 .../false_300_300_qos1_p32_50mps_3n_3v/cpu.png     | Bin 171693 -> 0 bytes
 .../false_300_300_qos1_p32_50mps_3n_3v/max.png     | Bin 484093 -> 0 bytes
 .../false_300_300_qos1_p32_50mps_3n_3v/mean.png    | Bin 432840 -> 0 bytes
 .../false_300_300_qos1_p32_50mps_3n_3v/mem.png     | Bin 235274 -> 0 bytes
 .../false_300_300_qos1_p32_50mps_3n_3v/p99.png     | Bin 453165 -> 0 bytes
 .../false_300_300_qos1_p32_50mps_3n_3v/qps.png     | Bin 367206 -> 0 bytes
 .../false_300_300_qos1_p32_50mps_3n_3v/result.html |  72 ---
 .../false_30k_30k_qos0_p256_1mps_3n_1v/cpu.png     | Bin 156205 -> 0 bytes
 .../false_30k_30k_qos0_p256_1mps_3n_1v/max.png     | Bin 447493 -> 0 bytes
 .../false_30k_30k_qos0_p256_1mps_3n_1v/mean.png    | Bin 455117 -> 0 bytes
 .../false_30k_30k_qos0_p256_1mps_3n_1v/mem.png     | Bin 221544 -> 0 bytes
 .../false_30k_30k_qos0_p256_1mps_3n_1v/p99.png     | Bin 446752 -> 0 bytes
 .../false_30k_30k_qos0_p256_1mps_3n_1v/qps.png     | Bin 374810 -> 0 bytes
 .../false_30k_30k_qos0_p256_1mps_3n_1v/result.html |  72 ---
 .../false_30k_30k_qos1_p256_1mps_3n_1v/cpu.png     | Bin 164699 -> 0 bytes
 .../false_30k_30k_qos1_p256_1mps_3n_1v/max.png     | Bin 480417 -> 0 bytes
 .../false_30k_30k_qos1_p256_1mps_3n_1v/mean.png    | Bin 458004 -> 0 bytes
 .../false_30k_30k_qos1_p256_1mps_3n_1v/mem.png     | Bin 217174 -> 0 bytes
 .../false_30k_30k_qos1_p256_1mps_3n_1v/p99.png     | Bin 434707 -> 0 bytes
 .../false_30k_30k_qos1_p256_1mps_3n_1v/qps.png     | Bin 372192 -> 0 bytes
 .../false_30k_30k_qos1_p256_1mps_3n_1v/result.html |  72 ---
 .../cpu.png                                        | Bin 156485 -> 0 bytes
 .../max.png                                        | Bin 392463 -> 0 bytes
 .../mean.png                                       | Bin 366103 -> 0 bytes
 .../mem.png                                        | Bin 230360 -> 0 bytes
 .../p99.png                                        | Bin 364874 -> 0 bytes
 .../qps.png                                        | Bin 396099 -> 0 bytes
 .../result.html                                    |  72 ---
 .../false_900_900_qos0_p32_50mps_3n_1v/cpu.png     | Bin 147359 -> 0 bytes
 .../false_900_900_qos0_p32_50mps_3n_1v/max.png     | Bin 415245 -> 0 bytes
 .../false_900_900_qos0_p32_50mps_3n_1v/mean.png    | Bin 424401 -> 0 bytes
 .../false_900_900_qos0_p32_50mps_3n_1v/mem.png     | Bin 247714 -> 0 bytes
 .../false_900_900_qos0_p32_50mps_3n_1v/p99.png     | Bin 427135 -> 0 bytes
 .../false_900_900_qos0_p32_50mps_3n_1v/qps.png     | Bin 341558 -> 0 bytes
 .../false_900_900_qos0_p32_50mps_3n_1v/result.html |  72 ---
 .../false_900_900_qos1_p32_50mps_3n_1v/cpu.png     | Bin 129250 -> 0 bytes
 .../false_900_900_qos1_p32_50mps_3n_1v/max.png     | Bin 432010 -> 0 bytes
 .../false_900_900_qos1_p32_50mps_3n_1v/mean.png    | Bin 433489 -> 0 bytes
 .../false_900_900_qos1_p32_50mps_3n_1v/mem.png     | Bin 235924 -> 0 bytes
 .../false_900_900_qos1_p32_50mps_3n_1v/p99.png     | Bin 431310 -> 0 bytes
 .../false_900_900_qos1_p32_50mps_3n_1v/qps.png     | Bin 359146 -> 0 bytes
 .../false_900_900_qos1_p32_50mps_3n_1v/result.html |  72 ---
 .../fanout_true_1_100000_qos0_p256_1mps_1n/cpu.png | Bin 138421 -> 0 bytes
 .../fanout_true_1_100000_qos0_p256_1mps_1n/max.png | Bin 482712 -> 0 bytes
 .../mean.png                                       | Bin 413584 -> 0 bytes
 .../fanout_true_1_100000_qos0_p256_1mps_1n/mem.png | Bin 186253 -> 0 bytes
 .../fanout_true_1_100000_qos0_p256_1mps_1n/p99.png | Bin 411878 -> 0 bytes
 .../fanout_true_1_100000_qos0_p256_1mps_1n/qps.png | Bin 389245 -> 0 bytes
 .../result.html                                    |  72 ---
 .../fanout_true_1_100000_qos1_p256_1mps_1n/cpu.png | Bin 138421 -> 0 bytes
 .../fanout_true_1_100000_qos1_p256_1mps_1n/max.png | Bin 482712 -> 0 bytes
 .../mean.png                                       | Bin 413584 -> 0 bytes
 .../fanout_true_1_100000_qos1_p256_1mps_1n/mem.png | Bin 186253 -> 0 bytes
 .../fanout_true_1_100000_qos1_p256_1mps_1n/p99.png | Bin 411878 -> 0 bytes
 .../fanout_true_1_100000_qos1_p256_1mps_1n/qps.png | Bin 389245 -> 0 bytes
 .../result.html                                    |  72 ---
 .../fanout_true_1_200000_qos1_p256_1mps_3n/cpu.png | Bin 174708 -> 0 bytes
 .../fanout_true_1_200000_qos1_p256_1mps_3n/max.png | Bin 463804 -> 0 bytes
 .../mean.png                                       | Bin 491642 -> 0 bytes
 .../fanout_true_1_200000_qos1_p256_1mps_3n/mem.png | Bin 210477 -> 0 bytes
 .../fanout_true_1_200000_qos1_p256_1mps_3n/p99.png | Bin 476914 -> 0 bytes
 .../fanout_true_1_200000_qos1_p256_1mps_3n/qps.png | Bin 392552 -> 0 bytes
 .../result.html                                    |  72 ---
 .../fanout_true_1_300000_qos0_p256_1mps_3n/cpu.png | Bin 168359 -> 0 bytes
 .../fanout_true_1_300000_qos0_p256_1mps_3n/max.png | Bin 425551 -> 0 bytes
 .../mean.png                                       | Bin 416007 -> 0 bytes
 .../fanout_true_1_300000_qos0_p256_1mps_3n/mem.png | Bin 208450 -> 0 bytes
 .../fanout_true_1_300000_qos0_p256_1mps_3n/p99.png | Bin 397548 -> 0 bytes
 .../fanout_true_1_300000_qos0_p256_1mps_3n/qps.png | Bin 397553 -> 0 bytes
 .../result.html                                    |  72 ---
 .../share_true_100k_1000_qos0_p256_1mps_1n/cpu.png | Bin 127396 -> 0 bytes
 .../share_true_100k_1000_qos0_p256_1mps_1n/max.png | Bin 468560 -> 0 bytes
 .../mean.png                                       | Bin 422977 -> 0 bytes
 .../share_true_100k_1000_qos0_p256_1mps_1n/mem.png | Bin 132604 -> 0 bytes
 .../share_true_100k_1000_qos0_p256_1mps_1n/p99.png | Bin 406178 -> 0 bytes
 .../share_true_100k_1000_qos0_p256_1mps_1n/qps.png | Bin 382632 -> 0 bytes
 .../result.html                                    |  72 ---
 .../share_true_100k_1000_qos1_p256_1mps_1n/cpu.png | Bin 127592 -> 0 bytes
 .../share_true_100k_1000_qos1_p256_1mps_1n/max.png | Bin 499702 -> 0 bytes
 .../mean.png                                       | Bin 459028 -> 0 bytes
 .../share_true_100k_1000_qos1_p256_1mps_1n/mem.png | Bin 131975 -> 0 bytes
 .../share_true_100k_1000_qos1_p256_1mps_1n/p99.png | Bin 477290 -> 0 bytes
 .../share_true_100k_1000_qos1_p256_1mps_1n/qps.png | Bin 391096 -> 0 bytes
 .../result.html                                    |  72 ---
 .../share_true_200k_2000_qos1_p256_1mps_3n/cpu.png | Bin 147805 -> 0 bytes
 .../share_true_200k_2000_qos1_p256_1mps_3n/max.png | Bin 476120 -> 0 bytes
 .../mean.png                                       | Bin 502200 -> 0 bytes
 .../share_true_200k_2000_qos1_p256_1mps_3n/mem.png | Bin 194208 -> 0 bytes
 .../share_true_200k_2000_qos1_p256_1mps_3n/p99.png | Bin 453390 -> 0 bytes
 .../share_true_200k_2000_qos1_p256_1mps_3n/qps.png | Bin 381698 -> 0 bytes
 .../result.html                                    |  72 ---
 .../share_true_300k_3000_qos0_p256_1mps_3n/cpu.png | Bin 138421 -> 0 bytes
 .../share_true_300k_3000_qos0_p256_1mps_3n/max.png | Bin 482712 -> 0 bytes
 .../mean.png                                       | Bin 413584 -> 0 bytes
 .../share_true_300k_3000_qos0_p256_1mps_3n/mem.png | Bin 186253 -> 0 bytes
 .../share_true_300k_3000_qos0_p256_1mps_3n/p99.png | Bin 411878 -> 0 bytes
 .../share_true_300k_3000_qos0_p256_1mps_3n/qps.png | Bin 389245 -> 0 bytes
 .../result.html                                    |  72 ---
 .../true_1.5k_1.5k_qos1_p32_100mps_1n/cpu.png      | Bin 128543 -> 0 bytes
 .../true_1.5k_1.5k_qos1_p32_100mps_1n/max.png      | Bin 519155 -> 0 bytes
 .../true_1.5k_1.5k_qos1_p32_100mps_1n/mean.png     | Bin 453879 -> 0 bytes
 .../true_1.5k_1.5k_qos1_p32_100mps_1n/mem.png      | Bin 135557 -> 0 bytes
 .../true_1.5k_1.5k_qos1_p32_100mps_1n/p99.png      | Bin 503262 -> 0 bytes
 .../true_1.5k_1.5k_qos1_p32_100mps_1n/qps.png      | Bin 393079 -> 0 bytes
 .../true_1.5k_1.5k_qos1_p32_100mps_1n/result.html  |  72 ---
 .../true_100k_100k_qos0_p256_1mps_1n/cpu.png       | Bin 136092 -> 0 bytes
 .../true_100k_100k_qos0_p256_1mps_1n/max.png       | Bin 456324 -> 0 bytes
 .../true_100k_100k_qos0_p256_1mps_1n/mean.png      | Bin 426233 -> 0 bytes
 .../true_100k_100k_qos0_p256_1mps_1n/mem.png       | Bin 138886 -> 0 bytes
 .../true_100k_100k_qos0_p256_1mps_1n/p99.png       | Bin 427125 -> 0 bytes
 .../true_100k_100k_qos0_p256_1mps_1n/qps.png       | Bin 399792 -> 0 bytes
 .../true_100k_100k_qos0_p256_1mps_1n/result.html   |  72 ---
 .../true_100k_100k_qos1_p256_1mps_1n/cpu.png       | Bin 108749 -> 0 bytes
 .../true_100k_100k_qos1_p256_1mps_1n/max.png       | Bin 532626 -> 0 bytes
 .../true_100k_100k_qos1_p256_1mps_1n/mean.png      | Bin 541320 -> 0 bytes
 .../true_100k_100k_qos1_p256_1mps_1n/mem.png       | Bin 139607 -> 0 bytes
 .../true_100k_100k_qos1_p256_1mps_1n/p99.png       | Bin 529164 -> 0 bytes
 .../true_100k_100k_qos1_p256_1mps_1n/qps.png       | Bin 414141 -> 0 bytes
 .../true_100k_100k_qos1_p256_1mps_1n/result.html   |  72 ---
 .../true_200k_200k_qos1_p256_1mps_3n/cpu.png       | Bin 144086 -> 0 bytes
 .../true_200k_200k_qos1_p256_1mps_3n/mem.png       | Bin 210516 -> 0 bytes
 .../true_200k_200k_qos1_p256_1mps_3n/result.html   |  72 ---
 .../true_250k_250k_qos0_p256_1mps_3n/cpu.png       | Bin 141368 -> 0 bytes
 .../true_250k_250k_qos0_p256_1mps_3n/max.png       | Bin 511336 -> 0 bytes
 .../true_250k_250k_qos0_p256_1mps_3n/mean.png      | Bin 441334 -> 0 bytes
 .../true_250k_250k_qos0_p256_1mps_3n/mem.png       | Bin 182460 -> 0 bytes
 .../true_250k_250k_qos0_p256_1mps_3n/p99.png       | Bin 439309 -> 0 bytes
 .../true_250k_250k_qos0_p256_1mps_3n/qps.png       | Bin 410246 -> 0 bytes
 .../true_250k_250k_qos0_p256_1mps_3n/result.html   |  72 ---
 .../images/true_2k_2k_qos0_p32_100mps_1n/cpu.png   | Bin 128590 -> 0 bytes
 .../images/true_2k_2k_qos0_p32_100mps_1n/max.png   | Bin 331258 -> 0 bytes
 .../images/true_2k_2k_qos0_p32_100mps_1n/mean.png  | Bin 341395 -> 0 bytes
 .../images/true_2k_2k_qos0_p32_100mps_1n/mem.png   | Bin 126026 -> 0 bytes
 .../images/true_2k_2k_qos0_p32_100mps_1n/p99.png   | Bin 339018 -> 0 bytes
 .../images/true_2k_2k_qos0_p32_100mps_1n/qps.png   | Bin 291957 -> 0 bytes
 .../true_2k_2k_qos0_p32_100mps_1n/result.html      |  72 ---
 .../images/true_4k_4k_qos1_p32_100mps_3n/cpu.png   | Bin 148154 -> 0 bytes
 .../images/true_4k_4k_qos1_p32_100mps_3n/max.png   | Bin 375398 -> 0 bytes
 .../images/true_4k_4k_qos1_p32_100mps_3n/mean.png  | Bin 353213 -> 0 bytes
 .../images/true_4k_4k_qos1_p32_100mps_3n/mem.png   | Bin 183773 -> 0 bytes
 .../images/true_4k_4k_qos1_p32_100mps_3n/p99.png   | Bin 347844 -> 0 bytes
 .../images/true_4k_4k_qos1_p32_100mps_3n/qps.png   | Bin 289837 -> 0 bytes
 .../true_4k_4k_qos1_p32_100mps_3n/result.html      |  72 ---
 .../images/true_5k_5k_qos0_p32_100mps_3n/cpu.png   | Bin 158592 -> 0 bytes
 .../images/true_5k_5k_qos0_p32_100mps_3n/max.png   | Bin 348310 -> 0 bytes
 .../images/true_5k_5k_qos0_p32_100mps_3n/mean.png  | Bin 327563 -> 0 bytes
 .../images/true_5k_5k_qos0_p32_100mps_3n/mem.png   | Bin 196465 -> 0 bytes
 .../images/true_5k_5k_qos0_p32_100mps_3n/p99.png   | Bin 323008 -> 0 bytes
 .../images/true_5k_5k_qos0_p32_100mps_3n/qps.png   | Bin 296054 -> 0 bytes
 .../true_5k_5k_qos0_p32_100mps_3n/result.html      |  72 ---
 .../version-4.0.x.json                             |  66 ---
 .../01_get_started/1_quick_install.md              |  13 -
 .../version-4.0.x/01_get_started/2_quick_verify.md |  30 --
 .../version-4.0.x/01_get_started/3_faq.md          |  44 --
 .../version-4.0.x/01_get_started/_category_.json   |   8 -
 .../01_get_started/images/newconn.jpg              | Bin 312148 -> 0 bytes
 .../01_get_started/images/publish.jpg              | Bin 298876 -> 0 bytes
 .../01_get_started/images/subscribe.jpg            | Bin 211030 -> 0 bytes
 .../version-4.0.x/01_get_started/intro.md          |  43 --
 .../version-4.0.x/02_installation/1_docker.md      |  35 --
 .../version-4.0.x/02_installation/2_linux.md       |  16 -
 .../version-4.0.x/02_installation/3_windows.md     |  17 -
 .../02_installation/4_install_from_source.md       |  32 --
 .../02_installation/5_config_migration.md          |   8 -
 .../02_installation/6_nodes_on_k8s.md              |  32 --
 .../version-4.0.x/02_installation/_category_.json  |   8 -
 .../version-4.0.x/02_installation/intro.md         |  39 --
 .../version-4.0.x/04_cluster/1_standardcluster.md  |  69 ---
 .../04_cluster/2_high_availability.md              |  68 ---
 .../version-4.0.x/04_cluster/3_upgrade.md          |  86 ----
 .../version-4.0.x/04_cluster/_category_.json       |   8 -
 .../04_cluster/images/IndependentWorkload.png      | Bin 231896 -> 0 bytes
 .../version-4.0.x/04_cluster/intro.md              |  34 --
 .../05_user_guide/1_basic/1_connect.md             |  20 -
 .../05_user_guide/1_basic/2_pubsub.md              |  39 --
 .../05_user_guide/1_basic/3_shared_sub.md          |  21 -
 .../05_user_guide/1_basic/_category_.json          |   8 -
 .../1_basic/images/pub-sub-pattern.png             | Bin 372353 -> 0 bytes
 .../1_basic/images/shared-subscription.png         | Bin 489533 -> 0 bytes
 .../version-4.0.x/05_user_guide/1_basic/intro.md   |  17 -
 .../05_user_guide/2_integration/1_integration.md   |  26 -
 .../05_user_guide/2_integration/_category_.json    |   8 -
 .../2_integration/images/bifromqapproach.jpg       | Bin 133675 -> 0 bytes
 .../2_integration/images/commonapproach.jpg        | Bin 129120 -> 0 bytes
 .../2_integration/images/integration.png           | Bin 300130 -> 0 bytes
 .../05_user_guide/2_integration/intro.md           |  56 ---
 .../05_user_guide/3_api/1_api_reference.md         | 127 -----
 .../05_user_guide/3_api/_category_.json            |   8 -
 .../05_user_guide/3_api/images/API-Arch.png        | Bin 25560 -> 0 bytes
 .../version-4.0.x/05_user_guide/3_api/intro.md     |  15 -
 .../version-4.0.x/05_user_guide/_category_.json    |   8 -
 .../version-4.0.x/05_user_guide/intro.md           |  19 -
 .../version-4.0.x/06_plugin/1_auth_provider.md     | 386 ---------------
 .../version-4.0.x/06_plugin/2_event_collector.md   |  42 --
 .../06_plugin/3_resource_throttler.md              | 135 -----
 .../4_setting_provider/1_tenantsetting.md          |  49 --
 .../06_plugin/4_setting_provider/_category_.json   |   8 -
 .../06_plugin/4_setting_provider/intro.md          | 123 -----
 .../version-4.0.x/06_plugin/5_plugin_practice.md   |  73 ---
 .../version-4.0.x/06_plugin/_category_.json        |   8 -
 .../version-4.0.x/06_plugin/intro.md               |  66 ---
 .../01_configuration/1_config_file_manual.md       | 116 -----
 .../01_configuration/2_bifromq_sys_props.md        |  54 --
 .../01_configuration/3_configs_print.md            |  88 ----
 .../01_configuration/_category_.json               |   8 -
 .../07_admin_guide/01_configuration/intro.md       |  11 -
 .../07_admin_guide/02_tuning/1_os_tuning_linux.md  |  58 ---
 .../07_admin_guide/02_tuning/_category_.json       |   8 -
 .../07_admin_guide/02_tuning/intro.md              |  29 --
 .../07_admin_guide/03_observability/01_logging.md  |  18 -
 .../07_admin_guide/03_observability/03_events.md   |  21 -
 .../03_observability/_category_.json               |   8 -
 .../07_admin_guide/03_observability/intro.md       |   7 -
 .../03_observability/metrics/_category_.json       |   8 -
 .../03_observability/metrics/intro.md              |  21 -
 .../03_observability/metrics/tenantmetrics.md      |  60 ---
 .../07_admin_guide/04_security/_category_.json     |   8 -
 .../07_admin_guide/04_security/intro.md            |  25 -
 .../version-4.0.x/07_admin_guide/_category_.json   |   8 -
 .../version-4.0.x/07_admin_guide/intro.md          |   7 -
 .../version-4.0.x/98_mqtt_best_practices/1_spec.md |  11 -
 .../98_mqtt_best_practices/2_about_mqtt.md         |  64 ---
 .../98_mqtt_best_practices/3_mqtt_parameters.md    |  49 --
 .../98_mqtt_best_practices/4_topicfilter_design.md |  32 --
 .../98_mqtt_best_practices/_category_.json         |   8 -
 .../version-4.0.x/999_bifromq_inside.md            |  18 -
 .../docusaurus-plugin-content-pages/roadmap.md     |  13 -
 i18n/zh-Hans/docusaurus-theme-classic/footer.json  |  34 --
 i18n/zh-Hans/docusaurus-theme-classic/navbar.json  |  22 -
 package.json                                       |   3 +-
 1690 files changed, 78 insertions(+), 32648 deletions(-)

diff --git a/docusaurus.config.ts b/docusaurus.config.ts
index ec1f69b7..ac05b02e 100644
--- a/docusaurus.config.ts
+++ b/docusaurus.config.ts
@@ -1,7 +1,7 @@
-import {themes as prismThemes} from 'prism-react-renderer';
-import type {Config} from '@docusaurus/types';
+import { themes as prismThemes } from 'prism-react-renderer';
+import type { Config } from '@docusaurus/types';
 import type * as Preset from '@docusaurus/preset-classic';
-import {releaseVersion} from './releaseInfo';
+import { releaseVersion } from './releaseInfo';
 
 const lightCodeTheme = prismThemes.github;
 const darkCodeTheme = prismThemes.dracula;
@@ -20,10 +20,7 @@ const config: Config = {
 
   onBrokenLinks: 'throw',
   trailingSlash: true,
-  i18n: {
-    defaultLocale: 'en',
-    locales: ['en'],
-  },
+
 
   markdown: {
     mermaid: true,
@@ -31,6 +28,24 @@ const config: Config = {
       onBrokenMarkdownLinks: 'throw',
     },
   },
+
+  headTags: [
+    {
+      tagName: 'link',
+      attributes: {
+        rel: 'preconnect',
+        href: 'https://fonts.googleapis.com',
+      },
+    },
+    {
+      tagName: 'link',
+      attributes: {
+        rel: 'preconnect',
+        href: 'https://fonts.gstatic.com',
+        crossorigin: 'anonymous',
+      },
+    },
+  ],
   themes: [
     [
       '@docusaurus/theme-mermaid',
@@ -52,7 +67,7 @@ const config: Config = {
       {
         docs: {
           sidebarPath: './sidebars.ts',
-          editUrl: ({versionDocsDirPath, docPath}) =>
+          editUrl: ({ versionDocsDirPath, docPath }) =>
             `https://github.com/apache/${siteRepoName}/tree/master/${versionDocsDirPath}/${docPath}`,
           lastVersion: 'current',
           versions: {
@@ -102,20 +117,21 @@ const config: Config = {
       },
     },
     navbar: {
-      title: 'Apache BifroMQ (Incubating)',
+      title: 'BifroMQ', // Minimalist title
       hideOnScroll: false,
       logo: {
-        alt: 'BifroMQ Logo',
+        alt: 'Apache BifroMQ',
         src: 'img/logo.svg',
         srcDark: 'img/logo_dark.svg',
-        className: 'bifromq-navbar-logo-class',
+        className: 'bifromq-navbar-logo-class', // Keep class for custom override if needed
+        style: { height: '32px', width: 'auto' }, // Inline hint, handled by CSS mostly
       },
       items: [
         {
           type: 'docSidebar',
           sidebarId: 'tutorialSidebar',
           position: 'right',
-          label: 'Docs',
+          label: 'Documentation',
         },
         {
           to: '/blog',
@@ -129,7 +145,7 @@ const config: Config = {
         },
         {
           to: '/download',
-          label: 'Download',
+          label: 'Downloads',
           position: 'right',
         },
         {
@@ -144,11 +160,11 @@ const config: Config = {
         },
         {
           type: 'dropdown',
-          label: 'ASF',
+          label: 'Foundation',
           position: 'right',
           items: [
             {
-              label: 'Foundation',
+              label: 'Apache Software Foundation',
               to: 'https://www.apache.org/',
             },
             {
@@ -159,10 +175,6 @@ const config: Config = {
               label: 'Events',
               to: 'https://www.apache.org/events/current-event.html',
             },
-            {
-              label: 'Privacy',
-              to: 'https://privacy.apache.org/policies/privacy-policy-public.html',
-            },
             {
               label: 'Security',
               to: 'https://www.apache.org/security/',
@@ -179,6 +191,10 @@ const config: Config = {
               label: 'Code of Conduct',
               to: 'https://www.apache.org/foundation/policies/conduct.html',
             },
+            {
+              label: 'Privacy Policy',
+              to: 'https://privacy.apache.org/policies/privacy-policy-public.html',
+            },
           ],
         },
         {
@@ -190,105 +206,74 @@ const config: Config = {
       ],
     },
     footer: {
-      style: 'dark',
+      style: 'light',
       links: [
         {
           title: 'Apache BifroMQ',
           items: [
             {
-              html: `<span class="footer__link-item">High-performance Apache MQTT broker with enterprise-grade reliability. Applicable to IoT, IM and other scenarios.</span>`,
+              html: `
+                <div style="margin-bottom: 2rem;">
+                  <div style="font-weight: 800; font-size: 1.25rem; letter-spacing: -0.02em; margin-bottom: 0.5rem;">BifroMQ</div>
+                  <p style="font-size: 0.9rem; line-height: 1.6; color: var(--color-text-secondary); max-width: 300px;">
+                    Next-generation high-performance, multi-tenant MQTT broker for industrial-scale IoT.
+                  </p>
+                </div>
+              `,
             },
+            { label: 'Introduction', to: '/docs/get_started/intro' },
+            { label: 'Downloads', to: '/download' },
+            { label: 'Changelog', href: 'https://github.com/apache/bifromq/releases' },
           ],
         },
         {
-          title: 'Contact / Community',
+          title: 'Development',
           items: [
-            {
-              label: 'Email: dev@bifromq.apache.org',
-              href: 'mailto:dev@bifromq.apache.org',
-            },
-            {
-              label: 'Discord: https://discord.gg/Pfs3QRadRB',
-              href: 'https://discord.gg/Pfs3QRadRB',
-            },
-            {
-              label: 'GitHub: https://github.com/apache/bifromq',
-              href: 'https://github.com/apache/bifromq',
-            },
+            { label: 'GitHub', href: 'https://github.com/apache/bifromq' },
+            { label: 'Issues', href: 'https://github.com/apache/bifromq/issues' },
+            { label: 'API Docs', to: '/docs/user_guide/api/openapi' },
           ],
         },
         {
-          title: 'Resources',
+          title: 'Community',
           items: [
-            {
-              label: 'GitHub: https://github.com/apache/bifromq',
-              href: 'https://github.com/apache/bifromq',
-            },
-            {
-              label: 'Releases: /docs/get_started/download/intro/',
-              to: '/docs/get_started/download/intro/',
-            },
-            {
-              label: 'Issues: https://github.com/apache/bifromq/issues',
-              href: 'https://github.com/apache/bifromq/issues',
-            },
+            { label: 'Discord', href: 'https://discord.gg/Pfs3QRadRB' },
+            { label: 'Mailing List', href: 'mailto:dev@bifromq.apache.org' },
+            { label: 'Blog', to: '/blog' },
+            { label: 'Contribution', to: '/community' },
           ],
         },
         {
           title: 'Apache',
           items: [
-            {
-              label: 'Apache Incubator: https://incubator.apache.org/',
-              href: 'https://incubator.apache.org/',
-            },
-            {
-              label: 'Code of Conduct: https://www.apache.org/foundation/policies/conduct',
-              href: 'https://www.apache.org/foundation/policies/conduct',
-            },
-            {
-              label: 'Apache 2.0 License: https://www.apache.org/licenses/LICENSE-2.0',
-              href: 'https://www.apache.org/licenses/LICENSE-2.0',
-            },
-          ],
-        },
-        {
-          title: 'Others',
-          items: [
-            {
-              label: 'Thanks OpenSource@Baidu: https://opensource.baidu.com/',
-              href: 'https://opensource.baidu.com/',
-            },
-            {
-              label:
-                'MQTT v3.1.1: https://docs.oasis-open.org/mqtt/mqtt/v3.1.1/os/mqtt-v3.1.1-os.html',
-              href: 'https://docs.oasis-open.org/mqtt/mqtt/v3.1.1/os/mqtt-v3.1.1-os.html',
-            },
-            {
-              label:
-                'MQTT v5.0: https://docs.oasis-open.org/mqtt/mqtt/v5.0/mqtt-v5.0.html',
-              href: 'https://docs.oasis-open.org/mqtt/mqtt/v5.0/mqtt-v5.0.html',
-            },
+            { label: 'Foundation', href: 'https://www.apache.org/' },
+            { label: 'License', href: 'https://www.apache.org/licenses/LICENSE-2.0' },
+            { label: 'Sponsorship', href: 'https://www.apache.org/foundation/sponsorship.html' },
+            { label: 'Security', href: 'https://www.apache.org/security/' },
           ],
         },
       ],
       logo: {
-        width: 200,
+        width: 180,
         src: '/img/apache-incubator.svg',
         href: 'https://incubator.apache.org/',
-        alt: 'Apache Incubator logo',
+        alt: 'Apache Incubator',
       },
-      copyright: `<div>
-      <p>
-        © 2026 Apache Software Foundation. Licensed under Apache License 2.0. <br/>
-        Apache Incubating
-      </p>
-      <p>
-        Apache ${projectName} 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 code, it does indicate t [...]
-      </p>
-      <p>
-        Apache, the names of Apache projects, and the feather logo are either registered trademarks or trademarks of the Apache Software Foundation in the United States and/or other countries.
-      </p>
-      </div>`,
+      copyright: `
+        <div style="font-size: 0.85rem; line-height: 1.8; color: var(--color-text-tertiary); margin-top: 2rem;">
+          <p>
+            Copyright © ${new Date().getFullYear()} The Apache Software Foundation. 
+            Licensed under the <a href="https://www.apache.org/licenses/LICENSE-2.0" style="color: var(--bifrost-blue); text-decoration: none;">Apache License, Version 2.0</a>.
+          </p>
+          <p>
+            Apache BifroMQ, BifroMQ, Apache, the Apache feather logo, and the Apache BifroMQ project logo are either 
+            registered trademarks or trademarks of The Apache Software Foundation.
+          </p>
+          <p style="margin-top: 1.5rem; font-style: italic; font-size: 0.8rem;">
+             Apache BifroMQ is an effort undergoing incubation at The Apache Software Foundation (ASF), sponsored by the Apache Incubator.
+          </p>
+        </div>
+      `,
     },
     prism: {
       theme: lightCodeTheme,
diff --git a/i18n/zh-Hans/code.json b/i18n/zh-Hans/code.json
deleted file mode 100644
index d5f9cea3..00000000
--- a/i18n/zh-Hans/code.json
+++ /dev/null
@@ -1,420 +0,0 @@
-{
-  "Comming soon": {
-    "message": "即将开源"
-  },
-  "Get Started": {
-    "message": "现在开始"
-  },
-  "is a Java-based high-performance MQTT Broker messaging middleware that adopts Multi-tenancy architecture.": {
-    "message": " 是一个高性能的 MQTT 消息中间件,采用原生多租户架构。"
-  },
-  "theme.ErrorPageContent.title": {
-    "message": "页面已崩溃。",
-    "description": "The title of the fallback page when the page crashed"
-  },
-  "theme.NotFound.title": {
-    "message": "找不到页面",
-    "description": "The title of the 404 page"
-  },
-  "theme.NotFound.p1": {
-    "message": "我们找不到您要找的页面。",
-    "description": "The first paragraph of the 404 page"
-  },
-  "theme.NotFound.p2": {
-    "message": "请联系原始链接来源网站的所有者,并告知他们链接已损坏。",
-    "description": "The 2nd paragraph of the 404 page"
-  },
-  "theme.admonition.note": {
-    "message": "备注",
-    "description": "The default label used for the Note admonition (:::note)"
-  },
-  "theme.admonition.tip": {
-    "message": "提示",
-    "description": "The default label used for the Tip admonition (:::tip)"
-  },
-  "theme.admonition.danger": {
-    "message": "危险",
-    "description": "The default label used for the Danger admonition (:::danger)"
-  },
-  "theme.admonition.info": {
-    "message": "信息",
-    "description": "The default label used for the Info admonition (:::info)"
-  },
-  "theme.admonition.caution": {
-    "message": "警告",
-    "description": "The default label used for the Caution admonition (:::caution)"
-  },
-  "theme.blog.archive.title": {
-    "message": "历史博客",
-    "description": "The page & hero title of the blog archive page"
-  },
-  "theme.blog.archive.description": {
-    "message": "历史博客",
-    "description": "The page & hero description of the blog archive page"
-  },
-  "theme.BackToTopButton.buttonAriaLabel": {
-    "message": "回到顶部",
-    "description": "The ARIA label for the back to top button"
-  },
-  "theme.blog.paginator.navAriaLabel": {
-    "message": "博客列表分页导航",
-    "description": "The ARIA label for the blog pagination"
-  },
-  "theme.blog.paginator.newerEntries": {
-    "message": "较新的博客",
-    "description": "The label used to navigate to the newer blog posts page (previous page)"
-  },
-  "theme.blog.paginator.olderEntries": {
-    "message": "较旧的博客",
-    "description": "The label used to navigate to the older blog posts page (next page)"
-  },
-  "theme.blog.post.paginator.navAriaLabel": {
-    "message": "博客分页导航",
-    "description": "The ARIA label for the blog posts pagination"
-  },
-  "theme.blog.post.paginator.newerPost": {
-    "message": "较新一篇",
-    "description": "The blog post button label to navigate to the newer/previous post"
-  },
-  "theme.blog.post.paginator.olderPost": {
-    "message": "较旧一篇",
-    "description": "The blog post button label to navigate to the older/next post"
-  },
-  "theme.blog.post.plurals": {
-    "message": "{count} 篇博客",
-    "description": "Pluralized label for \"{count} posts\". Use as much plural forms (separated by \"|\") as your language support (see https://www.unicode.org/cldr/cldr-aux/charts/34/supplemental/language_plural_rules.html)"
-  },
-  "theme.blog.tagTitle": {
-    "message": "{nPosts} 含有标签「{tagName}」",
-    "description": "The title of the page for a blog tag"
-  },
-  "theme.tags.tagsPageLink": {
-    "message": "查看所有标签",
-    "description": "The label of the link targeting the tag list page"
-  },
-  "theme.docs.breadcrumbs.navAriaLabel": {
-    "message": "页面路径",
-    "description": "The ARIA label for the breadcrumbs"
-  },
-  "theme.docs.DocCard.categoryDescription": {
-    "message": "{count} 个项目",
-    "description": "The default description for a category card in the generated index about how many items this category includes"
-  },
-  "theme.colorToggle.ariaLabel": {
-    "message": "切换浅色/暗黑模式(当前为{mode})",
-    "description": "The ARIA label for the navbar color mode toggle"
-  },
-  "theme.colorToggle.ariaLabel.mode.dark": {
-    "message": "暗黑模式",
-    "description": "The name for the dark color mode"
-  },
-  "theme.colorToggle.ariaLabel.mode.light": {
-    "message": "浅色模式",
-    "description": "The name for the light color mode"
-  },
-  "theme.docs.paginator.navAriaLabel": {
-    "message": "文件选项卡",
-    "description": "The ARIA label for the docs pagination"
-  },
-  "theme.docs.paginator.previous": {
-    "message": "上一页",
-    "description": "The label used to navigate to the previous doc"
-  },
-  "theme.docs.paginator.next": {
-    "message": "下一页",
-    "description": "The label used to navigate to the next doc"
-  },
-  "theme.docs.tagDocListPageTitle.nDocsTagged": {
-    "message": "{count} 篇文档带有标签",
-    "description": "Pluralized label for \"{count} docs tagged\". Use as much plural forms (separated by \"|\") as your language support (see https://www.unicode.org/cldr/cldr-aux/charts/34/supplemental/language_plural_rules.html)"
-  },
-  "theme.docs.tagDocListPageTitle": {
-    "message": "{nDocsTagged}「{tagName}」",
-    "description": "The title of the page for a docs tag"
-  },
-  "theme.docs.versionBadge.label": {
-    "message": "版本:{versionLabel}"
-  },
-  "theme.common.editThisPage": {
-    "message": "编辑此页",
-    "description": "The link label to edit the current page"
-  },
-  "theme.docs.versions.unreleasedVersionLabel": {
-    "message": "此为 {siteTitle} {versionLabel} 版尚未发行的文档。",
-    "description": "The label used to tell the user that he's browsing an unreleased doc version"
-  },
-  "theme.docs.versions.unmaintainedVersionLabel": {
-    "message": "此为 {siteTitle} {versionLabel} 版的文档,现已不再积极维护。",
-    "description": "The label used to tell the user that he's browsing an unmaintained doc version"
-  },
-  "theme.docs.versions.latestVersionSuggestionLabel": {
-    "message": "最新的文档请参阅 {latestVersionLink} ({versionLabel})。",
-    "description": "The label used to tell the user to check the latest version"
-  },
-  "theme.docs.versions.latestVersionLinkLabel": {
-    "message": "最新版本",
-    "description": "The label used for the latest version suggestion link label"
-  },
-  "theme.common.headingLinkTitle": {
-    "message": "{heading}的直接链接",
-    "description": "Title for link to heading"
-  },
-  "theme.lastUpdated.atDate": {
-    "message": "于 {date} ",
-    "description": "The words used to describe on which date a page has been last updated"
-  },
-  "theme.lastUpdated.byUser": {
-    "message": "由 {user} ",
-    "description": "The words used to describe by who the page has been last updated"
-  },
-  "theme.lastUpdated.lastUpdatedAtBy": {
-    "message": "最后{byUser}{atDate}更新",
-    "description": "The sentence used to display when a page has been last updated, and by who"
-  },
-  "theme.navbar.mobileVersionsDropdown.label": {
-    "message": "选择版本",
-    "description": "The label for the navbar versions dropdown on mobile view"
-  },
-  "theme.AnnouncementBar.closeButtonAriaLabel": {
-    "message": "关闭",
-    "description": "The ARIA label for close button of announcement bar"
-  },
-  "theme.tags.tagsListLabel": {
-    "message": "标签:",
-    "description": "The label alongside a tag list"
-  },
-  "theme.blog.sidebar.navAriaLabel": {
-    "message": "最近博客导航",
-    "description": "The ARIA label for recent posts in the blog sidebar"
-  },
-  "theme.CodeBlock.copied": {
-    "message": "复制成功",
-    "description": "The copied button label on code blocks"
-  },
-  "theme.CodeBlock.copyButtonAriaLabel": {
-    "message": "复制代码到剪贴板",
-    "description": "The ARIA label for copy code blocks button"
-  },
-  "theme.CodeBlock.copy": {
-    "message": "复制",
-    "description": "The copy button label on code blocks"
-  },
-  "theme.CodeBlock.wordWrapToggle": {
-    "message": "切换自动换行",
-    "description": "The title attribute for toggle word wrapping button of code block lines"
-  },
-  "theme.DocSidebarItem.toggleCollapsedCategoryAriaLabel": {
-    "message": "打开/收起侧边栏菜单「{label}」",
-    "description": "The ARIA label to toggle the collapsible sidebar category"
-  },
-  "theme.NavBar.navAriaLabel": {
-    "message": "主导航",
-    "description": "The ARIA label for the main navigation"
-  },
-  "theme.blog.post.readMore": {
-    "message": "阅读更多",
-    "description": "The label used in blog post item excerpts to link to full blog posts"
-  },
-  "theme.blog.post.readMoreLabel": {
-    "message": "阅读 {title} 的全文",
-    "description": "The ARIA label for the link to full blog posts from excerpts"
-  },
-  "theme.navbar.mobileLanguageDropdown.label": {
-    "message": "选择语言",
-    "description": "The label for the mobile language switcher dropdown"
-  },
-  "theme.blog.post.readingTime.plurals": {
-    "message": "阅读需 {readingTime} 分钟",
-    "description": "Pluralized label for \"{readingTime} min read\". Use as much plural forms (separated by \"|\") as your language support (see https://www.unicode.org/cldr/cldr-aux/charts/34/supplemental/language_plural_rules.html)"
-  },
-  "theme.docs.breadcrumbs.home": {
-    "message": "主页面",
-    "description": "The ARIA label for the home page in the breadcrumbs"
-  },
-  "theme.TOCCollapsible.toggleButtonLabel": {
-    "message": "本页总览",
-    "description": "The label used by the button on the collapsible TOC component"
-  },
-  "theme.docs.sidebar.collapseButtonTitle": {
-    "message": "收起侧边栏",
-    "description": "The title attribute for collapse button of doc sidebar"
-  },
-  "theme.docs.sidebar.collapseButtonAriaLabel": {
-    "message": "收起侧边栏",
-    "description": "The title attribute for collapse button of doc sidebar"
-  },
-  "theme.docs.sidebar.navAriaLabel": {
-    "message": "文档侧边栏",
-    "description": "The ARIA label for the sidebar navigation"
-  },
-  "theme.docs.sidebar.closeSidebarButtonAriaLabel": {
-    "message": "关闭导航栏",
-    "description": "The ARIA label for close button of mobile sidebar"
-  },
-  "theme.navbar.mobileSidebarSecondaryMenu.backButtonLabel": {
-    "message": "← 回到主菜单",
-    "description": "The label of the back button to return to main menu, inside the mobile navbar sidebar secondary menu (notably used to display the docs sidebar)"
-  },
-  "theme.docs.sidebar.toggleSidebarButtonAriaLabel": {
-    "message": "切换导航栏",
-    "description": "The ARIA label for hamburger menu button of mobile navigation"
-  },
-  "theme.docs.sidebar.expandButtonTitle": {
-    "message": "展开侧边栏",
-    "description": "The ARIA label and title attribute for expand button of doc sidebar"
-  },
-  "theme.docs.sidebar.expandButtonAriaLabel": {
-    "message": "展开侧边栏",
-    "description": "The ARIA label and title attribute for expand button of doc sidebar"
-  },
-  "theme.ErrorPageContent.tryAgain": {
-    "message": "重试",
-    "description": "The label of the button to try again rendering when the React error boundary captures an error"
-  },
-  "theme.common.skipToMainContent": {
-    "message": "跳到主要内容",
-    "description": "The skip to content label used for accessibility, allowing to rapidly navigate to main content with keyboard tab/enter navigation"
-  },
-  "theme.tags.tagsPageTitle": {
-    "message": "标签",
-    "description": "The title of the tag list page"
-  },
-  "Introduction": {
-    "message": "介绍"
-  },
-  "100% MQTT Support.": {
-    "message": "完整的 MQTT 支持。"
-  },
-  "Fully supports MQTT 3.1, 3.1.1 and 5.0 features over TCP, TLS, WS, WSS.": {
-    "message": "完全支持 MQTT 3.1、3.1.1 和 5.0 版本的特性,覆盖 TCP、TLS、WS、WSS。"
-  },
-  "Built-in storage engine.": {
-    "message": "内置存储引擎。"
-  },
-  "Optimized for critical load targeting, no third-party middleware dependencies.": {
-    "message": "针对关键负载定向优化,无第三方中间件依赖。"
-  },
-  "Native Multi-Tenancy.": {
-    "message": "原生支持多租户。"
-  },
-  "Built-in support for multi-tenancy resource sharing and workload isolation.": {
-    "message": "原生支持多租户资源共享和工作负载隔离。"
-  },
-  "Extensible Mechanisms.": {
-    "message": "扩展机制。"
-  },
-  "Supports extensions, including Authentication/Authorization, Event, and System/Tenant Monitoring.": {
-    "message": "支持各种扩展,包括认证/授权、事件和系统/租户级监控。"
-  },
-  "Trusted by the world’s most innovative teams": {
-    "message": "受到世界上具备创新精神的团队的信赖"
-  },
-  "Core Feature": {
-    "message": "核心特性"
-  },
-  "What is BifroMQ?": {
-    "message": "BifroMQ 是什么?"
-  },
-  "BifroMQ is a high-performance, distributed Apache MQTT broker implementation that seamlessly integrates native multi-tenancy support.": {
-    "message": "BifroMQ 是一个高性能的分布式 MQTT Broker 消息中间件实现,无缝集成了原生的多租户支持。"
-  },
-  "It is designed to support building large-scale IoT device connections and messaging systems, Currently, it serves as the foundational technology for Baidu IoT Core, a public cloud serverless service.": {
-    "message": "它旨在支持构建大规模的物联网设备连接和消息系统。它来源与百度物联网团队多年技术积累,并作为百度智能云物联网核心套件 IoT Core 的基础技术,这是一个公有云 Serverless 的 MQTT 服务。"
-  },
-  "Our track record": {
-    "message": "我们的成绩"
-  },
-  "Thanks to the operation of Baidu Intelligent Cloud (IoT Core), we have served thousands customers and a large number of device connections in the public cloud based on BifroMQ.": {
-    "message": "得益于百度智能云物联网核心套件(IoT Core)的运营,我们已经基于 BifroMQ 在公有云中服务了数千名客户,并经过亿级设备的接入验证。"
-  },
-  "Boost your productivity.": {
-    "message": "现在就来提高您的生产力吧。"
-  },
-  "Ready to get started ?": {
-    "message": "准备好开始了吗?"
-  },
-  "Get started": {
-    "message": "快速开始"
-  },
-  "Go to GitHub": {
-    "message": "前往 GitHub"
-  },
-  "MQTT Broker": {
-    "message": "MQTT Broker"
-  },
-  "High-Performance": {
-    "message": "性能强悍"
-  },
-  "Java-based": {
-    "message": "Java 技术栈实现"
-  },
-  "Native Multi-Tenancy": {
-    "message": "原生支持多租户"
-  },
-  "Open-Source": {
-    "message": "开源项目"
-  },
-  "Built-in Storage": {
-    "message": "内置存储引擎"
-  },
-  "Massive Connectivity": {
-    "message": "支持海量连接"
-  },
-  "Extensible": {
-    "message": "高度可扩展"
-  },
-  "100% MQTT Support": {
-    "message": "完整的 MQTT 支持"
-  },
-  "Fully supports MQTT 3.1, 3.1.1 and 5.0 features over TCP, TLS, WS, WSS. Complete protocol implementation with all advanced features.": {
-    "message": "完全支持 MQTT 3.1、3.1.1 和 5.0 版本的特性,覆盖 TCP、TLS、WS、WSS。完整的协议实现,包含所有高级特性。"
-  },
-  "Built-in Storage Engine": {
-    "message": "内置存储引擎"
-  },
-  "Optimized for critical load targeting, no third-party middleware dependencies. Deploy anywhere with confidence.": {
-    "message": "针对关键负载定向优化,无第三方中间件依赖。可在任何环境中放心部署。"
-  },
-  "Built-in support for multi-tenancy resource sharing and workload isolation. Perfect for SaaS platforms and enterprise environments.": {
-    "message": "原生支持多租户资源共享和工作负载隔离。非常适合 SaaS 平台和企业环境。"
-  },
-  "Extensible Mechanisms": {
-    "message": "扩展机制"
-  },
-  "Supports extensions, including Authentication/Authorization, Event, and System/Tenant Monitoring. Rich plugin architecture.": {
-    "message": "支持各种扩展,包括认证/授权、事件和系统/租户级监控。丰富的插件架构。"
-  },
-  "Java-based": {
-    "message": "基于 Java"
-  },
-  "Technology Stack": {
-    "message": "技术栈"
-  },
-  "Open Source": {
-    "message": "开源"
-  },
-  "License": {
-    "message": "许可证"
-  },
-  "GitHub Stars": {
-    "message": "GitHub 星标"
-  },
-  "Community Support": {
-    "message": "社区支持"
-  },
-  "Java-based high-performance MQTT Broker messaging middleware that adopts Multi-tenancy architecture. Open-sourced by Baidu.": {
-    "message": "基于 Java 的高性能 MQTT Broker 消息中间件,采用多租户架构。由百度开源。"
-  },
-  "Apache Incubator Project": {
-    "message": "Apache 孵化器项目"
-  },
-  "Apache Incubator": {
-    "message": "Apache 孵化器"
-  },
-  "Incubating Project": {
-    "message": "孵化中项目"
-  },
-  "Currently undergoing incubation at the Apache Software Foundation.": {
-    "message": "目前正在 Apache 软件基金会进行孵化。"
-  }
-}
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-blog/2023-07-07-bifromq-opensource-pr.md b/i18n/zh-Hans/docusaurus-plugin-content-blog/2023-07-07-bifromq-opensource-pr.md
deleted file mode 100644
index 1969328e..00000000
--- a/i18n/zh-Hans/docusaurus-plugin-content-blog/2023-07-07-bifromq-opensource-pr.md
+++ /dev/null
@@ -1,46 +0,0 @@
----
-slug: news-bifromq-opensource
-title: BifroMQ 正式开源:高性能多租户 MQTT 消息中间件
-authors: HaoYu
-tags: [BifroMQ,Open Source,MQTT,Serverless,Multi-Tenancy]
----
-
-# BifroMQ 正式开源:高性能多租户 MQTT 消息中间件
-
-BifroMQ 是一个高性能的分布式 MQTT 消息中间件,无缝集成了原生的多租户支持。它旨在支持构建大规模的物联网设备链接和消息系统。
-
-<!--truncate-->
-
-作为百度智能云天工 AIoT [物联网核心套件](https://cloud.baidu.com/product/iot.html)的基础底层中间件,BifroMQ 在百度的物联网技术栈中,扮演着支撑大规模设备连接和消息传输的关键角色。基于 BifroMQ 公有云集群服务中,百度智能云物联网核心套件已经服务了数千名企业开发者,连接了亿级设备,并处理了海量消息吞吐。这得益于 BifroMQ 的独立且可横向扩展的设计,它能够有效处理 MQTT 的关键负载,包括连接负载和消息负载。
-
-
-经过百度智能云物联网团队多年的技术积累和沉淀,BifroMQ 已经完整支持了 MQTT 3.1/3.1.1,包括通过 TCP、TLS、WS、WSS 方式使用 MQTT,另外也即将支持 MQTT 5.0。这使得 BifroMQ 在兼容性和标准实现上具有显著优势。
-
-为了推动互联网产业的卓越发展,也为了 BifroMQ 自身的成长,今日起,百度正式对外开源 BifroMQ!
-
-
-## 为什么叫做 BifroMQ
-
-BifroMQ 的名称灵感来自于北欧神话中的 `Bifröst` - 一座彩虹之桥,联接着人类的世界 Midgard 和神祇居住的世界 Asgard,是两个世界间的坚实而灵活的通道。BifroMQ 同样旨在成为连接各种系统或应用的枢纽,通过消息传递实现它们之间的交流。这与 MQTT 中间件在分布式系统中扮演的角色,即处理和转发消息,极为相似。
-
-此外,BifroMQ 在稳定性和可靠性方面的卓越表现及其在可扩展性和适应性上的优势,都与 `Bifröst` 的坚固性和灵活性有着极大的共通之处。因此,我们将MQTT 中间件取名为 `BifroMQ`,意寓其作为连接不同系统或应用的桥梁,坚固而灵活。
-
-## BifroMQ 架构及性能
-
-BifroMQ 是一款以 Serverless 为理念的 MQTT Broker 开源实现。它的设计理念是"共享资源,独享体验",重点解决多租户环境下的 MQTT 工作负载隔离和供需均衡。它采用了负载独立子集群设计,可以高效处理连接会话、消息转发和消息存储等工作负载。各子集群具备高可用性,支持横向扩展,并能灵活应对多租户场景。为克服路由表规模可能超过单机内存的问题,我们采用创新设计使路由表存储可扩展至多台机器。同时,BifroMQ 内置了优化的分布式存储引擎,无需依赖第三方存储中间件,保证了性能稳定。
-
-此外,BifroMQ 支持 Independent Workload Cluster、Standard Cluster 和 Standalone 三种部署模式,并允许通过插件进行定制,以满足不同业务需求。
-
-在性能方面,BifroMQ 经过严格的测试,展现出强大的处理能力和低时延。在一个标准的测试环境中,处理大量并发消息发布时,BifroMQ 保持了极低的消息时延及较低的 CPU 使用率。同时,与同类开源 MQTT 消息中间件相比,BifroMQ 在时延和性能稳定性方面表现出色。
-
-## BifroMQ 适用场景
-
-BifroMQ 可以广泛应用于各种物联网场景,包括但不限于智能家居、工业物联网、车联网和智能城市等多种领域。它能够为这些应用提供可靠、高性能的消息传输服务,支撑大规模设备连接和消息处理。例如,在智能家居领域,通过 BifroMQ,可以接入数千万家居设备,并可以实现远程控制、状态同步和数据上报等功能;在工业物联网领域,它可以支持大量传感器和设备进行实时数据收集和处理;对于车联网,BifroMQ 可以处理车辆之间以及车辆与基础设施之间的通信;在智能城市应用中,它能够协助管理和优化城市资源,如交通、能源和安全等。以更好的产品服务客服
-
-## 未来展望
-
-BifroMQ 在百度受到高度重视,也将得到百度的全力支持和广泛的资源投入。未来,BifroMQ 将继续完善对 MQTT 5 的支持,加强性能优化,丰富功能,并不断拓展在物联网领域的应用。同时,我们将继续秉持技术中立理念,进一步强化 BifroMQ 的「被集成」能力,使其能够更加轻松地与各种系统和应用协同工作。此外,BifroMQ 未来将会与更多的开源项目和标准化组织合作,共同推动物联网技术的发展,为全球物联网产业的升级迭代贡献力量。
-
-最后,作为一个开源项目,BifroMQ 非常欢迎各位开发者和企业深度参与项目开发和改进。为此,我们在BifroMQ官网([https://bifromq.io/](https://bifromq.io/))和GitHub社区平台([https://github.com/bifromqio/bifromq](https://github.com/bifromqio/bifromq)), **为开发者提供了丰富的文档、教程、问题解答和代码贡献** 等资源。同时,您可以 [通过电子邮件](mailto:hello@bifromq.io) 向我们发送您的微信 ID,以及为什么您对 BifroMQ 感兴趣的更多信息(我们很乐意听到),我们将尽快邀请您加入我们的群组。
-
-或加入我们的 Discord 群组:<a href="https://discord.gg/Pfs3QRadRB"><img src="https://img.shields.io/discord/1115542029531885599?logo=discord&logoColor=white" alt="BifroMQ Discord server" /></a>
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-blog/2023-09-04-bifromq-auth-plugin.mdx b/i18n/zh-Hans/docusaurus-plugin-content-blog/2023-09-04-bifromq-auth-plugin.mdx
deleted file mode 100644
index b540ef18..00000000
--- a/i18n/zh-Hans/docusaurus-plugin-content-blog/2023-09-04-bifromq-auth-plugin.mdx
+++ /dev/null
@@ -1,83 +0,0 @@
----
-slug: AnyAuth and Integration with BifroMQ
-title: "AnyAuth与BifroMQ的集成"
-authors: Jiawei
-tags: [Auth, Plugin]
----
-
-import ReactPlayer from 'react-player'
-
-**AnyAuth**插件根据BifroMQ `IAuthProvider`接口使用PF4J构建的插件服务。它旨在为BifroMQ提供无缝的身份验证和授权功能,使用户能够安全地访问各种
-客户端上的消息和资源。
-
-<!--truncate-->
-
-## BifroMQ与智能家居
-
-### 背景
-公司A是一家专门从事智能家居行业的公司。他们旨在通过结合IoT(物联网)技术来提高其产品的价值和用户体验,允许远程控制他们的产品。他们选择BifroMQ作为
-他们的MQTT消息中间件,将其集成到他们的IoT平台中,以将他们的智能家居设备连接到互联网。
-
-### 关键参与方
-* 公司A:希望通过IoT技术提高产品价值和用户体验的智能家居设备制造商。
-* 公司B:负责为A公司开发IoT平台和微信小程序的软件开发公司。
-* BifroMQ:提供可靠消息传输服务的MQTT消息中间件,由公司B集成到IoT平台中。
-
-### 终端用户
-作为智能家居设备的用户,我们期望能够远程控制设备,例如空调,调整温度,检查当前室内温度以及通过微信小程序监控空调的运行状态。
-
-### AnyAuth与BifroMQ
-**AnyAuth**插件支持多种身份验证机制,包括服务于设备的用户名/密码,服务于用户的auth0和微信。这意味着用户可以使用其喜欢的社交账户进行身份进行登录,
-简化了对BifroMQ的访问。
-
-此外,**AnyAuth**通过ACL提供基于角色的访问控制(RBAC)。此功能使用户能够定义不同的角色和权限,从而确保精细的访问控制。
-
-要了解更多信息和技术设计,请查看[文章](https://github.com/Gujiawei-Edinburgh/bifromq-plugin-anyAuth#readme)。
-## 设置步骤
-将**AnyAuth**集成到BifroMQ中,只需要按照如下步骤即可快速地将其集成其中:
-
-### 前提条件
-需要注意的是**AnyAuth**的主要聚焦于查询用户的凭证和相应的ACL规则。处理诸如用户注册和ACL规范之类的管理任务属于其他服务的范围。
-为确保顺利地进行数据检索,用户必须预先完成设备注册并指定相应的ACL。
-
-### AnyAuth插件配置信息
-
-由于**AnyAuth**支持多种认证方式(即:username/password,auth0和微信),因此需要对每一种认证方式配置好对应的参数。配置文件放置于
-`bifromq-plugin-anyAuth/auth-plugin/src/main/resources` 文件夹中,并且会打包置于产出JAR中。因此需要在编译前,指定好对应的参数。
-```yaml
-tenantId: ${TENANTID}
-device:
-  authUrl: ${AUTH_SERVICE_AUTH_URL}
-  checkUrl: ${AUTH_SERVICE_CHECK_URL}
-auth0:
-  domain: ${AUTH0_DOMAIN}
-wechat:
-  appId: ${APP_ID}
-  appSecret: ${APP_SECRET}
-  requestUrl: https://api.weixin.qq.com/sns/jscode2session?appid=
-```
-### 链接BifroMQ与插件
-进入到**AnyAuth**工程目录并执行以下命令获得对应的编译产出:
-```mvn
-cd bifromq-plugin-anyAuth && mvn clean package
-```
-该命令会生成 `auth-plugin-${VERSION}.jar` and `auth-service-${VERSION}.tar.gz`在各自的`target`文件夹中。
-
-为了保证BifroMQ可以正确地加载**AnyAuth**插件, 用户需要将JAR放置于正确的文件夹目录下, 即: `bifromq-${VERSION}/plugins`。 此外在
-BifroMQ配置文件中(`conf/standalone.yml`)还需要指定Fully Qualified Name (FQN),
-例如:`authProviderFQN: bifromq.plugin.auth.AuthProvider`。
-
-### 设置AnyAuth服务
-插件中的JAR部分在认证鉴权过程中充当了客户端的角色,对于数据库的查询操作则由**AnyAuth**服务来处理。部署**AnyAuth**服务时,用户需要制定其所用的
-MySQL的连接信息。
-
-对于部分测试和开发场景, **AnyAuth**还支持dummy storage的方式,将配置中的`type`设置成`Dummy`即可。
-
-## 端到端的示例
-完成所有设置步骤后,我们现在可以开始最后的联调了。通过微信小程序登录到BifroMQ,同时通过用户友好的GUI应用程序来模拟设备。下面的视频展示了一个典型
-场景:一个设备通过BifroMQ报告当前温度,同时一个微信小程序接收到了这个消息,随后根据数据发出指令。
-<div className="video__wrapper">
-    <ReactPlayer className="video__player" controls height="100%"
-    url="https://github.com/Gujiawei-Edinburgh/bifromq-plugin-anyAuth/assets/55412783/df9f9009-e96f-4c97-b25a-aa399196fbd9"
-    width="100%" />
-</div>
\ No newline at end of file
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-blog/2023-09-06-bifromq-architecture-overview.md b/i18n/zh-Hans/docusaurus-plugin-content-blog/2023-09-06-bifromq-architecture-overview.md
deleted file mode 100644
index e09db4ff..00000000
--- a/i18n/zh-Hans/docusaurus-plugin-content-blog/2023-09-06-bifromq-architecture-overview.md
+++ /dev/null
@@ -1,92 +0,0 @@
----
-slug: bifromq-tech-architecture 
-title: "BifroMQ 技术架构概览"
-authors: HaoYu
-tags: [BifroMQ,Open Source,MQTT,Serverless,Multi-Tenancy,Technical Architecture]
----
-
-# BifroMQ 技术架构概览
-
-在当今的物联网领域,MQTT 协议已经成为不可或缺的关键要素,为高效、实时的数据传递提供了核心技术支持。然而,目前市场上提供 MQTT 能力的项目主要集中在传统的、现有的 "开箱即用" 物联网设备管理平台上,导致更底层的 MQTT 协议实现缺乏足够的关注和探索。然而,我们深信 MQTT 协议的特性有着更广泛的应用前景,不仅仅局限于物联网领域。正是出于这一信念,经过多年的实践和技术积累我们推出了开源项目 BifroMQ,专注于 MQTT 协议的高效处理,尤其是在面对大规模负载时的卓越表现。
-
-<!--truncate-->
-**中立性和可扩展性兼具的 MQTT 协议中间件**
-
-相较于传统的物联网设备管理平台,BifroMQ 在设计上秉承与众不同的理念。我们大胆地抛弃了 "一揽子解决方案" 的传统范式,将注意力集中在高性能 MQTT 协议的需求上。我们坚信 MQTT 的协议特性具有更广泛的应用范式,因此 BifroMQ 致力于充分发挥 MQTT 协议的潜力,尤其是在处理大规模负载时的卓越性能。
-
-相较于在 MQTT 实现中内置与下游系统的集成逻辑 (如:Kafka),BifroMQ 更倾向于通过符合 MQTT 标准的方式与下游系统 "对接"。例如,通过共享订阅(Shared Subscription)机制,将集成逻辑外置,实现更加解耦的桥接和向异构系统转发消息的能力,同时保持高消息吞吐率。这种设计理念使得 BifroMQ 成为一个高度可定制的中间件,能够轻松适应各类下游系统,满足不同业务场景的需求。
-
-## 构建大规模多租户的 Serverless云服务
-
-BifroMQ 的使命在于构建适用于大规模多租户的 MQTT 消息系统,以支持开展 Serverless 类型云服务的业务特性。这一使命是基于对 MQTT 协议特性的深刻理解和对其更广泛应用的信心所驱动的。与传统的企业级架构不同,Serverless 云服务强调资源按需分配、弹性扩展及高度灵活的服务构建。正因如此,BifroMQ 通过其多租户架构和资源共享机制,为 Serverless 类型的业务提供了 "共享资源、独享体验" 的特性。
-
-## 企业级部署:灵活性与稳健性兼备
-
-虽然 BifroMQ 的目标是构建多租户的 Serverless 云服务,但多租户 + 共享资源本质上是单租户独享资源的抽象。与我们的理念一致,通过核心组件的自由组合和配置,BifroMQ 轻松支持常见的 "Shared Nothing" 企业级集群部署。实际上,这也是 BifroMQ 开源版本的默认部署模式。这种灵活性使得 BifroMQ 能够适应各种规模和需求的系统架构。
-
-## BifroMQ 的架构解析
-
-BifroMQ 的架构设计基于 "第一性原理",从技术角度分析实现设计目标所需的技术以及如何将这些技术 "有机" 地组合起来,以达到整体优化的效果。因此,仅从项目结构和代码逻辑很难全面地理解其内涵。下面将从三个主要角度对 BifroMQ 的整体架构进行高层次的描述。
-
-### 基于去中心化集群管理的模块化架构
-
-**首先**,抛开 MQTT 协议本身的实现逻辑,BifroMQ 的各个功能服务模块构建在一套去中心化的底层集群构建能力(base-cluster)之上,如下图所示:
-
-![BifroMQ 去中心化集群的模块化架构](images/2023-09-06-bifromq-architecture-overview/bifromq-architecture-1.png)
-<p class="text-gray-400 text-center">去中心化集群的模块化架构</p>
-
-base-cluster 构建的集群逻辑上分为两层:Underlay Cluster 和 Overlay Cluster。Underlay Cluster 被称为 "Host" Cluster,每个 Host 在 BifroMQ 中对应着运行在操作系统上的一个服务进程(Process)。Host Cluster 采用 Gossip 类的协议(SWIM Protocol)实现了 Host 成员服务(Membership),并为 Overlay Cluster 提供了 Host 地址的抽象。Overlay Cluster 被称为 "Agent" Cluster,它在 Host 地址的基础上提供了 Agent 级别的地址抽象(Agent Address)。在 BifroMQ 中,Agent 对应着实现具体功能的逻辑服务(Service)。这些逻辑服务(通过 base-rpc 框架统一实现)包括了客户端和服务端两种角色的模块,利用 Agent Cluster 的能力来实现服务的注册和发现。
-
-这种架构带来的好处包括:
-
-1. 逻辑服务与服务所在进程解耦,使得根据部署场景可以更加灵活地封装和组合。
-2. 逻辑服务的 "服务发现" 不依赖传统意义上的注册中心或名字服务,从而消除了单点故障的运维风险,使得集群规模能够自由伸缩。
-
-### 模块化的负载隔离与协作
-
-**接下来**,我们从协议实现的角度描述 BifroMQ 的结构。在从构建 Serverless 云服务的角度出发进行架构设计时,需要从负载隔离和管理的角度考虑功能实现的合理性,也就是负载的多租户化。我们将 MQTT 协议的工作负载进行了拆分,使得每种负载都能以独立子集群的形式存在,而这些子集群通过协作构建了完整的 MQTT 能力。下面是 BifroMQ 中 MQTT 负载相关的模块:
-
-* bifromq-mqtt:负责处理 MQTT 协议的长连接负载
-
-* bifromq-dist:负责维护 MQTT 订阅状态的高可靠存取和大规模消息路由
-
-* bifromq-inbox:负责 CleanSession=false 模式下订阅方会话消息的高可靠存取
-
-* bifromq-retain:负责 Retain 消息的高可靠存取
-
-这些模块之间的协作关系如下图所示:
-
-![BifroMQ 各模块协作关系 1](images/2023-09-06-bifromq-architecture-overview/bifromq-architecture-2-1.png)
-
-![BifroMQ 各模块协作关系 2](images/2023-09-06-bifromq-architecture-overview/bifromq-architecture-2-2.png)
-<p class="text-gray-400 text-center">各模块协作关系</p>
-
-值得一提的是,bifromq-dist、bifromq-inbox 和 bifromq-retain 模块都充分利用了 base-kv 的能力,实现了对关键负载的分布式强一致性持久化。在 Serverless 云服务的运维场景中,这点对保证 SLA 尤为重要。
-
-### 中立性:面向标准与可扩展的集成
-
-前文提到,BifroMQ 的定位是实现 MQTT 标准的中间件,更加强调中立性和被集成性。与其他包含 MQTT 能力的 "一揽子物联网平台" 项目并不处于同一层上。
-
-因此,判断 "BifroMQ 是否具备某种功能或未来是否会支持某种功能" 的标准非常简单:凡是 MQTT 协议定义的能力都属于 bifromq 项目需要支持的范畴,而一切超出 MQTT 协议定义的功能,我们更倾向于以独立组件或服务的方式存在,并通过符合 MQTT 标准的方式与 BifroMQ 集成。这种方法有助于构建更大规模的云服务并促进相关技术的成熟。
-
-当然,BifroMQ 的被集成性还体现在作为中间件本身与各种业务系统的集成上,主要包括三种机制:Plugin、API 和 Metrics:
-
-![典型场景集成架构](images/2023-09-06-bifromq-architecture-overview/bifromq-architecture-3.png)
-<p class="text-gray-400 text-center">典型场景集成架构</p>
-
-* Plugin 机制是实现业务逻辑集成的主要方式。bifromq 目前定义了以下 plugin 接口模块:
-  * bifromq-plugin-auth-provider:实现客户端认证和基于消息主题的 Pub/Sub 鉴权逻辑
-  * bifromq-plugin-event-collector:实现由各类 MQTT 相关事件触发的业务逻辑
-  * bifromq-plugin-setting-provider:实现租户级运行时设置变更管理逻辑
-
-* 这些接口的参考实现可以在 BifroMQ-Inside 项目中找到。
-
-* API 机制(即将推出)提供了 BifroMQ 的运行时 HTTP 管理接口,实现服务端订阅管理和断开连接等基本管理操作。
-
-* Metrics 机制通过使用 micrometer 库实现了指标的定义和采样,但没有限定收集端的类型,从而使业务集成方能够自定义(可以参考项目中的 build-plugin-demo 模块)。
-
-### 总结
-
-综上是对 BifroMQ 技术架构的整体介绍。请期待我们将在接下来发布的一系列专题文章中,深入探讨 BifroMQ 的各个组件和设计原则。同时,欢迎您加入 BifroMQ 开发者交流群,向我们反馈关于文章内容的意见和建议。您可以 [通过电子邮件](mailto:hello@bifromq.io) 向我们发送您的微信 ID,以及为什么您对 BifroMQ 感兴趣的更多信息(我们很乐意听到),我们将尽快邀请您加入我们的群组。如有 BifroMQ 合作需求,请填写[问卷](https://iwenjuan.baidu.com/?code=5x2ip1),我们会尽快与您联系。
-
-最后,为了帮助大家更好地了解 BifroMQ 的技术架构,我们将于** 9 月 21 日(周四)**举办一场 BifroMQ 线上直播公开课,欢迎各位关注 BifroMQ 开发者交流群内信息,提前锁定直播地址,与广大同行交流学习!
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-blog/2023-10-24-bifromq-standardcluster.mdx b/i18n/zh-Hans/docusaurus-plugin-content-blog/2023-10-24-bifromq-standardcluster.mdx
deleted file mode 100644
index cac35d0a..00000000
--- a/i18n/zh-Hans/docusaurus-plugin-content-blog/2023-10-24-bifromq-standardcluster.mdx
+++ /dev/null
@@ -1,71 +0,0 @@
----
-slug: bifromq-standardcluster
-title: "BifroMQ StandardCluster"
-authors: HaoYu
-tags: [BifroMQ,Open Source,MQTT,Cluster]
----
-import StandardCluster from './images/2023-10-24-bifromq-standardcluster/BifroMQ-StandardCluster.png';
-import DistSubCluster from './images/2023-10-24-bifromq-standardcluster/BifroMQ-Dist-SubCluster.png';
-import InboxSubCluster from './images/2023-10-24-bifromq-standardcluster/BifroMQ-Inbox-SubCluster.png';
-import LoadBasedSplitter from './images/2023-10-24-bifromq-standardcluster/BifroMQ-Inbox-LoadBasedSplitter.png';
-import APIService from './images/2023-10-24-bifromq-standardcluster/BifroMQ-API-Service.png';
-
-## 引言
-自 BifroMQ 首个版本发布以来,它已经获得了广泛的社区关注。其中,集群能力一直备受期待,也一直是 BifroMQ 团队优先考虑的工作项之一。近三个月的不懈努力后,我们正式推出 BifroMQ 的集群版本,我们将其称为**标准集群**。
-标准集群(StandardCluster)是 BifroMQ 开源版本的主要支持集群模式,每个节点在此模式下具备完整的 MQTT 协议能力。同时,HTTP API也在此版本中得以支持。
-
-<!--truncate-->
-
-## TLDR:
-* 安装包[地址](https://github.com/bifromqio/bifromq/releases)及部署[指南](/zh-Hans/docs/cluster/standardcluster/)
-<!-- * 测试[报告](/zh-Hans/docs/test_report/report/) -->
-* API[文档](/zh-Hans/docs/user_guide/api/intro/)
-
-## StandardCluster 的整体结构
-在先前的整体架构[文章](2023-09-06-bifromq-architecture-overview.md)中,我们提到 BifroMQ 将逻辑上的 MQTT 功能从负载的角度分解为若干子服务,每个子服务对应一类关键负载:
-* bifromq-mqtt:负责 MQTT 协议连接负载
-* bifromq-dist:负责订阅和消息路由分发负载
-* bifromq-inbox:负责持久会话中的离线消息队列负载
-* bifromq-retain:负责 Retain 消息存取负载
-
-从部署的角度看,BifroMQ StandardCluster是将这些独立负载的服务模块"封装"到一个节点服务进程的集群模式,从逻辑上来说,这是对 Standalone 运行模式的抽象(BifroMQ Standalone 可以看作是单个节点的 BifroMQ StandardCluster)。与其他支持集群的 MQTT Broker 不同,BifroMQ 内置了分布式持久化功能,因此单个 BifroMQ 节点是"有状态的"(Stateful)。
-
-<img src={StandardCluster} style={{width: 700}} />
-
-*注:本文所有插图中括号内的`bifromq-xxx`,即为代码中对应的模块名称*
-
-## 消息分发能力的水平扩展
-在 StandardCluster 集群模式下,每个节点进程内的 Dist Service 模块构成了逻辑上的负载子集群(Dist-SubCluster)。Dist Service 将订阅信息存储在内置的持久化引擎中,并通过持久化引擎的分布式功能在节点之间同步路由信息。在 StandardCluster 模式下,通过增加节点的方式,可以实现消息分发能力的水平扩展,特别是在 CleanSession 为 True 的情况下,这一点非常明显。
-
-<img src={DistSubCluster} style={{width: 700}} />
-
-## 离线消息队列的持久化、扩展性及高可靠性
-与 Dist Service 模块类似,节点进程内负责 MQTT 持久会话中离线消息队列的 Inbox Service 模块构成了另一个逻辑上的负载子集群(Inbox-SubCluster)。Inbox Service 将离线队列消息持久化到内置的存储引擎中,可以极大程度地减少因节点故障导致的数据丢失。在存储方面,Inbox Service 利用了内置存储引擎的分片功能,存储规模和处理能力可以水平扩展。此外,通过静态配置或运行时策略动态增加分片的副本数,可以进一步提高离线消息数据的可靠性。这对某些对数据可靠性要求更高的应用场景尤为重要。
-
-<img src={InboxSubCluster} style={{width: 700}} />
-
-*注1:由于增加分片副本数对 MQTT CleanSession 为 False 的消息负载有不可忽视的影响,需要根据实际需求确定资源投入以达到预期效果。因此,默认副本数为1,该设置可以通过 JVM 启动参数 `inbox_store_range_voter_count` 进行调整*
-
-*注2:Inbox Service 提供了离线消息队列的全局访问能力,因此 MQTT 客户端重新连接到任何集群节点时都可以访问所属队列中的离线消息,无需引入在其他MQTT Broker集群实现中常见的sticky session或session migration方案*
-
-## Inbox服务的基于负载的拆分策略
-如前文所述,StandardCluster 部署下,单个节点进程内的 Inbox Service 利用了内置存储引擎的分片功能来实现存储规模和处理能力的水平扩展。然而,分片策略对实际运行效果有着决定性的影响。在 BifroMQ StandardCluster 版本中,我们内置了开箱即用的基于负载的拆分策略(Load-based Splitting)。该策略通过统计最近一段时间内的负载情况来决定对KV Range的划分。可以视为一种"后验"拆分策略。当使用场景已经对离线消息负载的分布有提前规划和了解时,提前划分 Range 通常能在负载到来时带来更稳定的性能表现。对于深度使用 BifroMQ 的用户,可以通过 SPI 机制实现此类"先验"拆分策略。
-
-<img src={LoadBasedSplitter} style={{width: 400}} />
-
-## HTTP API模块
-BifroMQ StandardCluster 版本同时引入了 HTTP API 功能。每个集群节点都可以通过配置开放 API 访问端口。BifroMQ HTTP API 是无状态的全局接口,旨在支持业务层面的管理控制逻辑的集成。访问任何一个节点的 API 都可以实现对整个集群的操作。详细信息可以参见[此链接](/zh-Hans/docs/user_guide/api/intro/)。
-
-<img src={APIService} style={{width: 700}} />
-
-## 混合负载对性能的影响
-在 StandardCluster 部署下,单个节点具备完整的 MQTT 协议功能,承担各种类型的负载。因此,这种模式特别适用于以下两类企业级应用场景:
-1. 业务产生的负载类型相对单一
-2. 业务产生的负载类型多元化,但产生时间相对分散
-对于负载形式复杂且在时间维度上有集中产生的情况,我们建议用户通过模拟负载测试来获得单个 BifroMQ StandardCluster 集群下的最佳资源配置和参数设置,或者考虑使用多个 BifroMQ StandardCluster 来承载不同类型的业务负载。另外,您还可以与我们联系,获取 BifroMQ 商业版本的独立负载集群(Independent Workload Cluster)支持。
-
-## 部署过程和运维
-在之前的 BifroMQ 技术架构文章中,我们提到 BifroMQ 集群建立在一套内置的去中心化技术之上(base-cluster),无需依赖外部节点注册和发现服务。因此,构建 BifroMQ StandardCluster 的部署过程非常简单(详细过程请参考[此链接](/zh-Hans/docs/cluster/standardcluster/)),只需指定任何一个集群中的节点作为种子节点,即可完成新节点的加入。此外,BifroMQ 还内置了集群分裂后的自愈能力,可以极大地简化出现网络分区(Network Partition)等故障时的运维操作。
-
-## 未来展望
-BifroMQ 团队一直秉持技术中立理念,致力于大规模实现 MQTT 协议、提高可靠性和可维护性等方面。我们期待更多社区参与和深入使用反馈,共同推动这一技术的成熟。此外,您可以 [通过电子邮件](mailto:hello@bifromq.io) 向我们发送您的微信 ID,以及为什么您对 BifroMQ 感兴趣的更多信息(我们很乐意听到),我们将尽快邀请您加入我们的群组。或加入我们的 Discord 群组:<a href="https://discord.gg/Pfs3QRadRB"><img src="https://img.shields.io/discord/1115542029531885599?logo=discord&logoColor=white" alt="BifroMQ Discord server" /></a>
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-blog/2023-12-01-bifromq-high-availability.mdx b/i18n/zh-Hans/docusaurus-plugin-content-blog/2023-12-01-bifromq-high-availability.mdx
deleted file mode 100644
index 5a5f7f32..00000000
--- a/i18n/zh-Hans/docusaurus-plugin-content-blog/2023-12-01-bifromq-high-availability.mdx
+++ /dev/null
@@ -1,198 +0,0 @@
----
-slug: bifromq-high-availibility
-title: "BifroMQ:构建高效可用集群的技术揭秘"
-authors: [HaoYu, MaFei]
-tags: [BifroMQ,Open Source,MQTT,High Availability,Technical Architecture,Cluster,Distributed Key-Value,Load Balancing]
----
-
-
-import AutoEviction from './images/2023-12-01-bifromq-high-availability/BifroMQ-AutoEviction.png';
-import BrainSplit from './images/2023-12-01-bifromq-high-availability/BifroMQ-BrainSplit.png';
-import Domain from './images/2023-12-01-bifromq-high-availability/BifroMQ-Domain.png';
-import DynamicConfig from './images/2023-12-01-bifromq-high-availability/BifroMQ-DynamicConfig.png';
-import IndependentWorkload from './images/2023-12-01-bifromq-high-availability/BifroMQ-IndependentWorkload.png';
-import Join from './images/2023-12-01-bifromq-high-availability/BifroMQ-Join.png';
-import LeaderBalance from './images/2023-12-01-bifromq-high-availability/BifroMQ-LeaderBalance.png';
-import RangeBalancer from './images/2023-12-01-bifromq-high-availability/BifroMQ-RangeBalancer.png';
-import RangeLeaderBalancer from './images/2023-12-01-bifromq-high-availability/BifroMQ-RangeLeaderBalancer.png';
-import RangeSplit from './images/2023-12-01-bifromq-high-availability/BifroMQ-RangeSplit.png';
-import RangeSplitBalancer from './images/2023-12-01-bifromq-high-availability/BifroMQ-RangeSplitBalancer.png';
-import RecoveryBalancer from './images/2023-12-01-bifromq-high-availability/BifroMQ-RecoveryBalancer.png';
-import ReplicaCntBalancer from './images/2023-12-01-bifromq-high-availability/BifroMQ-ReplicaCntBalancer.png';
-import RPCCluster from './images/2023-12-01-bifromq-high-availability/BifroMQ-RPCCluster.png';
-
-
-
-# BifroMQ:构建高效可用集群的技术揭秘
-
-
-
-## 引言
-
-BifroMQ的集群版本已顺利推向社区,满足了用户在集群部署上对处理能力水平扩展与高可用性的核心需求。我们在之前关于[BifroMQ StandardCluster](2023-10-24-bifromq-standardcluster.mdx)的介绍中已详细阐述了其在性能水平扩展方面的能力。本篇文章,我们将专注于深入解析BifroMQ在确保高可用性方面所采用的技术特性。
-
-<!--truncate-->
-
-## 去中心化集群
-
-在BifroMQ的架构中,我们精心设计了MQTT协议工作负载的拆分方案。这一策略使得每类工作负载都能在独立的子集群中运作。这些功能性子集群均构建于一套精巧的去中心化底层集群构建框架(base-cluster)上。BifroMQ的集群框架包含两个逻辑层级:Underlay Cluster和Overlay Cluster,这样的构建使得架构变得清晰和解耦。有关这一设计的更多细节,请参见[《BifroMQ技术架构概览》](2023-09-06-bifromq-architecture-overview.md)。
-
-
-
-### Underlay Cluster
-
-Underlay Cluster是BifroMQ集群体系的核心,该层的成员代表一个运行中的BifroMQ进程,成员之间可以直接利用进程绑定的主机网络地址(HostAddress)进行通信。我们采用Gossip类的Membership协议([SWIM Protocol](https://ieeexplore.ieee.org/document/1028914))实现集群成员的失败检测(FailureDetection),并且对Membership信息的同步机制做了进一步优化,使得整体上具有的以下技术特性:
-
-* 集群构建无需依赖传统的注册中心或命名服务,有效消除了单点故障的运维风险,显著提升了集群的高可用性。
-* 通过采用SWIM协议,Underlay Cluster能够确保节点间探活机制的准确性,保障集群拓扑的最终一致性。
-* 使用CRDT技术实现集群Membership信息在节点间同步,可以同时做到极低的带宽占用和同步时效。
-
-
-
-#### 集群构建过程
-
-在去中心化的集群架构中,每个集群成员的地位是平等的,不存在专门负责管理集群拓扑信息的管控角色节点。从更高的视角来观察,运行BifroMQ StandardCluster服务进程的任何节点,实际上都可以视为一个拥有“单个节点”的独立集群。因此,集群的构建实质上是各独立集群的融合过程。为了实现这一过程,base-cluster框架提供了“join”操作,以便于这些独立集群的有效合并。
-
-<img src={Join} style={{width: 700}} />
-
-正如上图所示,集群的join操作可以由任一节点向目标集群的任一节点发起。为了简化讨论,我们将作为join操作目标的节点称为“seeds”。在部署过程中,这些seed节点的地址通常会被配置在新加入集群节点的配置文件([seedEndpoints](/zh-Hans/docs/admin_guide/configuration/config_file_manual/))中。集群成功合并后,BifroMQ集群中的每个节点都能在本地获取到完整的集群Membership信息。
-
-细心的读者可能已经注意到,在节点配置中直接指定seed地址的方式,在容器化环境下可能存在一定的局限性。为了解决这一问题,base-cluster框架内置了DNS解析功能。在容器环境中,我们可以通过将所有节点纳入一个固定的网络Domain(例如External DNS或Kubernetes Service),简化集群的部署过程。这样,新加入的节点可以使用由该Domain解析出的任意Remote地址作为seed,以完成join过程。
-
-<img src={Domain} style={{width: 700}} />
-
-
-#### 失败检测与自动驱逐
-
-在BifroMQ中,当节点正常退出时,它会主动清理自身在集群中的注册身份,并与集群中的其他节点同步此变化。此外,每个节点持续进行对其他进行节点失败检测(Failure Detection)。一旦检测到异常,它会立即将该节点的相关信息从本地的集群Membership中移除,并迅速完成集群间Membership的同步,防止这些不再活跃的节点对集群的正常功能产生影响。
-
-<img src={AutoEviction} style={{width: 500}} />
-
-与自动驱逐机制相配合的是BifroMQ的自愈机制,它有效防止了因为网络抖动或误判导致健康节点的注册信息被错误地移除。每个节点会在观察到集群信息发生变化时,重新检查自身的注册信息。如果发现信息缺失,节点将主动进行补充,从而确保集群信息的完整性和最终一致性。
-
-
-
-#### 脑裂恢复
-
-对于去中心化的集群服务来说,网络分区(Network Partition)导致的导致集群脑裂是个不能避免的问题,即单个集群分裂成了多个互相隔离的集群。
-
-base-cluster对于可能出现的脑裂故障做了保障,进一步提高了集群部署的高可用性,具体过程如下:当网络发生分区时,分裂被隔离的集群彼此都会检测到对方节点的失败,这些失败被移除的节点会加入至本地的"愈合列表",列表中的成员会被定时尝试join,直到超过部署时设定的 MTTR([Mean Time To Repair](https://en.wikipedia.org/wiki/Mean_time_to_repair))。不难发现,脑裂恢复的过程实际上与上文提到的集群构建过程是一致的。
-
-<img src={BrainSplit} style={{width: 500}} />
-
-
-### Overlay Cluster
-
-Overlay Cluster又称为Agent Cluster,构建于Underlay Cluster之上,利用Underlay Cluster的能力实现Membership管理和成员间通信,主要用于实现由不同逻辑服务单元组成的代理集群。借助Underlay Cluster的高效构建机制,Agent Cluster能够自动实现集群的构建,大幅简化了部署和运维过程。
-
-在 BifroMQ 中,由Agent Cluster实现的子服务集群,可被分类为无状态集群和有状态集群两类:无状态集群以RPC服务为主;有状态集群通常基于base-kv构建内置分布式KV存储引擎。
-
-
-
-#### RPC服务集群
-
-RPC服务集群成员通常被定义为客户端和服务端两种角色。利用Agent Cluster的特性,RPC的客户端与服务端无需依赖外部注册中心,即可实现高效的服务端发现与多样化的客户端请求路由逻辑。
-
-<img src={RPCCluster} style={{width: 700}} />
-
-#### BifroMQ的有状态子服务集群与分布式KV存储引擎
-
-在BifroMQ的有状态子服务集群中,内置了强一致性的分布式KV存储引擎(base-kv)。这个引擎具备基于Multi-Raft的sharding功能,是BifroMQ高度可靠性的关键组成部分。集群的Membership信息由Agent Cluster维护,而每个Range分片内的副本则通过Raft协议来实现强一致性同步。因此,要确保有状态服务的高可靠性,就必须充分利用并符合Raft协议的特性要求。
-
-
-
-##### KVRange Balancer
-
-base-kv使用内置的Range Balancer框架实现高效的Range副本管理。该框架综合考虑当前集群的拓扑结构和实时负载数据,生成用于均衡Range副本集的指令。这些指令包括Leader转移(LeaderTransfer)、成员配置变更(ConfigChange)、Range拆分(Split)和Range合并(Merge)。通过这一系列操作,base-kv能够有效地实现集群负载的平衡,优化吞吐性能,同时达成高可用性的目标。
-值得一提的是,Range Balancer同样采用了去中心化的设计理念。在base-kv的每个节点中,Balancer只负责管理本地的Leader Range。这样的设计使得多个节点上的Balancer能够并行运作,最终达成全局一致的均衡目标。
-
-<img src={RangeBalancer} style={{width: 600}} />
-
-为了确保用户能享受到即插即用的便利性,BifroMQ已预先内置了一系列常用的均衡策略实现。然而,对于那些有特定需求的高级用户,BifroMQ还提供了定制化均衡策略的能力(Balancer SPI),以便根据特定的应用场景进行优化。以下是我们提供的内置均衡策略的简要介绍。用户可以根据自己的需求,通过配置来启用这些策略。
-
-**ReplicaCntBalancer**
-
-ReplicaCntBalancer的主要作用是调节和平衡Range的副本数量。一旦启用,这个功能将允许Range的副本数根据BifroMQ StandardCluster集群中部署节点的数量灵活调整。这意味着,ReplicaCntBalancer能够根据集群当前的规模,自动优化并实现最佳的可用性配置,从而确保集群的高效运行。
-
-<img src={ReplicaCntBalancer} style={{width: 700}} />
-
-如图所示,工作过程如下:
-
-* **集群扩容情况**:假设最初BifroMQ集群中有3个节点,此时KVRange的副本数也是3,使得集群能够容忍1个节点的故障。当集群新增2个节点后,ReplicaCntBalancer自动将这些新节点纳入副本配置,并通过数据同步将副本数增加至5。这样,集群就能容忍2个节点的不可用状态,从而提升了集群的容错能力。
-* **集群缩容情况**:在另一种场景中,当BifroMQ集群包含5个节点且KVRange副本数同样为5时,若发生两个节点的宕机,依照Raft算法,集群仍能保持正常运作。然而,如果副本配置不变,再有一个节点宕机将导致整个Raft集群无法运作。此时,ReplicaCntBalancer会调整副本配置,调整VoterSet仅包含剩余的3个可用节点。这样的调整使得集群在容忍1个节点不可用的情况下依然保持高可用性。
-
-**RangeSplitBalancer**
-
-在BifroMQ中,单个Range的副本集是通过Raft协议管理的,其负载能力受到WAL复制机制的限制,因此存在一定的性能上限。特别是当业务工作负载高度集中于单个Range时,这种限制会变得尤为明显。在这种情况下,将一个Range拆分成多个部分是提升系统并行任务处理能力的有效手段,从而显著提高整个系统的整体性能。
-
-RangeSplitBalancer正是base-kv内置的用于实现这一功能的负载策略。它通过分析实际业务负载情况,及时生成Range拆分的指令,从而优化系统处理能力并提高性能表现。
-
-<img src={RangeSplitBalancer} style={{width: 600}} />
-
-**RangeLeaderBalancer**
-
-在Raft协议中,Leader节点承担了所有写请求和部分读请求的工作负载。因此,当多个Range的Leader副本集中在同一节点上时,很容易产生负载热点,影响系统性能。为了解决这一问题,base-kv集群在发生多个Range分裂的情况下,可以开启RangeLeaderBalancer。
-
-RangeLeaderBalancer专门负责监控和调整Range副本在各节点上的分布。它通过在节点间迁移Range,确保每个base-kv节点上的Leader副本数量均衡,避免了过度集中的负载热点。这种均衡不仅提高了整体负载处理的效率,还降低了单个节点出现故障时对集群瞬时可用性的影响。
-
-<img src={RangeLeaderBalancer} style={{width: 600}} />
-
-**RecoveryBalancer**
-
-在Non-Byzantine容错的强一致性协议中,正常工作的节点数量 n 必须满足 n≥2f+1 的条件,其中 f 代表可容忍的失败节点数。基于这一原则,任何Range副本都必须位于超过半数的正常集群节点中,才能保证正常运作。然而,在实际部署中,当集群中Range的数量较多,且单个base-kv节点可能承载多个不同Range的副本时,多个base-kv节点的同时故障可能导致n < 2f+1 的情况发生,这被称为Lost Majority。在Lost Majority的情况下,受影响的Range将无法正常工作。
-
-为应对这种情况,RecoveryBalancer提供了一项关键能力。它允许节点检测自身是否处于Lost Majority的状态,并在必要时主动缩减副本列表配置,以确保至少有半数的节点处于存活状态,从而使Range能够继续正常运作。然而,需要特别注意的是,在使用RecoveryBalancer自动恢复处于Lost Majority状态的Range时,如果原先失败的节点未经人工干预重新加入集群,可能会引起数据丢失和不一致问题。这种情况下,用户需要慎重考虑并结合实际的运维策略来决定是否启用RecoveryBalancer功能。
-
-<img src={RecoveryBalancer} style={{width: 700}} />
-
-### 应用场景
-
-BifroMQ的有状态子服务有三种:MQTT订阅路由、离线消息队列、Retain消息分。分别由对应的模块:dist-worker、inbox-store和retain-store来实现。每一模块部署后都构成了一个独立的base-kv集群。
-
-为了适应不同的使用场景和负载需求,BifroMQ允许每个独立集群根据其特定情况选择并启动相应的Balancer策略。这种策略的灵活配置使得每个集群都能在保持高可用性的同时,实现最优的数据处理吞吐性能。
-
-#### dist-worker
-
-在BifroMQ的架构中,dist-worker模块承担着管理订阅信息(Sub)和消息分发(Pub)的职责。在正常的使用场景下,这通常是一个以读操作为主、写操作较少的场景。
-
-考虑到这一使用场景和base-kv的负载处理能力,dist-worker采用了以下默认Balancer策略:
-
-* **启用ReplicaCntBalancer**:这一策略确保KVRange副本数与集群节点数保持一致,最大化查询吞吐效率。
-* **控制Voter副本数**:在保证高可用性的同时,将Raft Voter的数量限制在最多3个,其他副本则作为Learner角色,以此降低写操作的响应延迟。
-
-在大多数常见的使用场景中,一条Publish消息匹配到的订阅者数量通常并不多,且匹配过程也较为迅速。鉴于此,dist-worker模块在其默认配置下并没有激活Range拆分策略。这是因为在标准的操作环境中,当前的设置已能满足大部分性能要求。
-
-然而,当面对大规模Fanout场景,特别是那些对低延迟有更高需求的情况时,单个Range的查询效率可能会变成制约整体性能的瓶颈。为了应对这类挑战,我们计划在未来版本的BifroMQ中增强这一方面的处理能力,以优化大规模Fanout场景下的性能表现。
-
-#### retain-store
-
-Retain消息的工作负载与订阅信息和消息发送的处理相似,正常使用下主要表现为读操作多于写操作。基于这一特点,retain-store的默认Balancer策略被设置为与dist-worker模块一致,在此不做重复说明。
-
-#### inbox-store
-
-在BifroMQ中,inbox-store模块承担着管理每个`cleanSession=false`连接的离线消息的角色。对于这类连接,inbox-store会创建一个专属的持久化离线消息队列。归属于这些连接的Publish消息首先被写入这些队列中。当连接恢复在线状态时,消息将从队列中取出进行推送并随即删除。这构成了一个典型的高频读写场景,其中工作负载主要集中在Leader Range副本上,且KV存储操作的IO时延对整个系统的消息处理能力有着不可忽视的影响。
-
-考虑到这种特定的使用场景和base-kv的负载处理特性,inbox-store采取了以下默认的Balancer策略:
-
-* 默认限制Voter为1:由于副本数量越多可能导致写入响应时延增长,因此默认设置中将Range副本数限制为1,以优先保障消息的快速处理,但会有一定的可靠性损失,用户可以根据情况增加副本数量。
-* 启用RangeSplitBalancer和RangeLeaderBalancer:这一策略使得inbox-store能够随着工作负载的增长动态进行分片扩容,最终实现更加均衡的负载分布,提升系统整体性能。
-
-
-
-## StandardCluster的部署策略与灵活性评估
-
-BifroMQ StandardCluster采纳了一种集成所有功能模块于单一进程的部署策略。这种策略使得配置和部署过程相对简化,类似于业界普遍采用的"SharedNothing"集群架构。尽管如此,因为多个模块共享同一进程内的系统资源,这就限制了基于实际业务需求的动态配置能力。所有模块需统一进行扩缩容,这在某些情况下可能导致灵活性不足。这一点在云业务场景中尤为明显,因为不同类别的负载波动与时间相关,需要更加细致和灵活的资源管理。
-
-
-
-## IndependentWorkload Cluster的实施与过渡
-BifroMQ的独特架构设计使其能够轻松实现"单个模块独立进程"的部署模式,我们称之为IndependentWorkload Cluster(未来版本中推出)。这种模式不仅提供了更高的灵活性和精细的资源管理能力,还能够帮助用户根据业务的发展逐步从StandardCluster模式过渡到IndependentWorkload Cluster模式。这种渐进式的部署变化可在保持业务连续性的同时,优化资源配置和应对业务需求的波动。
-
-<img src={IndependentWorkload} style={{width: 700}} />
-
-## 总结
-
-以上内容为对BifroMQ高可用技术的全面介绍。BifroMQ通过实施多种机制确保了集群的整体高可用性。敬请关注我们即将发布的一系列专题文章,我们将在这些文章中继续深入剖析BifroMQ的各个组件及其设计原则,为您提供更多深度的技术见解。
-
-
-
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-blog/2023-12-04-bifromq-topic-subscription-mechanism.mdx b/i18n/zh-Hans/docusaurus-plugin-content-blog/2023-12-04-bifromq-topic-subscription-mechanism.mdx
deleted file mode 100644
index 71fbb8e2..00000000
--- a/i18n/zh-Hans/docusaurus-plugin-content-blog/2023-12-04-bifromq-topic-subscription-mechanism.mdx
+++ /dev/null
@@ -1,102 +0,0 @@
----
-slug: bifromq-topic-subscription
-title: "BifroMQ的Topic订阅机制"
-authors: [HaoYu]
-tags: [BifroMQ,MQTT,Topic,TopicFilter,Subscription,Serverless,Multi-Tenant]
----
-
-import MQTTTopicAndTopicFilter from './images/2023-12-03-bifromq-topic-subscription-mechanism/MQTT_Topic_TopicFilter.png';
-import TopicExpansionSet from './images/2023-12-03-bifromq-topic-subscription-mechanism/TopicExpansionSet.png';
-import OnePass from './images/2023-12-03-bifromq-topic-subscription-mechanism/OnePass.png';
-import DistService from './images/2023-12-03-bifromq-topic-subscription-mechanism/DistService.png';
-
-# BifroMQ的Topic订阅机制
-
-## 引言
-自从BifroMQ开源以来,我们频繁地收到有关其Topic订阅匹配实现技术的咨询。在MQTT的Pub/Sub机制中,Topic订阅匹配无疑是核心功能之一。在BifroMQ系统中,订阅信息的管理和消息Topic的匹配过程是由专门的Dist Service负责的。鉴于BifroMQ旨在支持构建大规模、多租户的Serverless系统,这一关键环节在实现时面临着诸多复杂挑战,尤其是订阅信息(TopicFilter)的分布式处理和相关的Topic匹配算法。本文将深入讲解BifroMQ Topic订阅匹配方案的设计思路,以及如何在Dist Service中实现。
-
-<!--truncate-->
-
-## MQTT的Topic和TopicFilter
-我们先简要回顾MQTT中关于Topic订阅和匹配的两个基本概念:*Topic*和*TopicFilter*。在MQTT的发布(Pub)过程中,Topic用于标识消息所属的具体主题,而在订阅(Sub)过程中,TopicFilter则用于表示对一系列主题的订阅意向。在本文中,我们将明确区分这两个概念:*Topic*和*TopicFilter*。
-
-*Topic*和*TopicFilter*都是类似于文件目录路径的UTF-8字符串,如“`/a/b/c`”、“`/a/b/c/`”、“`/+/b/c`”和“`+/b/#`”。在这些字符串中,“`/`”用作各级“目录”(或称*TopicLevel*)的分隔符。*TopicFilter*与*Topic*的主要区别在于*TopicLevel*的字符集:*TopicFilter*允许使用通配符“`+`”和“`#`”作为独立的`TopicLevel`。这些通配符用于表示对一系列主题的匹配逻辑。其中,“`+`”是单级通配符(Single-level Wildcard Character),可以出现在任何位置(例如:“`+`”、“`/+`”、“`+/+`”),用于匹配该级别上的所有*TopicLevel*;而“`#`”是多级通配符(Multi-level Wildcard Character),只能作为最后一级*TopicLevel*出现(例如:“`#`”、“`/#`”、“`+/+/#`”、“`+/#`”),用于匹配该级别及其所有下级的*TopicLevel*。
-
-*TopicFilter*按照从左至右的顺序对*Topic*进行匹配。以下是MQTT规范中的一些例子来说明这一点:
-首先,来看单级通配符“`+`”的应用。假设一个客户端订阅了“`sport/+/player1`”,它将接收到以下`Topic`名称发布的消息:
-* “`sport/tennis/player1`”
-* “`sport/badminton/player1`”
-* “`sport/golf/player1`”
-但它不会接收到“`sport/tennis/player2`”或“`sport/tennis/player1/ranking`”的消息。
-
-同样,如果客户端订阅了“`+/tennis/player1`”,它会接收到:
-* “`sport/tennis/player1`”
-* “`world/tennis/player1`”
-但不会接收到“`sport/tennis/player2`”或“`sport/badminton/player1`”。
-
-接下来,考虑多级通配符“`#`”。例如,如果客户端订阅了“`sport/tennis/player1/#`”,那么它将接收到以下*Topic*名称发布的消息:
-* “`sport/tennis/player1`”
-* “`sport/tennis/player1/ranking`”
-* “`sport/tennis/player1/score/wimbledon`”
-
-在使用“`#`”时,也有一些重要的点需要注意:
-* “`sport/#`”也能匹配单一的“`sport`”,因为“`#`”包括了父级别。
-* 单独订阅“`#`”将匹配所有`Topic`,接收所有主题的消息。
-* “`sport/tennis/#`”是有效的,而“`sport/tennis#`”和“`sport/tennis/#/ranking`”是无效的。
-
-这些例子清晰地展示了如何通过*TopicFilter*在MQTT中精确和灵活地匹配特定范围或类型的消息。
-不难发现,实现*TopicFilter*对*Topic*的匹配过程,逻辑上可以将*TopicFilter*组织成Trie(或Tree)的数据结构,匹配过程通过在*TopicFilter* Trie中逐级查找来完成。在遇到“`+`”和“`#`”这类特殊通配符时,采取相应的处理规则。以下是这一过程的简要说明:
-<img src={MQTTTopicAndTopicFilter} style={{width: '100%'}} />
-注:
-* *TopicFilter* Trie中的每个节点代表一个*TopicLevel*的字符串,这与传统String Prefix ['Trie'](https://en.wikipedia.org/wiki/Trie)中每个节点表示一个字符的做法有所不同
-* 当*TopicFilter*不包含通配符时,其匹配范围局限于具体的消息主题。在这种情况下,可以使用简单的Map结构来实现订阅匹配
-* 根据MQTT协议,以“`$`”开头的*Topic*被视为系统预留的特殊主题。这些主题不被通配符匹配,并在查找过程中会被特别忽略
-
-## BifroMQ面对的场景
-在这一章节中,我们将探讨BifroMQ在处理*TopicFilter* Trie时面临的特定场景及其挑战。
-
-通常的实现中,*TopicFilter* Trie在物理上被组织成内存中的Trie结构(或Tree)。在分布式环境下,每个MQTT Broker节点都本地存储有*TopicFilter* Trie的完整副本,并通过集群间通信确保各节点的Trie副本保持一致。鉴于对*TopicFilter* Trie的读请求(即匹配操作)的频率通常远高于写请求(更新操作),经典实现允许*Topic*匹配过程完全在本地进行,从而节省了远程访问的往返时间。然而,这种方法存在两个潜在的问题:
-1. *TopicFilter* Trie的大小受限于单个节点的存储资源。
-2. 当新增节点时,需要从其他节点全量同步*TopicFilter* Trie,其启动过程的准备时间与Trie的大小成正比。
-
-对于大多数企业级应用场景而言,这些潜在问题通常不会显现,因为订阅的规模很难达到单个节点资源的上限。但在云服务环境下,尤其是BifroMQ旨在实现的多租户Serverless服务场景中,这种传统方案显得不再适用。主要原因包括:
-1. 在多租户场景中,常见的问题之一是*TopicFilter* Trie的体积过大,以至于超出单个节点的资源上限。这种情况尤其普遍于那些拥有大量IoT设备的M2M场景,如智能家居,或者由于不恰当的订阅行为和测试活动所引起的情形。
-2. 当TopicFilter Trie体积庞大时,通常意味着业务处于高峰期。这时需要快速扩容,以便新增节点能尽快投入工作。但全量同步Trie会占用启动过程的准备时间。
-
-因此,BifroMQ需要探索与经典模式不同的解决方案,以更好地适应构建多租户Serverless服务的需求。该方案的核心挑战包括:
-1. 如何实现*TopicFilter* Trie的分布式化。
-2. 在分布式环境中如何高效执行匹配操作。
-
-解决这些挑战涉及到*TopicFilter* Trie的存储模式及相应的算法的全新设计,我们将这种新的方法称为“**OnePass**”。
-
-## The "OnePass" Solution
-在深入分析MQTT的topic匹配规则时,我们注意到一个重要的特点:对于任意确定的*Topic*,能够匹配该*Topic*的所有可能的*TopicFilter*构成了一个特定的集合。我们称这个集合为针对特定Topic的TopicFilter展开集(ExpansionSet)。下图像展示了这一概念:
-<img src={TopicExpansionSet} style={{width: '100%'}} />
-
-*TopicFilter*的展开集可以采用Trie结构来表示。在这个结构中,处于同一级的节点按照字节序进行排序。对展开集的Trie进行中序遍历,我们可以得到按字典序(Lexicographical Order)排列的所有可能的TopicFilter字符串。值得注意的是,在比较过程中,分隔符“`/`”不参与比较,或者可以用Unicode空字符("`\u0000`")来代替。展开集的大小(即可能的TopicFilter数量)与Topic的级数有关,可以通过公式`F(x) = 6*2^x - 1`来确定,其空间复杂度为O(2^x),随着级数的增加呈几何级数趋势上涨。
-
-然而,对于一个具体的*Topic*,实际发生的订阅仅是其展开集的一个很小的子集。因此,我们可以将系统内实际发生的订阅,以*TopicFilter*作为Key前缀的方式存储在有序的KV存储引擎中。在BifroMQ系统中,这一存储引擎由base-kv实现。订阅构成的*TopicFilter* Trie的存储模式可以简化为以下形式:
-* key: `<TenantId><0x00><TopicFilter><SessionId>`
-* value: `<MetadataAboutTheSubscription>`
-
-利用有序的KV存储,可以轻松实现逻辑上由实际订阅构成的*TopicFilter* Trie的分布式化。在BifroMQ中我们借助base-kv的分片能力实现这一目标:根据Topic订阅匹配的负载特性,按照一定的均衡策略进行Range分割和节点间分布。在系统扩容时,新增节点只需同步部分分片副本,无需同步全部订阅数据,从而也满足了快速扩容的需求。
-
-将订阅数据组织成有序KV形式后,下一个问题是如何实现MQTT的topic匹配逻辑。具体而言,当接收到一条MQTT Pub消息时,如何通过KV存储的读操作找到所有匹配该消息*Topic*的订阅记录。这个过程可以转化成一个集合问题:求得该*Topic*的展开集与当前系统实际发生的订阅的*TopicFilter*构成的集合的交集。这点很容易实现!
-<img src={OnePass} style={{width: '100%'}} />
-如图所示,左侧展示了*Topic* "`a/b/c`"的字节序展开集,而右侧是当前系统中存在的订阅关系,以有序KV存储的形式呈现。
-
-匹配算法的核心工作流程是从上至下依次扫描右侧的订阅关系KV,并在左侧的展开集中定位当前订阅的*TopicFilter*所在的位置。若左侧展开集中存在该*TopicFilter*,则认为找到了一个匹配。如果不存在,假设左侧展开集中下一个可能匹配的*TopicFilter*为T,则可以在右侧的订阅关系有序KV中跳过所有字节序小于T的部分,然后继续扫描。
-
-该算法在左右两个集合上均以单向方式执行,因此任何一个集合扫描完毕即标志着算法的结束。从空间复杂度的角度来看,左侧的展开集实际上充当了一种“索引”的角色,并不需要在内存中真实地展开。它只需根据字节序的展开规则确定下一个可能在右侧集合中出现的*TopicFilter*,因此左侧集合的空间开销可以被忽略。右侧集合代表的是当前系统中实际存在的订阅关系,其空间复杂度为`O(N)`,其中N是订阅的数量。算法的时间复杂度与实际存在的订阅关系数量有关,上限近似为`O(N*log(X))`,其中X是*Topic*的级数。当然最坏情况是右侧集合出现了所有*Topic*所有可能的订阅。
-
-由于算法执行过程中只需对订阅关系KV存储数据进行一次高效的扫描,因此我们将这个方法命名为“**OnePass**”。
-
-## The Dist Service
-Dist Service(bifromq-dist)是BifroMQ中处理订阅和消息路由分发的关键子服务,而“OnePass”方案则构成了其子服务架构的核心。Dist Service由两个服务端模块组成:DistServer和DistWorker。DistServer是一个无持久化状态的RPC服务模块,负责处理请求调度;而DistWorker则是一个具有持久化状态的模块,内嵌了KV存储引擎(base-kv),在其中实现了订阅关系的分布式存储。
-
-为了降低消息路由分发过程中内部通信所带来的时延开销,Dist Service被设计为数据与计算紧密耦合的形式。这里的“数据”有两重含义:一方面指的是MQTT Pub的消息本身,另一方面则是指订阅关系数据。而“计算”则指的是订阅匹配和分发过程。DistWorker将消息的topic匹配和分发过程封装成了base-kv的Range CoProcessor,确保了消息的匹配与分发过程在订阅信息存储的本地发生。这样的设计有效避免了额外数据传输对消息在BifroMQ系统内部时延的影响。
-<img src={DistService} style={{width: '100%'}} />
-上图展示了DistService在处理MQTT Pub/Sub时扮演的角色,为了提高订阅匹配的效率,Dist Worker对“OnePass”方案进行了进一步的优化,特别是通过引入缓存机制。在这种机制下,对于同一个*Topic*连续发布的消息,只需执行一次“OnePass”算法流程。匹配的结果会被缓存,供后续相似请求使用。这种引入缓存的策略不仅提升了处理速度,还减少了重复计算和本地IO的开销。值得注意的是,缓存带来的失效和更新策略是复杂的,但这些内容超出了本文的讨论范围,因此不再本文做详细展开。
-
-## 总结
-Topic订阅匹配构成了MQTT协议的核心功能,其灵活性也是MQTT能够广泛应用的关键因素。然而,多年来社区和行业累积的实现方案,在处理多租户Serverless服务业务场景时显示出了一定的局限性。BifroMQ的“OnePass”方案是基于第一性原理,从架构层面出发,对解决该问题的一次尝试。我们希望这一方案能够为社区带来新的启发,推动技术的发展与创新。
\ No newline at end of file
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-blog/2024-03-14-bifromq-3.0.0.mdx b/i18n/zh-Hans/docusaurus-plugin-content-blog/2024-03-14-bifromq-3.0.0.mdx
deleted file mode 100644
index 860e44cc..00000000
--- a/i18n/zh-Hans/docusaurus-plugin-content-blog/2024-03-14-bifromq-3.0.0.mdx
+++ /dev/null
@@ -1,27 +0,0 @@
----
-slug: bifromq-version-3
-title: "BifroMQ 3.0.0 Beta: 全面支持MQTT 5.0"
-authors: [ HaoYu ]
-tags: [ BifroMQ,MQTT,Topic,TopicFilter,Subscription,Serverless,Multi-Tenant ]
----
-
-我们非常高兴地宣布 BifroMQ 3.0.0 版本的 [beta](https://github.com/bifromqio/bifromq/releases/tag/v3.0.0-beta.1) 发布,这是 BifroMQ 项目取得重大进展的一个里程碑。此最新版本全面采用了 MQTT 5.0 标准,引入了一系列新特性。需要注意的是,为了实现对 MQTT5.0 版本的全面支持,BifroMQ
-3.0.0内部做了大量重构与优化,因此不能实现与之前版本产生的用户数据的兼容性。另外,插件接口也经过升级,以支持 MQTT 5.0 的功能,这意味着无法直接从旧版本进行滚动升级。
-
-<!--truncate-->
-
-**BifroMQ 3.0.0 的主要特点:**
-
-- **完全支持 MQTT 5.0:** 包括共享订阅、主题别名、订阅标识符、流控制、增强认证、会话过期、遗嘱延迟等,满足您所有的对 MQTT 5.0 的需求。
-
-- **增强的租户负载可观测性:** 最新版本改进了对租户负载的观测能力,通过[Tenant Metrics](/zh-Hans/docs/plugin/resource_throttler/)为每个租户的资源使用提供及时且准确的洞察。
-
-- **租户级资源限制:** 引入了新的插件类型——[Resource Throttler](/zh-Hans/docs/plugin/resource_throttler/),用于实现租户级运行时资源限制。这一功能有助于实现多租户系统中租户间资源和负载隔离。
-
-- **API易用性的改进:** 通过对接口用户概念的简化,进一步提升了 [API](/zh-Hans/docs/user_guide/api/intro/) 的易用性,使的用户系统更容易的与BifroMQ集成。
-
-- **背压保护:** 对过载做出及时响应,来确保系统的稳定性和可靠性。
-
-除了功能升级外,[官方文档](/docs/get_started/intro/)也进行了全面更新,使内容更加清晰、深入。
-
-我们鼓励您下载、测试并对 BifroMQ 3.0.0 的 beta 版本提供反馈。您的见解对我们持续改进非常重要。
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-blog/authors.yml b/i18n/zh-Hans/docusaurus-plugin-content-blog/authors.yml
deleted file mode 100644
index 88459a67..00000000
--- a/i18n/zh-Hans/docusaurus-plugin-content-blog/authors.yml
+++ /dev/null
@@ -1,12 +0,0 @@
-HaoYu:
-  name: Yonny(Yu) Hao
-  url: https://github.com/popduke
-  image_url: https://github.com/popduke.png
-MaFei:
-  name: Ma Fei
-  url: https://github.com/mafei6827
-  image_url: https://github.com/mafei6827.png
-Jiawei:
-  name: Gu Jiawei
-  url: https://github.com/Gujiawei-Edinburgh
-  image_url: https://github.com/Gujiawei-Edinburgh.png
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-blog/images/2023-09-06-bifromq-architecture-overview/bifromq-architecture-1.png b/i18n/zh-Hans/docusaurus-plugin-content-blog/images/2023-09-06-bifromq-architecture-overview/bifromq-architecture-1.png
deleted file mode 100644
index ee8f44be..00000000
Binary files a/i18n/zh-Hans/docusaurus-plugin-content-blog/images/2023-09-06-bifromq-architecture-overview/bifromq-architecture-1.png and /dev/null differ
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-blog/images/2023-09-06-bifromq-architecture-overview/bifromq-architecture-2-1.png b/i18n/zh-Hans/docusaurus-plugin-content-blog/images/2023-09-06-bifromq-architecture-overview/bifromq-architecture-2-1.png
deleted file mode 100644
index b578b592..00000000
Binary files a/i18n/zh-Hans/docusaurus-plugin-content-blog/images/2023-09-06-bifromq-architecture-overview/bifromq-architecture-2-1.png and /dev/null differ
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-blog/images/2023-09-06-bifromq-architecture-overview/bifromq-architecture-2-2.png b/i18n/zh-Hans/docusaurus-plugin-content-blog/images/2023-09-06-bifromq-architecture-overview/bifromq-architecture-2-2.png
deleted file mode 100644
index 4783ca93..00000000
Binary files a/i18n/zh-Hans/docusaurus-plugin-content-blog/images/2023-09-06-bifromq-architecture-overview/bifromq-architecture-2-2.png and /dev/null differ
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-blog/images/2023-09-06-bifromq-architecture-overview/bifromq-architecture-3.png b/i18n/zh-Hans/docusaurus-plugin-content-blog/images/2023-09-06-bifromq-architecture-overview/bifromq-architecture-3.png
deleted file mode 100644
index 72f7238b..00000000
Binary files a/i18n/zh-Hans/docusaurus-plugin-content-blog/images/2023-09-06-bifromq-architecture-overview/bifromq-architecture-3.png and /dev/null differ
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-blog/images/2023-10-24-bifromq-standardcluster/BifroMQ-API-Service.png b/i18n/zh-Hans/docusaurus-plugin-content-blog/images/2023-10-24-bifromq-standardcluster/BifroMQ-API-Service.png
deleted file mode 100644
index 697ade63..00000000
Binary files a/i18n/zh-Hans/docusaurus-plugin-content-blog/images/2023-10-24-bifromq-standardcluster/BifroMQ-API-Service.png and /dev/null differ
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-blog/images/2023-10-24-bifromq-standardcluster/BifroMQ-Dist-SubCluster.png b/i18n/zh-Hans/docusaurus-plugin-content-blog/images/2023-10-24-bifromq-standardcluster/BifroMQ-Dist-SubCluster.png
deleted file mode 100644
index 796ffad7..00000000
Binary files a/i18n/zh-Hans/docusaurus-plugin-content-blog/images/2023-10-24-bifromq-standardcluster/BifroMQ-Dist-SubCluster.png and /dev/null differ
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-blog/images/2023-10-24-bifromq-standardcluster/BifroMQ-Inbox-LoadBasedSplitter.png b/i18n/zh-Hans/docusaurus-plugin-content-blog/images/2023-10-24-bifromq-standardcluster/BifroMQ-Inbox-LoadBasedSplitter.png
deleted file mode 100644
index 94d6bcf8..00000000
Binary files a/i18n/zh-Hans/docusaurus-plugin-content-blog/images/2023-10-24-bifromq-standardcluster/BifroMQ-Inbox-LoadBasedSplitter.png and /dev/null differ
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-blog/images/2023-10-24-bifromq-standardcluster/BifroMQ-Inbox-SubCluster.png b/i18n/zh-Hans/docusaurus-plugin-content-blog/images/2023-10-24-bifromq-standardcluster/BifroMQ-Inbox-SubCluster.png
deleted file mode 100644
index d3a0dee0..00000000
Binary files a/i18n/zh-Hans/docusaurus-plugin-content-blog/images/2023-10-24-bifromq-standardcluster/BifroMQ-Inbox-SubCluster.png and /dev/null differ
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-blog/images/2023-10-24-bifromq-standardcluster/BifroMQ-StandardCluster.png b/i18n/zh-Hans/docusaurus-plugin-content-blog/images/2023-10-24-bifromq-standardcluster/BifroMQ-StandardCluster.png
deleted file mode 100644
index fcdf160b..00000000
Binary files a/i18n/zh-Hans/docusaurus-plugin-content-blog/images/2023-10-24-bifromq-standardcluster/BifroMQ-StandardCluster.png and /dev/null differ
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-blog/images/2023-12-01-bifromq-high-availability/BifroMQ-AutoEviction.png b/i18n/zh-Hans/docusaurus-plugin-content-blog/images/2023-12-01-bifromq-high-availability/BifroMQ-AutoEviction.png
deleted file mode 100644
index 5372615c..00000000
Binary files a/i18n/zh-Hans/docusaurus-plugin-content-blog/images/2023-12-01-bifromq-high-availability/BifroMQ-AutoEviction.png and /dev/null differ
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-blog/images/2023-12-01-bifromq-high-availability/BifroMQ-BrainSplit.png b/i18n/zh-Hans/docusaurus-plugin-content-blog/images/2023-12-01-bifromq-high-availability/BifroMQ-BrainSplit.png
deleted file mode 100644
index 87aebb47..00000000
Binary files a/i18n/zh-Hans/docusaurus-plugin-content-blog/images/2023-12-01-bifromq-high-availability/BifroMQ-BrainSplit.png and /dev/null differ
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-blog/images/2023-12-01-bifromq-high-availability/BifroMQ-Domain.png b/i18n/zh-Hans/docusaurus-plugin-content-blog/images/2023-12-01-bifromq-high-availability/BifroMQ-Domain.png
deleted file mode 100644
index bf1e05f1..00000000
Binary files a/i18n/zh-Hans/docusaurus-plugin-content-blog/images/2023-12-01-bifromq-high-availability/BifroMQ-Domain.png and /dev/null differ
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-blog/images/2023-12-01-bifromq-high-availability/BifroMQ-DynamicConfig.png b/i18n/zh-Hans/docusaurus-plugin-content-blog/images/2023-12-01-bifromq-high-availability/BifroMQ-DynamicConfig.png
deleted file mode 100644
index 879a132f..00000000
Binary files a/i18n/zh-Hans/docusaurus-plugin-content-blog/images/2023-12-01-bifromq-high-availability/BifroMQ-DynamicConfig.png and /dev/null differ
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-blog/images/2023-12-01-bifromq-high-availability/BifroMQ-IndependentWorkload.png b/i18n/zh-Hans/docusaurus-plugin-content-blog/images/2023-12-01-bifromq-high-availability/BifroMQ-IndependentWorkload.png
deleted file mode 100644
index f07d6b15..00000000
Binary files a/i18n/zh-Hans/docusaurus-plugin-content-blog/images/2023-12-01-bifromq-high-availability/BifroMQ-IndependentWorkload.png and /dev/null differ
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-blog/images/2023-12-01-bifromq-high-availability/BifroMQ-Join.png b/i18n/zh-Hans/docusaurus-plugin-content-blog/images/2023-12-01-bifromq-high-availability/BifroMQ-Join.png
deleted file mode 100644
index 945298a0..00000000
Binary files a/i18n/zh-Hans/docusaurus-plugin-content-blog/images/2023-12-01-bifromq-high-availability/BifroMQ-Join.png and /dev/null differ
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-blog/images/2023-12-01-bifromq-high-availability/BifroMQ-LeaderBalance.png b/i18n/zh-Hans/docusaurus-plugin-content-blog/images/2023-12-01-bifromq-high-availability/BifroMQ-LeaderBalance.png
deleted file mode 100644
index feb69f1c..00000000
Binary files a/i18n/zh-Hans/docusaurus-plugin-content-blog/images/2023-12-01-bifromq-high-availability/BifroMQ-LeaderBalance.png and /dev/null differ
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-blog/images/2023-12-01-bifromq-high-availability/BifroMQ-RPCCluster.png b/i18n/zh-Hans/docusaurus-plugin-content-blog/images/2023-12-01-bifromq-high-availability/BifroMQ-RPCCluster.png
deleted file mode 100644
index 74c34fd7..00000000
Binary files a/i18n/zh-Hans/docusaurus-plugin-content-blog/images/2023-12-01-bifromq-high-availability/BifroMQ-RPCCluster.png and /dev/null differ
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-blog/images/2023-12-01-bifromq-high-availability/BifroMQ-RangeBalancer.png b/i18n/zh-Hans/docusaurus-plugin-content-blog/images/2023-12-01-bifromq-high-availability/BifroMQ-RangeBalancer.png
deleted file mode 100644
index 1418d64a..00000000
Binary files a/i18n/zh-Hans/docusaurus-plugin-content-blog/images/2023-12-01-bifromq-high-availability/BifroMQ-RangeBalancer.png and /dev/null differ
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-blog/images/2023-12-01-bifromq-high-availability/BifroMQ-RangeLeaderBalancer.png b/i18n/zh-Hans/docusaurus-plugin-content-blog/images/2023-12-01-bifromq-high-availability/BifroMQ-RangeLeaderBalancer.png
deleted file mode 100644
index bc9c06c8..00000000
Binary files a/i18n/zh-Hans/docusaurus-plugin-content-blog/images/2023-12-01-bifromq-high-availability/BifroMQ-RangeLeaderBalancer.png and /dev/null differ
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-blog/images/2023-12-01-bifromq-high-availability/BifroMQ-RangeSplit.png b/i18n/zh-Hans/docusaurus-plugin-content-blog/images/2023-12-01-bifromq-high-availability/BifroMQ-RangeSplit.png
deleted file mode 100644
index 01274b93..00000000
Binary files a/i18n/zh-Hans/docusaurus-plugin-content-blog/images/2023-12-01-bifromq-high-availability/BifroMQ-RangeSplit.png and /dev/null differ
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-blog/images/2023-12-01-bifromq-high-availability/BifroMQ-RangeSplitBalancer.png b/i18n/zh-Hans/docusaurus-plugin-content-blog/images/2023-12-01-bifromq-high-availability/BifroMQ-RangeSplitBalancer.png
deleted file mode 100644
index 59b881f7..00000000
Binary files a/i18n/zh-Hans/docusaurus-plugin-content-blog/images/2023-12-01-bifromq-high-availability/BifroMQ-RangeSplitBalancer.png and /dev/null differ
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-blog/images/2023-12-01-bifromq-high-availability/BifroMQ-RecoveryBalancer.png b/i18n/zh-Hans/docusaurus-plugin-content-blog/images/2023-12-01-bifromq-high-availability/BifroMQ-RecoveryBalancer.png
deleted file mode 100644
index 144b509b..00000000
Binary files a/i18n/zh-Hans/docusaurus-plugin-content-blog/images/2023-12-01-bifromq-high-availability/BifroMQ-RecoveryBalancer.png and /dev/null differ
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-blog/images/2023-12-01-bifromq-high-availability/BifroMQ-ReplicaCntBalancer.png b/i18n/zh-Hans/docusaurus-plugin-content-blog/images/2023-12-01-bifromq-high-availability/BifroMQ-ReplicaCntBalancer.png
deleted file mode 100644
index a055408c..00000000
Binary files a/i18n/zh-Hans/docusaurus-plugin-content-blog/images/2023-12-01-bifromq-high-availability/BifroMQ-ReplicaCntBalancer.png and /dev/null differ
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-blog/images/2023-12-03-bifromq-topic-subscription-mechanism/DistService.png b/i18n/zh-Hans/docusaurus-plugin-content-blog/images/2023-12-03-bifromq-topic-subscription-mechanism/DistService.png
deleted file mode 100644
index c40cec4a..00000000
Binary files a/i18n/zh-Hans/docusaurus-plugin-content-blog/images/2023-12-03-bifromq-topic-subscription-mechanism/DistService.png and /dev/null differ
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-blog/images/2023-12-03-bifromq-topic-subscription-mechanism/MQTT_Topic_TopicFilter.png b/i18n/zh-Hans/docusaurus-plugin-content-blog/images/2023-12-03-bifromq-topic-subscription-mechanism/MQTT_Topic_TopicFilter.png
deleted file mode 100644
index f988ad00..00000000
Binary files a/i18n/zh-Hans/docusaurus-plugin-content-blog/images/2023-12-03-bifromq-topic-subscription-mechanism/MQTT_Topic_TopicFilter.png and /dev/null differ
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-blog/images/2023-12-03-bifromq-topic-subscription-mechanism/OnePass.png b/i18n/zh-Hans/docusaurus-plugin-content-blog/images/2023-12-03-bifromq-topic-subscription-mechanism/OnePass.png
deleted file mode 100644
index 8ef9a865..00000000
Binary files a/i18n/zh-Hans/docusaurus-plugin-content-blog/images/2023-12-03-bifromq-topic-subscription-mechanism/OnePass.png and /dev/null differ
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-blog/images/2023-12-03-bifromq-topic-subscription-mechanism/TopicExpansionSet.png b/i18n/zh-Hans/docusaurus-plugin-content-blog/images/2023-12-03-bifromq-topic-subscription-mechanism/TopicExpansionSet.png
deleted file mode 100644
index e4deeff2..00000000
Binary files a/i18n/zh-Hans/docusaurus-plugin-content-blog/images/2023-12-03-bifromq-topic-subscription-mechanism/TopicExpansionSet.png and /dev/null differ
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-blog/options.json b/i18n/zh-Hans/docusaurus-plugin-content-blog/options.json
deleted file mode 100644
index b747afc6..00000000
--- a/i18n/zh-Hans/docusaurus-plugin-content-blog/options.json
+++ /dev/null
@@ -1,14 +0,0 @@
-{
-  "title": {
-    "message": "博客",
-    "description": "The title for the blog used in SEO"
-  },
-  "description": {
-    "message": "博客",
-    "description": "The description for the blog used in SEO"
-  },
-  "sidebar.title": {
-    "message": "最近发布",
-    "description": "The label for the left sidebar"
-  }
-}
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/current.json b/i18n/zh-Hans/docusaurus-plugin-content-docs/current.json
deleted file mode 100644
index a1d39b3d..00000000
--- a/i18n/zh-Hans/docusaurus-plugin-content-docs/current.json
+++ /dev/null
@@ -1,66 +0,0 @@
-{
-  "version.label": {
-    "message": "3.3.x",
-    "description": "The label for version current"
-  },
-  "sidebar.tutorialSidebar.category.Get Started": {
-    "message": "快速开始",
-    "description": "The label for category Get Started in sidebar tutorialSidebar"
-  },
-  "sidebar.tutorialSidebar.category.Installation": {
-    "message": "安装",
-    "description": "The label for category Install & Deploy in sidebar tutorialSidebar"
-  },
-  "sidebar.tutorialSidebar.category.BifroMQ Cluster": {
-    "message": "BifroMQ 集群",
-    "description": "The label for category BifroMQ Cluster in sidebar tutorialSidebar"
-  },
-  "sidebar.tutorialSidebar.category.User Guide": {
-    "message": "用户指南",
-    "description": "The label for category User Guide in sidebar tutorialSidebar"
-  },
-  "sidebar.tutorialSidebar.category.Basic MQTT Features": {
-    "message": "MQTT 基础功能",
-    "description": "The generated-index page description for category User Guide in sidebar tutorialSidebar"
-  },
-  "sidebar.tutorialSidebar.category.Data Integration": {
-    "message": "数据集成",
-    "description": "The label for category Data Integration in sidebar tutorialSidebar"
-  },
-  "sidebar.tutorialSidebar.category.API Usage": {
-    "message": "API 使用",
-    "description": "The label for category API Usage in sidebar tutorialSidebar"
-  },
-  "sidebar.tutorialSidebar.category.Plugin": {
-    "message": "插件",
-    "description": "The label for category Plugin in sidebar tutorialSidebar"
-  },
-  "sidebar.tutorialSidebar.category.Administration": {
-    "message": "管理",
-    "description": "The label for category Administration in sidebar tutorialSidebar"
-  },
-  "sidebar.tutorialSidebar.category.Configuration": {
-    "message": "配置",
-    "description": "The label for category configs in sidebar tutorialSidebar"
-  },
-  "sidebar.tutorialSidebar.category.Tuning": {
-    "message": "调优",
-    "description": "The label for category Tuning in sidebar tutorialSidebar"
-  },
-  "sidebar.tutorialSidebar.category.Observability": {
-    "message": "可观测性",
-    "description": "The label for category Observability in sidebar tutorialSidebar"
-  },
-  "sidebar.tutorialSidebar.category.Security": {
-    "message": "安全",
-    "description": "The label for category Security in sidebar tutorialSidebar"
-  },
-  "sidebar.tutorialSidebar.category.MQTT Best Practices": {
-    "message": "MQTT 最佳实践",
-    "description": "The label for category Best Practices in sidebar tutorialSidebar"
-  },
-  "sidebar.tutorialSidebar.category.Test Report": {
-    "message": "测试报告",
-    "description": "The label for category Test Report in sidebar tutorialSidebar"
-  }
-}
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/01_get_started/1_quick_install.md b/i18n/zh-Hans/docusaurus-plugin-content-docs/current/01_get_started/1_quick_install.md
deleted file mode 100644
index 9de47b99..00000000
--- a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/01_get_started/1_quick_install.md
+++ /dev/null
@@ -1,13 +0,0 @@
----
-sidebar_position: 1
-title: "快速安装"
----
-
-推荐使用Docker,快速开启BifroMQ。
-```
-docker run -d --name bifromq -p 1883:1883 bifromq/bifromq:latest
-```
-
-## 其他安装选项
-
-有关更多安装替代方案,请参阅:[安装](../02_installation/intro.md)。
\ No newline at end of file
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/01_get_started/2_quick_verify.md b/i18n/zh-Hans/docusaurus-plugin-content-docs/current/01_get_started/2_quick_verify.md
deleted file mode 100644
index aa5414e5..00000000
--- a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/01_get_started/2_quick_verify.md
+++ /dev/null
@@ -1,30 +0,0 @@
----
-sidebar_position: 2
-title: "快速验证"
----
-
-以下是使用客户端工具MQTTX 快速验证 BifroMQ 基本 MQTT 功能的步骤。
-
-1. 访问 https://mqttx.app/ 下载并安装 MQTTX。
-2. 打开 MQTTX 并点击左侧边栏的“新建连接”或“+”号以创建新的连接配置。
-
-![newconn](./images/newconn.jpg)
-
-3. 填写所需字段:
-    * Name:此配置的名称。您可以选择任意名称。
-    * Client ID:客户端 ID,您可以手动设置或使用右侧的按钮随机生成。它必须包含字符“a-z”、“0-9”、“_”、“-”,并且不能超过 128 字节。使用 UTF8 编码且必须是唯一的。
-    * Host: 连接地址。以协议前缀开始(对于 TCP 使用 mqtt://,对于 TLS/SSL 使用 mqtts://,或对于 WSS 使用 wss://),后跟可以访问 BifroMQ 服务器的域名。
-    * Port: 连接端口。根据协议前缀选择适当的端口。默认端口是 TCP:1883,TLS/SSL:1884,WSS:443。
-    * Username & Password: 输入您拥有的用户名和密码,或者如果您的BifroMQ安装仅用于测试,则留空。
-    * MQTT Version: 选择 3.1、3.1.1、5.0
-
-4. 正确输入连接配置后,点击右上角的'连接'以连接到服务器。 
-5. 订阅一个主题:点击左上角的“新建订阅”按钮,并在弹出的对话框中输入主题。 
-
-![subscribe](./images/subscribe.jpg)
-
-6. 发布消息:在消息发送/接收界面,输入您在右下角订阅的相同主题。选择默认 QoS 0,输入消息内容,并点击发送按钮发布。
-
-![publish](./images/publish.jpg)
-
-7. 消息成功发送后,您应该能在界面的右侧看到发送的消息。
\ No newline at end of file
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/01_get_started/3_faq.md b/i18n/zh-Hans/docusaurus-plugin-content-docs/current/01_get_started/3_faq.md
deleted file mode 100644
index 7036fab3..00000000
--- a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/01_get_started/3_faq.md
+++ /dev/null
@@ -1,44 +0,0 @@
----
-sidebar_position: 3 
-title: "常见问题"
----
-
-## BifroMQ支持哪些版本的MQTT协议?
-BifroMQ全面支持以下MQTT协议版本:v3.1、v3.1.1 和 v5.0。这种多样性确保了BifroMQ能够适应广泛的IoT设备和应用程序,遵循不同的协议标准。此外,BifroMQ允许在运行时动态控制租户级别的协议能力,提供定制的连接选项以满足特定租户的需求。
-
-## BifroMQ的Java版本要求是什么?
-
-BifroMQ的Java版本要求可以分为两个方面:
-- **BifroMQ运行环境**: BifroMQ本身需要JDK 17或更高版本才能运行。
-- **BifroMQ插件开发**: 对于开发BifroMQ插件,没有强制要求特定的Java语言版本或JDK版本。然而,插件开发者需要确保他们的插件在更高的Java环境中能够正常工作。为了防止兼容性问题,我们建议将插件的运行环境与BifroMQ的保持一致。
-
-## BifroMQ包含内置规则引擎吗?
-
-与提供MQTT协议能力的其他产品或项目不同,BifroMQ的主要目标是作为一个高性能、多租户、分布式中间件,实现标准MQTT协议。"规则引擎"不是MQTT协议规范的一部分,因此不包含在BifroMQ中。BifroMQ更多地关注与上游和下游系统的以标准的方式集成。从这个角度看,"规则引擎"只是与BifroMQ集成的一种功能形式(甚至在不同的规则引擎项目中,还存在功能差异)。我们希望这种需求可以在BifroMQ开发者社区中以开放的方式得到满足。
-
-## 如何使用BifroMQ进行数据集成?
-
-使用BifroMQ进行数据集成的方法在很大程度上取决于您的业务场景:
-
-- **单租户系统**: 对于逻辑上的单租户系统,其他系统可以直接使用MQTT协议与BifroMQ[集成](../05_user_guide/2_integration/intro.md)。例如,可以利用共享订阅并行订阅消息,或MQTT客户端可以直接向BifroMQ发布消息。这种方法完全解耦了上游和下游系统,便于比较不同的MQTT中间件。大多数专有企业应用属于此类。
-
-- **多租户系统**: 对于共享资源架构的多租户业务场景,BifroMQ作为该类系统内的一个子系统,与其他多租户子系统共享同一个租户管理控制面。在这种情况下,系统集成需要采用BifroMQ的插件机制(目前还未开放)。下游系统将在插件级别与BifroMQ有一定程度的耦合,使得实现变得有些复杂。这通常用于构建Serverless云服务的业务场景。
-
-## BifroMQ内置存储引擎主要用于哪些数据持久化?
-
-BifroMQ的内置存储引擎主要用于持久化MQTT协议要求的SessionState(参见: [MQTT v3.1.1 3.1.2.4](http://docs.oasis-open.org/mqtt/mqtt/v3.1.1/os/mqtt-v3.1.1-os.html#_Toc398718028))和Retain消息。这有助于防止Broker重启或崩溃时丢失会话状态。需要注意的是,持久化引擎大多数情况下与消息的QoS没有直接关系。例如,当一个MQTT连接开始一个持久会话时,离线QoS0订阅消息仍将被持久化,直到会话恢复并完成推送。
-
-## 为什么BifroMQ没有管理控制台/UI界面?
-
-BifroMQ强调在各种类型的业务系统中的集成,因此它不在中间件级别定义更高级别的管理模式和概念。然而,BifroMQ确实提供了以下能力用于运行时控制集成和监控:
-- **[API](../05_user_guide/3_api/intro.md)**: 代理端控制逻辑,如强制断开连接。
-- **[Metrics](../07_admin_guide/03_observability/metrics/intro.md)**: BifroMQ的运行时指标,可以与现有监控系统集成。
-- **[EventCollector Plugin](../06_plugin/2_event_collector.md)**: BifroMQ操作过程中产生的各种事件,启用不同的事件溯源业务逻辑,如连接计数、在线/离线事件等。
-- **[ResourceThrottler Plugin](../06_plugin/3_resource_throttler.md)**: 用于控制租户级资源使用。
-- **[SettingProvider Plugin](../06_plugin/4_setting_provider/intro.md)**: 用于调整租户级运行时设置。
-
-我们也鼓励社区开发者参与满足这些需求,并构建多样化的UI管理界面。
-
-## BifroMQ和IoT Core之间的关系是什么?
-
-IoT Core是百度智能云提供的一套物联网核心套件,支持预付费和按量付费计费模式的公有云服务。BifroMQ和IoT Core有着密切的关系,因为BifroMQ是IoT Core的底层技术。BifroMQ的多租户、高性能和分布式能力为构建大规模的IoT Core设备连接和消息系统提供了强大支持。
\ No newline at end of file
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/01_get_started/_category_.json b/i18n/zh-Hans/docusaurus-plugin-content-docs/current/01_get_started/_category_.json
deleted file mode 100644
index 0cc7575a..00000000
--- a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/01_get_started/_category_.json
+++ /dev/null
@@ -1,8 +0,0 @@
-{
-  "label": "快速开始",
-  "position": 1,
-  "link": {
-    "type": "doc",
-    "id": "get_started/intro"
-  }
-}
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/01_get_started/images/newconn.jpg b/i18n/zh-Hans/docusaurus-plugin-content-docs/current/01_get_started/images/newconn.jpg
deleted file mode 100644
index 280f173e..00000000
Binary files a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/01_get_started/images/newconn.jpg and /dev/null differ
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/01_get_started/images/publish.jpg b/i18n/zh-Hans/docusaurus-plugin-content-docs/current/01_get_started/images/publish.jpg
deleted file mode 100644
index 9f1566b8..00000000
Binary files a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/01_get_started/images/publish.jpg and /dev/null differ
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/01_get_started/images/subscribe.jpg b/i18n/zh-Hans/docusaurus-plugin-content-docs/current/01_get_started/images/subscribe.jpg
deleted file mode 100644
index 66ebd860..00000000
Binary files a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/01_get_started/images/subscribe.jpg and /dev/null differ
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/01_get_started/intro.md b/i18n/zh-Hans/docusaurus-plugin-content-docs/current/01_get_started/intro.md
deleted file mode 100644
index 23387a8c..00000000
--- a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/01_get_started/intro.md
+++ /dev/null
@@ -1,43 +0,0 @@
----
-id: intro
-sidebar_position: 0
-title: "介绍"
----
-
-BifroMQ是一个Java实现的高性能、分布式MQTT Broker,无缝集成了原生的多租户支持。它旨在促进大规模 IoT 设备连接和消息系统的构建。目前,BifroMQ 作为基础技术,服务于百度公有云服务[IoTCore](https://cloud.baidu.com/product/iot.html)。
-
-## 名称由来
-
-BifroMQ 的名字来源于北欧神话中的 `Bifröst`——一座连接 Midgard(人类的世界)和 Asgard(神的领域)的彩虹桥。如同 Bifröst,BifroMQ 作为一个灵活而坚固的桥梁,连接不同的系统或应用程序,以实现通过消息交换进行通信。这与 MQTT 中间件的核心功能相符,即管理和加速分布式系统中的消息传递。
-
-Bifröst 的坚固象征着 BifroMQ 的稳定性和可靠性,其灵活性则标志着 BifroMQ 的可扩展性和适应性。简而言之,“BifroMQ”体现了一个连接各种系统或应用程序的、坚韧、可适应的 MQTT 中间件。
-
-## 功能列表
-
-* 完全支持 MQTT 3.1、3.1.1 和 5.0 版本的特性,覆盖 TCP、TLS、WS、WSS。
-* 原生支持多租户、资源共享和工作负载隔离。
-* 内置的分布式存储引擎,为 MQTT 工作负载优化,无需第三方中间件依赖。
-* 扩展机制支持:
-  * 认证/授权。
-  * 租户级运行时设置。
-  * 租户级资源限制。
-  * 事件。
-  * 系统/租户级监控。
-
-## 社区
-
-#### **问题跟踪**
-
-我们使用 GitHub [Issues](https://github.com/bifromqio/bifromq/issues) 来跟踪请求和错误。如果您有任何问题或遇到问题,随时开启一个 issue。
-
-#### **Discord**
-
-<a href="https://discord.gg/Pfs3QRadRB"><img src="https://img.shields.io/discord/1115542029531885599?logo=discord&logoColor=white" alt="BifroMQ Discord 服务器" /></a>
-
-#### **微信群组**
-
-[通过电子邮件](mailto:hello@bifromq.io) 向我们发送您的微信 ID,以及为什么您对 BifroMQ 感兴趣的更多信息(我们很乐意听到),我们将尽快邀请您加入我们的群组。
-
-## 专业服务
-
-欢迎 [通过电子邮件](mailto:hello@bifromq.io) 联系我们。
\ No newline at end of file
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/02_installation/1_docker.md b/i18n/zh-Hans/docusaurus-plugin-content-docs/current/02_installation/1_docker.md
deleted file mode 100644
index 93f6b444..00000000
--- a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/02_installation/1_docker.md
+++ /dev/null
@@ -1,35 +0,0 @@
----
-sidebar_position: 1
-title: "Docker"
----
-
-## 安装前提
-
-* 已安装 [Docker](https://www.docker.com/)。
-* 使用1883端口的权限,并且该端口可用。如果您没有权限,请更改为相应的端口。
-
-## Docker命令
-
-运行以下命令,在容器中以Linux用户 `bifromq` 的身份运行BifroMQ。
-
-```
-docker run -d --name bifromq -p 1883:1883 bifromq/bifromq:latest
-```
-
-## 内存限制
-
-默认情况下,BifroMQ进程启动时,会根据服务器的物理内存动态计算相关的JVM参数。然而,在容器化环境中启动时,它会内省主机机器的物理内存,可能会与Docker或容器施加的内存限制产生冲突,从而导致容器过早终止。
-
-为了规避此类挑战,建议主动限制容器的内存消耗,并通过环境变量将这些限制传达给容器运行时。在BifroMQ启动时,会优先根据 `MEM_LIMIT` 环境变量计算JVM参数。下面提供了一个具体示例:
-
-```
-docker run -d -m 10G -e MEM_LIMIT='10737418240' --name bifromq -p 1883:1883 bifromq/bifromq:latest
-```
-
-***注意:MEM_LIMIT的单位是字节。***
-
-进一步地,可以主动配置JVM堆内存,并直接将其传递给容器运行时,供BifroMQ使用。下面提供了一个具体示例:
-
-```
-docker run -d -m 10G -e JVM_HEAP_OPTS='-Xms2G -Xmx4G -XX:MetaspaceSize=128m -XX:MaxMetaspaceSize=500m -XX:MaxDirectMemorySize=1G' --name bifromq -p 1883:1883 bifromq/bifromq:latest
-```
\ No newline at end of file
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/02_installation/2_linux.md b/i18n/zh-Hans/docusaurus-plugin-content-docs/current/02_installation/2_linux.md
deleted file mode 100644
index ceada4ea..00000000
--- a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/02_installation/2_linux.md
+++ /dev/null
@@ -1,16 +0,0 @@
----
-sidebar_position: 2
-title: "Linux"
----
-
-## 安装前提
-
-* 运行环境已安装Java17或更高版本
-* 获取BifroMQ最新[发布版](https://github.com/bifromqio/bifromq/releases)
-
-## 执行命令
-
-```
-tar -zxvf bifromq-*-standalone.tar.gz --strip-components 1  -C /usr/share/bifromq/
-cd /usr/share/bifromq && ./bin/standalone.sh start
-```
\ No newline at end of file
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/02_installation/3_windows.md b/i18n/zh-Hans/docusaurus-plugin-content-docs/current/02_installation/3_windows.md
deleted file mode 100644
index 965b917f..00000000
--- a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/02_installation/3_windows.md
+++ /dev/null
@@ -1,17 +0,0 @@
----
-sidebar_position: 3
-title: "Windows"
----
-
-## 安装前提
-
-* 运行环境已安装Java17或更高版本
-* 获取BifroMQ最新[发布版](https://github.com/bifromqio/bifromq/releases)
-
-## 执行命令
-
-```
-unzip -zxvf bifromq-*-standalone-windows.zip
-cd bifromq\bin
-standalone.bat start
-```
\ No newline at end of file
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/02_installation/4_install_from_source.md b/i18n/zh-Hans/docusaurus-plugin-content-docs/current/02_installation/4_install_from_source.md
deleted file mode 100644
index a7ac1a6b..00000000
--- a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/02_installation/4_install_from_source.md
+++ /dev/null
@@ -1,32 +0,0 @@
----
-sidebar_position: 4
-title: "源码安装"
----
-
-## 安装前提
-
-* 运行环境已安装
-  * Java17或更高版本
-  * Maven 3.5.0或更高版本
-
-## 构建
-
-克隆仓库到本地工作区
-
-```
-cd <YOUR_WORKSPACE>
-git clone https://github.com/bifromqio/bifromq bifromq
-```
-切换目录到项目根文件夹并执行以下命令来构建整个项目
-
-```
-cd bifromq
-mvn wrapper:wrapper
-./mvnw -U clean package
-```
-
-构建的输出是两个 tar.gz 文件和一个 zip 文件,位于 /build/build-bifromq-starters/target/ 下
-
-* bifromq-xxx-all.tar.gz // 适用于 linux 和 mac os 的标准集群部署 tar.gz
-* bifromq-xxx-standalone.tar.gz // 适用于 linux 和 mac os 的独立部署 tar.gz
-* bifromq-xxx-windows-standalone.zip // 适用于 windows 的独立部署 zip
\ No newline at end of file
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/02_installation/5_config_migration.md b/i18n/zh-Hans/docusaurus-plugin-content-docs/current/02_installation/5_config_migration.md
deleted file mode 100644
index dccf547e..00000000
--- a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/02_installation/5_config_migration.md
+++ /dev/null
@@ -1,8 +0,0 @@
----
-sidebar_position: 5
-title: "配置约定与迁移"
----
-
-不同版本之间的配置可能会有所不同。在部署 BifroMQ 时,您可以使用以前的配置文件,这不会导致BifroMQ不能启动。然而,请注意,这些旧版本的配置可能不会生效。 
-
-为了简化BifroMQ的配置过程,配置文件standalone.yml中只包含常用配置项。对于未指定的配置项将使用默认值,BifroMQ启动后会在 `info.log` 的开头输出完整的配置文件内容。用户可以使用日志中的全量配置输出来比较和更新他们的standalone.yml配置。
\ No newline at end of file
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/02_installation/6_nodes_on_k8s.md b/i18n/zh-Hans/docusaurus-plugin-content-docs/current/02_installation/6_nodes_on_k8s.md
deleted file mode 100644
index 98a539d7..00000000
--- a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/02_installation/6_nodes_on_k8s.md
+++ /dev/null
@@ -1,32 +0,0 @@
----
-sidebar_position: 6
-title: "关于 Kubernetes 部署的说明"
----
-
-在Kubernetes上部署需要考虑BifroMQ有状态服务的特性,理解Kubernetes特定的集群操作和维护实践。以下是一些关键考虑因素和指导。
-
-## 有状态服务的考虑
-BifroMQ内置分布式存储引擎,选择在 Kubernetes 中运行 BifroMQ 的用户应仔细规划:
-
-- **Persistent Volume**
-- **StatefulSets**
-- **Headless Service**
-
-## 部署复杂性
-
-在 Kubernetes 中运行 BifroMQ 涉及的复杂性包括:
-
-- **网络**:选择合适的网络策略和Ingress Controller,以管理集群内部和外部客户端之间的通信。
-- **配置管理**:使用 ConfigMaps 或 Secrets 以动态、可扩展的方式管理 BifroMQ 配置。
-- **资源限制和请求**:定义适当的 CPU 和内存限制和请求,确保 BifroMQ 有足够的资源以获得最佳性能,而不会挤占其他应用程序。
-
-## 集群操作和维护
-
-在 Kubernetes 上成功部署 BifroMQ 需要深入理解:
-
-- **集群监控和日志**:实施全面的监控和日志记录,以快速识别和解决问题。
-- **可扩展性**:理解如何在 Kubernetes 中适当地扩展 BifroMQ,以处理不同的负载而不影响性能。
-
-## BifroMQ 团队支持
-
-在Kubernetes中部署BifroMQ带来了额外的复杂度,[BifroMQ 团队](mailto:hello@bifromq.io)提供专业的咨询服务,以帮助用户实现最佳的部署结果。
\ No newline at end of file
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/02_installation/_category_.json b/i18n/zh-Hans/docusaurus-plugin-content-docs/current/02_installation/_category_.json
deleted file mode 100644
index d6321019..00000000
--- a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/02_installation/_category_.json
+++ /dev/null
@@ -1,8 +0,0 @@
-{
-  "label": "Installation",
-  "position": 2,
-  "link": {
-    "type": "doc",
-    "id": "installation/intro"
-  }
-}
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/02_installation/intro.md b/i18n/zh-Hans/docusaurus-plugin-content-docs/current/02_installation/intro.md
deleted file mode 100644
index 2ff9d837..00000000
--- a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/02_installation/intro.md
+++ /dev/null
@@ -1,39 +0,0 @@
----
-id: intro
-sidebar_position: 0
-title: "安装概述"
----
-
-## 安装前提
-
-BifroMQ的运行需要 **Java 17** 或更高版本。在继续进行BifroMQ安装之前,请确保您的Java运行环境已更新,以满足这些要求。
-
-## 安装目录结构
-
-安装完成后,BifroMQ会按照以下目录结构组织其文件:
-
-| 目录       | 描述                                                         |
-|-----------|--------------------------------------------------------------|
-| `bin`     | 用于启动和管理BifroMQ的可执行脚本。                           |
-| `conf`    | 用于自定义BifroMQ操作的配置文件。                             |
-| `lib`     | 运行BifroMQ的程序库文件。                                     |
-| `plugins` | 以 [pf4j](https://pf4j.org) 兼容格式的BifroMQ插件。           |
-| `data`    | 用户的持久化数据。                                           |
-| `logs`    | 日志文件。                                                   |
-
-## 运行BifroMQ
-
-BifroMQ的启动脚本识别几个环境变量,允许自定义和优化其运行环境:
-
-| 环境变量          | 描述                                                                                     |
-|-------------------|------------------------------------------------------------------------------------------|
-| `LOG_DIR`         | 指定BifroMQ应该存储其日志文件的目录。如果未设置,默认为 `./logs`。                        |
-| `DATA_DIR`        | 确定存储BifroMQ数据的目录。如果未设置,默认为 `./data`。                                  |
-| `JAVA_HOME`       | 指定BifroMQ应使用的Java运行时环境(JRE)的路径。                                          |
-| `MEM_LIMIT`       | 限制BifroMQ可以使用的最大内存量。                                                         |
-| `JVM_PERF_OPTS`   | 用于调优运行BifroMQ的JVM实例的自定义JVM性能选项。                                         |
-| `JVM_GC_OPTS`     | 优化BifroMQ内存管理的垃圾收集(GC)选项。                                                 |
-| `JVM_HEAP_OPTS`   | 指定JVM堆大小和其他直接影响BifroMQ性能的内存设置。                                        |
-| `EXTRA_JVM_OPTS`  | 用户可能希望传递的其他JVM选项,以自定义BifroMQ运行环境。                                  |
-| `JVM_DEBUG`       | 启用JVM的调试选项,对于开发和故障排除很有用。                                             |
-| `JAVA_DEBUG_PORT` | 当启用 `JVM_DEBUG` 时,设置JVM调试器附加的端口。                                          |
\ No newline at end of file
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/04_cluster/1_standardcluster.md b/i18n/zh-Hans/docusaurus-plugin-content-docs/current/04_cluster/1_standardcluster.md
deleted file mode 100644
index a5017236..00000000
--- a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/04_cluster/1_standardcluster.md
+++ /dev/null
@@ -1,69 +0,0 @@
----
-sidebar_position: 1
-title: "部署StandardCluster"
----
-
-## 部署前提
-
-* 确保已安装 JDK 17 或更高版本。
-* 下载最新版本的 BifroMQ 发布包 [release](https://github.com/bifromqio/bifromq/releases).
-
-## 安装步骤
-
-本节演示 3 节点集群的部署过程。类似于 Linux 上的部署 [Linux 上的部署](../02_installation/2_linux.md), 您首先需要解压下载的压缩包。
-
-### 配置
-
-默认情况下提供了一个配置文件,其中包含以下设置:
-
-```yaml
-# To bootstrap cluster, at least one node must set bootstrap to true or alternatively configuring RangeBootstrapBalancer in StateStoreConfig
-bootstrap: true
-
-mqttServerConfig:
-  tcpListener:
-    port: 1883
-
-# BifroMQ Cluster Configuration
-clusterConfig:
-  # Cluster environment, cluster members under same environment can communicate with each other
-  env: "Test"
-  # Host address to bind for inter-member communication. If left blank, a site-local address will be used if available
-  host:
-  # Port for listening to cluster membership-related messages. If left blank, the operating system will automatically choose an available port.
-  # For seed nodes, it is recommended to specify an explicit port number to simplify the cluster building process.
-  port:
-  # Optional DNS domain name used to achieve cluster member address discovery, can be used in K8S environment deployment
-  clusterDomainName:
-  # Comma-separated list of <ADDRESS>:<PORT> for joining the cluster
-  seedEndpoints:
-```
-
-**注意**: 除了 `clusterConfig.port` 之外,BifroMQ 还使用专用端口进行集群间的 RPC 通信,例如 `RPCServerConfig.port`。如果这些端口未在配置文件中明确指定,系统将随机选择可用端口,这可能会导致在有防火墙的环境中集群间的 RPC 通信失败。在这种情况下,请参考
-完整的[配置文件](../07_admin_guide/01_configuration/1_config_file_manual.md),明确指定这些端口,并调整相应的防火墙规则。
-
-### 设置种子节点
-
-在设置集群之前,您需要以逗号分隔的 `<ADDRESS>:<PORT>`格式指定种子节点,例如:
-
-```yaml
-clusterConfig.seedEndpoints: ${NODE1_ADDR}:${PORT},${NODE2_ADDR}:${PORT},${NODE3_ADDR}:${PORT}
-```
-
-有关详细的配置信息,请参阅 BifroMQ [配置文档](../07_admin_guide/01_configuration/1_config_file_manual.md).
-
-### 启动节点
-
-使用以下命令启动节点:
-
-```shell
-./bin/standalone.sh start
-```
-
-建议首先启动 'bootstrap' 节点。
-
-### 检查集群状态
-
-运行脚本后,节点将形成集群并在各自的机器上生成 `AgentHost joined seedEndpoint: ${seedEndpoints}`日志。
-
-您还可以使用各种系统级[Metrics](../07_admin_guide/03_observability/metrics/intro.md)来监控集群的健康状况和性能。
\ No newline at end of file
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/04_cluster/2_high_availability.md b/i18n/zh-Hans/docusaurus-plugin-content-docs/current/04_cluster/2_high_availability.md
deleted file mode 100644
index 386426fd..00000000
--- a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/04_cluster/2_high_availability.md
+++ /dev/null
@@ -1,68 +0,0 @@
----
-sidebar_position: 2
-title: "高可用性"
----
-
-# 高可用性
-
-BifroMQ 通过其基于 Gossip 协议的去中心化集群构建能力(base-cluster)来实现高可用性。这种架构不需要额外的服务发现组件来建立集群,从而降低了与单点故障相关的运营风险。结果是一个能够灵活扩展并在集群所有节点中保持高可用性的系统。
-
-在内部,BifroMQ 将工作负载分解,并将其组织成逻辑上独立的子集群。每种类型的负载由一个独立的子集群管理,与存储相关的模块使用 Raft 算法来确保一致性和高可用性。
-
-## 如何在集群中启用高可用性
-
-BifroMQ StandardCluster 采用将所有工作负载封装在单个进程中的部署模型。由于不同的子集群对高可用性的要求不同,在 BifroMQ 集群中启用高可用性需要满足以下条件。
-
-### 集群节点数量
-
-对于集群中的有状态分布式存储引擎 base-kv,只有当集群中超过半数的节点存活时,才能保证服务的可用性。因此,**集群必须至少包含 3 个节点** 以确保高可用性。
-
-### 集群配置
-
-与 base-cluster 相关的配置集中在配置文件的 "clusterConfig" 部分:
-
-| 参数名称            | 默认值   | 推荐值                                                                                                   |
-|-------------------|---------|-----------------------------------------------------------------------------------------------------------|
-| env               | Test    | ***Prod*** 或 ***Test*** 以隔离集群,确保一个集群中的节点不会意外加入另一个集群。                               |
-| host              | 未设置    | 集群内各节点必须可以相互访问的 IP 地址。                                                                    |
-| port              | 未设置    | 集群内各节点必须可以相互访问的端口。                                                                        |
-| clusterDomainName | 未设置    | 集群节点注册的域名。                                                                                        |
-| seedEndpoints     | 不为空   | 集群中已有节点的列表。                                                                                      |
-
-### 副本数量配置
-
-BifroMQ 利用 base-kv 来支持三种原生的 MQTT 负载类型:
-
-- MQTT 动态订阅 (DistWorker)
-- MQTT 离线消息 (InboxStore)
-- MQTT 保留消息 (RetainStore)
-
-base-kv 模块使用 Raft 协议来确保分片副本的一致性和高可用性。要实现高可用性,您需要修改以下系统变量:
-
-| 系统变量名称                     | 默认值 | 推荐值                              |
-|--------------------------------|-------|--------------------------------------|
-| dist_worker_range_voter_count  | 3     | 至少 3,最好为奇数。                 |
-| inbox_store_range_voter_count  | 1     | 至少 3,最好为奇数。                 |
-| retain_store_range_voter_count | 3     | 至少 3,最好为奇数。                 |
-
-### StoreBalancer 配置
-
-BifroMQ 的 base-kv 模块以去中心化的方式实现持久化服务集群的自动管理,包括初始化、分片、负载均衡和恢复等功能。目前内置的 StoreBalancer 包括:
-
-- **RangeBootstrapBalancer**:初始化集群(与配置文件中的 ***bootstrap*** 设置效果相同)。
-- **RedundantEpochRemovalBalancer**:清理冗余的 Range。
-- **RangeLeaderBalancer**:在集群中均衡分布分片的 Leader。
-- **ReplicaCntBalancer**:根据配置的设置,在集群中均衡分片的副本数量(包括 Voter 和 Learner)。
-- **RangeSplitBalancer**:根据预定义的负载策略分片。
-- **UnreachableReplicaRemovalBalancer**:清理不可达的分片副本。
-- ~~**RecoveryBalancer**:自版本 3.3.0 起已废弃,不再使用。~~
-
-内置的 Balancer 适用于大多数使用场景。然而,对于更复杂的操作场景和 SLA 要求,用户可以根据需要定制 StoreBalancer,前提是对 base-kv 架构有深入了解。BifroMQ 团队还提供该领域的专业咨询服务。
-
-## 性能影响
-
-默认情况下,启用多个副本会产生以下性能影响:
-
-- **DistWorker**:默认优化为读性能,最多 3 个 Voter 副本;其余副本为 Learner。随着节点数量的增加,订阅路由性能可以水平扩展。
-- **InboxStore**:配置为通过分片平衡读写性能。由于写性能受到 Voter 副本数量的显著影响,默认配置使用单个副本。用户可以根据需要调整此设置以增强可用性。
-- **RetainStore**:默认优化为读性能,最多 3 个 Voter 副本;其余副本为 Learner。随着节点数量的增加,Retained消息匹配性能可以水平扩展。
\ No newline at end of file
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/04_cluster/3_upgrade.md b/i18n/zh-Hans/docusaurus-plugin-content-docs/current/04_cluster/3_upgrade.md
deleted file mode 100644
index 53da8e2a..00000000
--- a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/04_cluster/3_upgrade.md
+++ /dev/null
@@ -1,86 +0,0 @@
----
-sidebar_position: 3
-title: "升级指南"
----
-
-# 升级指南
-
-BifroMQ 支持多种升级策略,以确保版本之间的平滑过渡。本文件提供了 BifroMQ 升级的详细指南,包括版本兼容性、升级方法以及每种方法的具体步骤。
-
-## 版本兼容性
-
-BifroMQ 的版本兼容性分为两个主要方面:**数据兼容性** 和 **集群间 RPC 协议兼容性**。版本号采用语义化版本控制惯例:
-
-- **x.y.z**:
-    - **x**:主版本号。
-    - **y**:次版本号。
-    - **z**:修订版本号。
-
-### 兼容性规则
-
-1. **修订版本升级 (x.y.z)**:
-    - 当仅修订版本号 (z) 变化时,**数据兼容性和集群间 RPC 协议兼容性** 均得到保证。
-
-2. **次版本升级 (x.y)**:
-    - 当次版本号 (y) 变化时,**集群间 RPC 协议兼容性** 得到保证。
-    - **数据兼容性** 可能会发生变化,但任何此类变化将会明确说明。
-
-3. **主版本升级 (x)**:
-    - 主版本升级可能引入影响数据兼容性和集群间 RPC 协议兼容性的 **重大变化**。
-    - **集群内滚动升级不支持** 主版本升级,除非在发行说明中明确说明同时满足数据兼容性和集群间 RPC 协议兼容性。用户需要自行管理从旧版本集群到新版本集群的应用程序和数据迁移。
-
-## 升级方法
-
-BifroMQ 支持两种滚动升级方法:
-
-1. **原地升级**
-2. **替换升级**
-
-### 原地升级
-
-当新版本与现有版本保持数据兼容性和集群间 RPC 协议兼容性时,适合采用此方法。
-
-#### 原地升级步骤
-
-1. **停止当前版本**:
-    - 正常关闭 BifroMQ 服务。
-
-2. **保留数据目录**:
-    - 确保保留 `data` 目录。
-
-3. **更新文件和配置**:
-    - 替换必要的二进制文件并根据新版本的要求更新配置文件。
-
-4. **启动新版本**:
-    - 使用现有数据启动新版本的 BifroMQ。
-
-### 替换升级
-
-当新版本不保持数据兼容性或仅确保集群间 RPC 协议兼容性时,使用此方法。
-
-#### 替换升级步骤
-
-1. **添加新版本节点**:
-    - 逐步将运行新版本的节点引入集群。
-
-2. **移除旧版本节点**:
-    - 依次从集群中移除运行旧版本的节点,直到所有节点都升级到新版本。
-
-3. **自动数据迁移**:
-    - 在升级过程中,BifroMQ 会自动处理节点间的数据迁移和同步。
-
-#### 替换升级的重要注意事项
-
-- **Voter 配置**:
-    - 确保 `dist-worker`、`inbox-store` 和 `retain-store` 的以下 BifroSysProp 属性配置了多于一个的 Voter,否则不会发生数据迁移:
-        - `dist_worker_range_voter_count`
-        - `inbox_store_range_voter_count`
-        - `retain_store_range_voter_count`
-
-- **节点升级限制**:
-    - 不要同时升级超过半数的节点,以免导致集群不可用。
-
-## 总结
-
-- **原地升级**:适用于同一主版本和次版本 (x.y) 内的升级,其中数据和 RPC 协议兼容性得到保证。
-- **替换升级**:适用于跨次版本升级或数据兼容性可能无法保持的情况。请按照逐步过程确保平稳过渡。
\ No newline at end of file
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/04_cluster/_category_.json b/i18n/zh-Hans/docusaurus-plugin-content-docs/current/04_cluster/_category_.json
deleted file mode 100644
index 887daaa6..00000000
--- a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/04_cluster/_category_.json
+++ /dev/null
@@ -1,8 +0,0 @@
-{
-  "label": "BifroMQ Cluster",
-  "position": 4,
-  "link": {
-    "type": "doc",
-    "id": "cluster/intro"
-  }
-}
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/04_cluster/images/IndependentWorkload.png b/i18n/zh-Hans/docusaurus-plugin-content-docs/current/04_cluster/images/IndependentWorkload.png
deleted file mode 100644
index f07d6b15..00000000
Binary files a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/04_cluster/images/IndependentWorkload.png and /dev/null differ
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/04_cluster/intro.md b/i18n/zh-Hans/docusaurus-plugin-content-docs/current/04_cluster/intro.md
deleted file mode 100644
index 298fd609..00000000
--- a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/04_cluster/intro.md
+++ /dev/null
@@ -1,34 +0,0 @@
----
-id: intro
-sidebar_position: 0
-title: "BifroMQ 集群概述"
----
-
-BifroMQ 采用去中心化的集群方式,其中 MQTT 协议的工作负载分布在独立的子集群中,每个子集群负责特定的功能。这种设计建立在两层集群结构之上:底层集群 (Underlay Cluster) 和上层集群 (Overlay Cluster),以提高可扩展性和容错性。
-
-## 底层集群
-
-底层集群是 BifroMQ 集群系统的主干。该层通过消除单点故障并保持准确及时的集群拓扑一致性来确保高可用性。
-
-#### 主要功能:
-
-- **去中心化构建**: 无需依赖传统注册中心即可进行集群形成,从而降低运营风险。
-- **故障检测和自动剔除**: 通过主动故障检测和快速成员信息同步来增强集群可靠性。
-- **脑裂恢复**: 包含从网络分区中恢复的机制,以维护集群完整性和一致性。
-
-## 上层集群
-
-上层集群(也称为代理集群)建立在底层集群之上,专注于特定的功能服务,利用底层集群进行成员管理和节点间通信。简化了部署和运维流程,可以自动形成集群来支持无状态 RPC 服务和构建于分布式 KV 存储引擎上的状态服务。
-
-## 部署模型
-BifroMQ 引入了两种不同的部署模型来满足各种运维需求和工作负载场景:
-
-### Standard Cluster
-
-[StandardCluster](../04_cluster/1_standardcluster.md) 将所有功能模块集成在一个进程中,类似于“共享式”架构,简化了配置和部署。虽然这种模型简化了扩展,但它对不同模块之间资源分配的 “微调” 能力有限。
-
-### IndependentWorkload Cluster
-
-IndependentWorkloadCluster 模型允许将每个模块作为一个独立的进程进行部署。这提供了更大的灵活性、精确的资源管理以及更动态地适应业务需求的能力,从而促进从标准集群到更细粒度的部署方法的平滑过渡。
-![IndependentWorkloadCluster](images/IndependentWorkload.png)
-注意: 有关 IndependentWorkloadCluster 的信息将在以后的版本中提供。
\ No newline at end of file
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/05_user_guide/1_basic/1_connect.md b/i18n/zh-Hans/docusaurus-plugin-content-docs/current/05_user_guide/1_basic/1_connect.md
deleted file mode 100644
index dfe663e6..00000000
--- a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/05_user_guide/1_basic/1_connect.md
+++ /dev/null
@@ -1,20 +0,0 @@
----
-sidebar_position: 1
-title: "连接至BifroMQ"
----
-
-BifroMQ是一款标准的MQTT消息中间件,支持使用任何兼容MQTT 3.1、3.1.1或5.0版本的客户端进行连接。
-
-## 连接地址
-使用已启动服务的IP地址或域名。下面是默认端口及其用途:
-
-| 端口                     | 说明           |
-|-------------------------|----------------|
-| IP或域名:1883           | TCP连接        |
-| IP或域名:1884           | TLS连接        |
-| IP或域名:80/mqtt        | WS连接(WebSocket)|
-| IP或域名:443/mqtt       | WSS连接(安全WebSocket)|
-
-## 认证
-
-默认情况下,不启用认证。您可以在不提供用户名和密码的情况下连接。如果您需要认证,请参考[Auth Provider Plugin](../../06_plugin/1_auth_provider.md)。
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/05_user_guide/1_basic/2_pubsub.md b/i18n/zh-Hans/docusaurus-plugin-content-docs/current/05_user_guide/1_basic/2_pubsub.md
deleted file mode 100644
index 8d7da5c8..00000000
--- a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/05_user_guide/1_basic/2_pubsub.md
+++ /dev/null
@@ -1,39 +0,0 @@
----
-sidebar_position: 2
-title: "发布/订阅"
----
-
-根据MQTT协议,参与发送和接收消息的实体可以分为发布者(Publishers)和订阅者(Subscribers)。基本模型如下所示:
-
-![pub-sub pattern](images/pub-sub-pattern.png)
-
-* **发布消息**:客户端可以通过连接向服务器发布消息。消息基于`主题(topics)`发布,这些主题描述了通信内容,并且是层次化的(例如,`home/bedroom/temperature`)。
-
-  发布消息时,客户端需要指定一个主题,消息Payload包含通信的实际内容。此外,发布者必须为消息指定服务质量(QoS)。BifroMQ支持所有MQTT QoS等级:QoS0、QoS1和QoS2。它们的含义如下:
-
-  | QoS  | 描述                |
-      |------|---------------------|
-  | QoS0 | 至多一次传输         |
-  | QoS1 | 至少一次传输         |
-  | QoS2 | 确切一次传输         |
-
-* **订阅主题**:在订阅中,被订阅的主题称为`主题过滤器(topic filter)`。服务器接收来自客户端的订阅请求并记录这些订阅。通常,订阅可以是非通配符订阅或通配符订阅。
-
-    * 对于**非通配符订阅**:客户端订阅特定主题,不使用通配符。例如,如果客户端订阅`home/bedroom/temperature`,它将只匹配主题为`home/bedroom/temperature`的消息。
-
-    * 对于**通配符订阅**:订阅主题包括通配符字符(`+`或`#`)。`+`通配符匹配主题层次结构中的单一层级,而`#`通配符匹配多个层级。以下是使用通配符进行订阅的示例:
-
-      使用`+`通配符:
-
-        * 订阅`sensor/+/temperature`可以匹配诸如`sensor/bedroom/temperature`、`sensor/kitchen/temperature`等主题。
-        * 订阅`home/+/light/+`可以匹配诸如`home/livingroom/light/on`、`home/bedroom/light/off`等主题。
-
-      使用`#`通配符:
-
-        * 订阅`home/bedroom/#`可以匹配诸如`home/bedroom/light/on`、`home/bedroom/temperature`及其子主题的主题。
-        * 订阅`home/+/#`可以匹配诸如`home/bedroom/light/on`、`home/kitchen/temperature`及其子主题的主题。
-        * 订阅`#`可以匹配所有主题。
-
-      请注意,通配符订阅可能会导致订阅大量主题,因此在使用通配符订阅时应仔细考虑性能和资源消耗。
-
-      与发布消息类似,订阅主题时,客户端需要为该主题指定QoS。BifroMQ根据MQTT协议,在转发消息时会取已发布消息的QoS和订阅主题的QoS的最小值,即`Min(PublishQoS, SubscribeQoS)`。这意味着,即使订阅者以QoS2订阅了一个主题,它可能仍然会接收到QoS0的消息。
\ No newline at end of file
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/05_user_guide/1_basic/3_shared_sub.md b/i18n/zh-Hans/docusaurus-plugin-content-docs/current/05_user_guide/1_basic/3_shared_sub.md
deleted file mode 100644
index cc9a12cf..00000000
--- a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/05_user_guide/1_basic/3_shared_sub.md
+++ /dev/null
@@ -1,21 +0,0 @@
----
-sidebar_position: 3
-title: "共享订阅"
----
-
-MQTT共享订阅是MQTT 5.0版本协议中的一个特性,它允许多个订阅者公平地从同一主题接收消息,BifroMQ支持MQTT 3.1和3.1.1版本下使用共享订阅。
-
-![shared-subscription](images/shared-subscription.png)
-
-要开始共享订阅,需要使用`$share/{groupName}/{topicFilter}`格式的订阅主题。`{groupName}`指的是共享订阅的组名,如图中的`group1`所示。
-当不同的订阅者选择使用相同的topicFilter和groupName订阅时,他们加入同一个共享组。每当发布者发送消息时,BifroMQ会将这条消息转发给组内的一个订阅者。
-
-### 共享策略
-
-共享策略指向共享组内的成员转发消息时如何确定哪一个成员负责接收该消息,MQTT协议在这方面没有明确规定,结合共享订阅的使用场景,BifroMQ提供两种策略实现:
-
-1. **随机选择(`$share/{groupName}/topicFilter`)**:使用`$share`作为共享订阅的前缀,适用于消息处理逻辑无顺序性要求的应用。
-
-2. **有序绑定(`$oshare/{groupName}/topicFilter`)**:使用`$oshare`作为共享订阅的前缀,这种模式将来自同一客户端连接和同一主题的消息按发布顺序转发给同一个订阅者,适用于消息有顺序性要求的应用。
-
-**注意**:共享策略与共享组名的组合是唯一的,即使用`$share`和`$oshare`创建相同组名的共享订阅,实际上会创建组名相同但共享策略不同的两个共享订阅组。
\ No newline at end of file
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/05_user_guide/1_basic/_category_.json b/i18n/zh-Hans/docusaurus-plugin-content-docs/current/05_user_guide/1_basic/_category_.json
deleted file mode 100644
index c91e8a93..00000000
--- a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/05_user_guide/1_basic/_category_.json
+++ /dev/null
@@ -1,8 +0,0 @@
-{
-  "label": "Basic MQTT Features",
-  "position": 1,
-  "link": {
-    "type": "doc",
-    "id": "user_guide/basic/intro"
-  }
-}
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/05_user_guide/1_basic/images/pub-sub-pattern.png b/i18n/zh-Hans/docusaurus-plugin-content-docs/current/05_user_guide/1_basic/images/pub-sub-pattern.png
deleted file mode 100644
index bc6925c1..00000000
Binary files a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/05_user_guide/1_basic/images/pub-sub-pattern.png and /dev/null differ
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/05_user_guide/1_basic/images/shared-subscription.png b/i18n/zh-Hans/docusaurus-plugin-content-docs/current/05_user_guide/1_basic/images/shared-subscription.png
deleted file mode 100644
index 3a9e9770..00000000
Binary files a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/05_user_guide/1_basic/images/shared-subscription.png and /dev/null differ
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/05_user_guide/1_basic/intro.md b/i18n/zh-Hans/docusaurus-plugin-content-docs/current/05_user_guide/1_basic/intro.md
deleted file mode 100644
index 89057f20..00000000
--- a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/05_user_guide/1_basic/intro.md
+++ /dev/null
@@ -1,17 +0,0 @@
----
-id: intro
-sidebar_position: 0
-title: "MQTT基础特性概览"
----
-
-BifroMQ针对IoT应用和服务提供了全面的MQTT协议支持,体现在以下几方面:兼容不同版本的协议、提供针对租户的个性化配置、具备动态调整能力、支持跨版本的消息互通,以及在特定协议版本中实现共享订阅的功能。
-
-1. **全面协议支持**:BifroMQ兼容MQTT 3.1、3.1.1及5.0版本,支持所有使用这些版本协议的第三方客户端。这使得用户能够无缝集成BifroMQ至现有系统中,为开发者和管理员带来便捷的使用体验。
-
-2. **租户级配置自定义**:BifroMQ支持根据每个租户的具体需求和应用场景,定制协议相关的[参数设置](../../06_plugin/4_setting_provider/1_tenantsetting.md)。
-
-3. **运行时参数可调**:BifroMQ通过[Setting Provider Plugin](../../06_plugin/4_setting_provider/intro.md)支持协议参数设置的动态调整,适应快速变化的业务需求,提高灵活性和适应性。
-
-4. **协议版本间互通**:BifroMQ支持同一租户内使用不同MQTT协议版本建立的会话之间的消息交换,确保不同版本协议的设备和客户端能够无缝通信。
-
-5. **共享订阅功能**:BifroMQ为MQTT3.1和3.1.1版本提供[共享订阅](3_shared_sub.md)功能,使跨版本的客户端能够订阅同一主题,并在它们之间平衡消息负荷,从而提升消息处理的效率和可靠性。
\ No newline at end of file
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/05_user_guide/2_integration/1_integration.md b/i18n/zh-Hans/docusaurus-plugin-content-docs/current/05_user_guide/2_integration/1_integration.md
deleted file mode 100644
index 343cbe3b..00000000
--- a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/05_user_guide/2_integration/1_integration.md
+++ /dev/null
@@ -1,26 +0,0 @@
----
-sidebar_position: 1
-title: Integration SDK
----
-[Integration SDK](https://github.com/bifromqio/bifromq-data-integration),可以作为构建定制化数据集成解决方案的参考起点。由于服务间集中转发的消息吞吐量可能很大,超出单个MQTT连接的带宽限制。SDK提供的Integrator对象通过共享订阅(`$share/{groupName}/topicFilter`)从BifroMQ接收数据,并将数据传递给下游服务,如Kafka或MySQL。
-因此,业务方可以根据业务压力调整MQTT客户端连接的数量,实现`IProducer`接口来实现向具体的下游系统转发消息的逻辑。
-
-```java
-IIntegrator integrator = Integrator.builder()
-        .clientNum(5)
-        .groupName("g1")
-        .topicFilter("test/data/integration")
-        .cleanSession(true)
-        .userName("dev")
-        .password("dev")
-        .port(1883)
-        .host("BifroMQ host")
-        .build();
-integrator.onMessageArrive()
-          .doOnComplete(IProducer.DUMMY::close)
-          .subscribe(IProducer.DUMMY::produce);
-```
-
-## 注意事项
-* 共享组成员数的限制。BifroMQ中共享组成员数默认限制`200`个,超出数量的订阅将失败。这个限制是租户级的[配置项](../../06_plugin/4_setting_provider/intro.md)。
-* 路由缓存限制。为了提升路由效率,BifroMQ会缓存消息主题(topic)的路由结果,大量消息主题会导致缓存被提前驱逐,命中率下降,通过调整相应的[系统参数](../../07_admin_guide/01_configuration/2_bifromq_sys_props.md)可以提升缓存命中率。
\ No newline at end of file
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/05_user_guide/2_integration/_category_.json b/i18n/zh-Hans/docusaurus-plugin-content-docs/current/05_user_guide/2_integration/_category_.json
deleted file mode 100644
index 3471a8ef..00000000
--- a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/05_user_guide/2_integration/_category_.json
+++ /dev/null
@@ -1,8 +0,0 @@
-{
-  "label": "数据集成",
-  "position": 2,
-  "link": {
-    "type": "doc",
-    "id": "user_guide/integration/intro"
-  }
-}
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/05_user_guide/2_integration/images/bifromqapproach.jpg b/i18n/zh-Hans/docusaurus-plugin-content-docs/current/05_user_guide/2_integration/images/bifromqapproach.jpg
deleted file mode 100644
index 093d04cb..00000000
Binary files a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/05_user_guide/2_integration/images/bifromqapproach.jpg and /dev/null differ
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/05_user_guide/2_integration/images/commonapproach.jpg b/i18n/zh-Hans/docusaurus-plugin-content-docs/current/05_user_guide/2_integration/images/commonapproach.jpg
deleted file mode 100644
index e6100b4d..00000000
Binary files a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/05_user_guide/2_integration/images/commonapproach.jpg and /dev/null differ
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/05_user_guide/2_integration/images/integration.png b/i18n/zh-Hans/docusaurus-plugin-content-docs/current/05_user_guide/2_integration/images/integration.png
deleted file mode 100644
index b05d28b9..00000000
Binary files a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/05_user_guide/2_integration/images/integration.png and /dev/null differ
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/05_user_guide/2_integration/intro.md b/i18n/zh-Hans/docusaurus-plugin-content-docs/current/05_user_guide/2_integration/intro.md
deleted file mode 100644
index 7028a576..00000000
--- a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/05_user_guide/2_integration/intro.md
+++ /dev/null
@@ -1,56 +0,0 @@
----
-id: "intro"
-sidebar_position: 0
-title: "数据集成概览"
----
-
-BifroMQ更专注被深度集成的能力,为各类消息通讯类系统提供MQTT的基础能力,本章主要介绍BifroMQ建议的数据集成方法。
-
-## 理解与BifroMQ的数据集成
-
-与BifroMQ的数据集成涉及消息在BifroMQ和外部系统之间的双向流动,包括数据库、基于规则的消息转发系统、其他消息中间件或另一个MQTT Broker。这种集成包括几个关键方面:
-
-- **协议转换**
-- **服务质量匹配**
-- **消息路由**
-- **流量控制**
-- **监控**
-- **可扩展性考虑**
-
-### 常用模式
-
-常见的架构模式是在MQTT Broker中内置下游系统客户端。这种方法使用特定的通信机制和映射逻辑来实现协议转换,将MQTT协议实现和与异构系统的集成视为一个统一整体,提供开箱即用的集成功能。
-
-![常用方法](./images/commonapproach.jpg)
-
-### 非耦合模式
-
-与常见做法相反,BifroMQ建议数据集成采用非耦合的方法:集成逻辑直接利用MQTT协议作为客户端从BifroMQ中订阅消息,这种架构模式使得集成模块可以在不同MQTT Broker之间复用,因此BifroMQ项目本身并不内置开箱即用的数据集成功能。
-
-![bifromq方法](./images/bifromqapproach.jpg)
-
-## 消息流集成方向
-
-集成逻辑与BifroMQ之间有两个消息流动的方向:
-
-### 1. 从BifroMQ到外部系统
-
-BifroMQ推荐使用[共享订阅](../1_basic/3_shared_sub.md)功能,以平衡发送到下游系统的消息负载,利用MQTT的QoS能力进行语义消息转发。为此,BifroMQ在MQTT 3.1、3.1.1版本下同样支持共享订阅。
-
-### 2. 从外部系统到BifroMQ
-
-外部系统可以使用MQTT客户端或[HTTP Restful API](../../05_user_guide/3_api/intro.md)向BifroMQ发布消息。
-
-## 实现方面的注意事项
-
-在与BifroMQ集成数据时,请考虑以下几点:
-
-1. **带宽限制**:BifroMQ默认每个MQTT连接的带宽限制为512kb/s,可以通过租户[设置](../../06_plugin/4_setting_provider/1_tenantsetting.md)调整。
-
-2. **流量控制**:使用MQTT作为转发协议天然提供了流量控制。下游系统必须具有足够的资源接收转发的消息,以避免因背压导致的消息丢失。
-
-3. **监控**:得益于MQTT协议的使用,BifroMQ提供的监控指标可以在消息转发阶段直接复用,简化了集成监控过程。
-
-## 入门参考
-
-此[项目](https://github.com/bifromqio/bifromq-data-integration)展示了本指南中讨论的概念,可以作为类似项目的参考。
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/05_user_guide/3_api/1_api_reference.md b/i18n/zh-Hans/docusaurus-plugin-content-docs/current/05_user_guide/3_api/1_api_reference.md
deleted file mode 100644
index bf0fdf86..00000000
--- a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/05_user_guide/3_api/1_api_reference.md
+++ /dev/null
@@ -1,127 +0,0 @@
----
-sidebar_position: 1 
-title: API Reference
----
-
-## API Endpoints
-
-### 1. Publish a message to given topic
-
-- **URL**: `/pub`
-- **Method**: `POST`
-- **Headers**:
-    - `req_id` (optional): Optional caller-provided request ID. Integer (int64).
-    - `tenant_id` (required): The tenant ID. String.
-    - `topic` (required): The message topic. String.
-    - `qos` (required): QoS of the message to be retained. String.
-    - `expiry_seconds` (optional): The message expiry seconds. String.
-    - `client_type` (required): The publisher type. String.
-    - `client_meta_*`: The metadata header about the publisher, must start with `client_meta_`. String.
-- **Request Body**: Message payload will be treated as binary.
-- **Responses**:
-    - `200`: Success.
-
-### 2. Retain a message to given topic/Clear retained message for given topic
-
-- **URL**: `/retain`
-- **Method**: `POST`
-- **Headers**:
-    - `req_id` (optional): Optional caller-provided request ID. Integer (int64).
-    - `tenant_id` (required): The tenant ID. String.
-    - `topic` (required): The message topic. String.
-    - `qos` (required): QoS of the message to be retained. String.
-    - `expiry_seconds` (optional): The message expiry seconds. String.
-    - `client_type` (required): The publisher type. String.
-    - `client_meta_*`: The metadata header about the publisher, must start with `client_meta_`. String.
-- **Request Body**: Message payload will be treated as binary or zero-bytes for clearing retained message.
-- **Responses**:
-    - `200`: Success.
-
-### 3. Get session information of given user and client id
-
-- **URL**: `/session`
-- **Method**: `GET`
-- **Headers**:
-    - `req_id` (optional): Optional caller-provided request ID. Integer (int64).
-    - `tenant_id` (required): The ID of the tenant. String.
-    - `user_id` (required): The ID of the user who established the session. String.
-    - `client_id` (required): The client ID of the MQTT session. String.
-- **Responses**:
-    - `200`: Success.
-    - `404`: No session found for the given user and client ID.
-
-### 4. Expire inactive persistent session using given expiry time
-
-- **URL**: `/session`
-- **Method**: `DELETE`
-- **Headers**:
-    - `req_id` (optional): Optional caller-provided request ID. Integer (int64).
-    - `tenant_id` (required): The ID of the tenant. String.
-    - `expiry_seconds` (optional): The overridden session expiry seconds. String.
-- **Responses**:
-    - `200`: Success.
-#### Note
-Setting expiry_seconds to 0 will clean all inboxes under the specified tenant, including those still
-online. Connections will be disconnected due to the loss of metadata. It is crucial to set this parameter appropriately.
-
-
-### 5. Disconnect a MQTT client connection
-
-This API endpoint facilitates the disconnection of MQTT client connections based on various identifiers, such as tenant, user, or specific client.
-
-- **URL**: `/kill`
-- **Method**: `DELETE`
-- **Headers**:
-  - `req_id` (optional): Optional caller-provided request ID. Integer (int64).
-  - `tenant_id` (required): The ID of the tenant. String. This is mandatory for identifying the scope of connections to disconnect.
-  - `user_id` (optional): The ID of the user who established the session. String. If provided alongside tenant_id, all connections associated with this user_id within the tenant will be disconnected.
-  - `client_id` (optional): The client ID of the MQTT session. String. If provided alongside tenant_id and user_id, the specific connection identified by client_id will be disconnected.
-  - `client_type` (required): The kicker type. String.
-  - `client_meta_*`: The metadata header about the kicker, must start with `client_meta_`. String.
-- **Responses**:
-  - `200`: Success.
-  - `404`: Not Found.
-#### Note
-1. Disconnect a Specific Client Connection:
-  - Identifiers Required: tenant_id, user_id, and client_id.
-  - Behavior: Disconnects the specific connection uniquely identified by the combination of tenant_id, user_id, and client_id.
-2. Disconnect All Connections for a User:
-  - Identifiers Required: tenant_id and user_id.
-  - Behavior: Disconnects all connections created by the specified user_id under the provided tenant_id. This includes all connections associated with different client_ids for the given user.
-3. Disconnect All Connections for a Tenant:
-  - Identifier Required: tenant_id.
-  - Behavior: Disconnects all connections under the specified tenant_id, regardless of user_id or client_id.
-
-### 6. Add a Topic Subscription to an MQTT session
-
-- **URL**: `/sub`
-- **Method**: `PUT`
-- **Headers**:
-    - `req_id` (optional): Optional caller-provided request ID. Integer (int64).
-    - `tenant_id` (required): The tenant ID. String.
-    - `user_id` (required): The ID of the user who established the session. String.
-    - `client_id` (required): The client ID of the MQTT session. String.
-    - `topic_filter` (required): The topic filter. String.
-    - `sub_qos` (required): the subscription qos level. 0|1|2.
-
-- **Responses**:
-    - `200`: Success.
-    - `400`: Request is invalid.
-    - `401`: Unauthorized to make the subscription using the given topic filter.
-    - `404`: No session found for the given user and client ID.
-
-### 8. Remove a Topic Subscription from an MQTT session
-
-- **URL**: `/unsub`
-- **Method**: `DELETE`
-- **Headers**:
-    - `req_id` (optional): Optional caller-provided request ID. Integer (int64).
-    - `tenant_id` (required): The tenant ID. String.
-    - `user_id` (required): The ID of the user who established the session. String.
-    - `client_id` (required): The client ID of the MQTT session. String.
-    - `topic_filter` (required): The topic filter. String.
-
-- **Responses**:
-    - `200`: Success.
-    - `401`: Unauthorized to remove the subscription of the given topic filter.
-    - `404`: No session found for the given user and client ID.
\ No newline at end of file
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/05_user_guide/3_api/_category_.json b/i18n/zh-Hans/docusaurus-plugin-content-docs/current/05_user_guide/3_api/_category_.json
deleted file mode 100644
index 1a108d18..00000000
--- a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/05_user_guide/3_api/_category_.json
+++ /dev/null
@@ -1,8 +0,0 @@
-{
-  "label": "API Usage",
-  "position": 3,
-  "link": {
-    "type": "doc",
-    "id": "user_guide/api/intro"
-  }
-}
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/05_user_guide/3_api/images/API-Arch.png b/i18n/zh-Hans/docusaurus-plugin-content-docs/current/05_user_guide/3_api/images/API-Arch.png
deleted file mode 100644
index f96fee04..00000000
Binary files a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/05_user_guide/3_api/images/API-Arch.png and /dev/null differ
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/05_user_guide/3_api/intro.md b/i18n/zh-Hans/docusaurus-plugin-content-docs/current/05_user_guide/3_api/intro.md
deleted file mode 100644
index df2e251c..00000000
--- a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/05_user_guide/3_api/intro.md
+++ /dev/null
@@ -1,15 +0,0 @@
----
-id: intro
-sidebar_position: 0
-title: "API概述"
----
-
-BifroMQ内置了API能力,允许执行类似断开客户端连接、查询会话状态、发布消息和管理订阅的操作。利用这些功能,您可以将BifroMQ的管理操作集成到自定义管理工作流中。
-
-## 部署
-
-默认情况下,API服务能力在每个BifroMQ服务节点上自动启用,使用端口8091,参考[配置文件](../../07_admin_guide/01_configuration/1_config_file_manual.md),了解更多的设置选项。操作请求可以发送到任何节点,确保了默认部署中API能力的高可用性。
-
-![API-Arch.png](images%2FAPI-Arch.png)
-
-上图展示了一个常见的部署场景:利用前置负载均衡器,如:Nginx,分散API请求。
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/05_user_guide/_category_.json b/i18n/zh-Hans/docusaurus-plugin-content-docs/current/05_user_guide/_category_.json
deleted file mode 100644
index 38db2f8d..00000000
--- a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/05_user_guide/_category_.json
+++ /dev/null
@@ -1,8 +0,0 @@
-{
-  "label": "User Guide",
-  "position": 5,
-  "link": {
-    "type": "doc",
-    "id": "user_guide/intro"
-  }
-}
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/05_user_guide/intro.md b/i18n/zh-Hans/docusaurus-plugin-content-docs/current/05_user_guide/intro.md
deleted file mode 100644
index 23b1d1c1..00000000
--- a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/05_user_guide/intro.md
+++ /dev/null
@@ -1,19 +0,0 @@
----
-id: intro
-sidebar_position: 0
-title: "用户指南概述"
----
-
-BifroMQ是Java实现的MQTT Broker,提供高性能的分布式消息传递能力。凭借其对多租户的原生支持,BifroMQ适用于将MQTT功能整合到各种商业系统中,特别是那些面向大规模物联网设备通信和消息基础设施的系统。
-
-#### 关键特性和考虑因素:
-
-1. **支持多租户的灵活性集成**:BifroMQ旨在无缝集成到需要MQTT能力的各种商业系统中。BifroMQ对多租户的原生支持,这使得不同的租户(客户或客户组织)能够在同一个Broker集群实例中操作独立的环境。理解**租户**的概念和BifroMQ对多租户的处理方式在规划集成策略时至关重要。
-
-2. **租户识别和命名空间隔离**:在BifroMQ中,租户通过***tenantId***唯一识别,并被定义为“命名空间”。这种设计确保所有MQTT连接和会话都与特定的租户命名空间相关联。同一租户命名空间内的MQTT连接可以相互发布和订阅消息,而不同租户命名空间的连接保持隔离,增强了安全性和数据隐私。
-
-3. **由集成方管理租户生命周期**:与一些内置租户生命周期管理能力的系统不同,BifroMQ将租户的定义和管理委托给业务集成方。通过[Auth Provider Plugin](../06_plugin/1_auth_provider.md)实现,业务集成方在认证过程中为每个连接指定***tenantId***。这种模式可以认为是对传统单租户架构的一般化。
-
-4. **每个租户的资源和负载隔离**:除了逻辑隔离MQTT会话和消息发布/订阅外,BifroMQ使用租户空间作为资源和负载隔离的边界。这一能力通过[Tenant Metrics](../07_admin_guide/03_observability/metrics/tenantmetrics.md)和[Resource Throttler Plugin](../06_plugin/3_resource_throttler.md)实现,确保了资源的有效利用和系统的稳定性。
-
-5. **优化的租户能力与资源开销**:BifroMQ专为多租户而设计,然而多租户能力会带来一定资源开销,虽然在绝大多数多租户业务场景下无需考虑这些开销带来的影响。然而,需要注意的是,通过水平扩展BifroMQ集群规模无法实现集群内同时服务的租户数量的无限增长。因此在设计多租户业务时,应避免将BifroMQ的租户映射至过于细微的实体级别,如“每个连接对应一个租户”。
\ No newline at end of file
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/06_plugin/1_auth_provider.md b/i18n/zh-Hans/docusaurus-plugin-content-docs/current/06_plugin/1_auth_provider.md
deleted file mode 100644
index e9e7740d..00000000
--- a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/06_plugin/1_auth_provider.md
+++ /dev/null
@@ -1,386 +0,0 @@
----
-sidebar_position: 2
-title: "Auth Provider"
----
-
-Auth Provider插件为BifroMQ添加了MQTT客户端和Pub/Sub操作的认证与授权功能。
-插件接口定义在以下Maven模块中:
-
-```
-<dependency>
-    <groupId>com.baidu.bifromq</groupId>
-    <artifactId>bifromq-plugin-auth-provider</artifactId>
-    <version>X.Y.Z</version> <!--replace X.Y.Z with the latest version number-->
-</dependency>
-```
-
-BifroMQ一次只允许运行一个Auth Provider实例。需要通过[配置文件](../07_admin_guide/01_configuration/1_config_file_manual.md)指定实现类的完全限定名(FQN):
-
-```yaml
-authProviderFQN: "YOUR_AUTH_PROVIDER_CLASS"
-```
-
-## 认证
-
-在连接阶段,BifroMQ会回调Auth Provider Plugin的接口方法对3.1、3.1.1和5.0版本的MQTT客户端连接进行认证:
-
-```java
-// Authenticate MQTT 3.1 and 3.1.1 clients
-CompletableFuture<MQTT3AuthResult> auth(MQTT3AuthData authData);
-
-// Authenticate MQTT 5.0 clients
-CompletableFuture<MQTT5AuthResult> auth(MQTT5AuthData authData);
-
-// Enhanced authentication for MQTT 5.0 clients
-CompletableFuture<MQTT5ExtendedAuthResult> extendedAuth(MQTT5ExtendedAuthData authData); 
-```
-
-务必确保接口方法实现的高效和非阻塞,避免对连接性能造成负面影响。针对MQTT 5.0,BifroMQ支持两种认证方法:Basic和Extended。Basic认证提供兼容MQTT3的默认行为。
-
-接口方法的参数和返回类型使用Protobuf对象。
-
-#### [MQTT3AuthData](https://github.com/bifromqio/bifromq/blob/main/bifromq-plugin/bifromq-plugin-auth-provider/src/main/proto/mqtt3_auth_types.proto)
-
-```protobuf
-message MQTT3AuthData{
-  bool isMQIsdp = 1; // true indicates the client is using MQTT 3.1
-  optional string username = 2; // username specified by the client in Connect
-  optional bytes password = 3; // password specified by the client in Connect
-  optional bytes cert = 4; // TLS certificate used by the client in Base64 encoding
-  optional string clientId = 5; // client identifier specified by the client in Connect
-  string remoteAddr = 6; // source address of the client
-  uint32 remotePort = 7; // port of the client
-  string channelId = 8; // globally unique identifier for this connection
-}
-```
-
-#### [MQTT3AuthResult](https://github.com/bifromqio/bifromq/blob/main/bifromq-plugin/bifromq-plugin-auth-provider/src/main/proto/mqtt3_auth_types.proto)
-
-```protobuf
-message Ok{
-  string tenantId = 1;
-  string userId = 2;
-  map<string, string> attrs = 3; // additional attributes filled by auth provider plugin which will be copied to ClientInfo
-}
-
-message Reject{
-  enum Code {
-    BadPass = 0;
-    NotAuthorized = 1;
-    Error = 2;
-  }
-  Code code = 1;
-  optional string tenantId = 2; // optional if tenant can be determined
-  optional string userId = 3; // optional if user can be determined
-  optional string reason = 4; // optional description}
-
-  message MQTT3AuthResult {
-    oneof Type{
-      Ok ok = 1;
-      Reject reject = 2;
-    }
-  }
-```
-
-#### [MQTT5AuthData](https://github.com/bifromqio/bifromq/blob/main/bifromq-plugin/bifromq-plugin-auth-provider/src/main/proto/mqtt5_auth_types.proto) and [MQTT5ExtendedAuthData](https://github.com/bifromqio/bifromq/blob/main/bifromq-plugin/bifromq-plugin-auth-provider/src/main/proto/mqtt5_auth_types.proto)
-
-```protobuf
-message MQTT5AuthData{
-  optional string username = 1;
-  optional bytes password = 2;
-  optional bytes cert = 3;
-  optional string clientId = 4;
-  string remoteAddr = 5;
-  uint32 remotePort = 6;
-  string channelId = 7;
-  bool responseInfo = 8; // for MQTT5 request/response use case
-  commontype.UserProperties userProps = 9;
-}
-
-message MQTT5ExtendedAuthData{
-  message Initial{
-    MQTT5AuthData basic = 1;
-    string authMethod = 2;
-    bytes authData = 3;
-  }
-  message Auth{
-    string authMethod = 1;
-    bytes authData = 2;
-    commontype.UserProperties userProps = 3;
-    bool isReAuth = 4;
-  }
-  oneof Type{
-    Initial initial = 1;
-    Auth auth = 2;
-  }
-}
-```
-
-#### [MQTT5AuthResult](https://github.com/bifromqio/bifromq/blob/main/bifromq-plugin/bifromq-plugin-auth-provider/src/main/proto/mqtt5_auth_types.proto) and [MQTT5ExtendedAuthResult](https://github.com/bifromqio/bifromq/blob/main/bifromq-plugin/bifromq-plugin-auth-provider/src/main/proto/mqtt5_auth_types.proto)
-
-```protobuf
-message Success{
-  string tenantId = 1;
-  string userId = 2;
-  map<string, string> attrs = 3; // additional attributes filled by auth provider plugin which will be copied to ClientInfo
-  optional string ResponseInfo = 4; // for mqtt5 request/response use case
-  commontype.UserProperties userProps = 5; // user properties return back via mqtt5 connack
-}
-
-message Failed{
-  enum Code {
-    BadPass = 0;
-    NotAuthorized = 1;
-    Banned = 2;
-    BadAuthMethod = 3;
-    Error = 4;
-  }
-  Code code = 1;
-  optional string tenantId = 2; // optional if tenant can be determined
-  optional string userId = 3; // optional if user can be determined
-  optional string reason = 4; // optional description
-  commontype.UserProperties userProps = 5; // user properties return back via mqtt5 connack
-}
-
-message Continue{
-  bytes authData = 1;
-  optional string tenantId = 2; // optional if tenant can be determined
-  optional string userId = 3; // optional if user can be determined
-  optional string reason = 4;
-  commontype.UserProperties userProps = 5;
-}
-
-message MQTT5AuthResult {
-  oneof Type{
-    Success success = 1;
-    Failed failed = 2;
-  }
-}
-
-message MQTT5ExtendedAuthResult {
-  oneof Type{
-    Success success = 1;
-    Continue continue = 2;
-    Failed failed = 3;
-  }
-}
-```
-
-认证成功需返回一个Ok结构,包含tenantId、userId和额外的元数据attrs,元数据(如果有的话)将被复制到ClientInfo中;返回Reject表示不通过,结合Code字段表示失败原因认证信息不正确(BadPass)、未授权访问(NotAuthorized)或内部错误(Error),详细信息在可选字段中说明。
-
-## 鉴权
-
-BifroMQ通过以下接口方法检查发布、订阅和取消订阅操作的权限:
-
-```java
-CompletableFuture<CheckResult> checkPermission(ClientInfo client, MQTTAction action);
-```
-
-确保`checkPermission`方法实现的高效和非阻塞,避免对消息性能产生负面影响。方法传入的ClientInfo对象包含认证返回的元数据,利用它可以实现类似JWT的认证和鉴权机制。此外,权限检查方法不按客户端使用的MQTT协议版本区分。但对于使用MQTT
-5.0连接的客户端,MQTTAction对象会包含Control Packets中的UserProperties。
-
-在MQTT 5.0客户端授权失败的情况下,返回结果中包含的UserProperties将被回传给客户端,包含在相应的MQTT Control Packets的UserProperties中,有助于问题诊断。
-
-`checkPermission`方法的参数和返回类型也由Protobuf定义。
-
-#### [ClientInfo](https://github.com/bifromqio/bifromq/blob/main/bifromq-common-type/src/main/proto/commontype/ClientInfo.proto)
-
-```protobuf
-message ClientInfo{
-  string tenantId = 1;
-  string type = 2; // the type of the calling client, e.g. "mqtt"  
-  map<string, string> metadata = 3; // the metadata of the client
-}
-```
-
-BifroMQ会在`ClientInfo`对象的metadata属性中包含以下预定义的元数据:
-
-| Key           | Description                                        | Possible Values                                      |
-|---------------|----------------------------------------------------|------------------------------------------------------|
-| `ver`         | MQTT protocol version                              | `"3"` (MQTT 3.1), `"4"` (MQTT 3.1.1), `"5"` (MQTT 5) |
-| `userId`      | User ID                                            | User-defined string                                  |
-| `clientId`    | Client ID                                          | User-defined string                                  |
-| `channelId`   | Channel ID                                         | System-generated unique identifier                   |
-| `address`     | Client address                                     | IP address or hostname of the client                 |
-| `broker`      | Broker the client is connected to                  | Broker server identifier                             |
-| `sessionType` | Type of session                                    | `"t"` (Transient), `"p"` (Persistent)                |
-| `respInfo`    | Response information for MQTT 5.0 request/response | User-defined string                                  |
-
-这些元数据字段不会被认证结果中传递的属性(attrs)覆盖。
-
-#### [MQTTAction](https://github.com/bifromqio/bifromq/blob/main/bifromq-plugin/bifromq-plugin-auth-provider/src/main/proto/mqtt_actions.proto)
-
-```protobuf
-message PubAction {
-  string topic = 1;
-  commontype.QoS qos = 2;
-  bool isRetained = 3;
-  commontype.UserProperties userProps = 4;
-}
-
-message SubAction {
-  string topicFilter = 1;
-  commontype.QoS qos = 2;
-  commontype.UserProperties userProps = 5;
-}
-
-message UnsubAction {
-  string topicFilter = 1;
-  commontype.UserProperties userProps = 2;
-}
-
-message MQTTAction {
-  oneof Type{
-    PubAction pub = 1;
-    SubAction sub = 2;
-    UnsubAction unsub = 3;
-  }
-}
-```
-
-#### [CheckResult](https://github.com/bifromqio/bifromq/blob/main/bifromq-plugin/bifromq-plugin-auth-provider/src/main/proto/mqtt_actions.proto)
-
-```protobuf
-message Granted{
-  commontype.UserProperties userProps = 1; // user properties return back via mqtt5 pubAck/pubRel
-}
-
-message Denied{
-  optional string reason = 1;
-  commontype.UserProperties userProps = 2; // user properties return back via mqtt5 pubAck/pubRel or disconnect in case QoS0
-}
-
-message Error{
-  optional string reason = 1;
-  commontype.UserProperties userProps = 2; // user properties return back via mqtt5 pubAck/pubRel or disconnect in case QoS0
-}
-
-message CheckResult {
-  oneof Type{
-    Granted granted = 1;
-    Denied denied = 2;
-    Error error = 3;
-  }
-}
-```
-
-## Metrics
-
-因为AuthProvider插件的两个方法在连接认证以及处理消息发布和订阅转发的过程中会被频繁调用,BifroMQ记录并输出以下指标,以帮助插件实现者观察插件接口方法的性能指标:
-| Metric Name | Meter Type | Tag(`method`)        | Description |
-|------------------------|------------|----------------------|-----------------------------------------|
-| `call.exec.timer`      | TIMER | AuthProvider/auth | Latency for `auth` call |
-| `call.exec.fail.count` | COUNTER | AuthProvider/auth | Fail counter for `auth` call |
-| `call.exec.timer`      | TIMER | AuthProvider/extAuth | Latency for `extendedAuth` call |
-| `call.exec.fail.count` | COUNTER | AuthProvider/extAuth | Fail counter for `extendedAuth` call |
-| `call.exec.timer`      | TIMER | AuthProvider/check | Latency for `checkPermission` call |
-| `call.exec.fail.count` | COUNTER | AuthProvider/check | Fail counter for `checkPermission` call |
-
-## DevOnly Mode
-
-当未指定AuthPlugin类型时,BifroMQ会默认加载[DevOnlyAuthProvider](https://github.com/bifromqio/bifromq/blob/main/bifromq-server/src/main/java/com/baidu/bifromq/server/service/authprovider/DevOnlyAuthProvider.java)
-。DevOnlyAuthProvider会绕过了客户端认证和权限检查,因此仅用于测试和开发的目的。
-
-## 实现范例
-
-BifroMQ包含了一个基于WebHook的AuthProvider的示范实现,可以通过在[配置文件](../07_admin_guide/01_configuration/1_config_file_manual.md)中指定`authProviderFQN`为`com.baidu.demo.plugin.DemoAuthProvider`启用。范例实现利用JVM启动参数(
-`-Dplugin.authprovider.url`)来指定一个webhook的回调URL。
-
-当BifroMQ调用`auth`方法时,插件会发起一个HTTP POST请求,在这个请求中,我们将其body设置为`MQTT3AuthData`的JSON格式。响应Body内包含的字符串被解析成对应的`MQTT3AuthResult`值类型作为返回值。
-
-以下是一个Node实现的简单的WebhookServer用于测试示例插件,webhook的url地址为:`http://<ADDR>:<PORT>/auth`,`http://<ADDR>:<PORT>/check`,`http://<ADDR>:<PORT>/register`分别用于用户身份认证、sub/pub权限许可认证、注册用户信息。
-
-```js
-const http = require('http');
-const url = require('url'); 
-
-const authMap = {};
-const server = http.createServer((req, res) => {
-  const parsedUrl = url.parse(req.url, true);
-  const pathname = parsedUrl.pathname;
-
-  res.setHeader('Content-Type', 'text/plain');
-
-  if (pathname === '/auth') {
-    let body = '';
-    req.on('data', (chunk) => {
-      body += chunk.toString();
-    });
-
-    req.on('end', () => {
-      let data = {}
-      try {
-        data = JSON.parse(body);
-      } catch (error) {
-        res.writeHead(400, { 'Content-Type': 'text/plain' });
-        res.end('Invalid JSON');
-      }
-      if (data.username && data.password) {
-        const user = authMap[data.username];
-        if (user && user.password === data.password) {
-          res.writeHead(200, { 'Content-Type': 'application/json' });
-          res.end(JSON.stringify({ "ok": { "tenantId": user.tenantId, "userId": data.username} }));
-        } else {
-          res.writeHead(403, { 'Content-Type': 'application/json' });
-          res.end(JSON.stringify({ "reject": "NotAuthorized" }));
-        }
-      } else {
-        res.writeHead(400, { 'Content-Type': 'text/plain' });
-        res.end('Missing username or password');
-      }
-    });
-  } else if (pathname === '/check') {
-    if (!req.method === 'POST') {
-      res.writeHead(404);
-    }
-    const tenantId = req.headers['tenant_id'];
-    const userId = req.headers['user_id'];
-    if (tenantId && userId) {
-      res.writeHead(200, { 'Content-Type': 'text/plain' });
-      if (userId in authMap) {
-        res.end("true");
-      } else {
-        res.end("false");
-      }
-    } else {
-      res.writeHead(400, { 'Content-Type': 'text/plain' });
-      res.end("Missing user_id or tenant_id");
-    }
-  } else if (pathname === '/register') {
-    const tenantId = req.headers['tenant_id'];
-    const userId = req.headers['user_id'];
-    const password = req.headers['password'];
-
-    if (tenantId && userId && password) {
-      if (!authMap[userId]) {
-        authMap[userId] = {
-          password: btoa(password),
-          tenantId: tenantId
-        };
-        res.writeHead(200, { 'Content-Type': 'text/plain' });
-        res.end("User registered successfully");
-      } else {
-        res.writeHead(400, { 'Content-Type': 'application/json' });
-        res.end("User already exists");
-      }
-    } else {
-      res.writeHead(400, { 'Content-Type': 'text/plain' });
-      res.end("Missing user_id, password or tenant_id");
-    }
-  } else {
-    res.writeHead(404);
-    res.end('Not Found');
-  }
-});
-
-const args = process.argv.slice(2);
-const hostname = args[0] || 'localhost';
-const port = args[1] || 3000;
-
-server.listen(port, hostname, () => {
-  console.log(`Server listening on port ${server.address().port}`);
-});
-
-```
-
-请注意,这个示例里我们只是简单的将注册的密码转换为Base64格式进行存储,在实际使用时请选择更为安全稳妥的处理方式。
\ No newline at end of file
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/06_plugin/2_event_collector.md b/i18n/zh-Hans/docusaurus-plugin-content-docs/current/06_plugin/2_event_collector.md
deleted file mode 100644
index d9d98d85..00000000
--- a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/06_plugin/2_event_collector.md
+++ /dev/null
@@ -1,42 +0,0 @@
----
-sidebar_position: 3
-title: "Event Collector"
----
-
-Event Collector插件用于收集BifroMQ执行过程中发生的各种事件。插件的接口在以下Maven模块中定义:
-
-```
-<dependency>
-    <groupId>com.baidu.bifromq</groupId>
-    <artifactId>bifromq-plugin-event-collector</artifactId>
-    <version>X.Y.Z</version> <!--replace X.Y.Z with the latest version number-->
-</dependency>
-```
-
-启动时,BifroMQ会扫描plugins目录并加载所有可用的EventCollector实现。建议每个EventCollector专注于单一的特定任务,利用EventType功能来过滤掉与它们的目的不相关的事件。
-
-## 事件类型
-
-BifroMQ运行时生成的事件对象类型都继承自[Event](https://github.com/bifromqio/bifromq/blob/main/bifromq-plugin/bifromq-plugin-event-collector/src/main/java/com/baidu/bifromq/plugin/eventcollector/Event.java)
-类。每个特定的事件类对应一个[EventType](https://github.com/bifromqio/bifromq/blob/main/bifromq-plugin/bifromq-plugin-event-collector/src/main/java/com/baidu/bifromq/plugin/eventcollector/EventType.java)枚举,可以通过对象上的type()
-方法访问,以便于实现事件过滤逻辑。hlc()方法允许检索事件对象的时间戳。BifroMQ的时间戳是偏序的,反映了相关事件发生的顺序。这对于在BifroMQ的分布式部署中处理事件特别有用。
-
-## 接口方法
-
-当事件生成时,BifroMQ调用所有已加载EventCollector的report()方法。方法签名如下:
-
-```java
-public void report(Event<?> event);
-```
-
-此方法在BifroMQ的工作线程上调用。随着负载的增加,将生成大量事件。为了避免创建大量的事件对象和过多的内存开销,传入此方法的事件对象将在方法返回后被重用。因此,在实现事件收集插件时,需要考虑以下几点:
-避免在report方法内包含复杂的业务逻辑,以确保其快速返回;否则,可能会对BifroMQ的性能产生负面影响。
-传入的事件对象的所有权不会转移。如果业务逻辑是异步的,并且需要在report方法返回后访问事件的内容,可以在方法返回前使用clone()方法创建对象的浅拷贝。
-
-## Metrics
-
-因为`report`方法会被频繁调用,BifroMQ记录并输出以下指标,以帮助插件实现者观察插件接口方法的性能指标:
-
-| Metric Name | Meter Type | Tag(`method`)         | Description |
-|-------------------|------------|-----------------------|---------------------------|
-| `call.exec.timer` | TIMER | EventCollector/report | Latency for `report` call |
\ No newline at end of file
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/06_plugin/3_resource_throttler.md b/i18n/zh-Hans/docusaurus-plugin-content-docs/current/06_plugin/3_resource_throttler.md
deleted file mode 100644
index d603f887..00000000
--- a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/06_plugin/3_resource_throttler.md
+++ /dev/null
@@ -1,135 +0,0 @@
----
-sidebar_position: 4
-title: "Resource Throttler"
----
-
-在BifroMQ的多租户架构中,租户共享单个集群实例提供的资源。为了防止任何单个租户过度使用造成对其他租户的影响,需要在全局层面运行时控制每个租户的资源投入。注意,通过资源限制实现租户间负载隔离的前提,业务高峰期集群中有冗余资源。
-
-租户级全局资源限制需要实时监控每个租户的集群资源使用情况,BifroMQ提供了[租户级Metrics](../07_admin_guide/03_observability/metrics/tenantmetrics.md),用于衡量资源量级和速率,指标类型包括:Gauge、Counter和Summary。
-
-插件的接口在以下Maven模块中定义:
-
-```xml
-
-<dependency>
-    <groupId>com.baidu.bifromq</groupId>
-    <artifactId>bifromq-plugin-resource-throttler</artifactId>
-    <version>X.Y.Z</version> <!--replace X.Y.Z with the latest version number-->
-</dependency>
-```
-
-BifroMQ一次只允许运行一个Resource Throttler实例。需要在[配置文件](../07_admin_guide/01_configuration/1_config_file_manual.md)中指定实现类的完全限定名(FQN):
-
-```yaml
-resourceThrottlerFQN: "YOUR_SETTING_PROVIDER_CLASS"
-```
-
-## 接口方法
-
-```java
-public boolean hasResource(String tenantId, TenantResourceType type);
-```
-
-此方法在BifroMQ的工作线程被上同步调用,需要确保其实现的高效,以避免影响BifroMQ性能。当方法返回false时将产生限制行为,同时生成一个ResourceThrottling事件,并报告给[Event Collector](2_event_collector.md)。
-
-以下是`TenantResourceType`中定义的资源类型:
-
-| Enum Value                             | Description                                      | Action on Limiting(MQTT3)   | Action on Limiting(MQTT5)                                 |
-|----------------------------------------|--------------------------------------------------|-----------------------------|-----------------------------------------------------------|
-| `TotalConnections`                     | Total number of connections                      | ConnAck with code(0x03)     | ConnAck with code(0x97)                                   | 
-| `TotalSessionMemoryBytes`              | Total session memory usage in bytes              | ConnAck with code(0x03)     | ConnAck with code(0x97)                                   |
-| `TotalPersistentSessions`              | Total number of persistent sessions              | Close connection by server  | Disconnect with code(0x97) and close connection by server |
-| `TotalPersistentSessionSpaceBytes`     | Total persistent session storage space in bytes  | Close connection by server  | Disconnect with code(0x97) and close connection by server |
-| `TotalSharedSubscriptions`             | Total number of shared subscriptions             | SubAck with code(0x80)      | SubAck with code(0x97)                                    |
-| `TotalTransientSubscriptions`          | Total number of transient subscriptions          | SubAck with code(0x80)      | SubAck with code(0x97)                                    |
-| `TotalPersistentSubscriptions`         | Total number of persistent subscriptions         | SubAck with code(0x80)      | SubAck with code(0x97)                                    |
-| `TotalRetainMessageSpaceBytes`         | Total storage space for Retain messages in bytes | Ignore                      | Ignore                                                    |
-| `TotalRetainTopics`                    | Total number of Retain topics                    | Ignore                      | Ignore                                                    |
-| `TotalConnectPerSecond`                | Total connections per second                     | ConnAck with code(0x03)     | ConnAck with code(0x97)                                   |
-| `TotalInboundBytesPerSecond`           | Total inbound bytes per second                   | Slowdown throughput         | Slowdown throughput                                       |
-| `TotalTransientSubscribePerSecond`     | Total transient subscribes per second            | SubAck with code(0x80)      | SubAck with code(0x97)                                    |
-| `TotalPersistentSubscribePerSecond`    | Total persistent subscribes per second           | SubAck with code(0x80)      | SubAck with code(0x97)                                    |
-| `TotalTransientUnsubscribePerSecond`   | Total transient unsubscribes per second          | UnsubAck only               | UnsubAck with code(0x80)                                  |
-| `TotalPersistentUnsubscribePerSecond`  | Total persistent unsubscribes per second         | UnsubAck only               | UnsubAck with code(0x80)                                  |
-| `TotalTransientFanOutBytesPerSeconds`  | Total transient fan-out bytes per second         | Throttled to one subscriber | Throttled                                                 |
-| `TotalPersistentFanOutBytesPerSeconds` | Total persistent fan-out bytes per second        | Throttled to one subscriber | Throttled                                                 |
-| `TotalRetainedMessagesPerSeconds`      | Total Retain messages per second                 | Ignore                      | Ignore                                                    |
-| `TotalRetainedBytesPerSecond`          | Total bytes for Retain messages per second       | Ignore                      | Ignore                                                    |
-| `TotalRetainMatchPerSeconds`           | Total Retain message match requests per second   | SubAck with code(0x80)      | SubAck with code(0x97)                                    |
-| `TotalRetainMatchBytesPerSecond`       | Total bytes for Retain match requests per second | SubAck with code(0x80)      | SubAck with code(0x97)                                    |
-
-这些枚举值代表了在多租户BifroMQ设置中可以限流的资源类型,不同资源类型触发的限制后会产生不同的限制行为。
-
-## Metrics
-
-因为`hasResource`方法会被频繁调用,BifroMQ记录并输出以下指标,以帮助插件实现者观察插件接口方法的性能指标:
-
-| Metric Name            | Meter Type | Tag(`method`)                 | Description                         |
-|------------------------|------------|-------------------------------|-------------------------------------|
-| `call.exec.timer`      | TIMER      | ResourceThrottler/hasResource | Latency for `hasResource` call      |
-| `call.exec.fail.count` | COUNTER    | ResourceThrottler/hasResource | Fail counter for `hasResource` call |
-
-## 实现考量点
-
-利用BifroMQ实现多租户服务时有以下几点需要考虑,以有效管理资源使用并确保各租户之间的公平访问:
-
-1. **收集和聚合租户指标**:从BifroMQ收集租户的资源指标,为每个租户构建并维护实时资源使用视图。视图的实时性决定了限流策略的精准性。
-
-2. **制定资源限制策略**:基于实时资源视图,实现租户资源分配决策,并转化为具体的资源限制指令。
-
-3. **实施资源限制**:资源限制指令需要通过`hasResource`方法以非阻塞的方式反馈给BifroMQ。
-
-## 实现范例
-
-BifroMQ包含了一个Resource Throttler的示范实现,可以通过在[配置文件](../07_admin_guide/01_configuration/1_config_file_manual.md)中指定`resourceThrottlerFQN`为`com.baidu.demo.plugin.DemoResourceThrottler`启用。范例实现利用JVM启动参数(`
--Dplugin.resourcethrottler.url`)来指定一个webhook的回调URL。
-
-当BifroMQ调用hasResource方法时,插件会发起一个包含tenant_id和resource_type header的GET请求,对应于hasResource方法的两个调用的参数。请求是异步的,未返回结果前,hasResource始终返回true,确保处理不会因请求而被阻塞。
-
-请求的结果被缓存60秒,并且每秒刷新一次。响应Body内包含的字符串被解析成布尔值,这成为hasResource方法的返回值。
-
-以下是一个演示用webhook服务器实现(基于node.js),可以用来测试示例插件,webhook的url地址为:`http://<ADDR>:<PORT>/query`,`http://<ADDR>:<PORT>/throttle`和`http://<ADDR>:<PORT>/release`分别用于设置和取消给定租户的限流状态。
-
-```js
-const hasResourceMap = {};
-
-const args = process.argv.slice(2);
-const hostname = args[0] || 'localhost'; 
-const port = args[1] || 3000; 
-
-const server = http.createServer((req, res) => {
-const parsedUrl = url.parse(req.url, true); 
-const pathname = parsedUrl.pathname;
-res.setHeader('Content-Type', 'text/plain');
-
-if (pathname === '/query') {
-    const tenantId = req.headers['tenant_id'];
-    const resourceType = req.headers['resource_type'];
-    const key = `${tenantId}${resourceType}`;
-    const exists = key in hasResourceMap ? hasResourceMap[key] : true;
-    res.end(`${exists}`);
-}
-else if (pathname === '/throttle') {
-    const tenantId = req.headers['tenant_id'];
-    const resourceType = req.headers['resource_type'];
-    const key = `${tenantId}${resourceType}`;
-    hasResourceMap[key] = false;
-    res.end('Throttled');
-}
-else if (pathname === '/release') {
-    const tenantId = req.headers['tenant_id'];
-    const resourceType = req.headers['resource_type'];
-    const key = `${tenantId}${resourceType}`;
-    delete hasResourceMap[key];
-    res.end('Released');
-}
-else {
-    res.statusCode = 404;
-    res.end('Not Found');
-}
-});
-
-server.listen(port, hostname, () => {
-    console.log(`Server listening on port ${server.address().port} from address ${server.address().address}`);
-});
-```
\ No newline at end of file
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/06_plugin/4_setting_provider/1_tenantsetting.md b/i18n/zh-Hans/docusaurus-plugin-content-docs/current/06_plugin/4_setting_provider/1_tenantsetting.md
deleted file mode 100644
index 6d4afe50..00000000
--- a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/06_plugin/4_setting_provider/1_tenantsetting.md
+++ /dev/null
@@ -1,49 +0,0 @@
----
-sidebar_position: 2
-title: "租户级设置(Settings)"
----
-租户级设置允许对BifroMQ的功能和性能特性进行详细控制。每个设置都可以按租户进行调整,从而根据每个租户的特定要求和偏好实现定制化行为。这种粒度确保了BifroMQ能够满足各种用例和操作环境的需求。
-
-## 初始值调整
-
-这些设置的初始值可以通过JVM启动参数进行调整。这使得在每个租户的运行时定制之前,可以对系统范围内的默认值进行调整。例如,要默认禁用MQTT版本3.1客户端连接,可以使用参数`-DMQTT3Enabled=false`启动JVM。
-
-## 通过Setting Provider插件进行定制
-
-租户设置的管理责任被转移到业务端实现。通过开发和集成自定义Setting Provider插件来实现对这些设置的定制和运行时调整。这种方法允许企业根据变化的操作条件、监管要求或特定的业务逻辑动态调整设置。
-
-## 支持的设置
-
-
-| Name                             | Type    | Initial Value | Description                                                      |
-|----------------------------------|---------|---------------|------------------------------------------------------------------|
-| `MQTT3Enabled`                   | Boolean | true          | Enables or disables MQTT version 3.1 support.                    |
-| `MQTT4Enabled`                   | Boolean | true          | Enables or disables MQTT version 3.1.1 support.                  |
-| `MQTT5Enabled`                   | Boolean | true          | Enables or disables MQTT version 5.0 support.                    |
-| `DebugModeEnabled`               | Boolean | false         | Enables or disables debug mode.                                  |
-| `ForceTransient`                 | Boolean | false         | Forces transient mode for connections.                           |
-| `ByPassPermCheckError`           | Boolean | true          | Bypasses permission check errors.                                |
-| `PayloadFormatValidationEnabled` | Boolean | true          | Enables or disables payload format validation.                   |
-| `RetainEnabled`                  | Boolean | true          | Enables or disables message retain feature.                      |
-| `WildcardSubscriptionEnabled`    | Boolean | true          | Enables or disables wildcard subscriptions.                      |
-| `SubscriptionIdentifierEnabled`  | Boolean | true          | Enables or disables subscription identifiers.                    |
-| `SharedSubscriptionEnabled`      | Boolean | true          | Enables or disables shared subscriptions.                        |
-| `MaximumQoS`                     | Integer | 2             | Sets the maximum QoS level. Valid values: 0, 1, 2.               |
-| `MaxTopicLevelLength`            | Integer | 40            | Maximum length of each topic level.                              |
-| `MaxTopicLevels`                 | Integer | 16            | Maximum number of topic levels.                                  |
-| `MaxTopicLength`                 | Integer | 255           | Maximum total length of a topic.                                 |
-| `MaxTopicAlias`                  | Integer | 10            | Maximum number of topic aliases.                                 |
-| `MaxSharedGroupMembers`          | Integer | 200           | Maximum members in a shared subscription group.                  |
-| `MaxTopicFiltersPerInbox`        | Integer | 100           | Maximum topic filters per inbox.                                 |
-| `MsgPubPerSec`                   | Integer | 200           | Maximum number of messages published per second per connection.  |
-| `ReceivingMaximum`               | Integer | 200           | Maximum number of receiving messages per second per connection.  |
-| `InBoundBandWidth`               | Long    | 512 * 1024L   | Maximum inbound bandwidth in bytes per connection.               |
-| `OutBoundBandWidth`              | Long    | 512 * 1024L   | Maximum outbound bandwidth in bytes per connection.              |
-| `MaxUserPayloadBytes`            | Integer | 256 * 1024    | Maximum user payload size in bytes.                              |
-| `MaxResendTimes`                 | Integer | 3             | Maximum times a message can be resent when qos is 1 or 2.        |
-| `ResendTimeoutSeconds`           | Integer | 10            | Timeout in seconds before a message is considered for resend.    |
-| `MaxTopicFiltersPerSub`          | Integer | 10            | Maximum topic filters per subscription.                          |
-| `MaxSessionExpirySeconds`        | Integer | 24 * 60 * 60  | Maximum session expiry time in seconds.                          |
-| `SessionInboxSize`               | Integer | 1000          | Maximum size of session inbox.                                   |
-| `QoS0DropOldest`                 | Boolean | false         | Whether to drop the oldest QoS 0 messages first.                 |
-| `RetainMessageMatchLimit`        | Integer | 10            | Limit for retained message matches.                              |
\ No newline at end of file
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/06_plugin/4_setting_provider/_category_.json b/i18n/zh-Hans/docusaurus-plugin-content-docs/current/06_plugin/4_setting_provider/_category_.json
deleted file mode 100644
index de7bc786..00000000
--- a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/06_plugin/4_setting_provider/_category_.json
+++ /dev/null
@@ -1,8 +0,0 @@
-{
-  "label": "Setting Provider",
-  "position": 4,
-  "link": {
-    "type": "doc",
-    "id": "intro"
-  }
-}
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/06_plugin/4_setting_provider/intro.md b/i18n/zh-Hans/docusaurus-plugin-content-docs/current/06_plugin/4_setting_provider/intro.md
deleted file mode 100644
index 88d1a68d..00000000
--- a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/06_plugin/4_setting_provider/intro.md
+++ /dev/null
@@ -1,123 +0,0 @@
----
-id: "intro"
-sidebar_position: 0
-title: "Setting Provider"
----
-
-BifroMQ定义了一类租户级[设置](1_tenantsetting.md)(Settings),允许在运行时修改,从而实现针对单个租户动态调整BifroMQ的服务行为。Setting Provider Plugin的目的是在运行时为这些设置提供自定义值。
-
-插件的接口定义在以下Maven模块中:
-
-```xml
-
-<dependency>
-    <groupId>com.baidu.bifromq</groupId>
-    <artifactId>bifromq-plugin-setting-provider</artifactId>
-    <version>X.Y.Z</version> <!--replace X.Y.Z with the latest version number-->
-</dependency>
-```
-
-BifroMQ只允许运行一个Setting Provider实例。需要在配置文件指定要加载的具体实现类的完全限定名(FQN):
-
-```yaml
-settingProviderFQN: "YOUR_SETTING_PROVIDER_CLASS"
-```
-
-## 设置的初始值和验证
-
-每个设置都有一个初始值,例如,MaxTopicLength的初始值为255,并验证为介于0和65535之间的整数。可以通过与同名的系统属性覆盖设置的初始值,例如,在BifroMQ的JVM启动参数中添加`-DMaxTopicLength=128`。请注意,通过系统属性传递的初始值必须正确解析为相应的数据类型,否则覆盖将不会成功。
-
-## 更新设置的当前值
-
-BifroMQ通过调用SettingProvider插件的`provide`方法来更新设置的当前值。provide方法的签名如下:
-
-```java
-public <R> R provide(Setting setting, String tenantId);
-```
-
-此方法将由BifroMQ的线程池调用,因此在实现Setting Provider Plugin时需要牢记以下两点:
-
-1. 避免在provide方法中包含繁重的业务逻辑,以确保它能够快速返回,否则会对BifroMQ的性能产生负面影响。
-2. 当无法快速确定设置的值时,可以返回`null`,此时设置将继续使用其当前值。插件实现可以将多个Setting的请求聚合后异步处理。
-
-## 缓存行为
-
-不同Tenant的Setting值会被缓存,以减少对Setting Provider的调用次数。以下JVM系统属性用于控制缓存的行为,已达到运行时设置的即时性与请求负载的平衡:
-
-| System Property Name         | Default Value | Description                                                                                                        |
-|------------------------------|---------------|--------------------------------------------------------------------------------------------------------------------|
-| `setting_provide_init_value` | false         | Determines whether to call `provide` to populate the cache on a cache miss. By default, the initial value is used. |
-| `setting_refresh_seconds`    | 5             | The interval, in seconds, between refreshes of a cached setting.                                                   |
-| `setting_expire_seconds`     | 300           | The expiration time, in seconds, of a setting in the cache.                                                        |
-| `setting_tenant_cache_limit` | 100           | The maximum number of tenants' values that can be cached.                                                          |
-
-**注意:** 如果 `provide` 方法执行缓慢,启用 `setting_provide_init_value` 可能会阻塞 BifroMQ 的工作线程并导致性能问题。
-
-## Metrics
-
-BifroMQ记录并输出以下指标,以帮助插件实现者观察插件接口方法的性能指标:
-
-| Metric Name            | Meter Type | Tag(`method`)           | Description                     |
-|------------------------|------------|-------------------------|---------------------------------|
-| `call.exec.timer`      | TIMER      | SettingProvider/provide | Latency for `provide` call      |
-| `call.exec.fail.count` | COUNTER    | SettingProvider/provide | Fail counter for `provide` call |
-
-## 实现范例
-
-BifroMQ包含了一个基于WebHook的SettingProvider的示范实现,可以通过在[配置文件](../../07_admin_guide/01_configuration/1_config_file_manual.md)中指定`settingProviderFQN`为`com.baidu.demo.plugin.DemoSettingProvider`启用。范例实现利用JVM启动参数(
-`-Dplugin.settingprovider.url`)来指定一个webhook的回调URL。
-
-当BifroMQ调用`provide`方法时,插件会发起一个包含tenant_id和setting_name header的HTTP GET请求,对应于`provide`方法的两个调用的参数。响应Body内包含的字符串被解析成对应的Setting值类型作为返回值。
-
-以下是一个Node实现的简单的WebhookServer用于测试示例插件,webhook的url地址为:`http://<ADDR>:<PORT>/query`,`http://<ADDR>:<PORT>/provide`分别用于查询和设置给定租户的运行时Setting。
-
-```js
-const http = require('http');
-const url = require('url'); 
-
-const settingMap = {};
-const server = http.createServer((req, res) => {
-  const parsedUrl = url.parse(req.url, true);
-  const pathname = parsedUrl.pathname;
-
-  res.setHeader('Content-Type', 'text/plain');
-
-  if (pathname === '/query') {
-    const tenantId = req.headers['tenant_id'];
-    const settingName = req.headers['setting_name'];
-    const key = `${tenantId}${settingName}`;
-    if (key in settingMap) {
-      res.end(`${settingMap[key]}`);
-    } else {
-      res.statusCode = 404;
-      res.end("");
-    }
-  }
-  else if (pathname === '/provide') {
-    const tenantId = req.headers['tenant_id'];
-    const settingName = req.headers['setting_name'];
-    const key = `${tenantId}${settingName}`;
-
-    let body = [];
-    req.on('data', (chunk) => {
-      body.push(chunk);
-    }).on('end', () => {
-      body = Buffer.concat(body).toString();
-      settingMap[key] = body;
-      res.end('OK');
-    });
-  }
-  else {
-    res.statusCode = 404;
-    res.end('Not Found');
-  }
-});
-
-const args = process.argv.slice(2);
-const hostname = args[0] || 'localhost'; 
-const port = args[1] || 3000; 
-
-server.listen(port, hostname, () => {
-  console.log(`Server listening on port ${server.address().port} at ${server.address().address}`);
-});
-```
\ No newline at end of file
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/06_plugin/5_plugin_practice.md b/i18n/zh-Hans/docusaurus-plugin-content-docs/current/06_plugin/5_plugin_practice.md
deleted file mode 100644
index 2e621b0e..00000000
--- a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/06_plugin/5_plugin_practice.md
+++ /dev/null
@@ -1,73 +0,0 @@
----
-sidebar_position: 5
-title: "Plugin开发实践"
----
-
-本文概述了开发BifroMQ插件时一些基本的实践和注意事项。
-
-## 快速开始插件开发
-
-执行以下 Maven 命令,快速启动 BifroMQ 插件开发:
-
-```bash
-mvn archetype:generate \
-    -DarchetypeGroupId=com.baidu.bifromq \
-    -DarchetypeArtifactId=bifromq-plugin-archetype \
-    -DarchetypeVersion=<BIFROMQ_VERSION> \
-    -DgroupId=<YOUR_GROUP_ID> \
-    -DartifactId=<YOUR_ARTIFACT_ID> \
-    -Dversion=<YOUR_PROJECT_VERSION> \
-    -DpluginName=<YOUR_PLUGIN_CLASS_NAME> \
-    -DpluginContextName=<YOUR_PLUGIN_CONTEXT_CLASS_NAME> \
-    -DbifromqVersion=<BIFROMQ_VERSION> \
-    -DinteractiveMode=false
-```
-
-请将 `<YOUR_GROUP_ID>`、`<YOUR_ARTIFACT_ID>`、`<YOUR_PROJECT_VERSION>`、`<YOUR_PLUGIN_CLASS_NAME>`
-和 `<YOUR_PLUGIN_CONTEXT_CLASS_NAME>` 替换为您的具体信息。该命令生成一个准备就绪的、结构清晰的多模块项目,专为 BifroMQ
-插件开发而设计。
-
-**重要提示**:原型的版本应为 3.2.0 或更高版本,因为该原型从 3.2.0 版本开始兼容。确保 `<BIFROMQ_VERSION>` 设置正确。
-
-除了插件开发的基础代码框架外,生成的 BifroMQ 插件项目还为您提供以下机制:
-
-* PluginContext:定义插件上下文,方便传递插件运行所需信息。
-* 配置文件:使用独立的 config.yaml 文件来配置插件。
-* 日志配置:使用独立的 logback.xml 文件来配置插件日志。
-
-## BifroMQ的远程调试
-
-Java远程调试允许开发人员从IDE远程调试定制化插件。BifroMQ支持远程调试,可以通过环境变量JVM_DEBUG来启用。同时,还可以通过环境变量JAVA_DEBUG_PORT指定远程调试端口。如果没有指定,那么默认端口为8008。Linux Shell示例:
-
-```shell
-export JVM_DEBUG=true
-export JAVA_DEBUG_PORT=8009
-export DEBUG_SUSPEND_FLAG=n
-```
-
-确保正确配置调试端口,并且没有端口冲突。使用IDE(例如,IntelliJ或Eclipse)进行远程调试。
-设置`DEBUG_SUSPEND_FLAG=y`,可以帮助调试插件的初始化过程。
-
-## 注意Java类加载
-
-BifroMQ会为每个插件使用单独的ClassLoader从插件的classpath中加载使用到的类,所以请确保插件的打包中包含所有用到的依赖(除了BifroMQ[提供](intro.md#插件部署)的以外)。
-某些第三方类库可能其他方式加载类,导致类加载失败。大部分情况可以通过替换Thread ContextLoader的方式解决:
-
-```java
-class MyPlugin {
-    public void pluginMethod() {
-        ClassLoader originalLoader = Thread.currentThread().getContextClassLoader();
-        try {
-            Thread.currentThread().setContextClassLoader(this.getClass().getClassLoader());
-            // Initialize dependencies here  
-            dependenciesInit();
-        } finally {
-            Thread.currentThread().setContextClassLoader(originalLoader);
-        }
-    }
-}
-```
-
-## 正确组织插件目录
-
-开发插件时,请确保插件目录中没有无关的jar文件。[pf4j](https://pf4j.org)会递归检查插件目录中的jar文件,无关的jars可能导致PF4J验证错误。
\ No newline at end of file
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/06_plugin/_category_.json b/i18n/zh-Hans/docusaurus-plugin-content-docs/current/06_plugin/_category_.json
deleted file mode 100644
index 6526781a..00000000
--- a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/06_plugin/_category_.json
+++ /dev/null
@@ -1,8 +0,0 @@
-{
-  "label": "Plugin",
-  "position": 6,
-  "link": {
-    "type": "doc",
-    "id": "plugin/intro"
-  }
-}
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/06_plugin/intro.md b/i18n/zh-Hans/docusaurus-plugin-content-docs/current/06_plugin/intro.md
deleted file mode 100644
index 24c73459..00000000
--- a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/06_plugin/intro.md
+++ /dev/null
@@ -1,66 +0,0 @@
----
-id: intro
-sidebar_position: 0
-title: "插件能力概述"
----
-
-插件机制是BifroMQ与业务系统深度集成的主要方式。目前,BifroMQ开放了4种类型的插件扩展接口,满足不同的使用场景:
-
-* **[Auth Provider](1_auth_provider.md)**:集成认证和主题发布/订阅授权逻辑。
-* **[Event Collector](2_event_collector.md)**:收集运行时事件以实现各种事件驱动的业务逻辑。
-* **[Resource Throttler](3_resource_throttler.md)**:在租户级别使用动态控制资源使用。
-* **[Setting Provider](4_setting_provider/intro.md)**:动态调整租户的MQTT协议相关设置。
-
-## 插件开发
-
-* 项目组织:一个pf4j项目可以包含多个插件实现。
-* 单例插件:AuthProvider、Resource Throttler和Setting Provider类型的扩展在运行时是单例的。需要通过配置文件指定要加载的具体类型。
-* 多例插件:EventCollector允许多个不同类型的实例存在,这些EventCollector实例的接口方法将同时被回调。
-* 快速开发:提供了插件项目搭建工具,可以快速开始进行插件开发。参见[快速开始插件开发](../plugin_practice/#快速开始插件开发)
-
-## 插件部署
-
-* 插件目录:BifroMQ从其安装目录内的plugins子目录加载插件实现(JAR文件或目录)。
-* 类加载器隔离:每个插件使用独立的ClassLoader来隔离其代码与BifroMQ及其他插件。
-* BifroMQ为以下常用包提供类加载:
-    * `com.baidu.bifromq.type.*`
-    * `com.baidu.bifromq.plugin.*`
-    * `io.micrometer.core.*`
-    * `com.google.protobuf.*`
-
-**注意**:某些插件的依赖可能会使用`Thread.currentThread().getContextClassLoader()`加载class,从而导致`ClassNotFoundException`,为避免这种情况的发生,可以将加载依赖class的逻辑包含在如下try-finally结构中:
-
-```java
-public pluginMethod() {
-    ClassLoader contextLoader = Thread.currentThread().getContextClassLoader();
-    // using PluginClassLoader for context class loader 
-    Thread.currentThread().setContextClassLoader(this.getClass().getClassLoader());
-    try {
-        // loading 3rd party dependencies
-    } finally {
-        Thread.currentThread().setContextClassLoader(contextLoader);
-    }
-}
-```
-
-## 版本兼容性
-
-为了确保最佳兼容性并避免潜在问题,建议将自定义插件与BifroMQ主程序的主版本(major version)一致。
-
-示例:
-
-* 如果BifroMQ的版本为3.x.y,则插件所使用的接口定义模块版本也需为3.x.y。
-
-## 性能考虑
-
-BifroMQ会在工作线程上调用插件接口方法,确保插件接口实现的轻量和非阻塞,避免对性能产生负面影响。
-
-## Metrics和Logging
-
-- 鼓励插件开发者使用BifroMQ日志框架进行插件日志记录,使用同一个`logback.xml`进行日志配置即可。
-- BifroMQ在调用插件方法时捕获并记录指标,为调试和性能优化提供宝贵的洞察。
-
-
-## 配置Demo Plugin的参数
-BifroMQ 支持通过环境变量或系统属性配置Demo Plugin的参数,包括Prometheus指标抓取路径和服务器端口。
-注意:仅支持配置路径和端口参数。
\ No newline at end of file
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/07_admin_guide/01_configuration/1_config_file_manual.md b/i18n/zh-Hans/docusaurus-plugin-content-docs/current/07_admin_guide/01_configuration/1_config_file_manual.md
deleted file mode 100644
index 20081847..00000000
--- a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/07_admin_guide/01_configuration/1_config_file_manual.md
+++ /dev/null
@@ -1,116 +0,0 @@
----
-sidebar_position: 1
-title: "配置文件"
----
-
-BifroMQ的配置文件是一个位于conf目录下的standalone.yml的YAML文件。这个文件只包含部分常用的配置参数。启动BifroMQ时,你可以通过命令行参数-c或--config来指定配置文件的路径。如果没有指定配置文件路径,BifroMQ将尝试从conf目录加载standalone.yml文件。
-
-## StandaloneConfig
-
-| Configuration Name                                                   | Value Type             | Default Value              | Description                                                                                                                                                                                                                                                                                                                                                   |
-|----------------------------------------------------------------------|------------------------|----------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
-| `bootstrap`                                                          | Boolean                | false                      | If the node is responsible for cluster bootstrapping, this value should be set to true. Otherwise, it should be set to false. Note: In cluster deployments, there must be **exactly one** bootstrap node.                                                                                                                                                     |
-| `authProviderFQN`                                                    | String                 | null                       | Fully qualified class name of the custom Auth Provider implementation. If not configured, authentication and authorization will not be performed.                                                                                                                                                                                                             |
-| `resourceThrottlerFQN`                                               | String                 | null                       | Fully qualified class name of the custom Resource Throttler implementation. If not configured, resource limiting will not be performed.                                                                                                                                                                                                                       |
-| `settingProviderFQN`                                                 | String                 | null                       | Fully qualified class name of the custom Setting Provider implementation. If not configured, default initial values defined in Settings will be used.                                                                                                                                                                                                         |
-| `clusterConfig.env`                                                  | String                 | "Test"                     | Cluster environment name. Cluster nodes with different environment names are isolated from each other. Cannot be null or an empty string.                                                                                                                                                                                                                     |
-| `clusterConfig.host`                                                 | String                 |                            | Communication address of the node as a cluster node. If not configured, the actual value is determined by the following rules: If the value of `mqttServerConfig.tcpListener.host` is not "0.0.0.0", use that value; otherwise, if `rpcServerConfig.host` is configured, use that value; otherwise, use the SiteLocal address resolved from NetworkInterface. |
-| `clusterConfig.port`                                                 | Integer                | 0                          | Communication port number of the node as a cluster node. `0` means automatically selecting an unused port number. It is recommended to configure a specific port number for nodes with the `bootstrap role` to simplify the configuration process.                                                                                                            |
-| `clusterConfig.seedEndpoints`                                        | String                 | null                       | Addresses of seed nodes to join the cluster, in the form of `ip:port` addresses separated by `,`. It is recommended that nodes other than the `bootstrap role` configure the bootstrap node address to simplify the configuration process.                                                                                                                    |
-| `clusterConfig.clusterDomainName`                                    | String                 | null                       | Cluster domain name. Specifying the domain name here can further simplify the configuration process for cluster nodes when the cluster nodes are registered to a fixed domain name. BifroMQ will resolve this domain name to obtain the address of the cluster contact nodes.                                                                                 |
-| `mqttServerConfig.connTimeoutSec`                                    | Integer                | 20                         | The tolerable timeout duration from establishing a TCP connection to completing the MQTT connection operation. If this limit is exceeded, the server will proactively disconnect.                                                                                                                                                                             |
-| `mqttServerConfig.maxConnPerSec`                                     | Integer                | 2000                       | The maximum rate of MQTT connection operations accepted per second. Connections exceeding this limit will be limited by the token bucket and subsequently disconnected.                                                                                                                                                                                       |
-| `mqttServerConfig.maxDisconnPerSec`                                  | Integer                | 1000                       | The maximum rate of disconnecting connections per second when the node is gracefully shutting down.                                                                                                                                                                                                                                                           |
-| `mqttServerConfig.maxMsgByteSize`                                    | Integer                | 262144                     | This parameter is an initial setting for establishing a connection and effectively limits the size of the MQTT Connect Packet. If a Connect Packet, including the Will Message, exceeds this size, the connection will be rejected.                                                                                                                           |
-| `mqttServerConfig.maxConnBandwidth`                                  | Integer                | 524288                     | The maximum bandwidth allowed for a single connection, calculated separately for inbound and outbound traffic.                                                                                                                                                                                                                                                |
-| `mqttServerConfig.defaultKeepAliveSec`                               | Integer                | 300                        | The default keep-alive duration for connections. When clients do not actively set this, this value is used.                                                                                                                                                                                                                                                   |
-| `mqttServerConfig.bossELGThreads`                                    | Integer                | 1                          | The number of threads for accepting TCP connection requests.                                                                                                                                                                                                                                                                                                  |
-| `mqttServerConfig.workerELGThreads`                                  | Integer                | max(processor cores/2, 2)  | The number of worker threads for processing MQTT protocol signaling.                                                                                                                                                                                                                                                                                          |
-| `mqttServerConfig.tcpListener.enable`                                | Boolean                | true                       | Whether to enable MQTT over TCP connection method.                                                                                                                                                                                                                                                                                                            |
-| `mqttServerConfig.tcpListener.host`                                  | String                 | "0.0.0.0"                  | Communication address for MQTT over TCP connection method.                                                                                                                                                                                                                                                                                                    |
-| `mqttServerConfig.tcpListener.port`                                  | Integer                | 1883                       | Communication port for MQTT over TCP connection method.                                                                                                                                                                                                                                                                                                       |
-| `mqttServerConfig.tlsListener.enable`                                | Boolean                | false                      | Whether to enable MQTT over TLS connection method.                                                                                                                                                                                                                                                                                                            |
-| `mqttServerConfig.tlsListener.host`                                  | String                 | "0.0.0.0"                  | Communication address for MQTT over TLS connection method.                                                                                                                                                                                                                                                                                                    |
-| `mqttServerConfig.tlsListener.port`                                  | Integer                | 1884                       | Communication port for MQTT over TLS connection method.                                                                                                                                                                                                                                                                                                       |
-| `mqttServerConfig.tlsListener.sslConfig`                             | ServerSSLContextConfig | null                       | SSL configuration for MQTT over TLS connection method. Refer to the settings of the ServerSSLContextConfig object.                                                                                                                                                                                                                                            |
-| `mqttServerConfig.wsListener.enable`                                 | Boolean                | true                       | Whether to enable MQTT over WebSocket connection method.                                                                                                                                                                                                                                                                                                      |
-| `mqttServerConfig.wsListener.host`                                   | String                 | "0.0.0.0"                  | Communication address for MQTT over WebSocket connection method.                                                                                                                                                                                                                                                                                              |
-| `mqttServerConfig.wsListener.port`                                   | Integer                | 8080                       | Communication port for MQTT over WebSocket connection method.                                                                                                                                                                                                                                                                                                 |
-| `mqttServerConfig.wsListener.wsPath`                                 | String                 | "/mqtt"                    | Access path for MQTT over WebSocket connection method.                                                                                                                                                                                                                                                                                                        |
-| `mqttServerConfig.wssListener.enable`                                | Boolean                | false                      | Whether to enable MQTT over WebSocket Secure connection method.                                                                                                                                                                                                                                                                                               |
-| `mqttServerConfig.wssListener.host`                                  | String                 | "0.0.0.0"                  | Communication address for MQTT over WebSocket Secure connection method.                                                                                                                                                                                                                                                                                       |
-| `mqttServerConfig.wssListener.port`                                  | Integer                | 8443                       | Communication port for MQTT over WebSocket Secure connection method.                                                                                                                                                                                                                                                                                          |
-| `mqttServerConfig.wssListener.wsPath`                                | String                 | "/mqtt"                    | Access path for MQTT over WebSocket Secure connection method.                                                                                                                                                                                                                                                                                                 |
-| `mqttServerConfig.wssListener.sslConfig`                             | ServerSSLContextConfig | null                       | SSL configuration for MQTT over WebSocket Secure connection method. Refer to the settings of the ServerSSLContextConfig object.                                                                                                                                                                                                                               |
-| `rpcClientConfig.workerThreads` , `baseKVClientConfig.workerThreads` | Integer                | processor cores            | The number of worker threads when communicating between nodes as a client via RPC.                                                                                                                                                                                                                                                                            |
-| `rpcClientConfig.sslConfig`,`baseKVClientConfig.sslConfig`           | SSLContextConfig       | null                       | SSL configuration when Secure RPC is enabled. Refer to the settings of the SSLContextConfig object.                                                                                                                                                                                                                                                           |
-| `rpcServerConfig.host`,`baseKVServerConfig.host`                     | String                 |                            | See the rule description for ClusterConfig.host.                                                                                                                                                                                                                                                                                                              |
-| `rpcServerConfig.port`,`baseKVServerConfig.port`                     | Integer                | 0                          | See the rule description for ClusterConfig.port.                                                                                                                                                                                                                                                                                                              |
-| `rpcServerConfig.workerThreads`,`baseKVServerConfig.workerThreads`   | Integer                | 2                          | The number of worker threads when communicating between nodes as a server via RPC.                                                                                                                                                                                                                                                                            |
-| `rpcServerConfig.sslConfig`,`baseKVServerConfig.sslConfig`           | ServerSSLContextConfig | null                       | SSL configuration when Secure RPC is enabled. Refer to the settings of the ServerSSLContextConfig object.                                                                                                                                                                                                                                                     |
-| `stateStoreConfig.queryThreads`                                      | Integer                | min(available cores/2, 2)  | The number of threads for the built-in state storage service to execute query type requests.                                                                                                                                                                                                                                                                  |
-| `stateStoreConfig.tickerThreads`                                     | Integer                | min(available cores/20, 1) | The number of threads for the built-in state storage service to perform periodic tick operations.                                                                                                                                                                                                                                                             |
-| `stateStoreConfig.bgWorkerThreads`                                   | Integer                | min(available cores/4, 1)  | The number of threads for the built-in state storage service to perform background operations.                                                                                                                                                                                                                                                                |
-| `stateStoreConfig.distWorkerConfig.queryPipelinePerStore`            | Integer                | 1000                       | The number of queryPipelines for the Dist Worker state storage service.                                                                                                                                                                                                                                                                                       |
-| `stateStoreConfig.distWorkerConfig.compactWALThreshold`              | Integer                | 2500                       | The maximum number of logs before a compaction operation is performed in the Dist Worker state storage service.                                                                                                                                                                                                                                               |
-| `stateStoreConfig.distWorkerConfig.dataEngineConfig`                 | StorageEngineConfig    |                            | Data storage engine configuration for the Dist Worker state storage service. Refer to the settings of the StorageEngineConfig object.                                                                                                                                                                                                                         |
-| `stateStoreConfig.distWorkerConfig.walEngineConfig`                  | StorageEngineConfig    |                            | WAL storage engine configuration for the Dist Worker state storage service. Refer to the settings of the StorageEngineConfig object.                                                                                                                                                                                                                          |
-| `stateStoreConfig.distWorkerConfig.balanceConfig`                    | BalancerOptions        |                            | Balancer configuration for the Dist Worker state storage service. Refer to the settings of the BalancerOptions object.                                                                                                                                                                                                                                        |
-| `inboxStoreConfig.queryPipelinePerStore`                             | Integer                | 100                        | The number of queryPipelines for the Inbox Store state storage service.                                                                                                                                                                                                                                                                                       |
-| `inboxStoreConfig.compactWALThreshold`                               | Integer                | 2500                       | The maximum number of logs before a compaction operation is performed in the Inbox Store state storage service.                                                                                                                                                                                                                                               |
-| `inboxStoreConfig.gcIntervalSeconds`                                 | Integer                | 600                        | The interval (in seconds) for recycling expired Session data in the Inbox Store.                                                                                                                                                                                                                                                                              |
-| `inboxStoreConfig.dataEngineConfig`                                  | StorageEngineConfig    |                            | Data storage engine configuration for the Inbox Store state storage service. Refer to the settings of the StorageEngineConfig object.                                                                                                                                                                                                                         |
-| `inboxStoreConfig.walEngineConfig`                                   | StorageEngineConfig    |                            | WAL storage engine configuration for the Inbox Store state storage service. Refer to the settings of the StorageEngineConfig object.                                                                                                                                                                                                                          |
-| `inboxStoreConfig.balanceConfig`                                     | BalancerOptions        |                            | Balancer configuration for the Inbox Store state storage service. Refer to the settings of the BalancerOptions object.                                                                                                                                                                                                                                        |
-| `retainStoreConfig.queryPipelinePerStore`                            | Integer                | 100                        | The number of queryPipelines for the Retain Store state storage service.                                                                                                                                                                                                                                                                                      |
-| `retainStoreConfig.compactWALThreshold`                              | Integer                | 2500                       | The maximum number of logs before a compaction operation is performed in the Retain Store state storage service.                                                                                                                                                                                                                                              |
-| `retainStoreConfig.gcIntervalSeconds`                                | Integer                | 600                        | The interval (in seconds) for recycling expired data in the Retain Store.                                                                                                                                                                                                                                                                                     |
-| `retainStoreConfig.dataEngineConfig`                                 | StorageEngineConfig    |                            | Data storage engine configuration for the Retain Store state storage service. Refer to the settings of the StorageEngineConfig object.                                                                                                                                                                                                                        |
-| `retainStoreConfig.walEngineConfig`                                  | StorageEngineConfig    |                            | WAL storage engine configuration for the Retain Store state storage service. Refer to the settings of the StorageEngineConfig object.                                                                                                                                                                                                                         |
-| `retainStoreConfig.balanceConfig`                                    | BalancerOptions        |                            | Balancer configuration for the Retain Store state storage service. Refer to the settings of the BalancerOptions object.                                                                                                                                                                                                                                       |
-| `apiServerConfig.enable`                                             | Boolean                | true                       | Whether to enable HTTP API access.                                                                                                                                                                                                                                                                                                                            |
-| `apiServerConfig.host`                                               | String                 | null                       | Access address for the HTTP API. If not configured, the same rule as ClusterConfig.host is used to determine the address.                                                                                                                                                                                                                                     |
-| `apiServerConfig.httpPort`                                           | Integer                | 8091                       | Access port for the HTTP API.                                                                                                                                                                                                                                                                                                                                 |
-| `apiServerConfig.apiBossThreads`                                     | Integer                | 1                          | The number of threads for handling HTTP API TCP connection requests.                                                                                                                                                                                                                                                                                          |
-| `apiServerConfig.apiWorkerThreads`                                   | Integer                | 2                          | The number of worker threads for processing HTTP API requests.                                                                                                                                                                                                                                                                                                |
-| `apiServerConfig.httpsListenerConfig.enable`                         | Boolean                | false                      | Whether to enable HTTPS API access.                                                                                                                                                                                                                                                                                                                           |
-| `apiServerConfig.httpsListenerConfig.host`                           | String                 | null                       | Access address for the HTTPS API. If not configured, the same rule as ClusterConfig.host is used to determine the address.                                                                                                                                                                                                                                    |
-| `apiServerConfig.httpsListenerConfig.port`                           | Integer                | 8090                       | Access port for the HTTPS API.                                                                                                                                                                                                                                                                                                                                |
-| `apiServerConfig.httpsListenerConfig.sslConfig`                      | ServerSSLContextConfig | null                       | SSL configuration for the HTTPS API. Refer to the settings of the ServerSSLContextConfig object.                                                                                                                                                                                                                                                              |
-
-## SSLContextConfig && ServerSSLContextConfig
-
-`SSLContextConfig`用于设置客户端SSL连接的配置参数。`ServerSSLContextConfig`用于设置服务器SSL连接的配置参数。
-
-如果在相应的启用标志(`enable`)设置为 true 的情况下将 SSLContextConfig 或 ServerSSLContextConfig 置为 null,将会生成一个自签名证书,这在生产环境中不推荐使用。
-
-| Configuration Name | Value Type | Default Value | Description                                                                                                                                                                                                                                                                                                                                                                                      |
-|--------------------|------------|---------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
-| `certFile`         | String     | null          | The filename of the public certificate for the client or server.                                                                                                                                                                                                                                                                                                                                 |
-| `keyFile`          | String     | null          | The filename of the private key for the client or server.                                                                                                                                                                                                                                                                                                                                        |
-| `trustCertsFile`   | String     | null          | The filename of the root certificate for the client or server. If null, peer certification will not be verified, when clientAuth is OPTIONAL or REQUIRE.                                                                                                                                                                                                                                         |
-| `clientAuth`       | String     | "OPTIONAL"    | Only valid for ServerSSLContextConfig. Whether the server requires client verification. Possible values include: <br/>NONE: No verification required; <br/>OPTIONAL: Server requests client verification, but if the client does not provide a certificate, it will not fail; <br/>REQUIRE: Server requires client verification, and if the client does not provide a certificate, it will fail. |
-
-## StorageEngineConfig
-
-`StorageEngineConfig`用于设置内置状态服务的数据引擎和WAL引擎的配置参数。
-
-| Configuration Name        | Value Type | Description                                                                                                                                                                                                                                                                               |
-|---------------------------|------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
-| `type`                    | String     | Specifies the type of data engine used in the built-in storage service. Options include: rocksdb: Provides persistence functionality, allowing state to be recovered after a restart; memory: No persistence, data will be lost after a restart.                                          |
-| `dataPathRoot`            | String     | Effective when type is set to rocksdb. Specifies the directory to store data files. If configured as an absolute path, it will be directly loaded; if configured as a relative path, it will try to load from the directory specified by the `DATA_DIR` and `user.dir` system parameters. |
-| `compactMinTombstoneKeys` | Integer    | Effective when type is set to rocksdb. The number of Tombstone keys that trigger a compaction operation.                                                                                                                                                                                  |
-| `compactTombstonePercent` | Double     | Effective when type is set to rocksdb. When the number of deleted keys in a specific Range exceeds compactMinTombstoneKeys, and the proportion of deleted keys to the total exceeds compactTombstonePercent, a compaction operation will be performed on this range.                      |
-| `asyncWALFlush`           | Boolean    | Applicable only to the WAL engine, whether to enable asynchronous FlushWAL data to disk.                                                                                                                                                                                                  |
-| `fsyncWAL`                | Boolean    | Applicable only to the WAL engine. Whether to perform an fsync operation after writing to the WAL. If this flag is true, writing speed will be slower. If this flag is false, and the machine crashes, some recent writes may be lost.                                                    |
-
-## BalancerOptions
-
-`BalancerOptions`用于设置内置状态服务的负载均衡器的配置参数。
-
-| Configuration Name     | Value Type     | Default Value | Description                                                                                                                                                        |
-|------------------------|----------------|---------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------|
-| `scheduleIntervalInMs` | Long           | 5000          | The interval at which the Balancer attempts to balance the load.                                                                                                   |
-| `balancers`            | List of String |               | The fully qualified names of the balancer implementations that are enabled. Different balancer implementations can be set for different built-in storage services. |
-
-注意:调整与`StorageEngineConfig`和`BalancerOptions`相关的参数需要深入理解BifroMQ的存储引擎实现。配置不当可能导致状态存储服务的异常行为。
\ No newline at end of file
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/07_admin_guide/01_configuration/2_bifromq_sys_props.md b/i18n/zh-Hans/docusaurus-plugin-content-docs/current/07_admin_guide/01_configuration/2_bifromq_sys_props.md
deleted file mode 100644
index 6e102de9..00000000
--- a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/07_admin_guide/01_configuration/2_bifromq_sys_props.md
+++ /dev/null
@@ -1,54 +0,0 @@
----
-sidebar_position: 2
-title: "系统属性"
----
-
-在BifroMQ中调整系统属性前,需要对其内部机制有深入理解,不恰当的修改可能会引发非预期的行为。除此以外,这些系统属性与BifroMQ的内部实现紧密关联,可能会出现在不同版本中不兼容的情况。系统属性可以通过JVM启动参数进行设置,从而灵活地定制BifroMQ的行为。
-例如,通过设置`-Dmqtt_utf8_sanity_check=false`来禁用MQTT协议定义的UTF8字符串格式检查。
-
-下面表列出了当前版本支持的系统属性:
-
-| Property Key                                 | Default Value         | Description                                                                                                                                                                                                                                                                                                                                                                                                                         [...]
-|----------------------------------------------|-----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ [...]
-| `cluster_domain_resolve_timeout_seconds`     | 120                   | This parameter specifies the timeout duration for DNS resolution when constructing a cluster using the `clusterConfig.clusterDomainName`. The process involves resolving the cluster domain to discover seed nodes that can join the cluster. A successful resolution is marked by obtaining a non-empty set of IP addresses. This parameter controls the maximum amount of time allowed for this DNS resolution to complete succes [...]
-| `ingress_slowdown_direct_memory_usage`       | 0.95                  | Threshold for slowing down the acceptance of ingress traffic based on direct memory usage. When the direct memory usage exceeds this threshold, the system will begin to slow down incoming traffic to manage resource consumption effectively.                                                                                                                                                                                     [...]
-| `ingress_slowdown_heap_memory_usage`         | 0.9                   | Threshold for slowing down the acceptance of ingress traffic based on heap memory usage. When the heap memory usage exceeds this threshold, the system will initiate measures to slow down incoming traffic to prevent memory overload.                                                                                                                                                                                             [...]
-| `max_slowdown_timeout_seconds`               | 5                     | Maximum duration (in seconds) that the slowdown mechanism is allowed to operate before further backpressure protection measures are taken. This ensures that if the slowdown is not sufficient to manage resource usage, additional steps will be implemented to protect the system.                                                                                                                                                [...]
-| `mqtt_utf8_sanity_check`                     | false                 | Enables/disables UTF8 sanity checks according to MQTT-1.5.3.                                                                                                                                                                                                                                                                                                                                                                        [...]
-| `max_mqtt3_client_id_length`                 | 65535                 | Maximum client ID length for MQTT 3 clients.                                                                                                                                                                                                                                                                                                                                                                                        [...]
-| `max_mqtt5_client_id_length`                 | 65535                 | Maximum client ID length for MQTT 5 clients.                                                                                                                                                                                                                                                                                                                                                                                        [...]
-| `session_register_num`                       | 1000                  | Number of concurrent session registers.                                                                                                                                                                                                                                                                                                                                                                                             [...]
-| `data_plane_tolerable_latency_ms`            | 1000L                 | Tolerable latency in milliseconds for the data plane.                                                                                                                                                                                                                                                                                                                                                                               [...]
-| `data_plane_burst_latency_ms`                | 5000L                 | Burst latency in milliseconds for the data plane.                                                                                                                                                                                                                                                                                                                                                                                   [...]
-| `control_plane_tolerable_latency_ms`         | 2000L                 | Tolerable latency in milliseconds for the control plane.                                                                                                                                                                                                                                                                                                                                                                            [...]
-| `control_plane_burst_latency_ms`             | 5000L                 | Burst latency in milliseconds for the control plane.                                                                                                                                                                                                                                                                                                                                                                                [...]
-| `dist_server_dist_worker_call_queues`        | CPU cores             | Number of dist worker call queues.                                                                                                                                                                                                                                                                                                                                                                                                  [...]
-| `dist_worker_fanout_parallelism`             | Max(2, CPU cores)     | Parallelism level for fanout operations.                                                                                                                                                                                                                                                                                                                                                                                            [...]
-| `dist_worker_max_cached_subs_per_tenant`     | 200_000L              | Maximum cached subscriptions per tenant.                                                                                                                                                                                                                                                                                                                                                                                            [...]
-| `dist_worker_topic_match_expiry_seconds`     | 5                     | Expiry time in seconds for topic matches.                                                                                                                                                                                                                                                                                                                                                                                           [...]
-| `dist_worker_match_parallelism`              | Max(2, CPU cores / 2) | Parallelism level for match operations.                                                                                                                                                                                                                                                                                                                                                                                             [...]
-| `dist_worker_fanout_split_threshold`         | 100000                | Threshold for splitting fanout operations when fanout split hinter enabled.                                                                                                                                                                                                                                                                                                                                                         [...]
-| `dist_worker_split_max_cpu_usage`            | 0.8                   | Maximum CPU usage threshold for splitting operations when fanout split hinter enabled.                                                                                                                                                                                                                                                                                                                                              [...]
-| `dist_worker_load_estimation_window_seconds` | 5L                    | Time window in seconds for load estimation when fanout split hinter enabled.                                                                                                                                                                                                                                                                                                                                                        [...]
-| `dist_worker_split_io_nanos_limit`           | 30_000L               | Nanoseconds limit for I/O operations during split when fanout split hinter enabled.                                                                                                                                                                                                                                                                                                                                                 [...]
-| `dist_worker_split_max_io_density`           | 100                   | Maximum I/O density for split operations when fanout split hinter enabled.                                                                                                                                                                                                                                                                                                                                                          [...]
-| `dist_worker_range_voter_count`              | 3                     | Number of voters for range decisions.                                                                                                                                                                                                                                                                                                                                                                                               [...]
-| `dist_worker_recovery_timeout_millis`        | 10000L                | Timeout in milliseconds for worker recovery when recovery balancer enabled.                                                                                                                                                                                                                                                                                                                                                         [...]
-| `inbox_deliverers`                           | 100                   | Number of inbox deliverers.                                                                                                                                                                                                                                                                                                                                                                                                         [...]
-| `inbox_fetch_queues_per_range`               | Max(1, CPU cores / 4) | Number of fetch queues per range.                                                                                                                                                                                                                                                                                                                                                                                                   [...]
-| `inbox_check_queues_per_range`               | 1                     | Number of check queues per range.                                                                                                                                                                                                                                                                                                                                                                                                   [...]
-| `inbox_store_load_estimation_window_seconds` | 5L                    | Time window in seconds for load estimation in inbox store.                                                                                                                                                                                                                                                                                                                                                                          [...]
-| `inbox_store_range_split_limit`              | Max(1, CPU cores / 4) | Range split will stop when local inbox store hits the limit.                                                                                                                                                                                                                                                                                                                                                                        [...]
-| `inbox_store_range_split_max_cpu_usage`      | 0.8                   | Maximum CPU usage threshold for range split in inbox store.                                                                                                                                                                                                                                                                                                                                                                         [...]
-| `inbox_store_range_split_io_nanos_limit`     | 30_000                | Nanoseconds limit for I/O operations during range split in inbox store.                                                                                                                                                                                                                                                                                                                                                             [...]
-| `inbox_store_range_split_max_io_density`     | 100                   | Maximum I/O density for range split operations in inbox store.                                                                                                                                                                                                                                                                                                                                                                      [...]
-| `inbox_store_range_voter_count`              | 1                     | Number of voters for range decisions in inbox store.                                                                                                                                                                                                                                                                                                                                                                                [...]
-| `inbox_store_recovery_timeout_millis`        | 10000L                | Timeout in milliseconds for inbox store recovery.                                                                                                                                                                                                                                                                                                                                                                                   [...]
-| `mqtt_deliverers_per_server`                 | CPU cores             | Number of MQTT deliverers per server.                                                                                                                                                                                                                                                                                                                                                                                               [...]
-| `retain_store_range_split_limit`             | Max(1, CPU cores / 4) | Range split will stop when local retain store hits the limit.                                                                                                                                                                                                                                                                                                                                                                       [...]
-| `retain_store_range_split_max_cpu_usage`     | 0.8                   | Maximum CPU usage threshold for range split in retain store.                                                                                                                                                                                                                                                                                                                                                                        [...]
-| `retain_store_range_split_io_nanos_limit`    | 30_000L               | Nanoseconds limit for I/O operations during range split in retain store.                                                                                                                                                                                                                                                                                                                                                            [...]
-| `retain_store_range_split_max_io_density`    | 100                   | Maximum I/O density for range split operations in retain store.                                                                                                                                                                                                                                                                                                                                                                     [...]
-| `retain_store_range_voter_count`             | 3                     | Number of voters for range decisions in retain store.                                                                                                                                                                                                                                                                                                                                                                               [...]
-| `retain_store_load_est_window_seconds`       | 5L                    | Time window in seconds for load estimation in retain store.                                                                                                                                                                                                                                                                                                                                                                         [...]
-| `retain_store_recovery_timeout_millis`       | 10000L                | Timeout in milliseconds for retain store recovery.                                                                                                                                                                                                                                                                                                                                                                                  [...]
\ No newline at end of file
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/07_admin_guide/01_configuration/3_configs_print.md b/i18n/zh-Hans/docusaurus-plugin-content-docs/current/07_admin_guide/01_configuration/3_configs_print.md
deleted file mode 100644
index 1c7a6dc2..00000000
--- a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/07_admin_guide/01_configuration/3_configs_print.md
+++ /dev/null
@@ -1,88 +0,0 @@
----
-sidebar_position: 3
-title: "配置输出"
----
-
-当BifroMQ启动时,它会在信息日志中打印各种配置的值。打印配置信息有助于您了解BifroMQ服务的具体设置,便于故障排除。当在社区寻求帮助时,也建议包括打印出的配置信息。
-
-有关如何查看日志的信息,请参阅:[日志记录](../03_observability/01_logging.md)
-
-## 输出内容
-日志中输出的配置信息主要由四个部分组成:
-
-### JVM 参数
-
-JVM参数指的是使用-D参数启动BifroMQ时传递给JVM的参数。输出的示例如下:
-
-```text
-15:21:46.890 [main] INFO c.b.b.starter.StandaloneStarter - JVM arguments:
--Xms1045m
--Xmx4096m
--Xlog:gc:file=/usr/share/bifromq-standalone/bin/../logs/gc-%t.log:time,tid,tags:filecount=5,filesize=50m
--DLOG_DIR=/usr/share/bifromq-standalone/bin/../logs
--DCONF_DIR=/usr/share/bifromq-standalone/bin/../conf
--DDATA_DIR=/usr/share/bifromq-standalone/bin/../data
--Dpf4j.pluginsDir=/usr/share/bifromq-standalone/bin/../plugins
--Dfile.encoding=UTF-8
-```
-
-### [Setting](../../06_plugin/4_setting_provider/intro.md)的初始值
-
-有关设置及其初始值的信息,请参阅:[Setting Provider Plugin](../../06_plugin/4_setting_provider/intro.md)。
-
-需要注意的是,这里打印的值代表了BifroMQ启动时设置的初始值。这些值可以在运行时通过您的自定义设置提供者插件进行修改,因此这里打印的值可能不一定是实际的运行时值。输出的示例如下:
-
-```text
-15:21:46.890 [main] INFO c.b.b.starter.StandaloneStarter - Settings, which can be modified at runtime, allowing for dynamic adjustment of BifroMQ's service behavior per tenant. See https://bifromq.io/docs/plugin/setting_provider/
-15:21:46.890 [main] INFO c.b.b.starter.StandaloneStarter - Following is the initial value of each setting:
-15:21:46.913 [main] INFO c.b.b.starter.StandaloneStarter - Setting: DebugModeEnabled=false
-15:21:46.913 [main] INFO c.b.b.starter.StandaloneStarter - Setting: MaxTopicLevelLength=40
-15:21:46.913 [main] INFO c.b.b.starter.StandaloneStarter - Setting: MaxTopicLevels=16
-15:21:46.913 [main] INFO c.b.b.starter.StandaloneStarter - Setting: MaxTopicLength=255
-15:21:46.913 [main] INFO c.b.b.starter.StandaloneStarter - Setting: MaxSharedGroupMembers=200
-15:21:46.913 [main] INFO c.b.b.starter.StandaloneStarter - Setting: MaxTopicFiltersPerInbox=100
-15:21:46.913 [main] INFO c.b.b.starter.StandaloneStarter - Setting: MsgPubPerSec=200
-...
-```
-
-### BifroMQ[系统属性](./2_bifromq_sys_props.md)
-
-输出的示例如下:
-
-```text
-17:21:34.067 [main] INFO  c.b.b.starter.StandaloneStarter - BifroMQ system properties: 
-17:21:34.070 [main] INFO  c.b.b.starter.StandaloneStarter - BifroMQSysProp: mqtt_utf8_sanity_check=false
-17:21:34.070 [main] INFO  c.b.b.starter.StandaloneStarter - BifroMQSysProp: max_client_id_length=65535
-17:21:34.070 [main] INFO  c.b.b.starter.StandaloneStarter - BifroMQSysProp: session_register_num=1000
-17:21:34.070 [main] INFO  c.b.b.starter.StandaloneStarter - BifroMQSysProp: data_plane_tolerable_latency_ms=100
-17:21:34.070 [main] INFO  c.b.b.starter.StandaloneStarter - BifroMQSysProp: data_plane_burst_latency_ms=1000
-17:21:34.070 [main] INFO  c.b.b.starter.StandaloneStarter - BifroMQSysProp: control_plane_tolerant_latency_ms=200
-17:21:34.070 [main] INFO  c.b.b.starter.StandaloneStarter - BifroMQSysProp: control_plane_burst_latency_ms=5000
-...
-```
-
-### BifroMQ Configuration File
-
-配置文件部分会包含整合后完整的配置文件内容,输出的示例如下:
-
-```text
-17:21:34.098 [main] INFO  c.b.b.starter.StandaloneStarter - Consolidated Config: 
----
-bootstrap: true
-clusterConfig:
-  env: "Test"
-  host: "127.0.0.1"
-  port: 0
-mqttServerConfig:
-  connTimeoutSec: 20
-  maxConnPerSec: 2000
-  maxDisconnPerSec: 1000
-  maxMsgByteSize: 262144
-  maxResendTimes: 5
-  maxConnBandwidth: 524288
-  defaultKeepAliveSec: 300
-  qos2ConfirmWindowSec: 5
-  bossELGThreads: 1
-  workerELGThreads: 4
-...
-```
\ No newline at end of file
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/07_admin_guide/01_configuration/_category_.json b/i18n/zh-Hans/docusaurus-plugin-content-docs/current/07_admin_guide/01_configuration/_category_.json
deleted file mode 100644
index 6c670ff4..00000000
--- a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/07_admin_guide/01_configuration/_category_.json
+++ /dev/null
@@ -1,8 +0,0 @@
-{
-  "label": "Configuration",
-  "position": 1,
-  "link": {
-    "type": "doc",
-    "id": "admin_guide/configuration/intro"
-  }
-}
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/07_admin_guide/01_configuration/intro.md b/i18n/zh-Hans/docusaurus-plugin-content-docs/current/07_admin_guide/01_configuration/intro.md
deleted file mode 100644
index 20509f91..00000000
--- a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/07_admin_guide/01_configuration/intro.md
+++ /dev/null
@@ -1,11 +0,0 @@
----
-id: "intro"
-sidebar_position: 0 
-title: "配置概述"
----
-
-根据不同的使用场景,BifroMQ将配置分为系统级和租户级。系统级配置在系统启动时设置,并且之后不能更改。相比之下,租户级配置可以根据需要在运行时动态调整,其初始值也可以在系统启动时自定义。租户级设置的能力需要实现一个自定义的[Setting Provider](../../06_plugin/4_setting_provider/intro.md)插件,本章不涵盖此内容。
-
-系统级配置根据它们的常用性、是否处于实验阶段或是否未最终确定等标准进行分类。它们可以通过[配置文件](1_config_file_manual.md)(位于conf目录的standalone.yml中)或通过JVM系统[属性](2_bifromq_sys_props.md)(以-D`conf`=`value`的格式)提供。
-
-配置文件通常包含常见且相对稳定的配置项,而其他设置则通过JVM系统属性提供。因此,随着版本更新,系统级配置的内容和方法可能会发生变化。为简化系统级配置的迁移过程,BifroMQ提供了辅助手段,详细信息可在[配置约定与迁移](../../02_installation/5_config_migration.md)中找到。
\ No newline at end of file
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/07_admin_guide/02_tuning/1_os_tuning_linux.md b/i18n/zh-Hans/docusaurus-plugin-content-docs/current/07_admin_guide/02_tuning/1_os_tuning_linux.md
deleted file mode 100644
index d1f27bbe..00000000
--- a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/07_admin_guide/02_tuning/1_os_tuning_linux.md
+++ /dev/null
@@ -1,58 +0,0 @@
----
-sidebar_position: 2 
-title: "Linux Kernel Tuning"
----
-
-The following Kernel parameters can affect the maximum number of connections that the machine hosting BifroMQ can accept.
-
-## Memory
-
-* vm.max_map_count: Limits the number of VMAs (Virtual Memory Areas) that a process can have. It can be increased to 221184.
-
-## Maximum Open Files
-
-* nofile: Specifies the maximum number of files that a single process can open.
-* nr_open: Specifies the maximum number of files that can be allocated per process, usually defaulting to 1024 * 1024 = 1048576.
-* file-max: Specifies the maximum number of files that the system kernel can open, with a default value of 185745.
-
-## Max user processes
-* nproc: Indicates the maximum number of processes that a single user can launch. For Java processes, each thread will also occupy a Linux proc resource. In certain versions, for non-root users, this parameter defaults to 4096 and may need to be appropriately increased.
-
-## NetFilter Tuning
-
-Use `sysctl -a | grep conntrack` to view the current parameters. The following parameters determine the maximum number of connections:
-
-* net.netfilter.nf_conntrack_buckets: The size of the hashtable buckets that record connection entries.
-  * Modification command: `echo 262144 > /sys/module/nf_conntrack/parameters/hashsize`
-* net.netfilter.nf_conntrack_max: The maximum number of entries in the hashtable, generally equal to nf_conntrack_buckets * 4.
-* net.nf_conntrack_max: Same as net.netfilter.nf_conntrack_max.
-* net.netfilter.nf_conntrack_tcp_timeout_fin_wait: Default 120s -> Recommended 30s.
-* net.netfilter.nf_conntrack_tcp_timeout_time_wait: Default 120s -> Recommended 30s.
-* net.netfilter.nf_conntrack_tcp_timeout_close_wait: Default 60s -> Recommended 15s.
-* net.netfilter.nf_conntrack_tcp_timeout_established: Default 432000 seconds (5 days) -> Recommended 300s.
-
-The following sysctl parameters can affect the performance of TCP channels under high load:
-
-## Server-Side and Load Testing TCP-related Tuning
-
-It is recommended to use the CentOS 7 and above environment for deployment and stress testing.
-
-For CentOS 6, system parameter tuning is required:
-* net.core.wmem_max: Maximum TCP data send window size (bytes).
-  * Modification command: `echo 'net.core.wmem_max=16777216' >> /etc/sysctl.conf`
-* net.core.wmem_default: Default TCP data send window size (bytes).
-  * Modification command: `echo 'net.core.wmem_default=262144' >> /etc/sysctl.conf`
-* net.core.rmem_max: Maximum TCP data receive window size (bytes).
-  * Modification command: `echo 'net.core.rmem_max=16777216' >> /etc/sysctl.conf`
-* net.core.rmem_default: Default TCP data receive window size (bytes).
-  * Modification command: `echo 'net.core.rmem_default=262144' >> /etc/sysctl.conf`
-* net.ipv4.tcp_rmem: Memory usage of the socket receive buffer - minimum, warning, maximum.
-  * Modification command: `echo 'net.ipv4.tcp_rmem= 1024 4096 16777216' >> /etc/sysctl.conf`
-* net.ipv4.tcp_wmem: Memory usage of the socket send buffer - minimum, warning, maximum.
-  * Modification command: `echo 'net.ipv4.tcp_wmem= 1024 4096 16777216' >> /etc/sysctl.conf`
-* net.core.optmem_max: The maximum buffer size (in bytes) allowed for each socket.
-  * Modification command: `echo 'net.core.optmem_max = 16777216' >> /etc/sysctl.conf`
-* net.core.netdev_max_backlog: The length of the queue into which network device places requests.
-  * Modification command:`echo 'net.core.netdev_max_backlog = 16384' >> /etc/sysctl.conf`
-
-After making the modifications, use `sysctl -p` and restart the server for them to take effect.
\ No newline at end of file
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/07_admin_guide/02_tuning/_category_.json b/i18n/zh-Hans/docusaurus-plugin-content-docs/current/07_admin_guide/02_tuning/_category_.json
deleted file mode 100644
index 7c1f220a..00000000
--- a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/07_admin_guide/02_tuning/_category_.json
+++ /dev/null
@@ -1,8 +0,0 @@
-{
-  "label": "Tuning",
-  "position": 2,
-  "link": {
-    "type": "doc",
-    "id": "admin_guide/tuning/intro"
-  }
-}
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/07_admin_guide/02_tuning/intro.md b/i18n/zh-Hans/docusaurus-plugin-content-docs/current/07_admin_guide/02_tuning/intro.md
deleted file mode 100644
index 362842ee..00000000
--- a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/07_admin_guide/02_tuning/intro.md
+++ /dev/null
@@ -1,29 +0,0 @@
----
-id: "intro"
-sidebar_position: 1
-title: "调优概述"
----
-
-BifroMQ性能调优需要从运行环境和针对工作负载的特定优化两方面入手。
-
-## 运行环境调优
-BifroMQ的性能优化起点是其运行环境的调整。这方面的调整通常依赖于托管环境供应商的技术能力与建议。举个例子,当BifroMQ部署在Linux操作系统上时,有一些系统级的调优[选择](../02_tuning/1_os_tuning_linux.md)能够对性能产生显著的影响:
-
-- **网络堆栈调优**:通过调整TCP的设置,比如缓冲区的大小、积压设置以及启用TCP快速开启功能,可以降低延迟并增加吞吐量。
-- **文件描述符限制**:提高文件描述符的上限能够避免因大量并发连接而导致的瓶颈。
-- **磁盘I/O优化**:在需要大量数据持久化的部署中,优化磁盘I/O设置和选择合适的文件系统能够加快消息的存储与检索速度。
-
-深入了解并应用这些调优措施,可以显著提升BifroMQ在特定环境下的性能表现。具体内容,请参考运行环境的优化指导手册。
-
-
-## 针对工作负载的调优
-
-BifroMQ专门处理MQTT协议的各种工作负载,每种工作负载都具有独特的特征和优化需求。高效地调优这些工作负载首先需要对您的应用程序产生的MQTT流量模式进行详细分析。通过这种分析,可以 pinpoint 出需要优化的关键领域,例如消息吞吐量、客户端连接处理、会话持久化以及主题订阅管理等。BifroMQ从设计之初就考虑到了这些需求,提供了一系列专门的机制和配置选项,用以优化MQTT工作负载的各个方面。
-
-针对工作负载调优的关键领域主要包括:
-
-- **连接和会话管理**:通过优化客户端连接和会话状态相关的参数,BifroMQ能够更高效地处理大量并发客户端连接。
-- **消息吞吐量和QoS处理**:调整消息队列大小、消息重传机制以及QoS等级处理的配置,有助于提升消息处理的吞吐量和交付的可靠性。
-- **订阅和主题匹配**:微调订阅管理和主题匹配机制,能够使消息更快速、更准确地被路由至正确的客户端。
-
-要有效地调优这些代理的方面,对BifroMQ的系统架构有深入的了解是必不可少的。[BifroMQ团队](mailto:hello@bifromq.io)提供专业的咨询服务,帮助您分析特定的MQTT工作负载并识别出最有效的调优策略。通过这些专业的建议和服务,您可以确保BifroMQ部署的优化,以获得最佳性能,满足您的业务需求。
\ No newline at end of file
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/07_admin_guide/03_observability/01_logging.md b/i18n/zh-Hans/docusaurus-plugin-content-docs/current/07_admin_guide/03_observability/01_logging.md
deleted file mode 100644
index 0fe360aa..00000000
--- a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/07_admin_guide/03_observability/01_logging.md
+++ /dev/null
@@ -1,18 +0,0 @@
----
-sidebar_position: 1
-title: "Logging"
----
-
-BifroMQ采用标准的SLF4J接口进行日志记录,并选择Logback作为其日志后端。日志被组织成五个不同的级别:TRACE、DEBUG、INFO、WARN和ERROR,其中INFO设置为默认日志级别。
-
-### Logback配置文件
-
-Logback配置文件名为`logback.xml`,位于BifroMQ安装文件夹内的`conf`目录中。该文件允许对日志行为进行详细自定义,包括日志级别设置、输出格式和文件轮转策略。
-
-### 日志目录
-
-默认情况下,BifroMQ将日志文件存储在安装文件夹中的`log`目录。如有必要,可以通过设置`LOG_DIR`环境变量来指定一个替代的日志目录。
-
-### 插件日志
-
-插件开发者也可以利用标准的SLF4J接口进行日志记录。这意味着插件生成的日志可以通过相同的Logback配置文件进行管理和配置,就像主系统日志一样。这种统一的日志处理方法简化了日志文件的管理,并确保了系统及其扩展功能之间的一致性。
\ No newline at end of file
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/07_admin_guide/03_observability/03_events.md b/i18n/zh-Hans/docusaurus-plugin-content-docs/current/07_admin_guide/03_observability/03_events.md
deleted file mode 100644
index 3cc76c52..00000000
--- a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/07_admin_guide/03_observability/03_events.md
+++ /dev/null
@@ -1,21 +0,0 @@
----
-sidebar_position: 3 
-title: "Events"
----
-
-BifroMQ在其工作流程中的关键节点生成事件,为用户提供了实现自定义事件收集插件以捕获和处理这些事件的能力。
-
-## 事件收集与使用
-
-在BifroMQ中实现事件收集插件可以收集系统生成的事件,然后在各种业务场景中使用这些事件。虽然BifroMQ没有规定这些事件的具体用途,但常见的应用包括计费、风险管理、实时诊断等。
-
-## 演示和参考实现
-
-为了帮助用户开发自己的事件收集解决方案,BifroMQ提供了DemoPlugin,其中包含[EventLogger](https://github.com/bifromqio/bifromq/blob/main/build/build-plugin-demo/src/main/java/com/baidu/demo/plugin/EventLogger.java)作为EventCollector实现的示例。
-
-## 接口稳定性与实施指导
-
-虽然事件对象是事件收集插件接口的重要组成部分,但由于它们与BifroMQ内部机制紧密相关,其稳定性被认为相对较低。鉴于此,建议插件开发者确保他们的实现与他们基于的接口定义版本保持同步。为了避免兼容性问题,应避免在BifroMQ中跨不同接口版本部署插件。
-
-## 插件开发最佳实践
-对于那些有兴趣通过插件开发扩展BifroMQ功能的人,包括事件收集,更多的指导和最佳实践可以在相关[章节](../../06_plugin/5_plugin_practice.md)中找到。
\ No newline at end of file
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/07_admin_guide/03_observability/_category_.json b/i18n/zh-Hans/docusaurus-plugin-content-docs/current/07_admin_guide/03_observability/_category_.json
deleted file mode 100644
index 10c8f478..00000000
--- a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/07_admin_guide/03_observability/_category_.json
+++ /dev/null
@@ -1,8 +0,0 @@
-{
-  "label": "可观察性",
-  "position": 3,
-  "link": {
-    "type": "doc",
-    "id" : "admin_guide/observability/intro"
-  }
-}
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/07_admin_guide/03_observability/intro.md b/i18n/zh-Hans/docusaurus-plugin-content-docs/current/07_admin_guide/03_observability/intro.md
deleted file mode 100644
index 401c5c32..00000000
--- a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/07_admin_guide/03_observability/intro.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-id: "intro"
-sidebar_position: 0 
-title: "可观察性概述"
----
-
-在管理BifroMQ时,全面了解系统的运行状况是实现有效管理和维护的关键。BifroMQ作为一个能够处理多租户场景的MQTT代理,其可观察性功能不仅对日常运维非常有帮助,而且对于管理复杂的多租户环境尤为重要。本节主要介绍BifroMQ在可观察性方面的核心要素:日志记录、度量指标和事件监控,并特别强调这些功能如何适应和支持多租户环境。
\ No newline at end of file
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/07_admin_guide/03_observability/metrics/_category_.json b/i18n/zh-Hans/docusaurus-plugin-content-docs/current/07_admin_guide/03_observability/metrics/_category_.json
deleted file mode 100644
index fe902e03..00000000
--- a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/07_admin_guide/03_observability/metrics/_category_.json
+++ /dev/null
@@ -1,8 +0,0 @@
-{
-  "label": "Metrics",
-  "position": 2,
-  "link": {
-    "type": "doc",
-    "id": "admin_guide/observability/metrics/intro"
-  }
-}
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/07_admin_guide/03_observability/metrics/intro.md b/i18n/zh-Hans/docusaurus-plugin-content-docs/current/07_admin_guide/03_observability/metrics/intro.md
deleted file mode 100644
index 725ba9ab..00000000
--- a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/07_admin_guide/03_observability/metrics/intro.md
+++ /dev/null
@@ -1,21 +0,0 @@
----
-id: "intro"
-sidebar_position: 0
-title: "Metrics概述"
----
-
-BifroMQ采用[Micrometer](https://micrometer.io/)作为其Metrics收集框架,类似于其使用SLF4J和Logback进行日志记录。Micrometer在BifroMQ中充当“Metrics的SLF4J”,虽然Micrometer便于收集Metrics,但它并不将用户绑定到特定的Metrics收集后端。相反,用户可以自由选择他们偏好的监控系统,并可以通过BifroMQ的插件机制将Metrics导向该系统。
-
-## 通过DemoPlugin集成Prometheus
-
-BifroMQ通过其捆绑的[DemoPlugin](https://github.com/bifromqio/bifromq/blob/main/build/build-plugin-demo/src/main/java/com/baidu/demo/plugin/DemoPlugin.java)提供了对Prometheus的开箱即用支持,BifroMQ暴露了一个Prometheus采集端点(`http://<BIFROMQ_NODE_HOST>:9090/metrics`),允许Prometheus直接抓取Metrics。
-
-## 面向多租户的租户级Metrics
-
-BifroMQ引入了一套租户级[Metrics](tenantmetrics.md)。通过收集和聚合,可以实时反映了单个租户的资源使用和活动情况。当与[Resource Throttler](../../../06_plugin/3_resource_throttler.md)结合使用时,租户级Metrics有助于实现有效的负载隔离策略。
-
-## 高级诊断和调优
-
-除了租户级洞察之外,BifroMQ从其各个功能模块收集了广泛的内部Metrics。这些Metrics对于深度系统调优和运行时诊断是不可或缺的。然而,由于这些深度Metrics与BifroMQ的内部机制和架构密切相关,它们可能会在BifroMQ版本之间有所变化,并且不保证在更新中保持一致。因此,为了避免兼容性问题,这些度量并未作为一般用途文档化。
-
-对于深度使用需要深入了解BifroMQ运作机制的客户,[BifroMQ团队](mailto:hello@bifromq.io)提供专业咨询服务。
\ No newline at end of file
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/07_admin_guide/03_observability/metrics/tenantmetrics.md b/i18n/zh-Hans/docusaurus-plugin-content-docs/current/07_admin_guide/03_observability/metrics/tenantmetrics.md
deleted file mode 100644
index f841eafb..00000000
--- a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/07_admin_guide/03_observability/metrics/tenantmetrics.md
+++ /dev/null
@@ -1,60 +0,0 @@
----
-sidebar_position: 1 
-title: "租户级Metrics"
----
-
-以下表格详细介绍了BifroMQ租户级的Metrics指标,包括其在Micrometer中的Metrics名称、所使用的Meter类型,以及每项指标测量内容的简要说明。需要注意的是,这些Metrics指标在收集后端的命名可能会因所采用的Collector不同而有所变化。若需了解详细的映射关系,请参考Micrometer的官方文档。
-
-| Metric Name                    | Meter Type           | Description                                          |
-|--------------------------------|----------------------|------------------------------------------------------|
-| `mqtt.connection.num.gauge`    | GAUGE                | Current number of MQTT connections.                  |
-| `mqtt.auth.failure.count`      | COUNTER              | the counter of authentication failures.              |
-| `mqtt.connect.count`           | COUNTER              | The counter of MQTT connect.                         |
-| `mqtt.disconnect.count`        | COUNTER              | the counter of MQTT disconnect.                      |
-| `mqtt.session.mem.gauge`       | GAUGE                | Memory usage by MQTT sessions.                       |
-| `mqtt.psession.space.gauge`    | GAUGE                | Storage space used by persistent MQTT sessions.      |
-| `mqtt.psession.live.num.gauge` | GAUGE                | Number of live persistent MQTT sessions.             |
-| `mqtt.psession.num.gauge`      | GAUGE                | Total number of persistent MQTT sessions.            |
-| `mqtt.ingress.bytes`           | DISTRIBUTION_SUMMARY | Bytes received by the broker.                        |
-| `mqtt.egress.bytes`            | DISTRIBUTION_SUMMARY | Bytes sent from the broker.                          |
-| `mqtt.channel.latency`         | TIMER                | Latency of network channels.                         |
-| `mqtt.ingress.qos0.bytes`      | DISTRIBUTION_SUMMARY | Bytes received for QoS 0 messages.                   |
-| `mqtt.qos0.dist.bytes`         | DISTRIBUTION_SUMMARY | Distribution of QoS 0 message bytes.                 |
-| `mqtt.ingress.qos1.bytes`      | DISTRIBUTION_SUMMARY | Bytes received for QoS 1 messages.                   |
-| `mqtt.qos1.dist.bytes`         | DISTRIBUTION_SUMMARY | Distribution of QoS 1 message bytes.                 |
-| `mqtt.ingress.qos2.bytes`      | DISTRIBUTION_SUMMARY | Bytes received for QoS 2 messages.                   |
-| `mqtt.qos2.dist.bytes`         | DISTRIBUTION_SUMMARY | Distribution of QoS 2 message bytes.                 |
-| `mqtt.egress.qos0.bytes`       | DISTRIBUTION_SUMMARY | Bytes sent from broker for QoS 0 messages.           |
-| `mqtt.egress.qos1.bytes`       | DISTRIBUTION_SUMMARY | Bytes sent from broker for QoS 1 messages.           |
-| `mqtt.deliver.qos1.bytes`      | DISTRIBUTION_SUMMARY | Bytes delivered for QoS 1 messages.                  |
-| `mqtt.egress.qos2.bytes`       | DISTRIBUTION_SUMMARY | Bytes sent from broker for QoS 2 messages.           |
-| `mqtt.deliver.qos2.bytes`      | DISTRIBUTION_SUMMARY | Bytes delivered for QoS 2 messages.                  |
-| `mqtt.in.qos0.latency`         | TIMER                | Internal latency for QoS 0 message processing.       |
-| `mqtt.in.qos1.latency`         | TIMER                | Internal latency for QoS 1 message processing.       |
-| `mqtt.ex.qos1.latency`         | TIMER                | External latency for QoS 1 message delivery.         |
-| `mqtt.in.qos2.latency`         | TIMER                | Internal latency for QoS 2 message processing.       |
-| `mqtt.ex.qos2.latency`         | TIMER                | External latency for QoS 2 message delivery.         |
-| `mqtt.tfanout.bytes`           | DISTRIBUTION_SUMMARY | Bytes fanned out for transient messages.             |
-| `mqtt.pfanout.bytes`           | DISTRIBUTION_SUMMARY | Bytes fanned out for persistent messages.            |
-| `mqtt.route.space.gauge`       | GAUGE                | Space used for message routing.                      |
-| `mqtt.shared.sub.num.gauge`    | GAUGE                | Number of shared subscriptions.                      |
-| `mqtt.tsub.count`              | COUNTER              | Count of transient subscriptions.                    |
-| `mqtt.tsub.latency`            | TIMER                | Latency in handling transient subscriptions.         |
-| `mqtt.psub.count`              | COUNTER              | Count of persistent subscriptions.                   |
-| `mqtt.psub.latency`            | TIMER                | Latency in handling persistent subscriptions.        |
-| `mqtt.tunsub.count`            | COUNTER              | Count of transient unsubscriptions.                  |
-| `mqtt.tunsub.latency`          | TIMER                | Latency in handling transient unsubscriptions.       |
-| `mqtt.punsub.count`            | COUNTER              | Count of persistent unsubscriptions.                 |
-| `mqtt.punsub.latency`          | TIMER                | Latency in handling persistent unsubscriptions.      |
-| `mqtt.tsub.num.gauge`          | GAUGE                | Number of transient subscriptions currently active.  |
-| `mqtt.psub.num.gauge`          | GAUGE                | Number of persistent subscriptions currently active. |
-| `mqtt.ingress.retain.bytes`    | DISTRIBUTION_SUMMARY | Bytes received for retained messages.                |
-| `mqtt.retained.bytes`          | DISTRIBUTION_SUMMARY | Total bytes of retained messages stored.             |
-| `mqtt.retained.num.gauge`      | GAUGE                | Number of retained messages stored.                  |
-| `mqtt.retain.match.count`      | COUNTER              | Count of retained message matches.                   |
-| `mqtt.retain.matched.bytes`    | DISTRIBUTION_SUMMARY | Bytes of retained messages delivered after matching. |
-| `mqtt.retain.space.gauge`      | GAUGE                | Space used for storing retained messages.            |
-
-* **Internal** latency measures the time between the broker receiving a message and the broker sending the message to subscribing clients.
-* **External** latency measures the time between the broker sending the message to subscribing clients and the broker got the acknowledgement from clients, so it's only applied to QoS1 messages(when PubAck received) and QoS2 messages(when
-  PubComp received).
\ No newline at end of file
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/07_admin_guide/04_security/_category_.json b/i18n/zh-Hans/docusaurus-plugin-content-docs/current/07_admin_guide/04_security/_category_.json
deleted file mode 100644
index c39ac213..00000000
--- a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/07_admin_guide/04_security/_category_.json
+++ /dev/null
@@ -1,8 +0,0 @@
-{
-  "label": "Security",
-  "position": 4,
-  "link": {
-    "type": "doc",
-    "id": "admin_guide/security/intro"
-  }
-}
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/07_admin_guide/04_security/intro.md b/i18n/zh-Hans/docusaurus-plugin-content-docs/current/07_admin_guide/04_security/intro.md
deleted file mode 100644
index 438452ce..00000000
--- a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/07_admin_guide/04_security/intro.md
+++ /dev/null
@@ -1,25 +0,0 @@
----
-sidebar_position: 0 
-title: "安全概述"
----
-
-安全性对于任何系统都是重要的考虑因素,BifroMQ在设计时充分考虑了这一点。为确保部署的安全,BifroMQ提供了一系列安全功能,包括集群隔离、客户端认证和恶意客户端行为的风险管理。
-
-## 集群隔离与节点间的安全通信
-
-### 分布式集群构建
-BifroMQ采用分布式方式构建集群,节点只需向任何现有集群成员发送`join`请求即可加入。为避免操作失误导致意外的集群合并,BifroMQ允许在[配置文件](../01_configuration/1_config_file_manual.md)中设置“集群环境”,以逻辑上隔离不同用途的集群。
-
-### 节点间的安全通信
-BifroMQ节点间的通信主要通过`base-cluster`的P2P通信和`base-rpc`的RPC通信完成。这两种通信方式都支持配置绑定地址和端口,进一步增强了对防火墙规则的控制。特别地,base-rpc支持TLS配置,确保了节点间RPC通信的端到端安全。
-
-## 客户端认证与授权
-
-### Auth Provider
-BifroMQ处理客户端安全问题,包括认证(确认客户端身份)和授权(授予执行各类操作的权限)。为此,BifroMQ使用[Auth Provider](../../06_plugin/1_auth_provider.md)来统一管理客户端安全。
-
-### 安全的通信
-BifroMQ支持通过TLS和WSS进行的MQTT通信,确保客户端与代理之间的安全交流。企业可以根据自身安全需求选择单向或双向认证。在双向认证场景下,插件实现可以获取证书全文,有助于管理大规模客户端证书的生命周期。
-
-## 不良行为客户端风险管理
-识别并管理违反协议标准或过度消耗系统资源的不良行为客户端对于维护系统完整性至关重要,尤其是在大型多租户MQTT部署中。BifroMQ通过Event Collector插件进行实时事件收集和分析,以此应对挑战。通过识别恶意行为并在Auth Provider插件中集成风控策略,BifroMQ使得管理员能够有效地阻止违规客户端的访问。尽管这些策略的实施超出了BifroMQ核心功能的范畴,但[BifroMQ团队](mailto:hello@bifromq.io)为面临类似挑战的用户提供专业咨询服务。
\ No newline at end of file
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/07_admin_guide/_category_.json b/i18n/zh-Hans/docusaurus-plugin-content-docs/current/07_admin_guide/_category_.json
deleted file mode 100644
index 42000548..00000000
--- a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/07_admin_guide/_category_.json
+++ /dev/null
@@ -1,8 +0,0 @@
-{
-  "label": "Administration",
-  "position": 7,
-  "link": {
-    "type": "doc",
-    "id": "admin_guide/overview"
-  }
-}
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/07_admin_guide/intro.md b/i18n/zh-Hans/docusaurus-plugin-content-docs/current/07_admin_guide/intro.md
deleted file mode 100644
index 019028bb..00000000
--- a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/07_admin_guide/intro.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-id: "overview"
-sidebar_position: 0 
-title: "管理概述"
----
-
-BifroMQ的管理包含两个层次:系统级管理和租户级管理。前者主要针对系统管理员和运维人员,而租户级管理需求大多需要与具体的业务结合,因此更多提现在被集成的能力上。
\ No newline at end of file
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/98_mqtt_best_practices/1_spec.md b/i18n/zh-Hans/docusaurus-plugin-content-docs/current/98_mqtt_best_practices/1_spec.md
deleted file mode 100644
index 415ea07b..00000000
--- a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/98_mqtt_best_practices/1_spec.md
+++ /dev/null
@@ -1,11 +0,0 @@
----
-id: "mqtt"
-sidebar_position: 1
-title: "支持的规范"
----
-
-BifroMQ完全支持以下MQTT规范:
-
-* [MQTT 3.1](https://public.dhe.ibm.com/software/dw/webservices/ws-mqtt/mqtt-v3r1.html)
-* [MQTT 3.1.1](http://docs.oasis-open.org/mqtt/mqtt/v3.1.1/os/mqtt-v3.1.1-os.html)
-* [MQTT 5.0](https://docs.oasis-open.org/mqtt/mqtt/v5.0/os/mqtt-v5.0-os.html) 
\ No newline at end of file
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/98_mqtt_best_practices/2_about_mqtt.md b/i18n/zh-Hans/docusaurus-plugin-content-docs/current/98_mqtt_best_practices/2_about_mqtt.md
deleted file mode 100644
index 8724f445..00000000
--- a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/98_mqtt_best_practices/2_about_mqtt.md
+++ /dev/null
@@ -1,64 +0,0 @@
----
-sidebar_position: 2
-title: "关于MQTT"
----
-
-## 为什么在物联网中使用 MQTT 协议?与 HTTP 协议相比有哪些优势?
-
-物联网设备通常需要发送和接收小数据包,例如传感器读数、设备状态等。MQTT(消息队列遥测传输)是一种基于发布/订阅模式的轻量级通信协议,专为低带宽
-和不可靠网络环境设计,非常适合物联网应用。
-
-与 HTTP 协议相比,MQTT 协议具有以下优势:
-
-- **更轻量级**:与 HTTP 笨重的协议头相比,MQTT 协议非常简洁,其消息体比 HTTP 小,能够减轻网络传输负担。
-- **更低功耗**:MQTT 协议的低功耗特性使其非常适合物联网设备,例如传感器、智能家居等,这些设备的电池寿命通常非常有限。
-- **更高效**:MQTT 协议采用推送方式传递消息,可以大大减少客户端和服务器之间的通信开销。同时,MQTT 协议的 QoS 机制还能确保消息的可靠传输,
-  使通信更加稳定高效。
-- **更具扩展性**:MQTT 协议采用主题的发布/订阅模式,使系统具有更高的扩展性,能够快速适应新设备和应用场景。相比之下,HTTP 协议需要在服务器端
-  部署 RESTful 接口,限制了系统的扩展性。
-
-总的来说,MQTT 协议适用于需要低功耗、小数据包和高效传输的物联网设备,而 HTTP 协议更适用于需要大数据量传输和更复杂请求/响应的应用场景。
-
----
-
-## 如何处理客户端与服务器之间的异常断开?
-
-鉴于物联网设备经常工作在不稳定的网络环境中,MQTT 协议和常见的开源客户端实现对异常断开都有相应的设计和处理。
-
-请为客户端设置自动重连功能,并在客户端负责订阅主题的情况下,设置重连后自动重新订阅。
-
-如果不希望在断开期间丢失重要消息,可以在订阅设置中将 `cleanSession` 设置为 `False`。但请谨慎使用此设置,并合理设置 `topicfilter`,
-将重要消息与大量普通消息分开,仅对最必要的消息订阅使用。大量不合理使用 `cleanSession=False` 的设置会带来严重的性能压力和更大的消息丢失风险。
-
-如果出现意外的高频率断开现象,请检查从客户端到服务器的网络链接。
-
----
-
-## 为什么会出现消息丢失,订阅者未收到成功发送的消息?
-
-消息丢失可能有多种原因:
-
-- **网络不稳定导致数据包丢失**:根据物联网设备的具体网络环境,可能会发生不同程度的数据包丢失。如果需要确保消息到达,可以使用 `qos=1` 
-  设置发送和订阅消息,但这也会消耗更多性能。
-- **订阅者断开连接**:如果某个主题未被订阅,该消息会被直接丢弃。
-- **单连接收发消息超出限制**:默认情况下,单个客户端每秒限制为 200 条消息,带宽为 512MB。如果是发送方,超出限制的消息将发送失败;
-  如果是订阅者,超出限制且 `cleanSession=True` 的情况下,消息将被丢弃。
-- **消息发送频率过高导致下游溢出**:可能出现 `cleanSession=True` 下的订阅溢出、规则引擎下游溢出、`cleanSession=False` 
-  下的收件箱消息缓存溢出等情况。可以合理拆分主题,降低每个订阅者接收的消息频率,或使用共享订阅。
-- **资源不足**:如果 BifroMQ 服务部署的内存或 CPU 资源不足以支撑业务规模,也可能出现这种情况,需要合理评估和扩展业务规模。
-
----
-
-## 订阅者接收的消息顺序是否与发送顺序一致?
-
-根据 MQTT 协议,我们保证消息顺序。
-
-特别是在 QoS 0 下,单个发送者发送的消息必须按照发送顺序到达。在 QoS 1 下,由于存在消息重发的情况,可能会偶尔出现顺序混乱,但在消息重发后,
-根据协议,重发消息后的消息会再次按顺序发送,确保客户端接收的消息序列中至少有一个子序列是完全有序的。
-
----
-
-## 为什么会出现连接-断开-重连-断开的重复现象?
-
-通常是由于设备间的互相踢出导致的。`ClientID` 必须唯一,否则已经连接的冲突设备会被断开。如果两个设备都设置了自动重连,
-那么它们会不断互相踢出,从而导致此问题。
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/98_mqtt_best_practices/3_mqtt_parameters.md b/i18n/zh-Hans/docusaurus-plugin-content-docs/current/98_mqtt_best_practices/3_mqtt_parameters.md
deleted file mode 100644
index 8500f1ec..00000000
--- a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/98_mqtt_best_practices/3_mqtt_parameters.md
+++ /dev/null
@@ -1,49 +0,0 @@
----
-sidebar_position: 3
-title: "MQTT参数选择"
----
-
-MQTT 是一种轻量级消息协议,广泛应用于物联网 (IoT)、传感器网络和移动应用等领域。在使用 MQTT 建立连接时,合理选择参数可以提升通信效率和可靠性。
-
----
-
-## Client ID
-
-Client ID 是 MQTT 连接的唯一标识符。在 IoT Core 中,不同的实例彼此隔离,因此实际上由 CoreID 和 ClientID 的组合唯一标识一个客户端连接。
-
-如果多个客户端尝试使用相同的 Client ID 连接到同一个 MQTT 服务器,则只有最近的连接会被保留,其余的连接将被强制断开。
-
-在使用 MQTT 连接时,确保 Client ID 的唯一性和易于识别至关重要。一种常见的做法是使用固定前缀结合随机生成的 UUID 作为 Client ID。
-前缀可以用来标识客户端的身份或组别,而 UUID 则确保了唯一性。
-
----
-
-## QoS 等级
-
-MQTT 中的服务质量 (QoS) 等级是确保消息可靠传递的参数。MQTT 定义了三个 QoS 等级:0、1 和 2。
-
-- **QoS 0**:表示“至多一次”传递。消息发送后不需要接收方的确认,因此可能丢失。
-- **QoS 1**:表示“至少一次”传递。消息会在接收到确认之前重复发送,确保消息能够到达,但可能会出现重复消息。
-- **QoS 2**:表示“仅一次”传递,确保消息严格按照一次交付。
-
-选择更高的 QoS 等级可以提高消息传递的可靠性,但同时也会增加通信延迟、带宽消耗以及服务器资源需求。
-
-对于可以容忍偶尔丢失少量消息的场景,建议使用 QoS 等级 0。否则,可以使用 QoS 等级 1,但需要注意在部署时分配必要的资源。
-
----
-
-## Clean Session 标志位
-
-MQTT 中的 Clean Session 标志位决定了客户端与 MQTT 服务器之间的连接状态是否需要被保留。
-
-当 Clean Session 设置为 `True` 时,MQTT 服务器会清除客户端之前发布的所有消息以及与该客户端相关的连接状态信息。相反,当 Clean Session 
-设置为 `False` 时,MQTT 服务器会保留连接状态信息,以便客户端在离线期间发布的消息能被其重新连接后接收。
-
-默认情况下,建议选择 Clean Session 设置为 `True` 的连接方式。在这种设置下,消息传递速度更快,且服务器资源需求显著降低。
-对于高频率且消息数量较多的订阅,强烈建议将 Clean Session 设置为 `True`。
-
-如果某些主题的消息在订阅者离线时不允许丢失,可以将 Clean Session 设置为 `False`。但需要注意,与 Clean Session 设置为 `True` 的情况相比,
-这种设置需要显著更高的服务器性能。此外,由于中间消息的缓存,还存在消息传递延迟和消息溢出的风险。
-
-> 一般来说,应优先选择 Clean Session 设置为 `True`,仅在绝对必要时使用 Clean Session 设置为 `False`。
-> 在使用 Clean Session 设置为 `False` 时,应尽量减少消息的数量,从而获得更好的性能并降低风险。
\ No newline at end of file
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/98_mqtt_best_practices/4_topicfilter_design.md b/i18n/zh-Hans/docusaurus-plugin-content-docs/current/98_mqtt_best_practices/4_topicfilter_design.md
deleted file mode 100644
index 74979185..00000000
--- a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/98_mqtt_best_practices/4_topicfilter_design.md
+++ /dev/null
@@ -1,32 +0,0 @@
----
-sidebar_position: 4 
-title: "主题过滤器(Topic Filters)设计"
----
-
-在 MQTT 中,主题过滤器 (Topic Filters) 是一种用于订阅主题的机制,允许客户端接收其感兴趣的主题消息。在选择和设计主题过滤器时,
-可以参考以下建议:
-
----
-
-- **适当的粒度**:  
-  主题过滤器的粒度应与应用程序的需求相匹配。如果粒度过粗,客户端可能会接收到大量不必要的消息,从而增加网络流量和资源消耗;反之,如果粒度过细,
-  客户端可能无法接收到其感兴趣的消息,影响应用程序的正常运行。因此,应根据实际情况选择适当的粒度。
-
-- **考虑使用通配符**:  
-  主题过滤器支持使用通配符,包括单层通配符和多层通配符。单层通配符 `"+"` 可匹配单层中的任意字符,而多层通配符 `"#"` 可匹配
-  任意数量层级中的字符。在设计主题过滤器时,可以考虑使用通配符来简化过滤规则并扩展过滤范围。
-
-- **尽量避免使用 `"#"` 通配符**:  
-  虽然多层通配符 `"#"` 能匹配任意层级的字符,但也可能带来安全问题。如果使用 `"#"` 通配符订阅了高度敏感的主题,
-  可能会导致未经授权的客户端接收到敏感信息。因此,在设计主题过滤器时,应尽量避免使用 `"#"` 通配符。
-
-- **考虑主题命名规范**:  
-  为确保主题的可读性和可用性,采用主题命名规范是一个好习惯。主题命名规范可以规定主题的格式、约定和规则,使主题更易于管理和使用。
-
-- **考虑主题的层次结构**:  
-  主题的层次结构会影响主题过滤器的设计和使用。在设计主题的层次结构时,可以考虑按照功能、区域、设备等对主题进行分类。
-  这有助于实现更精细的主题过滤器和更灵活的主题订阅机制。
-
----
-
-总之,主题过滤器的选择和设计应充分考虑应用程序的需求和场景,并遵循适当的规范和最佳实践。
\ No newline at end of file
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/98_mqtt_best_practices/_category_.json b/i18n/zh-Hans/docusaurus-plugin-content-docs/current/98_mqtt_best_practices/_category_.json
deleted file mode 100644
index 28a19fc5..00000000
--- a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/98_mqtt_best_practices/_category_.json
+++ /dev/null
@@ -1,8 +0,0 @@
-{
-  "label": "MQTT最佳实践",
-  "position": 21,
-  "link": {
-    "type": "doc",
-    "id": "mqtt"
-  }
-}
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/999_bifromq_inside.md b/i18n/zh-Hans/docusaurus-plugin-content-docs/current/999_bifromq_inside.md
deleted file mode 100644
index 1b63e33f..00000000
--- a/i18n/zh-Hans/docusaurus-plugin-content-docs/current/999_bifromq_inside.md
+++ /dev/null
@@ -1,18 +0,0 @@
----
-sidebar_position: 999
-title: "BifroMQ Inside"
----
-本页面列出了与BifroMQ集成的项目或产品。如果您的项目与BifroMQ集成,请在[此处提交](https://github.com/bifromqio/bifromq-docs/issues/new?assignees=visoar&labels=BifroMQ+Inside&projects=&template=bifromq-inside.md&title=%5BBifroMQ+Inside%5D+Your+Project%2FProduct+Name)。
-
-### 云
-
-* [百度IoTCore](https://cloud.baidu.com/product/iot.html) - IoTCore是一个Serverless服务,提供大规模设备连接和管理、规则引擎等功能。帮您轻松完成构建IoT应用程序的第一步。
-
-### IoT平台
-
-* [百度物联网平台](https://iot.baidu.com/) - 百度天工物联网平台利用云端-边缘-设备能力,提供全面、用户友好和行业专用的物联网解决方案。
-* [ThingLinks](https://mqttsnet.yuque.com/gt6zkc/thinglinks) - ThingLinks物联网平台提供多样化和广泛的设备连接能力。它帮助用户收集大量设备数据,并快速集成应用程序,构建物联网业务。
-
-### 插件
-
-* [BifroMQ-plugin-anyAuth](https://github.com/Gujiawei-Edinburgh/bifromq-plugin-anyAuth) - 这个BifroMQ认证插件支持微信和Auth0认证,并可以扩展到其他社交媒体账号。该项目使用访问控制列表(ACL)来管理授权。每个动作,如发布和订阅,都有基于用户设置而不是特定客户端的自定义权限规则。
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x.json b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x.json
deleted file mode 100644
index 39226586..00000000
--- a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x.json
+++ /dev/null
@@ -1,130 +0,0 @@
-{
-  "version.label": {
-    "message": "1.0.x",
-    "description": "The label for version current"
-  },
-  "sidebar.tutorialSidebar.category.Introduction": {
-    "message": "介绍",
-    "description": "The label for category Introduction in sidebar tutorialSidebar"
-  },
-  "sidebar.tutorialSidebar.category.Introduction.link.generated-index.description": {
-    "message": "BifroMQ 介绍,特性列表,系统限制和发布日志",
-    "description": "The generated-index page description for category Introduction in sidebar tutorialSidebar"
-  },
-  "sidebar.tutorialSidebar.category.Get Started": {
-    "message": "快速开始",
-    "description": "The label for category Get Started in sidebar tutorialSidebar"
-  },
-  "sidebar.tutorialSidebar.category.Get Started.link.generated-index.description": {
-    "message": "BifroMQ 介绍,特性列表,系统限制和发布日志",
-    "description": "The generated-index page description for category Get Started in sidebar tutorialSidebar"
-  },
-  "sidebar.tutorialSidebar.category.Install & Deploy": {
-    "message": "安装部署",
-    "description": "The label for category Install & Deploy in sidebar tutorialSidebar"
-  },
-  "sidebar.tutorialSidebar.category.Install & Deploy.link.generated-index.description": {
-    "message": "BifroMQ 安装和部署",
-    "description": "The generated-index page description for category Install & Deploy in sidebar tutorialSidebar"
-  },
-  "sidebar.tutorialSidebar.category.Configuration": {
-    "message": "配置",
-    "description": "The label for category Configuration in sidebar tutorialSidebar"
-  },
-  "sidebar.tutorialSidebar.category.Configuration.link.generated-index.description": {
-    "message": "BifroMQ 配置.",
-    "description": "The generated-index page description for category Configuration in sidebar tutorialSidebar"
-  },
-  "sidebar.tutorialSidebar.category.User Guide": {
-    "message": "用户指南",
-    "description": "The label for category User Guide in sidebar tutorialSidebar"
-  },
-  "sidebar.tutorialSidebar.category.User Guide.link.generated-index.description": {
-    "message": "BifroMQ 用户指南",
-    "description": "The generated-index page description for category User Guide in sidebar tutorialSidebar"
-  },
-  "sidebar.tutorialSidebar.category.Connect to BifroMQ": {
-    "message": "连接及消息",
-    "description": "The label for category Connect to BifroMQ in sidebar tutorialSidebar"
-  },
-  "sidebar.tutorialSidebar.category.Connect to BifroMQ.link.generated-index.description": {
-    "message": "连接到 BifroMQ 并进行消息发布、订阅。",
-    "description": "The generated-index page description for category Connect to BifroMQ in sidebar tutorialSidebar"
-  },
-  "sidebar.tutorialSidebar.category.Data Integration": {
-    "message": "数据集成",
-    "description": "The label for category Data Integration in sidebar tutorialSidebar"
-  },
-  "sidebar.tutorialSidebar.category.Data Integration.link.generated-index.description": {
-    "message": "BifroMQ 数据集成",
-    "description": "The generated-index page description for category Data Integration in sidebar tutorialSidebar"
-  },
-  "sidebar.tutorialSidebar.category.API Usage": {
-    "message": "API 使用",
-    "description": "The label for category API Usage in sidebar tutorialSidebar"
-  },
-  "sidebar.tutorialSidebar.category.API Usage.link.generated-index.description": {
-    "message": "BifroMQ API 使用.",
-    "description": "The generated-index page description for category API Usage in sidebar tutorialSidebar"
-  },
-  "sidebar.tutorialSidebar.category.Plugin": {
-    "message": "插件",
-    "description": "The label for category Plugin in sidebar tutorialSidebar"
-  },
-  "sidebar.tutorialSidebar.category.Plugin.link.generated-index.description": {
-    "message": "BifroMQ 插件.",
-    "description": "The generated-index page description for category Plugin in sidebar tutorialSidebar"
-  },
-  "sidebar.tutorialSidebar.category.Operations": {
-    "message": "运维",
-    "description": "The label for category Operations in sidebar tutorialSidebar"
-  },
-  "sidebar.tutorialSidebar.category.Operations.link.generated-index.description": {
-    "message": "BifroMQ 运维.",
-    "description": "The generated-index page description for category Operations in sidebar tutorialSidebar"
-  },
-  "sidebar.tutorialSidebar.category.configs": {
-    "message": "配置",
-    "description": "The label for category configs in sidebar tutorialSidebar"
-  },
-  "sidebar.tutorialSidebar.category.Best Practices": {
-    "message": "最佳实践",
-    "description": "The label for category Best Practices in sidebar tutorialSidebar"
-  },
-  "sidebar.tutorialSidebar.category.Best Practices.link.generated-index.description": {
-    "message": "最佳实践",
-    "description": "The generated-index page description for category Best Practices in sidebar tutorialSidebar"
-  },
-  "sidebar.tutorialSidebar.category.FAQ": {
-    "message": "常见问题",
-    "description": "The label for category FAQ in sidebar tutorialSidebar"
-  },
-  "sidebar.tutorialSidebar.category.FAQ.link.generated-index.description": {
-    "message": "常见问题",
-    "description": "The generated-index page description for category FAQ in sidebar tutorialSidebar"
-  },
-  "sidebar.tutorialSidebar.category.MQTT": {
-    "message": "MQTT",
-    "description": "The label for category MQTT in sidebar tutorialSidebar"
-  },
-  "sidebar.tutorialSidebar.category.MQTT.link.generated-index.description": {
-    "message": "MQTT 协议链接",
-    "description": "The generated-index page description for category MQTT in sidebar tutorialSidebar"
-  },
-  "sidebar.tutorialSidebar.category.Test Report": {
-    "message": "测试报告",
-    "description": "The label for category Test Report in sidebar tutorialSidebar"
-  },
-  "sidebar.tutorialSidebar.category.Test Report.link.generated-index.description": {
-    "message": "BifroMQ 测试报告",
-    "description": "The generated-index page description for category Test Report in sidebar tutorialSidebar"
-  },
-  "sidebar.tutorialSidebar.category.Configs": {
-    "message": "Configs",
-    "description": "The label for category Configs in sidebar tutorialSidebar"
-  },
-  "sidebar.tutorialSidebar.category.Configs.link.generated-index.description": {
-    "message": "Configs",
-    "description": "The generated-index page description for category Configs in sidebar tutorialSidebar"
-  }
-}
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/00_Readme.md b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/00_Readme.md
deleted file mode 100644
index 1ee14898..00000000
--- a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/00_Readme.md
+++ /dev/null
@@ -1,29 +0,0 @@
----
-sidebar_position: 0
----
-
-# BifroMQ
-
-BifroMQ 是一个基于 Java 实现的高性能、分布式 MQTT Broker 消息中间件,无缝集成了原生的多租户支持。它旨在支持构建大规模的物联网设备连接和消息系统。
-
-BifroMQ 源自百度物联网团队多年技术积累,目前,它作为百度智能云[物联网核心套件 IoT Core](https://cloud.baidu.com/product/iot.html)的基础技术,这是一个公有云的 Serverless 服务。
-
-## 名称的由来
-
-BifroMQ 的名称灵感来自于北欧神话中的`Bifröst`,一座彩虹之桥,联接着人类的世界 Midgard 和神祇居住的世界 Asgard。Bifröst 作为两个世界间的坚实而灵活的通道,BifroMQ 同样旨在成为连接各种系统或应用的枢纽,通过消息传递实现它们之间的交流。这与 MQTT 中间件在分布式系统中扮演的角色,即处理和转发消息,极为相似。
-
-此外,Bifröst 的坚固性寓意着 BifroMQ 在稳定性和可靠性方面的卓越表现,而它的灵活性则象征着 BifroMQ 在可扩展性和适应性上的优势。总的来说,`BifroMQ` 是一个坚固、灵活的 MQTT 中间件,作为连接不同系统或应用的桥梁。
-
-## 讨论组
-
-### 微信群
-
-如果你对我们的项目感兴趣,你可以加入我们的微信群。
-
-[通过电子邮件](mailto:hello@bifromq.io) 向我们发送您的微信 ID,以及为什么您对 BifroMQ 感兴趣的更多信息(我们很乐意听到),我们将尽快邀请您加入我们的群组。
-
-### Discord
-
-或加入我们的 Discord 群组(英文)
-
-<a href="https://discord.gg/Pfs3QRadRB"><img src="https://img.shields.io/discord/1115542029531885599?logo=discord&logoColor=white" alt="BifroMQ Discord server" /></a>
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/01_intro/_category_.json b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/01_intro/_category_.json
deleted file mode 100644
index 010ca759..00000000
--- a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/01_intro/_category_.json
+++ /dev/null
@@ -1,8 +0,0 @@
-{
-  "label": "Introduction",
-  "position": 1,
-  "link": {
-    "type": "generated-index",
-    "description": "BifroMQ overview introduction, features list, system limitations, release log, etc."
-  }
-}
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/01_intro/features_list.md b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/01_intro/features_list.md
deleted file mode 100644
index 05a358a9..00000000
--- a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/01_intro/features_list.md
+++ /dev/null
@@ -1,15 +0,0 @@
----
-sidebar_position: 1
----
-
-# 功能列表
-
-* 完全支持 MQTT 3.1/3.1.1 的特性,包括 TCP/TLS/WS/WSS,即将支持 MQTT 5.0
-* 原生支持多租户资源共享和工作负载隔离
-* 内置存储引擎,针对关键负载定向优化,无第三方中间件依赖。
-* 扩展机制支持:
-    * 认证/授权 (Authentication/Authorization)
-    * 运行时设置 (Runtime Setting)
-    * 桥接 (Bridging)
-    * 事件 (Event)
-    * 系统/租户级别的监控 (System/Tenant-level Monitoring)
\ No newline at end of file
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/02_get_started/1_quick_install.md b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/02_get_started/1_quick_install.md
deleted file mode 100644
index b69edff4..00000000
--- a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/02_get_started/1_quick_install.md
+++ /dev/null
@@ -1,15 +0,0 @@
----
-sidebar_position: 1
-title: 安装BifroMQ
----
-
-# 安装BifroMQ
-
-## Docker
-```
-docker run -d --name bifromq -p 1883:1883 bifromq/bifromq:latest
-```
-
-## bash
-
-关于更多的安装选项,详情请见:[安装和部署](../../category/install--deploy/)章节。
\ No newline at end of file
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/02_get_started/2_connect_to.md b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/02_get_started/2_connect_to.md
deleted file mode 100644
index 65c8f21a..00000000
--- a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/02_get_started/2_connect_to.md
+++ /dev/null
@@ -1,35 +0,0 @@
----
-sidebar_position: 2
----
-
-# 连接到BifroMQ
-
-## 使用 MQTT Client 简单连接验证
-使用已有的第三方 MQTT 客户端工具,可以快速验证是否可以实现与 BifroMQ 提供的 MQTT 服务交流发送或者接收消息。
-
-免费的第三方 MQTT 客户端工具较多,常见的有 MQTT.fx、MQTTBox、MQTTLens、MQTTX等。这里以 MQTTX 为例。
-
-1. 访问 https://mqttx.app/ 下载 MQTTX 并安装。
-2. 打开 MQTTX,点击“New Connection”或者左侧边栏上的“+”,创建一个新的连接配置。
-
-![image.png](https://bce.bdstatic.com/doc/IOTSTACK/iotcore/image_4636166.png)
-
-3. 填入各项必填配置:
-
-    * Name:本配置的名字,可随意填写。
-    * ClientID:客户端ID,自行设置或使用右边的按钮随机生成。支持“a-z”,“0-9”,“_”,“-”字符且不能大于128bytes,UTF8编码,不可重名。
-    * Host:连接地址。前面的协议头可以自行选择,mqtt://、mqtts://、wss:// 分别对应 MQTT 连接中的 TCP、TLS/SSL、WSS 三种方式。后面域名请填写可以实际访问到 BifroMQ MQTT 服务的地址。
-    * Port:连接端口。根据选择的协议头确定对应的端口。端口默认:	TCP:1883、TLS/SSL:1884、WSS:443。
-    * Username & Password:您拥有的用户名和密码。
-    * MQTT Version:选择3.1.1
-
-4. 正确填写连接配置后,点击右上角 Connect 连接服务器。一切正常会提示Connect Successful,并转入消息收发界面。
-5. 订阅主题:点击左上的“New Subscription”按钮,并在弹出的对话框中填入主题Topic。请注意,必须填写您有订阅权限的主题,这里我们使用一个测试主题,对应此设备为$iot/device1/user/fortest,选择默认的QoS 0,点击右下的“Confirm”进行订阅操作。
-
-![image.png](https://bce.bdstatic.com/doc/IOTSTACK/iotcore/image_62a12ac.png)
-
-6. 发布消息:在消息收发界面右下填入主题Topic,这里我们依然填写刚才的测试主题,自己给自己发送一条消息。选择默认的QoS 0,填写消息内容后点击发送按钮完成发送。
-
-![image.png](https://bce.bdstatic.com/doc/IOTSTACK/iotcore/image_e3d5f14.png)
-
-7. 发送成功后,可以在右方看到已发送的消息。MQTT服务工作正常的话,已经订阅了该主题的我们可以收到该消息,也会展示在对话界面左边。
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/02_get_started/_category_.json b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/02_get_started/_category_.json
deleted file mode 100644
index 9397afae..00000000
--- a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/02_get_started/_category_.json
+++ /dev/null
@@ -1,8 +0,0 @@
-{
-  "label": "Get Started",
-  "position": 2,
-  "link": {
-    "type": "generated-index",
-    "description": "BifroMQ overview introduction, features list, system limitations, release log, etc."
-  }
-}
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/03_deploy/11_build_from_source.md b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/03_deploy/11_build_from_source.md
deleted file mode 100644
index 927e9409..00000000
--- a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/03_deploy/11_build_from_source.md
+++ /dev/null
@@ -1,33 +0,0 @@
----
-sidebar_position: 11
----
-
-# 从源码编译部署
-
-## 前提条件
-
-* JDK 17+
-* Maven 3.5.0+
-  
-## 编译构建
-
-克隆版本库到本地
-
-```
-cd <YOUR_WORKSPACE>
-git clone https://github.com/bifromqio/bifromq bifromq
-```
-
-执行以下命令,进入项目根目录,构建整个项目
-
-```
-cd bifromq
-mvn wrapper:wrapper
-./mvnw -U clean package
-```
-
-构建输出是两个 tar.gz 和一个 zip 文件,位于 `/build/build-bifromq-starters/target/`
-
-* bifromq-xxx-all.tar.gz // 适用于 Linux 和 macOS 的 standalone 集群部署 tar.gz 包
-* bifromq-xxx-standalone.tar.gz  // 适用于 Linux 和 macOS 的 standalone 部署 tar.gz 包
-* bifromq-xxx-windows-standalone.zip // 适用于 Windows 的 standalone 部署的 zip 包
\ No newline at end of file
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/03_deploy/1_deploy_with_docker.md b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/03_deploy/1_deploy_with_docker.md
deleted file mode 100644
index 423bf4d9..00000000
--- a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/03_deploy/1_deploy_with_docker.md
+++ /dev/null
@@ -1,19 +0,0 @@
----
-sidebar_position: 1
----
-
-# 使用 Docker 部署
-
-## 前提条件
-
-* 已安装 [Docker](https://www.docker.com/)
-* 有对应端口使用权限且端口空闲,如无权限请更换端口
-
-## Docker 命令
-
-运行以下命令,会将 BifroMQ 以 linux 用户 `bifromq` 在容器中以 `standalone` 模式运行。
-
-```
-docker run -d --name bifromq -p 1883:1883 bifromq/bifromq:latest
-```
-
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/03_deploy/21_cluster.md b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/03_deploy/21_cluster.md
deleted file mode 100644
index fbb650a7..00000000
--- a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/03_deploy/21_cluster.md
+++ /dev/null
@@ -1,9 +0,0 @@
----
-sidebar_position: 21
----
-
-# 部署群集
-
-## Cluster
-
-文档待整理,如有需求请[联系我们](mailto:need-cluster@bifromq.io)。
\ No newline at end of file
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/03_deploy/2_deploy_on_linux_mac.md b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/03_deploy/2_deploy_on_linux_mac.md
deleted file mode 100644
index e6d008c0..00000000
--- a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/03_deploy/2_deploy_on_linux_mac.md
+++ /dev/null
@@ -1,19 +0,0 @@
----
-sidebar_position: 1
----
-
-# 在 Linux 或者 macOS 部署
-
-## 前提条件
-
-* 安装 JDK 17+ 环境
-* 在 [bifromq_release](https://github.com/bifromqio/bifromq/releases) 获取 BifroMQ 的最新版本
-
-## Linux或者macOS
-
-运行以下命令即可运行 BifroMQ。
-
-```
-tar -zxvf bifromq-*-standalone.tar.gz --strip-components 1  -C /usr/share/bifromq/
-cd bifromq && ./bin/standalone.sh start
-```
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/03_deploy/3_deploy_on_windows.md b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/03_deploy/3_deploy_on_windows.md
deleted file mode 100644
index 8cf9a352..00000000
--- a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/03_deploy/3_deploy_on_windows.md
+++ /dev/null
@@ -1,20 +0,0 @@
----
-sidebar_position: 4
----
-
-# 在 Windows 部署 
-
-## 前提条件
-
-* 安装 JDK 17+ 环境
-* 在 [bifromq_release](https://github.com/bifromqio/bifromq/releases) 获取 BifroMQ 的最新版本
-
-## Windows
-
-打开命令行工具,运行以下命令即可运行 BifroMQ。
-
-```
-unzip -zxvf bifromq-*-standalone-windows.zip
-cd bifromq\bin
-standalone.bat start
-```
\ No newline at end of file
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/03_deploy/_category_.json b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/03_deploy/_category_.json
deleted file mode 100644
index 181c7b1d..00000000
--- a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/03_deploy/_category_.json
+++ /dev/null
@@ -1,8 +0,0 @@
-{
-  "label": "Install & Deploy",
-  "position": 3,
-  "link": {
-    "type": "generated-index",
-    "description": "Install And Deploy BifroMQ."
-  }
-}
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/04_configuration/1_configs_introduction.md b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/04_configuration/1_configs_introduction.md
deleted file mode 100644
index 6255d7af..00000000
--- a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/04_configuration/1_configs_introduction.md
+++ /dev/null
@@ -1,22 +0,0 @@
----
-sidebar_position: 1
----
-
-
-# 配置简介
-
-BifroMQ的系统参数主要通过配置文件进行设置,本章节会分别介绍这部分配置及其含义。
-
-
-## 配置文件介绍
-
-主配置文件名称为standalone.yml,位置位于:
-
-| 安装方式   | 文件位置                               |
-| :--------- | -------------------------------------- |
-| 压缩包解压 | ./conf/standalone.yml                  |
-| Docker容器 | /usr/share/bifromq/conf/standalone.yml |
-
-主配置文件包含了大部分必须的配置项,其余配置项如果没有在配置文件中明确指定,将使用默认配置。 所有可用的配置项及其说明见:[配置文件手册](2_file_configs_manual.md)
-
-
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/04_configuration/2_file_configs_manual.md b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/04_configuration/2_file_configs_manual.md
deleted file mode 100644
index 624e88f6..00000000
--- a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/04_configuration/2_file_configs_manual.md
+++ /dev/null
@@ -1,414 +0,0 @@
----
-sidebar_position: 2
----
-
-# 配置文件手册
-
-## 简介
-
-BifroMQ 配置文件参数介绍。
-
-### host
-
-- 类型:String
-
-- 默认值:0.0.0.0
-
-- 描述:mqtt-server绑定的地址,用于对外提供mqtt接入点。
-
-### tcpPort
-
-- 类型:int
-
-- 默认值:1883
-
-- 描述:mqtt-server绑定的端口,用于对外暴露mqtt tcp接入端口。
-
-### tlsPort
-
-- 类型:int
-
-- 默认值:1884
-
-- 描述:mqtt-server绑定的端口,用于对外暴露mqtt tls接入端口。
-
-### wsPort
-
-- 类型:int
-
-- 默认值:80
-
-- 描述:mqtt-server绑定的端口,用于对外暴露mqtt websocket接入端口。
-
-### wssPort
-
-- 类型:int
-
-- 默认值:1883
-
-- 描述:mqtt-server绑定的端口,用于对外暴露mqtt websocket security接入端口。
-
-### wsPath
-
-- 类型:String
-
-- 默认值:/mqtt
-
-- 描述:mqtt-server中ws及wss接入路径。
-
-### tcpEnabled
-
-- 类型:Boolean
-
-- 默认值:true
-
-- 描述:是否在mqtt-server中构建tcp接入能力。
-
-### tlsEnabled
-
-- 类型:Boolean
-
-- 默认值:false
-
-- 描述:是否在mqtt-server中构建tls接入能力。
-
-### wsEnabled
-
-- 类型:Boolean
-
-- 默认值:false
-
-- 描述:是否在mqtt-server中构建ws接入能力。
-
-### wssEnabled
-
-- 类型:Boolean
-
-- 默认值:false
-
-- 描述:是否在mqtt-server中构建wss接入能力。
-
-### connTimeoutSec
-
-- 类型:Integer
-
-- 默认值:20
-
-- 描述:从TCP连接建立,到Connect动作完成,能够容忍的超时时间。超过限制后,服务端会主动断开此次连接。
-
-### maxConnPerSec
-
-- 类型:Integer
-
-- 默认值:1000
-
-- 描述:每秒接受的最大Connect频率,通过令牌桶进行限制,超限的连接会在后续进行断开。
-
-### maxDisconnPerSec
-
-- 类型:Integer
-
-- 默认值:1000
-
-- 描述:每秒接受的最大DisConnect频率,通过令牌桶进行限制。
-
-### maxMsgByteSize
-
-- 类型:Integer
-
-- 默认值:256 * 1024
-
-- 描述:允许的最大mqtt packet大小。
-
-### maxResendTimes
-
-- 类型:Integer
-
-- 默认值:5
-
-- 描述:QoS1及QoS2消息的最大重发次数,超过后会丢弃。
-
-### maxConnBandwidth
-
-- 类型:Integer
-
-- 默认值:512 * 1024
-
-- 描述:单个MQTT连接允许的最大带宽,入向和出向独立计算。
-
-### defaultKeepAliveSec
-
-- 类型:Integer
-
-- 默认值:300
-
-- 描述:默认的MQTT连接keepAlive时长,client未主动设置时采用此值。
-
-### qos2ConfirmWindowSec
-
-- 类型:Integer
-
-- 默认值:5
-
-- 描述:内部为QoS2消息缓存messageId的过期时间。
-
-### authProviderFQN
-
-- 类型:String
-
-- 默认值:Null
-
-- 描述:通过Pf4j加载生效的authProvider的名称,如果未配置,采用内置DefaultAuthProvider。
-
-### settingProviderFQN
-
-- 类型:String
-
-- 默认值:Null
-
-- 描述:通过Pf4j加载生效的settingProviderFQN的名称,如果未配置,采用内置DefaultSettingProvider。
-
-### eventCollectorReportBufferSize
-
-- 类型:Integer
-
-- 默认值:8192
-
-- 描述:内部EventCollectorManager中Disruptor的ringBufferSize。
-
-### settingProviderProvideBufferSize
-
-- 类型:Integer
-
-- 默认值:2048
-
-- 描述:内部SettingProviderManager中Disruptor的ringBufferSize。
-
-### brokerSSLCtxConfig.type
-
-- 类型:String
-
-- 默认值:server
-
-- 描述:固定值,无需修改。
-
-### brokerSSLCtxConfig.clientAuth
-
-- 类型:String
-
-- 默认值:OPTIONAL
-
-- 描述:用于设定在mqtt-server与client建立ssl连接时,是否需要验证客户端身份。可选值如下:
-
-* NONE:无需验证
-* OPTIONAL:服务端会请求验证客户端身份,如果客户端不提供证书也不会失败。
-* REQUIRE:服务端要求验证客户端身份,如果客户端不提供会失败。
-
-### brokerSSLCtxConfig.certFile
-
-- 类型:String
-
-- 默认值:Null
-
-- 描述:mqtt-server模块在对外提供tls及wss接入能力时,服务端所用证书公钥文件名称。会尝试从系统参数“CONF_DIR”指定的目录下加载,或者从当前classpath下加载。
-
-### brokerSSLCtxConfig.keyFile
-
-- 类型:String
-
-- 默认值:Null
-
-- 描述:mqtt-server模块在对外提供tls及wss接入能力时,服务端所用证书私钥文件名称。会尝试从系统参数“CONF_DIR”指定的目录下加载,或者从当前classpath下加载。
-
-### brokerSSLCtxConfig.trustCertsFile
-
-- 类型:String
-
-- 默认值:Null
-
-- 描述:mqtt-server模块在对外提供tls及wss接入能力时,服务端所用根证书文件名称。会尝试从系统参数“CONF_DIR”指定的目录下加载,或者从当前classpath下加载。
-
-### distWorkerConfig.dataEngineConfig.type
-
-- 类型:String
-
-- 默认值:Null
-
-- 描述:dist-worker模块中的BaseKV存储使用的dataEngine类型,可选:
-
-* rocksDB:具有持久化能力,重启后可恢复状态。
-* memory:无持久化能力,重启数据丢失。
-
-### distWorkerConfig.dataEngineConfig.gcIntervalInSec
-
-- 类型:Integer
-
-- 默认值:300
-
-- 描述:dist-worker模块中的BaseKV使用的dataEngine进行GC的间隔。
-
-### distWorkerConfig.dataEngineConfig.dataPathRoot
-
-- 类型:String
-
-- 默认值:Null
-
-- 描述:type指定rocksDB时生效。dist-worker模块中dataEngine存储数据文件的目录,若配置为绝对路径则直接加载,若为相对路径则会依次尝试在系统参数“DATA_DIR”及“user.dir”对应的目录下加载。
-
-### distWorkerConfig.dataEngineConfig.compactMinTombstoneKeys
-
-- 类型:Integer
-
-- 默认值:50,000
-
-- 描述:type指定rocksDB时生效。
-
-### distWorkerConfig.dataEngineConfig.compactTombstonePercent
-
-- 类型:Double
-
-- 默认值:0.3
-
-- 描述:type指定rocksDB时生效。当dataEngine所用的rocksDB中某个Range删除超过compactMinTombstoneKeys数量的keys,并且已删除的keys数量占总数的比例超过compactTombstonePercent时,对这个Range空间执行compact操作。
-
-### distWorkerConfig.walEngineConfig.type
-
-- 类型:String
-
-- 默认值:Null
-
-- 描述:dist-worker模块中的BaseKV存储使用的walEngine类型,可选:
-
-* rocksDB:具有持久化能力,重启后可恢复状态。
-* memory:无持久化能力,重启数据丢失。
-
-### distWorkerConfig.walEngineConfig.gcIntervalInSec
-
-- 类型:Integer
-
-- 默认值:300
-
-- 描述:dist-worker模块中的BaseKV使用的walEngine进行GC的间隔。
-
-### distWorkerConfig.walEngineConfig.dataPathRoot
-
-- 类型:String
-
-- 默认值:Null
-
-- 描述:type指定rocksDB时生效。dist-worker模块中walEngine存储数据文件的目录,若配置为绝对路径则直接加载,若为相对路径则会依次尝试在系统参数“DATA_DIR”及“user.dir”对应的目录下加载。
-
-### distWorkerConfig.walEngineConfig.compactMinTombstoneKeys
-
-- 类型:Integer
-
-- 默认值:50,000
-
-- 描述:type指定rocksDB时生效。
-
-### distWorkerConfig.walEngineConfig.compactTombstonePercent
-
-- 类型:Double
-
-- 默认值:0.3
-
-- 描述:type指定rocksDB时生效。当walEngine所用的rocksDB中某个Range删除超过compactMinTombstoneKeys数量的keys,并且已删除的keys数量占总数的比例超过compactTombstonePercent时,对这个Range空间执行compact操作。
-
-### distWorkerConfig.distWorkerClientConfig.execPipelinePerServer
-
-- 类型:Integer
-
-- 默认值:5
-
-- 描述:dist-server跟dist-worker之间,预先建立好的exec请求pipeline的数量。
-
-### distWorkerConfig.distWorkerClientConfig.queryPipelinePerServer
-
-- 类型:Integer
-
-- 默认值:5
-
-- 描述:dist-server跟dist-worker之间,预先建立好的query请求pipeline的数量。
-
-### inboxStoreConfig.dataEngineConfig.*
-
-描述:结构同distWorkerConfig.dataEngineConfig,不再赘述。
-
-### inboxStoreConfig.walEngineConfig.*
-
-描述:结构同distWorkerConfig.walEngineConfig,不再赘述。
-
-### inboxStoreConfig.inboxStoreClientConfig.*
-
-描述:结构同distWorkerConfig.distWorkerClientConfig,不再赘述。
-
-### retainStoreConfig.dataEngineConfig.*
-
-描述:结构同distWorkerConfig.dataEngineConfig,不再赘述。
-
-### retainStoreConfig.walEngineConfig.*
-
-描述:结构同distWorkerConfig.walEngineConfig,不再赘述。
-
-### retainStoreConfig.inboxStoreClientConfig.*
-
-描述:结构同distWorkerConfig.distWorkerClientConfig,不再赘述。
-
-### executorConfig.mqttWorkerThreads
-
-- 类型:Integer
-
-- 默认值:当前CPU可用核数
-
-- 描述:mqtt-server中构建netty server时的workerGroup的大小。
-
-### executorConfig.ioClientParallelism
-
-- 类型:Integer
-
-- 默认值:当前CPU可用核数 / 3,最小为2
-
-- 描述:请求dist-worker、inbox-store、retain-store中BaseKV存储中的数据时,请求端的执行线程池核心线程数和最大线程数。
-
-### executorConfig.ioServerParallelism
-
-- 类型:Integer
-
-- 默认值:当前CPU可用核数 / 3,最小为2
-
-- 描述:内部dist-server、inbox-server、retain-server模块中服务端执行线程池的核心线程数和最大线程数。
-
-### executorConfig.queryThreads
-
-- 类型:Integer
-
-- 默认值:当前CPU可用核数 / 4,最小为2
-
-- 描述:dist-worker、inbox-store、retain-store中的BaseKV存储执行query类型请求所用线程池的核心线程数和最大线程数。
-
-### executorConfig.mutationThreads
-
-- 类型:Integer
-
-- 默认值:3
-
-- 描述:dist-worker、inbox-store、retain-store中的BaseKV存储内部所用的异步回调线程池的核心线程数和最大线程数。
-
-### executorConfig.tickerThreads
-
-- 类型:Integer
-
-- 默认值:当前CPU可用核数 / 20,最小为1
-
-- 描述:dist-worker、inbox-store、retain-store中的BaseKV存储内部执行定时tick动作所用线程池的核心线程数和最大线程数。
-
-### executorConfig.bgWorkerThreads
-
-- 类型:Integer
-
-- 默认值:当前CPU可用核数 / 20,最小为1
-
-- 描述:dist-worker、inbox-store、retain-store中的BaseKV存储内部执行background动作所用线程池的核心线程数和最大线程数。
-
-
-
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/04_configuration/3_performance_tuning_linux.md b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/04_configuration/3_performance_tuning_linux.md
deleted file mode 100644
index d01c229c..00000000
--- a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/04_configuration/3_performance_tuning_linux.md
+++ /dev/null
@@ -1,57 +0,0 @@
----
-sidebar_position: 3
----
-
-# 系统参数调优(Linux)
-
-以下Kernel参数会影响BifroMQ所在机器能接受的最大连接数
-
-## 内存
-
-* vm.max_map_count: 限制一个进程可以拥有的VMA(虚拟内存区域)的数量, 可放大到221184
-
-## 最大打开文件数
-
-* nofile: 指单进程的最大打开文件数
-* nr_open: 指单个进程可分配的最大文件数,通常默认值为1024*1024=1048576
-* file-max: 系统内核一共可以打开的最大值,默认值是185745
-
-## NetFilter调优
-
-通过`sysctl -a | grep conntrack`查看当前的参数,以下几个参数决定了最大连接数:
-
-* net.netfilter.nf_conntrack_buckets: 记录连接条目的hashtable的bucket大小
-  * 修改命令:`echo 262144 > /sys/module/nf_conntrack/parameters/hashsize`
-* net.netfilter.nf_conntrack_max: hashtable最大的条目数,一般为nf_conntrack_buckets * 4
-* net.nf_conntrack_max: 同net.netfilter.nf_conntrack_max
-* net.netfilter.nf_conntrack_tcp_timeout_fin_wait: 默认 120s -> 30s
-* net.netfilter.nf_conntrack_tcp_timeout_time_wait: 默认 120s -> 30s
-* net.netfilter.nf_conntrack_tcp_timeout_close_wait: 默认 60s -> 15s
-* net.netfilter.nf_conntrack_tcp_timeout_established: 默认 432000 秒(5天)-> 300s
-
-
-以下sysctl参数会影响大压力下tcp channel性能表现
-
-## Server端及测试发压端TCP相关调优
-
-推荐使用centos7环境进行部署及压力测试。
-
-centos6环境需要进行系统参数调优:
-* net.core.wmem_max: 最大的TCP数据发送窗口大小(字节)
-  * 修改命令:`echo 'net.core.wmem_max=16777216' >> /etc/sysctl.conf`
-* net.core.wmem_default: 默认的TCP数据发送窗口大小(字节)
-  * 修改命令:`echo 'net.core.wmem_default=262144' >> /etc/sysctl.conf`
-* net.core.rmem_max: 最大的TCP数据接收窗口大小(字节)
-  * 修改命令:`echo 'net.core.rmem_max=16777216' >> /etc/sysctl.conf`
-* net.core.rmem_default: 默认的TCP数据接收窗口大小(字节)
-  * 修改命令:`echo 'net.core.rmem_default=262144' >> /etc/sysctl.conf`
-* net.ipv4.tcp_rmem: socket接收缓冲区内存使用的下限  警戒值  上限
-  * 修改命令:`echo 'net.ipv4.tcp_rmem= 1024 4096 16777216' >> /etc/sysctl.conf`
-* net.ipv4.tcp_rmem: socket发送缓冲区内存使用的下限  警戒值  上限
-  * 修改命令:`echo 'net.ipv4.tcp_wmem= 1024 4096 16777216' >> /etc/sysctl.conf`
-* net.core.optmem_max: 每个socket所允许的最大缓冲区的大小 (字节)
-  * 修改命令:`echo 'net.core.optmem_max = 16777216' >> /etc/sysctl.conf`
-* net.core.netdev_max_backlog: 网卡设备将请求放入队列的长度
-  * 修改命令:`echo 'net.core.netdev_max_backlog = 16384' >> /etc/sysctl.conf`
-
-修改完配置通过`sysctl -p`并重启服务器生效。
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/04_configuration/_category_.json b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/04_configuration/_category_.json
deleted file mode 100644
index db925eaf..00000000
--- a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/04_configuration/_category_.json
+++ /dev/null
@@ -1,8 +0,0 @@
-{
-  "label": "Configuration",
-  "position": 4,
-  "link": {
-    "type": "generated-index",
-    "description": "BifroMQ Configuration."
-  }
-}
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/05_user_guide/1_connect/1_connect.md b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/05_user_guide/1_connect/1_connect.md
deleted file mode 100644
index 47beb228..00000000
--- a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/05_user_guide/1_connect/1_connect.md
+++ /dev/null
@@ -1,22 +0,0 @@
----
-sidebar_position: 1
----
-
-# 连接到 BifroMQ
-
-BifroMQ 是一个标准的 MQTT 消息中间件,你可以使用支持 MQTT 3.1/3.1.1 的任何 Client 进行连接。
-
-## 连接地址
-
-使用启动服务对应的 IP 或域名,默认端口及用途如下。
-
-端口|用途
----|---
-IP或域名:1883|TCP连接
-IP或域名:1884|TLS连接
-IP或域名:80/mqtt|WS连接
-IP或域名:443/mqtt|WSS连接
-
-## 鉴权
-
-默认情况下未开启鉴权,可将用户名密码留空进行连接。如需认证鉴权,请参考[认证鉴权插件](../../06_plugin/2_auth_provider.md)。
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/05_user_guide/1_connect/2_pubsub.md b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/05_user_guide/1_connect/2_pubsub.md
deleted file mode 100644
index 49a60a30..00000000
--- a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/05_user_guide/1_connect/2_pubsub.md
+++ /dev/null
@@ -1,41 +0,0 @@
----
-sidebar_position: 2
----
-
-# 发布/订阅
-
-根据MQTT协议按照消息发送和接收的角色可以分为发送方(Publisher)和订阅方(Subscriber),其基本模式如下图所示:
-
-![pub-sub-pattern](./images/pub-sub-pattern.png)
-
-* 发布消息。客户端可以通过连接向服务器发布消息。消息以主题(`topic`)为基础进行发布。主题是被订阅者感兴趣的通信内容的一种描述方式, 且具有层次结构(例如`home/bedroom/temperature`)。
-
-  客户端发布消息时需要指定主题,消息体中包含实际通信的内容。除此之外,发送方还需指定该条的QoS(Quality of Service),BifroMQ全量支持MQTT的所有QoS即QoS0/QoS1/QoS2。其具体含义如下:
-
-  | QoS  | 描述 |
-    | ---- | ---- |
-  | QoS0 | 至多一次传输 |
-  | QoS1 | 至少一次传输 |
-  | QoS2 | 正好一次传输 |
-
-* 订阅主题。在订阅中,订阅者的主题称为`topicFilter`。服务器端接收客户端发送的订阅请求,并记录该订阅。通常情况下,订阅可以分为非通配订阅(non-wildcard)和通配订阅(wildcard)。
-
-    * 对于非通配订阅:直接订阅特定的主题而不使用通配符,若订阅的主题为`home/bedroom/temperature`,则只能匹配主题为`home/bedroom/temperature`的消息。
-
-    * 对于通配订阅:订阅的主题中包含了通配符(`+`或`#`)。`+` 通配符匹配单级主题层级,`#` 通配符:匹配多级主题层级。下面是一些示例来说明如何使用通配符进行订阅: 
-
-      使用 `+` 通配符:  
-
-      * 订阅主题 `sensor/+/temperature`:匹配 `sensor/bedroom/temperature`、`sensor/kitchen/temperature` 等主题。
-      * 订阅主题 `home/+/light/+`:匹配 `home/livingroom/light/on`、`home/bedroom/light/off` 等主题。  
-
-      使用 `#` 通配符:  
-
-      * 订阅主题 `home/bedroom/#`:匹配 `home/bedroom/light/on`、`home/bedroom/temperature` 等主题及其子主题。
-      * 订阅主题 `home/+/#`:匹配 `home/bedroom/light/on`、`home/kitchen/temperature` 等主题及其子主题。
-      * 订阅主题 `#`:匹配所有主题。  
-
-      需要注意的是,通配符订阅可能会导致订阅的主题数量庞大,因此在使用通配符订阅时,应谨慎考虑性能和资源消耗。  
-
-      除此之外,与发布主题一样,订阅主题时还需要制定该主题的QoS。需要注意的是,BifroMQ在进行消息转发时,根据MQTT协议将取对应发送消息主题的QoS与订阅主题QoS的较小值,
-      即:`Min(PublishQoS, SubscribeQoS)`。因此即便订阅方订阅的主题为QoS2,依然有可能收到QoS0的对应消息。
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/05_user_guide/1_connect/3_shared_sub.md b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/05_user_guide/1_connect/3_shared_sub.md
deleted file mode 100644
index 2dab7154..00000000
--- a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/05_user_guide/1_connect/3_shared_sub.md
+++ /dev/null
@@ -1,18 +0,0 @@
----
-sidebar_position: 3
----
-
-# 共享订阅
-MQTT共享订阅(Shared Subscription)是MQTT协议的一个特性,它允许多个订阅者(Subscribers)共享同一个主题,并以一种公平的方式接收消息。以下为共享订阅的基本模式:
-
-![shared-subscription](./images/shared-subscription.png)
-
-共享订阅的订阅形式需满足`$share/{groupName}/topic`,其中`{groupName}`为共享组,图例中为`group1`,当多个订阅者订阅相同的主题时,会加入同一个共享组中,当有来自发送方的消息时,首先会找到共享组,然后以一种公平的方式(BifroMQ实现时采用随机选取组中的某一个订阅者)进行消息的推送。这样做有以下好处:
-
-* 负载均衡:MQTT共享订阅允许多个订阅者共享同一个主题,以一种公平的方式接收消息。当有消息发布到订阅主题时,MQTT代理服务器会选择一个订阅者来接收该消息,而不是将消息传递给所有订阅者。这样可以实现负载均衡,确保消息在订阅者之间平均分配,避免某个订阅者处理过多的消息负载。
-
-* 灵活性和扩展性:使用共享订阅,可以轻松地添加或删除订阅者,而无需修改发布者或其他订阅者的逻辑。这提供了灵活性和扩展性,使系统能够适应动态变化的订阅者数量。
-
-* 节省网络带宽:共享订阅可以减少网络带宽的使用。在普通的订阅模式下,每个订阅者都会收到相同的消息副本,导致网络带宽的浪费。而在共享订阅中,消息只会发送给一个订阅者,有效地减少了消息在网络上的传输量,从而节省了带宽资源。
-
-
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/05_user_guide/1_connect/_category_.json b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/05_user_guide/1_connect/_category_.json
deleted file mode 100644
index d8cd99f1..00000000
--- a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/05_user_guide/1_connect/_category_.json
+++ /dev/null
@@ -1,8 +0,0 @@
-{
-  "label": "Connect to BifroMQ",
-  "position": 4,
-  "link": {
-    "type": "generated-index",
-    "description": "Connect to BifroMQ"
-  }
-}
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/05_user_guide/1_connect/images/pub-sub-pattern.png b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/05_user_guide/1_connect/images/pub-sub-pattern.png
deleted file mode 100644
index bc6925c1..00000000
Binary files a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/05_user_guide/1_connect/images/pub-sub-pattern.png and /dev/null differ
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/05_user_guide/1_connect/images/shared-subscription.png b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/05_user_guide/1_connect/images/shared-subscription.png
deleted file mode 100644
index 3a9e9770..00000000
Binary files a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/05_user_guide/1_connect/images/shared-subscription.png and /dev/null differ
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/05_user_guide/2_integration/1_integration.md b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/05_user_guide/2_integration/1_integration.md
deleted file mode 100644
index f59117d3..00000000
--- a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/05_user_guide/2_integration/1_integration.md
+++ /dev/null
@@ -1,50 +0,0 @@
----
-title: 数据集成
-sidebar_position: 1
----
-
-# 数据集成
-
-## 基本概念
-
-用户除了使用传统的设备接收来自BifroMQ的消息与事件之外,还可以采用SDK的方式进行服务间数据的接入与集成。集成方式如下图所示:
-
-![integration](./images/integration.png)
-
-集成方通过共享订阅的方式(`$share/{groupName}/topicFilter`)接收来自BifroMQ的数据,并将数据传递给下游例如Kafka或者MySQL。由于服务间集成数据量较大,
-因此对于单个MQTT连接而言负载较大,带宽存在上限。采用共享订阅的方式正好利用了其负载均衡的特点,且随着业务的发展可以灵活地增减相应MQTT Client数量。
-
-因此,对于接入方而言需要根据自身的业务来估算数据量的大小以及所对应的带宽资源,从而估算出所需要的MQTT Client数量。
-例如来自BifroMQ的消息频率为10MB/s,单个Client的带宽为512KB/s,则至少需要20个Client。
-
-对于SDK而言,其中已经封装了MQTT Client,用户在使用时需要指定对应的Client数量以及共享订阅的共享组,主题和是否为`cleanSession`,并实现MQTT Client接收到数据之后的业务。
-[Demo SDK](https://github.com/Gujiawei-Edinburgh/Data-Integration),根据上图所示进行了实现,给出了示例。
-```java
-IIntegrator integrator = Integrator.builder()
-                .clientNum(5)
-                .groupName("g1")
-                .topicFilter("test/data/integration")
-                .cleanSession(true)
-                .userName("dev")
-                .password("dev")
-                .port(1883)
-                .host("BifroMQ host")
-                .build();
-integrator.onMessageArrive()
-        .doOnComplete(IProducer.DUMMY::close)
-        .subscribe(IProducer.DUMMY::produce);
-```
-由于`IIntegrator`封装了MQTT Client,因此需要给定对应的连接信息。
-为了保证消息的传输质量,`IIntegrator`默认使用`QoS = 1`的方式进行传输,即:至少一次。因此对于下游服务而言可能存在消息的重复。
-MQTT相关参数可以参考[MQTT协议](..%2F..%2F21_mqtt%2F1_mqtt.md),共享订阅的相关信息可以参考[共享订阅](..%2F1_connect%2F1_connect.md)。
-
-对于接入者而言,可以实现`IProducer`接口,从而实现具体的业务逻辑。示例中给出了`IProducer.DUMMY`,即打印收到的消息。
-
-## 使用注意点
-* 共享组的限制。目前BifroMQ支持的最大的共享组容量默认为200,集成方可以使用[setting_provider](..%2F..%2F06_plugin%2F4_setting_provider.md)来修改相关限制。若集成方期望的客户端数量超过限制,则会导致超出部分订阅失败。
-* 集成方topicFilter的选择。根据MQTT协议,订阅分为非通配订阅和通配订阅。以下根据BifroMQ的实现,对于非通配订阅和通配订阅两种场景进行论述:
-    * 非通配订阅:集成方与上游的发送方的主题保持一致,在BifroMQ中对应的路由信息以一条entry被缓存起来,因此这类场景下缓存命中率较高。
-    * 通配订阅:上游发送方均使用相同的主题,该场景与非通配订阅类似,具有较高的缓存命中率。若上游发送方使用不同的主题,例如`test/data/{clientId}`,
-      则会导致(1)BifroMQ中缓存大量的entry,甚至超出缓存的大小限制;(2)若此时共享组也较大,则会导致对于一个主题的路由查询时延增大,
-      对于大量不同的主题,则会导致大量的主题无法命中路由缓存,导致整体性能的裂化和OOM。因此对于问题(1)可以调整缓存的大小(``SysProp: DIST_MAX_CACHED_SUBS_PER_TRAFFIC``)
-      提升缓存命中率;对于问题(2)可以增加缓存的过期时间(`expireAfterAccess`)来提高命中率。
\ No newline at end of file
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/05_user_guide/2_integration/_category_.json b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/05_user_guide/2_integration/_category_.json
deleted file mode 100644
index 97dee067..00000000
--- a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/05_user_guide/2_integration/_category_.json
+++ /dev/null
@@ -1,8 +0,0 @@
-{
-  "label": "Data Integration",
-  "position": 4,
-  "link": {
-    "type": "generated-index",
-    "description": "BifroMQ Data Integration."
-  }
-}
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/05_user_guide/2_integration/images/integration.png b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/05_user_guide/2_integration/images/integration.png
deleted file mode 100644
index b05d28b9..00000000
Binary files a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/05_user_guide/2_integration/images/integration.png and /dev/null differ
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/05_user_guide/3_API/1_api.md b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/05_user_guide/3_API/1_api.md
deleted file mode 100644
index 3e8f658e..00000000
--- a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/05_user_guide/3_API/1_api.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-sidebar_position: 1
----
-
-# API
-
-待补充
\ No newline at end of file
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/05_user_guide/3_API/_category_.json b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/05_user_guide/3_API/_category_.json
deleted file mode 100644
index 78b3394d..00000000
--- a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/05_user_guide/3_API/_category_.json
+++ /dev/null
@@ -1,8 +0,0 @@
-{
-  "label": "API Usage",
-  "position": 4,
-  "link": {
-    "type": "generated-index",
-    "description": "BifroMQ API Usage."
-  }
-}
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/05_user_guide/_category_.json b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/05_user_guide/_category_.json
deleted file mode 100644
index 22a5408b..00000000
--- a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/05_user_guide/_category_.json
+++ /dev/null
@@ -1,8 +0,0 @@
-{
-  "label": "User Guide",
-  "position": 5,
-  "link": {
-    "type": "generated-index",
-    "description": "BifroMQ User Guide."
-  }
-}
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/06_plugin/1_plugin.md b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/06_plugin/1_plugin.md
deleted file mode 100644
index cf051a3d..00000000
--- a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/06_plugin/1_plugin.md
+++ /dev/null
@@ -1,33 +0,0 @@
----
-sidebar_position: 1
-title: "概述"
----
-
-# 插件概述
-
-BifroMQ的plugin机制允许用户将自定义的业务逻辑与BifroMQ在运行时集成。目前BifroMQ定义了3种Plugin接口,用于不同的使用场景:
-
-* Auth Provider: 认证与主题Pub/Sub鉴权逻辑的集成
-* Event Collector: 收集运行时事件,实现各类事件驱动的业务逻辑
-* Setting Provider: 运行时向BifroMQ提供控制设置项,实现控制面业务逻辑的集成
-
-# Plugin 开发和部署
-
-BifroMQ使用[pf4j](https://pf4j.org)管理插件的运行时生命周期。您可以参考pf4j的文档搭建插件工程,并通过Maven中央仓库获取对应版本的Plugin的接口定义模块作为依赖。BifroMQ启动时会加载安装目录下plugins子目录中的plugin实现(pf4j支持的格式),每个plugin实现都使用独立的ClassLoader,以下package下的class加载将由bifromq负责:
-
-* `com.baidu.bifromq.*`
-* `io.micrometer.core.*`
-* `com.google.protobuf.*`
-* `org.slf4j.*`
-
-**注意**:插件内部的一些依赖项,例如 KafkaProducer,可以在其实例化期间使用了Java反射。 这个过程可能会使用Thread.currentThread().getContextClassLoader()来加载目标类,这会导致ClassNotFoundException。 对于这种情况,用户应该显式地将上下文类加载器设置为对应的插件类加载器。例如,在AuthPlugin中:
-```java
-ClassLoader calledLoader = Thread.currentThread().getContextClassLoader());
-Thread.currentThread().setContextClassLoader(yourAuthProviderInstance.getClass().getClassLoader());
-initKafkaProducer();
-Thread.currentThread().setContextClassLoader(calledLoader);
-```
-
-# 性能考量
-
-由于BifroMQ的插件接口实现会在连接和消息分发过程中被调用,应尽量保证轻量,否则将造成阻塞,严重影响连接和消息性能。
\ No newline at end of file
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/06_plugin/2_auth_provider.md b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/06_plugin/2_auth_provider.md
deleted file mode 100644
index 43a011c4..00000000
--- a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/06_plugin/2_auth_provider.md
+++ /dev/null
@@ -1,161 +0,0 @@
----
-sidebar_position: 2
-title: "Auth Provider"
----
-
-# Auth Provider Plugin
-
-Auth Provider插件旨在为BifroMQ运行时提供验证MQTT客户端连接和授权发布/订阅消息主题的能力。该插件的接口定义在以下Maven模块中:
-```
-<dependency>
-    <groupId>com.baidu.bifromq</groupId>
-    <artifactId>bifromq-plugin-auth-provider</artifactId>
-    <version>X.Y.Z</version> <!-- X.Y.Z 需替换成最新版本号-->
-</dependency>
-```
-
-## 身份认证
-
-MQTT客户端连接的认证是在连接阶段进行的。BifroMQ目前支持使用MQTT 3.1和3.1.1协议的客户端认证。该插件的回调接口如下:
-
-```java
-CompletableFuture<MQTT3AuthResult> auth(MQTT3AuthData authData);
-```
-
-实施者应该确保接口的实现是轻量级和非阻塞的,以避免对BifroMQ的连接性能产生负面影响。
-[MQTT3AuthData](https://github.com/bifromqio/bifromq/blob/main/bifromq-plugin/bifromq-plugin-auth-provider/src/main/proto/mqtt3_auth_types.proto)
-和[MQTT3AuthResult](https://github.com/bifromqio/bifromq/blob/main/bifromq-plugin/bifromq-plugin-auth-provider/src/main/proto/mqtt3_auth_types.proto)是Protobuf对象,定义如下:
-
-#### MQTT3AuthData
-
-```protobuf
-message MQTT3AuthData{
-  bool isMQIsdp = 1; // true 表示客户端使用MQTT 3.1 
-  optional string username = 2; // 客户端在Connect中指定的username
-  optional bytes password = 3; // 客户端在Connect中指定的password
-  optional bytes cert = 4; // 客户端使用的TLS连接证书
-  optional string clientId = 5; // 客户端在Connect中指定的client identifier
-  string remoteAddr = 6; // 客户端的源地址
-  uint32 remotePort = 7; // 客户端的端口
-  string channelId = 8; // 本次连接的全局唯一标识
-}
-```
-
-#### MQTT3AuthResult
-
-```protobuf
-message Ok{
-  string tenantId = 1;
-  string userId = 2;
-}
-
-message Reject{
-  enum Code {
-    BadPass = 0;
-    NotAuthorized = 1;
-    Error = 2;
-  }
-  Code code = 1;
-  optional string reason = 2; // 可选描述
-}
-
-message MQTT3AuthResult {
-  oneof Type{
-    Ok ok = 1;
-    Reject reject = 2;
-  }
-}
-```
-
-当客户端成功通过身份验证时,BifroMQ期望接口返回一个Ok结构体,包含以下字段:
-
-* tenantId:表示客户端身份所属的租户标识符
-
-* userId:表示客户端的标识符
-
-拒绝(Reject)返回值表示身份验证失败。目前支持三个原因:
-
-* BadPass:表示认证信息不正确。相关行为包括::
-  * MQTT客户端将收到 `0x04 Connection Refused, bad user name or password`。
-  * 会产生一个`NOT_AUTHORIZED_CLIENT`事件。
-
-* NotAuthorized:表示客户端身份确认,但不被授权连接,并对应以下行为
-  * 应MQTT客户端将收到`0x05 Connection Refused, not authorized`
-  * 产生`UNAUTHENTICATED_CLIENT`事件
-  
-* Error:其他认证过程中发生内部错误,额外错误信息可以通过reason可选字段补充,并对应以下行为
-  * 对应MQTT客户端将收到`0x03 Connection Refused, Server unavailable`
-  * 产生`AUTH_ERROR`事件,事件中包含reason中的内容
-
-## 行为鉴权
-
-BifroMQ目前支持对客户端操作(如发布、订阅和取消订阅)进行权限检查。插件的回调接口如下:
-
-```java
-CompletableFuture<Boolean> check(ClientInfo client,MQTTAction action);
-```
-实施者应确保接口实现轻量且非阻塞,以避免对BifroMQ的消息性能产生负面影响。
-
-[ClientInfo](https://github.com/bifromqio/bifromq/blob/main/bifromq-common-type/src/main/proto/commontype/ClientInfo.proto)
-
-与[MQTTAction](https://github.com/bifromqio/bifromq/blob/main/bifromq-plugin/bifromq-plugin-auth-provider/src/main/proto/mqtt_actions.proto)是Protobuf对象,定义如下:
-
-#### ClientInfo
-
-```protobuf
-message MQTT3ClientInfo{
-  bool isMQIsdp = 1; // true 表示客户端使用MQTT 3.1 
-  string clientId = 2; // 客户端指定的clientId
-  string ip = 3; // 客户端的源IP地址
-  uint32 port = 4; // 客户端的端口
-  string channelId = 5; // 客户端连接的全局唯一标识
-}
-
-message SysClientInfo{
-  string type = 1;
-}
-
-message ClientInfo{
-    string tenantId = 1; // 与auth方法返回Ok结构中的tenantId一致
-    string userId = 2; // 与auth方法返回Ok结构中的userId一致
-    oneof client_type{
-    SysClientInfo sysClientInfo = 3;
-    MQTT3ClientInfo mqtt3ClientInfo = 4;
-  }
-}
-```
-
-#### MQTTAction
-
-```protobuf
-message PubAction {
-  string topic = 1;
-  commontype.QoS qos = 2;
-  bool isRetained = 3;
-}
-
-message SubAction {
-  string topicFilter = 1;
-  commontype.QoS qos = 2;
-}
-
-message UnsubAction {
-  string topicFilter = 1;
-}
-
-message MQTTAction {
-  oneof Type{
-    PubAction pub = 1;
-    SubAction sub = 2;
-    UnsubAction unsub = 3;
-  }
-}
-```
-
-check方法以异步方式返回一个布尔值;true表示授予权限,false表示拒绝。如果check方法以异常终止,则最终行为由运行时设置`ByPassPermissionCheck`来控制。默认情况下,该设置为true,这意味着如果check返回异常,BifroMQ将认为权限检查已通过。然而,BifroMQ始终会生成一个`ACCESS_CONTROL_ERROR`事件。
-
-## DevOnly Mode
-
-为了方便开发和测试,当未指定AuthPlugin实现类型时,BifroMQ使用默认的[DevOnlyAuthProvider](https://github.com/bifromqio/bifromq/blob/main/bifromq-server/src/main/java/com/baidu/bifromq/server/service/authprovider/DevOnlyAuthProvider.java)。该默认实现不对客户端进行身份验证或权限检查。
-
-请注意,仅建议在开发和测试环境中使用DevOnly模式。在生产环境中绝不能使用它,因为它缺乏安全措施。
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/06_plugin/3_event_collector.md b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/06_plugin/3_event_collector.md
deleted file mode 100644
index ed4e70da..00000000
--- a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/06_plugin/3_event_collector.md
+++ /dev/null
@@ -1,29 +0,0 @@
----
-sidebar_position: 3
-title: "Event Collector"
----
-# Event Collector Plugin
-
-Event Collector Plugin 用于收集BifroMQ运行中产生的各类事件,您可以通过事件类型筛选所关注的事件,实现各类业务逻辑,典型的有:用量统计、监控告警等。Plugin的接口定义在以下Maven模块:
-
-```
-<dependency>
-    <groupId>com.baidu.bifromq</groupId>
-    <artifactId>bifromq-plugin-event-collector</artifactId>
-    <version>X.Y.Z</version> <!-- X.Y.Z 需替换成最新版本号-->
-</dependency>
-```
-
-## Event类型
-
-BifroMQ运行时产生的事件对象的类型都继承自[Event](https://github.com/bifromqio/bifromq/blob/main/bifromq-plugin/bifromq-plugin-event-collector/src/main/java/com/baidu/bifromq/plugin/eventcollector/Event.java)类。
-每个具体事件类都对应一个[EventType](https://github.com/bifromqio/bifromq/blob/main/bifromq-plugin/bifromq-plugin-event-collector/src/main/java/com/baidu/bifromq/plugin/eventcollector/EventType.java)枚举,可以通过对象上的`type()`获取,方便实现事件过滤逻辑。通过`hlc()`方法可以获取Event对象的时间戳,BifroMQ的时间戳是偏序的,可以反映事件发生的先后顺序。这对于BifroMQ在分布式部署时的事件处理逻辑十分有用。
-
-## Report方法
-当事件发生时BifroMQ会回调Plugin的`report()`方法,该方法签名如下:
-```java
-public void report(Event<?> event);
-```
-该方法会在BifroMQ的工作线程上被调用,随着负载的增加会产生大量事件,为避免创建大量的事件对象,产生过高的内存开销,传入该方法的event对象在该方法返回后会被重复使用。因此实现Event Collector Plugin需要注意以下两点:
-1. 避免在report方法中包含将过重的业务逻辑,保证report方法能快速返回,否则会对BifroMQ的性能产生负面影响
-2. 传入的event的所有权(Ownership)并未转移,如果业务逻辑是异步的,需要在report方法返回后如仍然能访问event的内容,需要在返回前使用`clone()`方法创建一个浅拷贝副本
\ No newline at end of file
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/06_plugin/4_setting_provider.md b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/06_plugin/4_setting_provider.md
deleted file mode 100644
index 3a5451a0..00000000
--- a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/06_plugin/4_setting_provider.md
+++ /dev/null
@@ -1,28 +0,0 @@
----
-sidebar_position: 4
-title: "Setting Provider"
----
-
-# Setting Provider Plugin
-
-BifroMQ定义了一类可以运行时变更的设置项([Setting](https://github.com/bifromqio/bifromq/blob/main/bifromq-plugin/bifromq-plugin-setting-provider/src/main/java/com/baidu/bifromq/plugin/settingprovider/ISettingProvider.java))
-,可以用于在租户级别动态调整BifroMQ的运行时行为。Setting Provider Plugin的作用即是为这些设置项提供运行时的自定义的值。Plugin的接口定义在以下Maven模块:
-```
-<dependency>
-    <groupId>com.baidu.bifromq</groupId>
-    <artifactId>bifromq-plugin-setting-provider</artifactId>
-    <version>X.Y.Z</version> <!-- X.Y.Z 需替换成最新版本号-->
-</dependency>
-```
-
-## Setting的初始值和校验
-每个Setting都有初始值,如:MaxTopicLength的初始值为255,校验规则为0 < MaxTopicLength < 65535的整数。Setting的初始值可以使用同名的System Property覆盖,如:BifroMQ的JVM启动参数增加`-DMaxTopicLength=128`。注意,通过System Property传入的初始值必须能够被正确解析成对应的数据类型,否则将覆盖不成功。
-
-## 更新Setting的当前值
-BifroMQ通过回调SettingProvider Plugin的`provide`方法更新Setting的当前值。provide方法的签名如下:
-```java
-public <R> R provide(Setting setting, String tenantId);
-```
-该方法会被BifroMQ的工作线程调用,因此实现Setting Provider Plugin需要注意以下两点:
-1. 避免在provide方法中包含将过重的业务逻辑,保证方法能快速返回,否则会对BifroMQ的性能产生负面影响
-2. 当不能快速决定Setting的值时,可以返回`null`,此时Setting将仍然使用当前的值,此种情况可以将Setting的决定逻辑变为异步
\ No newline at end of file
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/06_plugin/5_plugin_practice.md b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/06_plugin/5_plugin_practice.md
deleted file mode 100644
index 5e392691..00000000
--- a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/06_plugin/5_plugin_practice.md
+++ /dev/null
@@ -1,53 +0,0 @@
----
-sidebar_position: 5
-title: "BifroMQ插件实践和注意事项"
----
-# BifroMQ 中的插件实践和注意事项
-BifroMQ是一个强大的消息传递系统,允许自身与自定义服务之间进行无缝通信。在使用BifroMQ插件时,遵循最佳实践并注意一些考虑事项,以确保顺利集成和调试。
-本文概述了开发BifroMQ插件时的一些基本实践和注意事项。
-## 设置插件的完全限定名(FQN)
-在开发 BifroMQ 插件时,需要在`standalone.yml`配置文件中设置插件的完全限定名(FQN)。FQN能唯一标识插件,并帮助BifroMQ有效地加载和管理插件。
-FQN应该在配置的根级别进行设置。
-示例:
-```yaml
-authProviderFQN: com.example.plugin.MyPlugin
-```
-在此示例中,插件的FQN为`com.example.plugin.MyPlugin`。开发者应确保FQN准确地表示插件的包和类名。
-特别需要注意的是:在BifroMQ目前的实现中,[authProvider](2_auth_provider.md)和[settingProvider](4_setting_provider.md)需要指定FQN。
-对于[eventCollector](3_event_collector.md)则不需要,并且允许多种eventCollector的实现。
-## 充分利用Java 远程调试功能
-Java远程调试允许开发人员从集成开发环境(IDE)远程调试自定义插件。BifroMQ支持远程调试,可以通过环境变量`JVM_DEBUG`来启用。
-同时,还可以通过环境变量`JAVA_DEBUG_PORT`指定远程调试端口,默认端口为8008。
-在 Linux Shell 中的示例:
-```shell
-export JVM_DEBUG=true
-export JAVA_DEBUG_PORT=8009
-```
-确保正确配置调试端口,并避免端口冲突。开发者可以使用该端口连接IDE(如[IntelliJ](https://www.jetbrains.com/help/idea/tutorial-remote-debug.html) 
-或 [Eclipse](https://www.eclipse.org/community/eclipse_newsletter/2017/june/article1.php))以进行远程调试。
-若开发者期望JVM挂起直到IDE连接上去,可通过指定参数`export DEBUG_SUSPEND_FLAG=y`来改变JVM的行为。
-## 注意 Java 类加载
-在开发插件时,Java类加载非常重要,特别是如果插件依赖外部库或模块。确保在插件初始化和其他阶段正确处理类加载器。
-
-例如,`KafkaProducer`可能依赖的类使用了`ContextClassLoader`对其进行初始化。如果当前的`ContextClassLoader`指向`AppClassLoader`,
-可能会导致`ClassNotFoundException`。BifroMQ 在插件初始化阶段包含了一些场景,但开发人员在其他阶段应该保持警惕,以避免潜在的类加载问题。例如在
-某个方法中需要初始化的依赖涉及到了上述场景,可以按照如下所述的示例进行初始化。
-```java
-class MyAuthProvider {
-    public void method() {
-        try {
-            ClassLoader originalLoader = Thread.currentThread().getContextClassLoader();
-            ClassLoader targetLoader = this.getClass().getClassLoader();
-            Thread.currentThread().setContextClassLoader(targetLoader);
-            // Initialize dependencies here
-            dependenciesInit();
-        }finally {
-            Thread.currentThread().setContextClassLoader(originalLoader);
-        }
-    }
-}
-```
-## 正确组织插件目录
-在开发插件时,请确保插件目录中没有无关的jar文件。PF4J(用于 Java 的插件框架)会递归检查插件目录中的jar文件,无关的jar可能导致PF4J验证错误。
-
-保持插件目录的整洁,只包含必要的jar文件,确保插件加载顺利,避免任何冲突或验证问题。
\ No newline at end of file
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/06_plugin/_category_.json b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/06_plugin/_category_.json
deleted file mode 100644
index d5e7a03d..00000000
--- a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/06_plugin/_category_.json
+++ /dev/null
@@ -1,8 +0,0 @@
-{
-  "label": "Plugin",
-  "position": 6,
-  "link": {
-    "type": "generated-index",
-    "description": "BifroMQ Plugin."
-  }
-}
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/07_operations/1_tls.md b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/07_operations/1_tls.md
deleted file mode 100644
index 87d32613..00000000
--- a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/07_operations/1_tls.md
+++ /dev/null
@@ -1,18 +0,0 @@
----
-sidebar_position: 1
----
-
-# TLS 配置
-
-## 简介
-
-TLS允许使用加密方法在客户机和服务器的网络上传输信息,防止任何未经授权的人监听您的通信或访问您通过网络发送的数据。
-BifroMQ提供丰富的SSL/TLS接入能力支持,包括TLS接入及WebSocket Security接入。同时支持灵活的切换单/双向认证,您可以根据配置选择不同的认证级别。
-
-## 前置准备
-
-您需要准备配置使用的SSL/TLS证书,在测试环境使用openssl工具生成自签名证书即可,在生产环境应使用可信CA机构签发的证书。
-
-## 通过配置开启
-
-按照[配置文件手册](../04_configuration/2_file_configs_manual.md)中`brokerSSLCtxConfig`部分参数的介绍:开启对应的认证级别,填写对应的证书名称,并将证书文件放置在配置参数描述中的位置。
\ No newline at end of file
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/07_operations/2_high_availability.md b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/07_operations/2_high_availability.md
deleted file mode 100644
index 9c68d091..00000000
--- a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/07_operations/2_high_availability.md
+++ /dev/null
@@ -1,8 +0,0 @@
----
-sidebar_position: 2
----
-
-# 高可用
-
-待补充
-
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/07_operations/4_logs_observable.md b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/07_operations/4_logs_observable.md
deleted file mode 100644
index 4ea8c82c..00000000
--- a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/07_operations/4_logs_observable.md
+++ /dev/null
@@ -1,53 +0,0 @@
----
-sidebar_position: 4
----
-
-# 日志和可观察性
-
-## 日志
-
-BifroMQ基于标准的slf4j接口产出日志,日志内容分为TRACE、DEBUG、INFO、WARN、ERROR五个等级的内容,您可通过修改配置文件自行决定打印其中任意日志内容。
-
-### 配置文件
-
-日志配置文件名称为logback.xml,位置位于:
-
-| 安装方式   | 文件位置                            |
-| :--------- | ----------------------------------- |
-| 压缩包解压 | ./conf/logback.xml                  |
-| Docker容器 | /usr/share/bifromq/conf/logback.xml |
-
-日志配置文件为标准的logback配置方式,此处不再进行详细介绍,您可自行修改配置。
-
-需要额外关注的是:自带的logback配置文件,会根据系统参数中的“LOG_DIR”及“user.dir”设置日志文件所在目录。
-
-
-
-## Event事件收集
-
-BifroMQ在运行过程中,会将内部一些关键运行节点的实时执行信息提炼为Event,统一通过 EventCollectorManager 写出。
-
-Event类型大致分为:
-
-* MQTT协议相关Event,如连接、断连、订阅、推送消息等。
-* 告警类型相关Event,如违反协议行为、内部错误、容量超限等。
-
-Event写出的目的地,为启动时通过pf4j加载的IEventCollector扩展点的实现。
-
-您可参考[DemoEventLogger](https://github.com/bifromqio/bifromq/blob/main/build/build-plugin-demo/src/main/java/com/baidu/demo/plugin/EventLogger.java) 来实现自己的EventCollector,用来获取BifroMQ提供的丰富的运行时事件。
-
-
-
-## Metrics
-
-BifroMQ内置了丰富的基于Micrometer的Metrics系统指标来帮助使用者了解当前服务实时状态,监测系统健康度和定位系统的性能问题。
-
-您可以通过集成至prometheus的方式将Metrics进行输出,也可以选择通过Micrometer支持的其余方式进行输出。
-
-### Prometheus集成方式
-
-BifroMQ本身没有默认内置Micrometer向Prometheus输出的组件,您可以创建由pf4j框架加载的Plugin,在Plugin中实现Micrometer向Prometheus的推送或者拉取。
-
-您下载的压缩包解压得到的./plugins/demo-plugin-1.0.0-SNAPSHOT.jar已经提供了Endpoint供Prometheus进行Metrics的拉取:`http://127.0.0.1:9090/metrics`
-
-也可以参考[DemoPlugin](https://github.com/bifromqio/bifromq/blob/main/build/build-plugin-demo/src/main/java/com/baidu/demo/plugin/DemoPlugin.java) 来实现自己的Plugin。
\ No newline at end of file
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/07_operations/_category_.json b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/07_operations/_category_.json
deleted file mode 100644
index 79159095..00000000
--- a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/07_operations/_category_.json
+++ /dev/null
@@ -1,8 +0,0 @@
-{
-  "label": "Operations",
-  "position": 7,
-  "link": {
-    "type": "generated-index",
-    "description": "BifroMQ operations."
-  }
-}
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/08_best_practices/1_mqtt_parameters.md b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/08_best_practices/1_mqtt_parameters.md
deleted file mode 100644
index 94651fa1..00000000
--- a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/08_best_practices/1_mqtt_parameters.md
+++ /dev/null
@@ -1,40 +0,0 @@
----
-sidebar_position: 1
----
-
-# MQTT参数选取
-
-MQTT是一种轻量级的消息传输协议,它被广泛应用于物联网、传感器网络和移动应用程序等领域。当使用MQTT连接时,合理选择参数可以提高通信效率和可靠性。
-
-## 客户端ID(ClientID)
-
-ClientID 是MQTT连接的唯一标识符。在IoTCore中,不同实例之间是隔离的,故实际上 CoreID + ClientID 唯一标识了一个客户端连接。
-
-如果多个客户端使用相同的 ClientID 连接到MQTT服务器,那么只有最后一个连接会被保留,其他连接会被强制断开。
-
-在使用MQTT连接时,客户端ID应该是唯一的,并且应该易于识别。一个通常的做法是,使用固定前缀加上随机生成的UUID作为ClientID:前缀可以用来标识客户端的身份或分组,UUID保证了唯一性。
-
-## QoS级别
-
-QoS级别是MQTT中用于确保消息可靠传递的参数。MQTT定义了三个QoS级别,分别是0、1和2。
-
-- QoS 0表示最多一次传递(At Most Once),消息推送出去后并不检查是否到达。
-- QoS 1表示至少一次传递(At Least Once),消息推送后会检查服务端/设备端返回的Ack,若超时则会重发。能保证对方收到消息,但可能存在消息重复。
-- QoS 2表示恰好一次传递(Exactly Once)。
-选择较高的QoS级别可以提高消息传递的可靠性,但同时也会增加通信的延迟和带宽消耗,并增大对服务器资源的需求。
-
-对于偶尔丢失少量影响不大的消息,建议使用 QoS 0。否则可以使用 QoS 1,并在部署时考虑到这一点,以满足相应的资源需求。
-
-
-## 清理会话标志(cleanSession)
-
-cleanSession 标志在MQTT中用于确定客户端与MQTT服务器之间是否要保存连接状态。
-
-cleanSession 设置为 True 时,MQTT服务器会清除客户端之前发布的所有消息,同时清除与该客户端相关的连接状态信息。而设置为 False时,MQTT服务器将保留与该客户端相关的连接状态信息,以便客户端可以接收之前发布的消息。
-
-默认情况下,应该选择 cleanSession 为 True 的连接设置。在这种设置下,消息的推送更加快速,需求的服务器资源也将大大减少。我们强烈建议将高频、数量大的消息的订阅连接设置为 cleanSession True。
-
-如果某些Topic下的消息需要在订阅端断线的情况下也不丢失,可以在订阅时设置 cleanSession 为 False。但请注意,这个设置下的消息推送需求的服务器性能大大高于 cleanSession True 的情况,并且因为中间还存在缓存消息的环节,其消息推送的延迟和消息溢出的风险也明显更高。
-
-> 尽量选择 cleanSession True 的设置,只在最必要的情况下使用 cleanSession False。
-> 尽量降低使用 cleanSession False 的消息量,这会带来更好的性能和更低的风险。
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/08_best_practices/2_topicfilter.md b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/08_best_practices/2_topicfilter.md
deleted file mode 100644
index a033f2c5..00000000
--- a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/08_best_practices/2_topicfilter.md
+++ /dev/null
@@ -1,20 +0,0 @@
----
-sidebar_position: 1
----
-
-# 主题设计
-
-主题 TopicFilter 是MQTT中用于订阅主题的一种机制,它可以让客户端只接收到自己感兴趣的Topic消息。在选择和设计TopicFilter时,以下是一些建议:
-
-- 粒度要适当:TopicFilter的粒度应该与应用程序需求相匹配。如果粒度太粗,会导致客户端接收到大量不必要的消息,从而增加网络流量和资源消耗。而如果粒度太细,会导致客户端无法接收到自己感兴趣的消息,从而影响应用程序的正常运行。应当根据实际情况进行适当的粒度选择。
-
-- 考虑通配符:TopicFilter支持通配符的使用,包括单层通配符和多层通配符。单层通配符“+”用于匹配单个层级的任意字符,而多层通配符“#”用于匹配任意层数的字符。在设计TopicFilter时,可以考虑使用通配符来简化过滤规则和扩展过滤范围。
-
-- 尽量避免使用“#”通配符:虽然多层通配符“#”可以匹配任意层数的字符,但它也可能会导致安全问题。如果将“#”通配符用于订阅高度敏感的Topic,可能会导致未经授权的客户端接收到敏感信息。因此,在设计TopicFilter时,应该尽量避免使用“#”通配符。
-
-- 考虑Topic命名规范:为了保证Topic的可读性和易用性,可以考虑采用Topic命名规范。Topic命名规范可以指定主题的命名格式、命名约定和命名规则等,从而使Topic更易于管理和使用。
-
-- 考虑Topic的层级结构:Topic的层级结构可以影响TopicFilter的设计和使用。在设计Topic层级结构时,可以考虑将Topic按照功能、区域、设备等分类,从而实现更精细的TopicFilter和更灵活的Topic订阅机制。
-
-总的来说,TopicFilter的选择和设计应该考虑应用程序的需求和场景,并遵循合适的规范和最佳实践。
-
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/08_best_practices/_category_.json b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/08_best_practices/_category_.json
deleted file mode 100644
index fbe1e3bc..00000000
--- a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/08_best_practices/_category_.json
+++ /dev/null
@@ -1,8 +0,0 @@
-{
-  "label": "Best Practices",
-  "position": 8,
-  "link": {
-    "type": "generated-index",
-    "description": "Best Practices."
-  }
-}
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/09_faq/1_bifromq.md b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/09_faq/1_bifromq.md
deleted file mode 100644
index 8e1be46a..00000000
--- a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/09_faq/1_bifromq.md
+++ /dev/null
@@ -1,46 +0,0 @@
----
-sidebar_position: 1
----
-
-# BifroMQ 的使用与集成
-
-## BifroMQ 对于 Java 版本的需求是什么?
-
-对于 BifroMQ 的 Java 版本需求,我们可以将其分为两个部分:
-
-- **BifroMQ 运行环境**:BifroMQ 本身的运行需要 JDK 17 或更高版本。
-- **BifroMQ 插件开发**:在开发 BifroMQ 插件时,我们并不强制要求特定的 Java 语言版本和 JDK 版本。但是,插件开发者需要注意确保其插件在高版本的 Java 环境中能够正常运行。为了避免兼容性问题,我们建议插件的运行环境与 BifroMQ 的运行环境保持一致。
-
-## BifroMQ 是否内置了规则引擎功能?
-
-不同于其他提供 MQTT 协议能力的产品或项目,BifroMQ 的明确定位是作为一个实现了标准 MQTT 协议、具有多租户架构和高性能的分布式中间件。"规则引擎"并不属于 MQTT 协议规范的内容,因此不会作为 BifroMQ 的一部分出现。
-BifroMQ 更专注于以标准的方式实现上下游系统的集成。从这个角度来看,"规则引擎"只是与 BifroMQ "集成"的一种功能形态(而且不同规则引擎项目之间也存在功能差别)。我们更希望这部分需求能以开放的方式,在 BifroMQ 的开发社区内得到满足。
-
-## 如何使用 BifroMQ 进行数据集成?
-
-使用 BifroMQ 进行数据集成的方式主要取决于您的业务场景:
-
-- **单租户系统**:对于逻辑上的单租户系统,其他系统可以直接使用 MQTT 协议与 BifroMQ 集成。例如,可以使用共享订阅来并行订阅消息,或者使用 MQTT Client 直接向 BifroMQ 发布消息。这种方式可以实现上下游系统的完全解耦,并且也便于进行不同 MQTT 中间件的替换比较。一般的企业自用应用系统属于此类。
-
-- **多租户系统**:对于多租户业务场景,BifroMQ 将作为整个多租户业务系统的一个子系统。在这种情况下,系统集成需要使用 BifroMQ 的插件机制。下游系统与 BifroMQ 在插件层面会有一定的耦合,因此实现起来相对复杂。一般用于对外提供业务支持或云服务等场景。
-
-## BifroMQ 的内置存储引擎主要用于哪些数据的持久化?
-
-BifroMQ 的内置存储引擎主要用于 MQTT 协议定义的需要持久化(CleanSession=false)的 SessionState(详见:[MQTT v3.1.1 3.1.2.4](http://docs.oasis-open.org/mqtt/mqtt/v3.1.1/os/mqtt-v3.1.1-os.html#_Toc398718028))和 Retain Topic 的消息。这样可以避免在 Broker 重启或宕机时造成会话状态丢失。
-值得注意的是,持久化引擎在绝大多数情况下与消息的 QoS 没有直接关系,例如:当 MQTT 连接开启持久会话时,离线阶段收到的 QoS0 订阅消息仍然会被持久化,直到会话恢复时完成推送。
-
-## BifroMQ 为什么没有管理控制台/ UI 界面?
-
-BifroMQ 更注重在各种类型的业务系统中的集成性,因此在中间件层面并未定义更上层的管理模式和概念。然而,BifroMQ 提供了以下能力,可以实现运行时的控制面集成和监控:
-
-- **[API](../05_user_guide/3_API/1_api.md)**:Broker 侧的控制逻辑,如强制断开连接等(待开放)。
-- **[Metrics](../07_operations/4_logs_observable.md)**:BifroMQ 的运行时指标,可以与已有的监控系统集成。
-- **[EventCollectorPlugin](../06_plugin/3_event_collector.md)**:BifroMQ 运行中产生的各类事件,可以实现各类 Event Sourcing 的业务逻辑,如连接数统计,上下线事件等。
-- **[SettingProviderPlugin](../06_plugin/3_event_collector.md)**:用于实现租户级运行时设置的调整。
-
-我们同样鼓励社区开发者用户能参与满足这方面的需求,封装出多样化的 UI 管理界面。
-
-## BifroMQ 与 IoT Core 之间的关系是什么?
-
-物联网核心套件 IoT Core 是百度智能云的一个公有云服务,支持预付费和按需计费。
-BifroMQ 与 IoT Core 的关系非常紧密,因为 BifroMQ 是 IoT Core 的底层基础技术。BifroMQ 的多租户、高性能、分布式的能力,为构建大规模的 IoT Core 设备连接和消息系统提供了强大的支持。
\ No newline at end of file
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/09_faq/2_mqtt.md b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/09_faq/2_mqtt.md
deleted file mode 100644
index 9ffa1813..00000000
--- a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/09_faq/2_mqtt.md
+++ /dev/null
@@ -1,44 +0,0 @@
----
-sidebar_position: 2
----
-
-# MQTT 的使用
-
-## 为什么物联网要使用MQTT协议?对比HTTP协议有什么优势?
-
-物联网设备通常需要发送和接收小型的数据包,如传感器读数、设备状态等等。MQTT (Message Queuing Telemetry Transport)是一个基于发布/订阅模式的轻量级通信协议,专门为低带宽和不可靠网络环境设计,非常适合于物联网应用。
-
-相对于HTTP协议,MQTT具有以下优势:
-
-- 更轻量级:对比HTTP的庞大协议头,MQTT协议非常精简,消息体比HTTP更小,可以减少网络传输负担。
-- 更低功耗:MQTT协议的低功耗特性使其非常适合于物联网设备,例如传感器、智能家居等设备,这些设备通常拥有非常有限的电池寿命。
-- 更高效率:MQTT协议采用了推送的方式来传递消息,可以大大减少客户端和服务器之间的通信开销。同时,MQTT协议的QoS机制也可以确保消息的可靠传输,使得通信更加稳定和高效。
-- 更易扩展:MQTT协议采用了主题(Topic)的发布/订阅模式,使得系统的可扩展性更高,可以快速适应新的设备和应用场景。相比之下,HTTP协议需要在服务器端部署RESTful接口,限制了系统的扩展性。
-
-总之,MQTT协议适用于需要低功耗、小型数据包和高效传输的物联网设备,HTTP协议则适用于需要大量数据传输和更复杂请求响应的应用场景。
-
-## 如何应对客户端与服务端的连接不正常断开?
-考虑到物联网设备经常工作在不稳定的网络环境,MQTT协议以及常见的开源客户端实现都对连接意外中断有相应设计和处理。
-
-请为客户端设置断线自动重连,如果客户端还负责订阅主题的话,还需要设置重连后自动重新订阅。
-
-如果不希望丢失断线期间的重要消息,可以将订阅设置中的cleanSession设置为False。但请慎重的使用这一设置,并合理设置topicfilter,将重要消息与大量的普通消息分开,仅为最必要的消息订阅使用。大量不合理的使用cleanSession False设置会带来严重的性能压力和更大的消息丢失风险。
-
-如果出现不符合预期的高频率意外断连,请检查客户端到服务端的网络链路。
-
-## 为什么会出现消息丢失,发送成功的消息订阅端没有收到?
-消息丢失存在多种可能:
-
-- 网络不稳定导致丢包:依物联网设备的具体网络环境可能出现不同程度的丢包。如果需要保证消息到达,可以使用 qos 1 的设置来发送和订阅消息。这一设置也会消耗更多的性能。
-- 订阅端掉线:如果一个topic没有被订阅,那么消息会被直接丢弃。
-- 单连接收发消息超限:默认配置下单个客户端拥有每秒200条消息、512MB带宽的限制。如果是发送端,超出这个限制的消息会发送失败,而如果是订阅端超出,cleanSession True设置下的消息会被丢弃。
-- 发送消息的频率太高导致下游溢出:cleanSession True下的订阅端、规则引擎下游溢出,cleanSession False下的inbox消息缓存溢出等。可以合理拆分topic来降低每个订阅端收到的消息频率,或是使用共享订阅。
-- 资源不足:若部署 BifroMQ 服务的内存或CPU资源,不足以支持业务规模,也可能造成此情况,需要评估业务规模并合理扩容。
-
-## 订阅端收到的消息顺序和发送顺序一致吗?
-依据MQTT协议,我们保证了消息顺序。
-
-特别的,在QoS 0下,单一发送端发送的消息一定是先发送的先到达。在QoS 1下,因为存在重发消息的情况,可能存在偶尔的乱序,但重发消息后,按照协议,会按顺序将重发消息后面的消息再按序发送,保证客户收到的消息序列中,至少存在一条子序列是完全有序的。
-
-# 为什么会重复出现连接 - 断开 - 重连 - 再断开的情况?
-一般是因为互踢。ClientID必须唯一,否则会断开前面已经连接的冲突设备。如果这两个设备都设置了断线自动重连,那么就会反复互踢,出现此问题的情况。
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/09_faq/_category_.json b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/09_faq/_category_.json
deleted file mode 100644
index d69e9cf0..00000000
--- a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/09_faq/_category_.json
+++ /dev/null
@@ -1,8 +0,0 @@
-{
-  "label": "FAQ",
-  "position": 8,
-  "link": {
-    "type": "generated-index",
-    "description": "Frequently Asked Questions."
-  }
-}
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/21_mqtt/1_mqtt.md b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/21_mqtt/1_mqtt.md
deleted file mode 100644
index 9d6a7d91..00000000
--- a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/21_mqtt/1_mqtt.md
+++ /dev/null
@@ -1,9 +0,0 @@
----
-sidebar_position: 1
----
-
-# MQTT 规范
-
-在此查看  [MQTT 3.1.1](https://public.dhe.ibm.com/software/dw/webservices/ws-mqtt/mqtt-v3r1.html) 或 [MQTT 3.1.1](http://docs.oasis-open.org/mqtt/mqtt/v3.1.1/os/mqtt-v3.1.1-os.html)(推荐)规范的全文,BifroMQ 中完全支持该规范。
-
-你也可以参考 [MQTT 5.0 共享订阅](https://docs.oasis-open.org/mqtt/mqtt/v5.0/os/mqtt-v5.0-os.html#_Toc3901250) 中的`共享订阅`部分,BifroMQ 也支持。
\ No newline at end of file
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/21_mqtt/_category_.json b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/21_mqtt/_category_.json
deleted file mode 100644
index e3ab68a7..00000000
--- a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/21_mqtt/_category_.json
+++ /dev/null
@@ -1,8 +0,0 @@
-{
-  "label": "MQTT",
-  "position": 21,
-  "link": {
-    "type": "generated-index",
-    "description": "MQTT Specification Link."
-  }
-}
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/999_bifromq_inside.md b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/999_bifromq_inside.md
deleted file mode 100644
index def23db7..00000000
--- a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/999_bifromq_inside.md
+++ /dev/null
@@ -1,26 +0,0 @@
----
-sidebar_position: 999
----
-
-# BifroMQ Inside
-
-本页记录了 `集成` 了 BifroMQ 的项目或产品。如果你的项目集成了 BifroMQ 或为 BifroMQ 开发(如插件、控制台),可在[这里提交](https://github.com/bifromqio/bifromq-docs/issues/new?assignees=visoar&labels=BifroMQ+Inside&projects=&template=bifromq-inside.md&title=%5BBifroMQ+Inside%5D+Your+Project%2FProduct+Name)。
-
-### Cloud
-
-* [Baidu IoT Core](https://cloud.baidu.com/product/iot.html) - 物联网核心套件(IoT Core)是全托管的 Serverless 云服务,提供海量设备接入与管理、规则引擎等能力,轻松完成物联网应用搭建的第一步。
-
-### IoT Platforms
-
-* [Baidu IoT platform](https://iot.baidu.com/) - 百度天工AIoT物联网平台利用云-边缘-设备的能力,提供全面、人性化和针对特定行业的物联网解决方案。
-* [ThingLinks](https://mqttsnet.yuque.com/gt6zkc/thinglinks) - ThingLinks 物联网平台具备了多样的、广泛的设备连接能力,帮助用户将海量设备数据采集上云,快速集成应用构建物联网业务。
-
-### 插件
-
-* [BifroMQ-plugin-anyAuth](https://github.com/Gujiawei-Edinburgh/bifromq-plugin-anyAuth) - 一个BifroMQ的身份验证插件,支持微信和Auth0身份验证,并且可以扩展以适应更多社交媒体账户的认证需求。在授权方面,该项目使用了访问控制列表(ACL)进行管理。每个动作(如发布和订阅)均有其自定义的权限规则,这些规则是基于每个用户设定的,而不是针对单一客户端。
-
-
-
-
-
-
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/1_test_report.md b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/1_test_report.md
deleted file mode 100644
index a758dd0d..00000000
--- a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/1_test_report.md
+++ /dev/null
@@ -1,416 +0,0 @@
-# 测试报告
-
-## 测试目的
-
-测试BifroMQ单机版在不同消息吞吐模式下,响应时间及资源消耗等性能指标。
-
-## 测试工具、测试环境
-
-### 测试工具
-
-基于vertx-mqtt开发的测试工具,具有较灵活的使用方式及优良的性能表现。
-
-### 测试环境
-
-BifroMQ部署机:CentOS release 7.6, 32核, 128G内存(实际配置JVM内存40G)
-发压机:CentOS release 7.6, 32核, 128G内存(实际配置JVM内存32G)
-
-
-## 测试场景
-
-本测试报告主要针对消息吞吐测试。  
-测试维度分为:  
-
-* Pub & Sub比例:1对1、1对多
-* cleanSession配置:true | false
-* QoS:0 | 1 | 2
-* payload大小:32b | 1024b
-* 单连接消息频率:1 ~ 100不等
-* 共享订阅
-
-每个场景的测试由以上维度组合而来。
-
-## 测试报告
-
-### 参数说明
-
-场景名称由测试用例中各维度参数组合而来,如100_100_qos0_p1024_50mps表示:
-
-* 100个Pub MQTT client
-* 100个Sub MQTT client
-* 消息及订阅质量使用QoS0
-* 单个消息payload大小1024 bytes
-* 单个Pub client每秒发送50条message至BifroMQ
-
-| 参数 | 说明                      |
-| ---- | ------------------------- |
-| C    | 测试用例总MQTT连接数      |
-| m/s  | 每秒发送至BifroMQ的消息数 |
-| ms   | 响应时间,单位毫秒        |
-
-### 结果说明
-
-1. cleanSession=true高频场景消息吞吐最高可达20W/s以上,低频场景消息吞吐最高可达10W/s以上。
-2. cleanSession=false高频场景消息吞吐最高可达1.5W/s以上,低频场景消息吞吐最高可达1W/s以上。
-3. 消息从Pub端至Sub端的响应时间均为毫秒级,CPU负载均处于低位。
-4. 系统吞吐及时延性能受QoS质量影响较大,其中QoS0与QoS1场景差距不明显,QoS2场景受影响较为明显,原因为协议本身复杂度导致。
-5. 在一些测试场景附图中的首个采样点的latency数据偏大,是测试用例未经预热直接冷启动引起的压力负荷突变导致,平稳运行中的服务不会出现此情况。
-6. cleanSession=false与cleanSession=true场景的性能结果存在数倍的差距。原因是BifroMQ的架构是为构建serverless云服务而设计的,离线消息的可靠性是云服务SLA的重要指标,因此BifroMQ选择了基于磁盘而非内存的持久化策略,在宕机或重启时不会丢失数据。单机(Standalone)版本的离线消息存储性能受到当前测试机器本地磁盘 IO 性能的限制,采用高性能磁盘替换,或在集群环境下搭配合适的负载策略,都可以有效提升性能。
-
-### cleanSession=true高频场景
-
-#### QoS0场景
-| 场景组合                     | QoS | 单连接m/s | Payload(byte) | 连接数C | 总消息m/s | 平均响应时间ms | P99响应时间ms | CPU |
-|--------------------------|-----|--------|---------------|------|--------|----------|-----------|-----|
-| 100_100_qos0_p1024_50mps | 0   | 50     | 1024          | 200  | 5k     | 0.31     | 0.43      | 2.5% |
-| 1k_1k_qos0_p1024_50mps   | 0   | 50     | 1024          | 2k   | 50k    | 0.42     | 1.30      | 21% |
-| 2k_2k_qos0_p32_100mps    | 0   | 100    | 32            | 4k   | 200k   | 2.38   | 15.72    | 40% |
-| 4k_4k_qos0_p32_50mps     | 0   | 50     | 32            | 8k   | 200k   | 6.65    | 48.23    | 31% |
-| 5k_5k_qos0_p32_50mps     | 0   | 50     | 32            | 10k  | 226k   | 12.51    | 56.61    | 30% |
-
-4k_4k_qos0_p32_50mps场景附图:
-
-![qps](./images/true_4k_4k_qos0_p32_50mps/qps.png)
-![mean](./images/true_4k_4k_qos0_p32_50mps/mean.png)
-![p99](./images/true_4k_4k_qos0_p32_50mps/p99.png)
-![max](./images/true_4k_4k_qos0_p32_50mps/max.png)
-
-#### QoS1场景
-| 场景组合                     | QoS | 单连接m/s | Payload(byte) | 连接数C | 总消息m/s | 平均响应时间ms | P99响应时间ms | CPU |
-|--------------------------|-----|--------|---------------|------|--------|----------|-----------|-----|
-| 100_100_qos1_p1024_50mps | 1   | 50     | 1024          | 200  | 5k     | 0.27     | 0.42      | 2.6% |
-| 1k_1k_qos1_p1024_50mps   | 1   | 50     | 1024          | 2k   | 50k    | 0.49     | 1.89      | 23% |
-| 2k_2k_qos1_p32_100mps    | 1   | 100    | 32            | 4k   | 182k   | 20.89   | 218.1    | 38% |
-| 4k_4k_qos1_p32_50mps     | 1   | 50     | 32            | 8k   | 179k   | 31.35    | 352.31    | 26% |
-| 5k_5k_qos1_p32_50mps     | 1   | 50     | 32            | 10k  | 189k   | 54.43    | 419.42    | 36% |
-
-2k_2k_qos1_p32_50mps场景附图:
-
-![qps](./images/true_2k_2k_qos1_p32_50mps/qps.png)
-![mean](./images/true_2k_2k_qos1_p32_50mps/mean.png)
-![p99](./images/true_2k_2k_qos1_p32_50mps/p99.png)
-![max](./images/true_2k_2k_qos1_p32_50mps/max.png)
-
-#### QoS2场景
-
-| 场景组合                     | QoS | 单连接m/s | Payload(byte) | 连接数C | 总消息m/s | 平均响应时间ms | P99响应时间ms | CPU |
-|--------------------------|-----|--------|---------------|------|--------|----------|-----------|-----|
-| 1.2k_1.2k_qos2_p32_50mps   | 2   | 100     | 32          | 2.4k   | 120k    | 7.08     | 41.93      | 40% |
-| 2k_2k_qos2_p32_100mps    | 2   | 100    | 32            | 4k   | 138k   | 38.02   | 201.31    | 40% |
-
-1.2k_1.2k_qos2_p32_50mps场景附图:
-
-![qps](./images/true_1.2k_1.2k_qos2_p32_50mps/qps.png)
-![mean](./images/true_1.2k_1.2k_qos2_p32_50mps/mean.png)
-![p99](./images/true_1.2k_1.2k_qos2_p32_50mps/p99.png)
-![max](./images/true_1.2k_1.2k_qos2_p32_50mps/max.png)
-
-### cleanSession=true低频场景
-
-#### QoS0场景
-| 场景组合                      | QoS | 单连接m/s | Payload(byte) | 连接数C | 总消息m/s | 平均响应时间ms | P99响应时间ms | CPU |
-|---------------------------|-----|--------|---------------|------|--------|------|-------|-----|
-| 50k_50k_qos0_p1024_1mps   | 0   | 1      | 1024          | 100k | 50k    | 0.85 | 4.16  | 23% |
-| 100k_100k_qos0_p1024_1mps | 0   | 1      | 1024          | 200k | 100k   | 13.54     | 209.68      | 40%  |
-
-100k_100k_qos0_p1024_1mps场景附图:
-
-![qps](./images/true_100k_100k_qos0_p1024_1mps/qps.png)
-![mean](./images/true_100k_100k_qos0_p1024_1mps/mean.png)
-![p99](./images/true_100k_100k_qos0_p1024_1mps/p99.png)
-![max](./images/true_100k_100k_qos0_p1024_1mps/max.png)
-
-#### QoS1场景
-| 场景组合                      | QoS | 单连接m/s | Payload(byte) | 连接数C | 总消息m/s | 平均响应时间ms | P99响应时间ms | CPU |
-|---------------------------|-----|--------|---------------|------|--------|----------|-----|-----|
-| 50k_50k_qos1_p1024_1mps   | 1   | 1      | 1024          | 100k | 50k    | 5.55     | 14.12 | 32% |
-| 100k_100k_qos1_p1024_1mps | 1   | 1      | 1024          | 200k | 100k   | 27.36    | 603.95    | 30% |
-
-100k_100k_qos1_p1024_1mps场景附图:
-
-![qps](./images/true_100k_100k_qos1_p1024_1mps/qps.png)
-![mean](./images/true_100k_100k_qos1_p1024_1mps/mean.png)
-![p99](./images/true_100k_100k_qos1_p1024_1mps/p99.png)
-![max](./images/true_100k_100k_qos1_p1024_1mps/max.png)
-
-#### QoS2场景
-| 场景组合                      | QoS | 单连接m/s | Payload(byte) | 连接数C | 总消息m/s | 平均响应时间ms | P99响应时间ms | CPU |
-|---------------------------|-----|--------|---------------|------|--------|----------|-----------|-----|
-| 50k_50k_qos2_p1024_1mps   | 2   | 1      | 1024          | 100k | 50k    | 25.32    | 184.48    | 25% |
-
-50k_50k_qos2_p1024_1mps场景附图:
-
-![qps](./images/true_50k_50k_qos2_p1024_1mps/qps.png)
-![mean](./images/true_50k_50k_qos2_p1024_1mps/mean.png)
-![p99](./images/true_50k_50k_qos2_p1024_1mps/p99.png)
-![max](./images/true_50k_50k_qos2_p1024_1mps/max.png)
-
-### cleanSession=true共享订阅场景
-
-| 场景组合                    | QoS | 单连接m/s | Payload(byte) | 连接数C   | 总消息m/s | 平均响应时间ms | P99响应时间ms | CPU |
-|-------------------------|-----|--------|---------------|--------|--------|----------|-----------|-----|
-| 40k_400_qos0_p1024_1mps | 0   | 1      | 1024          | 400.4k | 40k    | 0.32     | 3.40      | 18% |
-| 40k_400_qos1_p1024_1mps | 1   | 1      | 1024          | 400.4k | 40k    | 0.61     | 6.81      | 19% |
-| 40k_400_qos2_p1024_1mps | 2   | 1      | 1024          | 400.4k | 40k    | 0.81   | 7.06    | 23% |
-
-40k_400_qos2_p1024_1mps场景附图:
-
-![qps](./images/share_true_40k_400_qos2_p1024_1mps/qps.png)
-![mean](./images/share_true_40k_400_qos2_p1024_1mps/mean.png)
-![p99](./images/share_true_40k_400_qos2_p1024_1mps/p99.png)
-![max](./images/share_true_40k_400_qos2_p1024_1mps/max.png)
-
-### cleanSession=false共享订阅场景
-
-| 场景组合                  | QoS | 单连接m/s | Payload(byte) | 连接数C   | 总消息m/s | 平均响应时间ms | P99响应时间ms | CPU |
-|-----------------------|-----|--------|---------------|--------|--------|----------|-------|-----|
-| 5k_50_qos0_p1024_1mps | 0   | 1      | 1024          | 5050   | 5k     | 7.22     | 30.38 | 7%  |
-| 5k_50_qos1_p1024_1mps | 1   | 1      | 1024          | 5050 | 5k     | 6.79     | 27.23 | 7%  |
-| 5k_50_qos2_p1024_1mps | 2   | 1      | 1024          | 5050 | 5k     | 16.24     | 56.56      | 7%  |
-
-5k_50_qos2_p1024_1mps场景附图:
-
-![qps](./images/share_false_40k_400_qos2_p1024_1mps/qps.png)
-![mean](./images/share_false_40k_400_qos2_p1024_1mps/mean.png)
-![p99](./images/share_false_40k_400_qos2_p1024_1mps/p99.png)
-![max](./images/share_false_40k_400_qos2_p1024_1mps/max.png)
-
-### cleanSession=true fanOut场景
-
-少量客户端作为Publisher,大量客户端订阅相同的topic作为Subscriber,形成每条消息被大规模fanOut广播的场景。
-
-| 场景组合              | QoS  | 单连接m/s | Payload(byte) | Pub连接数C | Sub连接数 | Pub消息m/s | Sub消息m/s | 平均响应时间ms | P99响应时间ms | CPU  |
-| --------------------- | ---- | --------- | ------------- | ---------- | --------- | ---------- | ---------- | -------------- | ------------- | ---- |
-| 1_1k_qos1_p32_1mps    | 1    | 1         | 32            | 1          | 1k        | 1          | 1k         | 6              | 18            | 4%   |
-
-1_1k_qos1_p32_1mps场景附图:
-
-![qps](./images/true_1_1k_qos1_p32_1mps/qps.png)
-![mean](./images/true_1_1k_qos1_p32_1mps/mean.png)
-![p99](./images/true_1_1k_qos1_p32_1mps/p99.png)
-![max](./images/true_1_1k_qos1_p32_1mps/max.png)
-
-
-
-
-### cleanSession=false 1对1 低频场景
-
-
-#### QoS0场景
-
-| 场景组合                | QoS  | 单连接m/s | Payload(byte) | 连接数C | 总消息m/s | 平均响应时间ms | P99响应时间ms | CPU  |
-| ----------------------- | ---- | --------- | ------------- | ------- | --------- | -------------- | ------------- | ---- |
-| 1k_1k_qos0_p32_1mps     | 0    | 1         | 32            | 2k      | 1k        | 1.3            | 2.2           | 6%   |
-| 1k_1k_qos0_p1024_1mps   | 0    | 1         | 1024          | 2k      | 1k        | 1.4            | 2.3           | 6%   |
-| 5k_5k_qos0_p32_1mps     | 0    | 1         | 32            | 10k     | 5k        | 2.7            | 5.2           | 18%  |
-| 5k_5k_qos0_p1024_1mps   | 0    | 1         | 1024          | 10k     | 5k        | 3.0            | 6.5           | 18%  |
-| 10k_10k_qos0_p32_1mps   | 0    | 1         | 32            | 20k     | 10k       | 9.6            | 29            | 26%  |
-| 10k_10k_qos0_p1024_1mps | 0    | 1         | 1024          | 20k     | 10k       | 21             | 63            | 26%  |
-
-10k_10k_qos0_p32_1mps场景附图:
-
-![qps](./images/false_10k_10k_qos0_p32_1mps/qps.png)
-![mean](./images/false_10k_10k_qos0_p32_1mps/mean.png)
-![p99](./images/false_10k_10k_qos0_p32_1mps/p99.png)
-![max](./images/false_10k_10k_qos0_p32_1mps/max.png)
-
-10k_10k_qos0_p1024_1mps场景附图:
-
-![qps](./images/false_10k_10k_qos0_p1024_1mps/qps.png)
-![mean](./images/false_10k_10k_qos0_p1024_1mps/mean.png)
-![p99](./images/false_10k_10k_qos0_p1024_1mps/p99.png)
-![max](./images/false_10k_10k_qos0_p1024_1mps/max.png)
-
-
-
-
-#### QoS1场景
-
-| 场景组合                | QoS  | 单连接m/s | Payload(byte) | 连接数C | 总消息m/s | 平均响应时间ms | P99响应时间ms | 常驻内存 | CPU  |
-| ----------------------- | ---- | --------- | ------------- | ------- | --------- | -------------- | ------------- | -------- | ---- |
-| 1k_1k_qos1_p32_1mps     | 1    | 1         | 32            | 2k      | 1k        | 1.4            | 2.3           |          | 8%   |
-| 1k_1k_qos1_p1024_1mps   | 1    | 1         | 1024          | 2k      | 1k        | 1.4            | 2.3           |          | 8%   |
-| 5k_5k_qos1_p32_1mps     | 1    | 1         | 32            | 10k     | 5k        | 3.2            | 7.0           |          | 20%  |
-| 5k_5k_qos1_p1024_1mps   | 1    | 1         | 1024          | 10k     | 5k        | 3.1            | 7.6           |          | 20%  |
-| 10k_10k_qos1_p32_1mps   | 1    | 1         | 32            | 20k     | 10k       | 13             | 30            |          | 30%  |
-| 10k_10k_qos1_p1024_1mps | 1    | 1         | 1024          | 20k     | 10k       | 49             | 117           |          | 30%  |
-
-10k_10k_qos1_p32_1mps场景附图:
-
-![qps](./images/false_10k_10k_qos1_p32_1mps/qps.png)
-![mean](./images/false_10k_10k_qos1_p32_1mps/mean.png)
-![p99](./images/false_10k_10k_qos1_p32_1mps/p99.png)
-![max](./images/false_10k_10k_qos1_p32_1mps/max.png)
-
-
-
-10k_10k_qos1_p1024_1mps场景附图:
-
-![qps](./images/false_10k_10k_qos1_p1024_1mps/qps.png)
-![mean](./images/false_10k_10k_qos1_p1024_1mps/mean.png)
-![p99](./images/false_10k_10k_qos1_p1024_1mps/p99.png)
-![max](./images/false_10k_10k_qos1_p1024_1mps/max.png)
-
-
-
-#### QoS2场景
-
-| 场景组合              | QoS  | 单连接m/s | Payload(byte) | 连接数C | 总消息m/s | 平均响应时间ms | P99响应时间ms | CPU  |
-| --------------------- | ---- | --------- | ------------- | ------- | --------- | -------------- | ------------- | ---- |
-| 1k_1k_qos2_p32_1mps   | 2    | 1         | 32            | 2k      | 1k        | 1.6            | 2.8           | 8%   |
-| 1k_1k_qos2_p1024_1mps | 2    | 1         | 1024          | 2k      | 1k        | 1.7            | 3.0           | 8%   |
-| 5k_5k_qos2_p32_1mps   | 2    | 1         | 32            | 10k     | 5k        | 3.8            | 8.3           | 22%  |
-| 5k_5k_qos2_p1024_1mps | 2    | 1         | 1024          | 10k     | 5k        | 8.2            | 40            | 22%  |
-| 7k_7k_qos2_p32_1mps   | 2    | 1         | 32            | 14k     | 7k        | 9.6            | 28            | 24%  |
-| 7k_7k_qos2_p1024_1mps | 2    | 1         | 1024          | 14k     | 7k        | 15             | 50            | 24%  |
-
-7k_7k_qos2_p32_1mps场景附图:
-
-![qps](./images/false_7k_7k_qos2_p32_1mps/qps.png)
-![mean](./images/false_7k_7k_qos2_p32_1mps/mean.png)
-![p99](./images/false_7k_7k_qos2_p32_1mps/p99.png)
-![max](./images/false_7k_7k_qos2_p32_1mps/max.png)
-
-7k_7k_qos2_p1024_1mps场景附图:
-
-![qps](./images/false_7k_7k_qos2_p1024_1mps/qps.png)
-![mean](./images/false_7k_7k_qos2_p1024_1mps/mean.png)
-![p99](./images/false_7k_7k_qos2_p1024_1mps/p99.png)
-![max](./images/false_7k_7k_qos2_p1024_1mps/max.png)
-
-### cleanSession=false 1对1 高频场景
-
-#### QoS0场景
-
-| 场景组合                 | QoS  | 单连接m/s | Payload(byte) | 连接数C | 总消息m/s | 平均响应时间ms | P99响应时间ms | 常驻内存 | CPU  |
-| ------------------------ | ---- | --------- | ------------- | ------- | --------- | -------------- | ------------- | -------- | ---- |
-| 20_20_qos0_p32_50mps     | 0    | 50        | 32            | 40      | 1k        | 11             | 96            |          | 8%   |
-| 20_20_qos0_p1024_50mps   | 0    | 50        | 1024          | 40      | 1k        | 21             | 117           |          | 8%   |
-| 100_100_qos0_p32_50mps   | 0    | 50        | 32            | 200     | 5k        | 23             | 84            |          | 14%  |
-| 100_100_qos0_p1024_50mps | 0    | 50        | 1024          | 200     | 5k        | 28             | 92            |          | 14%  |
-| 200_200_qos0_p32_50mps   | 0    | 50        | 32            | 400     | 10k       | 47             | 113           |          | 18%  |
-| 200_200_qos0_p1024_50mps | 0    | 50        | 1024          | 400     | 10k       | 58             | 130           |          | 18%  |
-| 300_300_qos0_p32_50mps   | 0    | 50        | 32            | 600     | 15k       | 67             | 142           |          | 22%  |
-| 300_300_qos0_p1024_50mps | 0    | 50        | 1024          | 600     | 15k       | 90             | 184           |          | 22%  |
-
-300_300_qos0_p32_50mps场景附图:
-
-![qps](./images/false_300_300_qos0_p32_50mps/qps.png)
-![mean](./images/false_300_300_qos0_p32_50mps/mean.png)
-![p99](./images/false_300_300_qos0_p32_50mps/p99.png)
-![max](./images/false_300_300_qos0_p32_50mps/max.png)
-
-300_300_qos0_p1024_50mps场景附图:
-
-![qps](./images/false_300_300_qos0_p1024_50mps/qps.png)
-![mean](./images/false_300_300_qos0_p1024_50mps/mean.png)
-![p99](./images/false_300_300_qos0_p1024_50mps/p99.png)
-![max](./images/false_300_300_qos0_p1024_50mps/max.png)
-
-
-
-#### QoS1场景
-
-| 场景组合                 | QoS  | 单连接m/s | Payload(byte) | 连接数C | 总消息m/s | 平均响应时间ms | P99响应时间ms | 常驻内存 | CPU  |
-| ------------------------ | ---- | --------- | ------------- | ------- | --------- | -------------- | ------------- | -------- | ---- |
-| 20_20_qos1_p32_50mps     | 1    | 50        | 32            | 40      | 1k        | 4.6            | 38            |          | 10%  |
-| 20_20_qos1_p1024_50mps   | 1    | 50        | 1024          | 40      | 1k        | 20             | 117           |          | 10%  |
-| 100_100_qos1_p32_50mps   | 1    | 50        | 32            | 200     | 5k        | 26             | 92            |          | 20%  |
-| 100_100_qos1_p1024_50mps | 1    | 50        | 1024          | 200     | 5k        | 32             | 101           |          | 20%  |
-| 200_200_qos1_p32_50mps   | 1    | 50        | 32            | 400     | 10k       | 58             | 151           |          | 23%  |
-| 200_200_qos1_p1024_50mps | 1    | 50        | 1024          | 400     | 10k       | 72             | 210           |          | 23%  |
-| 300_300_qos1_p32_50mps   | 1    | 50        | 32            | 600     | 15k       | 81             | 210           |          | 28%  |
-| 300_300_qos1_p1024_50mps | 1    | 50        | 1024          | 600     | 15k       | 107            | 260           |          | 28%  |
-
-300_300_qos1_p32_50mps场景附图:
-
-![qps](./images/false_300_300_qos1_p32_50mps/qps.png)
-![mean](./images/false_300_300_qos1_p32_50mps/mean.png)
-![p99](./images/false_300_300_qos1_p32_50mps/p99.png)
-![max](./images/false_300_300_qos1_p32_50mps/max.png)
-
-300_300_qos1_p1024_50mps场景附图:
-
-![qps](./images/false_300_300_qos1_p1024_50mps/qps.png)
-![mean](./images/false_300_300_qos1_p1024_50mps/mean.png)
-![p99](./images/false_300_300_qos1_p1024_50mps/p99.png)
-![max](./images/false_300_300_qos1_p1024_50mps/max.png)
-
-#### QoS2 场景
-
-| 场景组合                 | QoS  | 单连接m/s | Payload(byte) | 连接数C | 总消息m/s | 平均响应时间ms | P99响应时间ms | 常驻内存 | CPU  |
-| ------------------------ | ---- | --------- | ------------- | ------- | --------- | -------------- | ------------- | -------- | ---- |
-| 20_20_qos2_p32_50mps     | 0    | 50        | 32            | 40      | 1k        | 16             | 75            |          | 10%  |
-| 20_20_qos2_p1024_50mps   | 0    | 50        | 1024          | 40      | 1k        | 19             | 92            |          | 10%  |
-| 100_100_qos2_p32_50mps   | 0    | 50        | 32            | 200     | 5k        | 37             | 92            |          | 15%  |
-| 100_100_qos2_p1024_50mps | 0    | 50        | 1024          | 200     | 5k        | 44             | 109           |          | 15%  |
-
-100_100_qos2_p32_50mps场景附图:
-
-![qps](./images/false_100_100_qos2_p32_50mps/qps.png)
-![mean](./images/false_100_100_qos2_p32_50mps/mean.png)
-![p99](./images/false_100_100_qos2_p32_50mps/p99.png)
-![max](./images/false_100_100_qos2_p32_50mps/max.png)
-
-100_100_qos2_p1024_50mps场景附图:
-
-![qps](./images/false_100_100_qos2_p1024_50mps/qps.png)
-![mean](./images/false_100_100_qos2_p1024_50mps/mean.png)
-![p99](./images/false_100_100_qos2_p1024_50mps/p99.png)
-![max](./images/false_100_100_qos2_p1024_50mps/max.png)
-
-
-
-## 系统参数优化
-
-以下Kernel参数会影响BifroMQ所在机器能接受的最大连接数
-
-### 内存
-
-* vm.max_map_count: 限制一个进程可以拥有的VMA(虚拟内存区域)的数量, 可放大到221184
-
-### 最大打开文件数
-
-* nofile: 指单进程的最大打开文件数
-* nr_open: 指单个进程可分配的最大文件数,通常默认值为1024*1024=1048576
-* file-max: 系统内核一共可以打开的最大值,默认值是185745
-
-### NetFilter调优
-
-通过`sysctl -a | grep conntrack`查看当前的参数,以下几个参数决定了最大连接数:
-
-* net.netfilter.nf_conntrack_buckets: 记录连接条目的hashtable的bucket大小
-    * 修改命令:`echo 262144 > /sys/module/nf_conntrack/parameters/hashsize`
-* net.netfilter.nf_conntrack_max: hashtable最大的条目数,一般为nf_conntrack_buckets * 4
-* net.nf_conntrack_max: 同net.netfilter.nf_conntrack_max
-* net.netfilter.nf_conntrack_tcp_timeout_fin_wait: 默认 120s -> 30s
-* net.netfilter.nf_conntrack_tcp_timeout_time_wait: 默认 120s -> 30s
-* net.netfilter.nf_conntrack_tcp_timeout_close_wait: 默认 60s -> 15s
-* net.netfilter.nf_conntrack_tcp_timeout_established: 默认 432000 秒(5天)-> 300s
-
-
-以下sysctl参数会影响大压力下tcp channel性能表现
-
-### Server端及测试发压端TCP相关调优
-
-推荐使用centos7环境进行部署及压力测试。
-
-centos6环境需要进行系统参数调优: 
-* net.core.wmem_max: 最大的TCP数据发送窗口大小(字节)
-  * 修改命令:`echo 'net.core.wmem_max=16777216' >> /etc/sysctl.conf`
-* net.core.wmem_default: 默认的TCP数据发送窗口大小(字节)
-  * 修改命令:`echo 'net.core.wmem_default=262144' >> /etc/sysctl.conf`
-* net.core.rmem_max: 最大的TCP数据接收窗口大小(字节)
-  * 修改命令:`echo 'net.core.rmem_max=16777216' >> /etc/sysctl.conf`
-* net.core.rmem_default: 默认的TCP数据接收窗口大小(字节)
-  * 修改命令:`echo 'net.core.rmem_default=262144' >> /etc/sysctl.conf`
-* net.ipv4.tcp_rmem: socket接收缓冲区内存使用的下限  警戒值  上限
-  * 修改命令:`echo 'net.ipv4.tcp_rmem= 1024 4096 16777216' >> /etc/sysctl.conf`
-* net.ipv4.tcp_rmem: socket发送缓冲区内存使用的下限  警戒值  上限
-  * 修改命令:`echo 'net.ipv4.tcp_wmem= 1024 4096 16777216' >> /etc/sysctl.conf`
-* net.core.optmem_max: 每个socket所允许的最大缓冲区的大小 (字节)
-  * 修改命令:`echo 'net.core.optmem_max = 16777216' >> /etc/sysctl.conf`
-* net.core.netdev_max_backlog: 网卡设备将请求放入队列的长度
-  * 修改命令:`echo 'net.core.netdev_max_backlog = 16384' >> /etc/sysctl.conf`
-
-修改完配置通过`sysctl -p`并重启服务器生效。
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/_category_.json b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/_category_.json
deleted file mode 100644
index 9291b3e1..00000000
--- a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/_category_.json
+++ /dev/null
@@ -1,8 +0,0 @@
-{
-  "label": "Test Report",
-  "position": 99,
-  "link": {
-    "type": "generated-index",
-    "description": "Test Report of BifroMQ."
-  }
-}
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_100_100_qos2_p1024_50mps/cpu.png b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_100_100_qos2_p1024_50mps/cpu.png
deleted file mode 100644
index c56495a0..00000000
Binary files a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_100_100_qos2_p1024_50mps/cpu.png and /dev/null differ
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_100_100_qos2_p1024_50mps/max.png b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_100_100_qos2_p1024_50mps/max.png
deleted file mode 100644
index d93c2181..00000000
Binary files a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_100_100_qos2_p1024_50mps/max.png and /dev/null differ
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_100_100_qos2_p1024_50mps/mean.png b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_100_100_qos2_p1024_50mps/mean.png
deleted file mode 100644
index 912f2e50..00000000
Binary files a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_100_100_qos2_p1024_50mps/mean.png and /dev/null differ
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_100_100_qos2_p1024_50mps/p99.png b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_100_100_qos2_p1024_50mps/p99.png
deleted file mode 100644
index 6779040f..00000000
Binary files a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_100_100_qos2_p1024_50mps/p99.png and /dev/null differ
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_100_100_qos2_p1024_50mps/qps.png b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_100_100_qos2_p1024_50mps/qps.png
deleted file mode 100644
index 1a289d6a..00000000
Binary files a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_100_100_qos2_p1024_50mps/qps.png and /dev/null differ
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_100_100_qos2_p32_50mps/cpu.png b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_100_100_qos2_p32_50mps/cpu.png
deleted file mode 100644
index c935b43d..00000000
Binary files a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_100_100_qos2_p32_50mps/cpu.png and /dev/null differ
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_100_100_qos2_p32_50mps/max.png b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_100_100_qos2_p32_50mps/max.png
deleted file mode 100644
index 69dd6327..00000000
Binary files a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_100_100_qos2_p32_50mps/max.png and /dev/null differ
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_100_100_qos2_p32_50mps/mean.png b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_100_100_qos2_p32_50mps/mean.png
deleted file mode 100644
index 320156c9..00000000
Binary files a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_100_100_qos2_p32_50mps/mean.png and /dev/null differ
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_100_100_qos2_p32_50mps/p99.png b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_100_100_qos2_p32_50mps/p99.png
deleted file mode 100644
index ebf3a760..00000000
Binary files a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_100_100_qos2_p32_50mps/p99.png and /dev/null differ
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_100_100_qos2_p32_50mps/qps.png b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_100_100_qos2_p32_50mps/qps.png
deleted file mode 100644
index 835f1c24..00000000
Binary files a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_100_100_qos2_p32_50mps/qps.png and /dev/null differ
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_10k_10k_qos0_p1024_1mps/cpu.png b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_10k_10k_qos0_p1024_1mps/cpu.png
deleted file mode 100644
index ad62e243..00000000
Binary files a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_10k_10k_qos0_p1024_1mps/cpu.png and /dev/null differ
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_10k_10k_qos0_p1024_1mps/max.png b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_10k_10k_qos0_p1024_1mps/max.png
deleted file mode 100644
index 1992a5cd..00000000
Binary files a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_10k_10k_qos0_p1024_1mps/max.png and /dev/null differ
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_10k_10k_qos0_p1024_1mps/mean.png b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_10k_10k_qos0_p1024_1mps/mean.png
deleted file mode 100644
index 3be0ef74..00000000
Binary files a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_10k_10k_qos0_p1024_1mps/mean.png and /dev/null differ
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_10k_10k_qos0_p1024_1mps/p99.png b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_10k_10k_qos0_p1024_1mps/p99.png
deleted file mode 100644
index f5d2c242..00000000
Binary files a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_10k_10k_qos0_p1024_1mps/p99.png and /dev/null differ
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_10k_10k_qos0_p1024_1mps/qps.png b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_10k_10k_qos0_p1024_1mps/qps.png
deleted file mode 100644
index e46ca559..00000000
Binary files a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_10k_10k_qos0_p1024_1mps/qps.png and /dev/null differ
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_10k_10k_qos0_p32_1mps/cpu.png b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_10k_10k_qos0_p32_1mps/cpu.png
deleted file mode 100644
index db097c0f..00000000
Binary files a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_10k_10k_qos0_p32_1mps/cpu.png and /dev/null differ
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_10k_10k_qos0_p32_1mps/max.png b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_10k_10k_qos0_p32_1mps/max.png
deleted file mode 100644
index 184fae33..00000000
Binary files a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_10k_10k_qos0_p32_1mps/max.png and /dev/null differ
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_10k_10k_qos0_p32_1mps/mean.png b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_10k_10k_qos0_p32_1mps/mean.png
deleted file mode 100644
index 471f39ba..00000000
Binary files a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_10k_10k_qos0_p32_1mps/mean.png and /dev/null differ
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_10k_10k_qos0_p32_1mps/p99.png b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_10k_10k_qos0_p32_1mps/p99.png
deleted file mode 100644
index 5563a231..00000000
Binary files a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_10k_10k_qos0_p32_1mps/p99.png and /dev/null differ
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_10k_10k_qos0_p32_1mps/qps.png b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_10k_10k_qos0_p32_1mps/qps.png
deleted file mode 100644
index 474e7150..00000000
Binary files a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_10k_10k_qos0_p32_1mps/qps.png and /dev/null differ
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_10k_10k_qos1_p1024_1mps/cpu.png b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_10k_10k_qos1_p1024_1mps/cpu.png
deleted file mode 100644
index 19ddbf05..00000000
Binary files a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_10k_10k_qos1_p1024_1mps/cpu.png and /dev/null differ
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_10k_10k_qos1_p1024_1mps/max.png b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_10k_10k_qos1_p1024_1mps/max.png
deleted file mode 100644
index 7e36452f..00000000
Binary files a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_10k_10k_qos1_p1024_1mps/max.png and /dev/null differ
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_10k_10k_qos1_p1024_1mps/mean.png b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_10k_10k_qos1_p1024_1mps/mean.png
deleted file mode 100644
index b817a86c..00000000
Binary files a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_10k_10k_qos1_p1024_1mps/mean.png and /dev/null differ
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_10k_10k_qos1_p1024_1mps/p99.png b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_10k_10k_qos1_p1024_1mps/p99.png
deleted file mode 100644
index cc4e80e8..00000000
Binary files a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_10k_10k_qos1_p1024_1mps/p99.png and /dev/null differ
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_10k_10k_qos1_p1024_1mps/qps.png b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_10k_10k_qos1_p1024_1mps/qps.png
deleted file mode 100644
index eac7b427..00000000
Binary files a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_10k_10k_qos1_p1024_1mps/qps.png and /dev/null differ
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_10k_10k_qos1_p32_1mps/cpu.png b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_10k_10k_qos1_p32_1mps/cpu.png
deleted file mode 100644
index 954974c7..00000000
Binary files a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_10k_10k_qos1_p32_1mps/cpu.png and /dev/null differ
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_10k_10k_qos1_p32_1mps/max.png b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_10k_10k_qos1_p32_1mps/max.png
deleted file mode 100644
index 12bab660..00000000
Binary files a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_10k_10k_qos1_p32_1mps/max.png and /dev/null differ
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_10k_10k_qos1_p32_1mps/mean.png b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_10k_10k_qos1_p32_1mps/mean.png
deleted file mode 100644
index b5490317..00000000
Binary files a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_10k_10k_qos1_p32_1mps/mean.png and /dev/null differ
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_10k_10k_qos1_p32_1mps/p99.png b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_10k_10k_qos1_p32_1mps/p99.png
deleted file mode 100644
index ad241870..00000000
Binary files a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_10k_10k_qos1_p32_1mps/p99.png and /dev/null differ
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_10k_10k_qos1_p32_1mps/qps.png b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_10k_10k_qos1_p32_1mps/qps.png
deleted file mode 100644
index 2ca8baa8..00000000
Binary files a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_10k_10k_qos1_p32_1mps/qps.png and /dev/null differ
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_300_300_qos0_p1024_50mps/cpu.png b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_300_300_qos0_p1024_50mps/cpu.png
deleted file mode 100644
index 2560437d..00000000
Binary files a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_300_300_qos0_p1024_50mps/cpu.png and /dev/null differ
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_300_300_qos0_p1024_50mps/max.png b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_300_300_qos0_p1024_50mps/max.png
deleted file mode 100644
index ddf82894..00000000
Binary files a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_300_300_qos0_p1024_50mps/max.png and /dev/null differ
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_300_300_qos0_p1024_50mps/mean.png b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_300_300_qos0_p1024_50mps/mean.png
deleted file mode 100644
index 94ffc7be..00000000
Binary files a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_300_300_qos0_p1024_50mps/mean.png and /dev/null differ
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_300_300_qos0_p1024_50mps/p99.png b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_300_300_qos0_p1024_50mps/p99.png
deleted file mode 100644
index 1008df8d..00000000
Binary files a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_300_300_qos0_p1024_50mps/p99.png and /dev/null differ
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_300_300_qos0_p1024_50mps/qps.png b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_300_300_qos0_p1024_50mps/qps.png
deleted file mode 100644
index f079e2df..00000000
Binary files a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_300_300_qos0_p1024_50mps/qps.png and /dev/null differ
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_300_300_qos0_p32_50mps/cpu.png b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_300_300_qos0_p32_50mps/cpu.png
deleted file mode 100644
index c1e79a8c..00000000
Binary files a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_300_300_qos0_p32_50mps/cpu.png and /dev/null differ
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_300_300_qos0_p32_50mps/max.png b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_300_300_qos0_p32_50mps/max.png
deleted file mode 100644
index 2a4df8b5..00000000
Binary files a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_300_300_qos0_p32_50mps/max.png and /dev/null differ
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_300_300_qos0_p32_50mps/mean.png b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_300_300_qos0_p32_50mps/mean.png
deleted file mode 100644
index dc82df7d..00000000
Binary files a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_300_300_qos0_p32_50mps/mean.png and /dev/null differ
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_300_300_qos0_p32_50mps/p99.png b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_300_300_qos0_p32_50mps/p99.png
deleted file mode 100644
index cf162811..00000000
Binary files a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_300_300_qos0_p32_50mps/p99.png and /dev/null differ
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_300_300_qos0_p32_50mps/qps.png b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_300_300_qos0_p32_50mps/qps.png
deleted file mode 100644
index 1213fa76..00000000
Binary files a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_300_300_qos0_p32_50mps/qps.png and /dev/null differ
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_300_300_qos1_p1024_50mps/cpu.png b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_300_300_qos1_p1024_50mps/cpu.png
deleted file mode 100644
index 8d1a3dca..00000000
Binary files a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_300_300_qos1_p1024_50mps/cpu.png and /dev/null differ
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_300_300_qos1_p1024_50mps/max.png b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_300_300_qos1_p1024_50mps/max.png
deleted file mode 100644
index 8f97c306..00000000
Binary files a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_300_300_qos1_p1024_50mps/max.png and /dev/null differ
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_300_300_qos1_p1024_50mps/mean.png b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_300_300_qos1_p1024_50mps/mean.png
deleted file mode 100644
index 64a62b8d..00000000
Binary files a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_300_300_qos1_p1024_50mps/mean.png and /dev/null differ
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_300_300_qos1_p1024_50mps/p99.png b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_300_300_qos1_p1024_50mps/p99.png
deleted file mode 100644
index 1f55b1e9..00000000
Binary files a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_300_300_qos1_p1024_50mps/p99.png and /dev/null differ
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_300_300_qos1_p1024_50mps/qps.png b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_300_300_qos1_p1024_50mps/qps.png
deleted file mode 100644
index c7e294f7..00000000
Binary files a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_300_300_qos1_p1024_50mps/qps.png and /dev/null differ
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_300_300_qos1_p32_50mps/cpu.png b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_300_300_qos1_p32_50mps/cpu.png
deleted file mode 100644
index 10e10762..00000000
Binary files a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_300_300_qos1_p32_50mps/cpu.png and /dev/null differ
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_300_300_qos1_p32_50mps/max.png b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_300_300_qos1_p32_50mps/max.png
deleted file mode 100644
index 2031bf0c..00000000
Binary files a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_300_300_qos1_p32_50mps/max.png and /dev/null differ
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_300_300_qos1_p32_50mps/mean.png b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_300_300_qos1_p32_50mps/mean.png
deleted file mode 100644
index e5c25315..00000000
Binary files a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_300_300_qos1_p32_50mps/mean.png and /dev/null differ
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_300_300_qos1_p32_50mps/p99.png b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_300_300_qos1_p32_50mps/p99.png
deleted file mode 100644
index 848fd5ea..00000000
Binary files a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_300_300_qos1_p32_50mps/p99.png and /dev/null differ
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_300_300_qos1_p32_50mps/qps.png b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_300_300_qos1_p32_50mps/qps.png
deleted file mode 100644
index ff688bce..00000000
Binary files a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_300_300_qos1_p32_50mps/qps.png and /dev/null differ
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_7k_7k_qos2_p1024_1mps/cpu.png b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_7k_7k_qos2_p1024_1mps/cpu.png
deleted file mode 100644
index 16911baf..00000000
Binary files a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_7k_7k_qos2_p1024_1mps/cpu.png and /dev/null differ
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_7k_7k_qos2_p1024_1mps/max.png b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_7k_7k_qos2_p1024_1mps/max.png
deleted file mode 100644
index bc18a003..00000000
Binary files a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_7k_7k_qos2_p1024_1mps/max.png and /dev/null differ
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_7k_7k_qos2_p1024_1mps/mean.png b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_7k_7k_qos2_p1024_1mps/mean.png
deleted file mode 100644
index cad9686b..00000000
Binary files a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_7k_7k_qos2_p1024_1mps/mean.png and /dev/null differ
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_7k_7k_qos2_p1024_1mps/p99.png b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_7k_7k_qos2_p1024_1mps/p99.png
deleted file mode 100644
index 81d73a67..00000000
Binary files a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_7k_7k_qos2_p1024_1mps/p99.png and /dev/null differ
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_7k_7k_qos2_p1024_1mps/qps.png b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_7k_7k_qos2_p1024_1mps/qps.png
deleted file mode 100644
index 10d8ce3c..00000000
Binary files a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_7k_7k_qos2_p1024_1mps/qps.png and /dev/null differ
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_7k_7k_qos2_p32_1mps/cpu.png b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_7k_7k_qos2_p32_1mps/cpu.png
deleted file mode 100644
index 806c53d7..00000000
Binary files a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_7k_7k_qos2_p32_1mps/cpu.png and /dev/null differ
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_7k_7k_qos2_p32_1mps/max.png b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_7k_7k_qos2_p32_1mps/max.png
deleted file mode 100644
index c3b20d69..00000000
Binary files a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_7k_7k_qos2_p32_1mps/max.png and /dev/null differ
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_7k_7k_qos2_p32_1mps/mean.png b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_7k_7k_qos2_p32_1mps/mean.png
deleted file mode 100644
index 16a3e92b..00000000
Binary files a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_7k_7k_qos2_p32_1mps/mean.png and /dev/null differ
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_7k_7k_qos2_p32_1mps/p99.png b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_7k_7k_qos2_p32_1mps/p99.png
deleted file mode 100644
index 5369c54e..00000000
Binary files a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_7k_7k_qos2_p32_1mps/p99.png and /dev/null differ
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_7k_7k_qos2_p32_1mps/qps.png b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_7k_7k_qos2_p32_1mps/qps.png
deleted file mode 100644
index 075e5b38..00000000
Binary files a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/false_7k_7k_qos2_p32_1mps/qps.png and /dev/null differ
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/share_false_40k_400_qos2_p1024_1mps/max.png b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/share_false_40k_400_qos2_p1024_1mps/max.png
deleted file mode 100644
index 093e212d..00000000
Binary files a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/share_false_40k_400_qos2_p1024_1mps/max.png and /dev/null differ
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/share_false_40k_400_qos2_p1024_1mps/mean.png b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/share_false_40k_400_qos2_p1024_1mps/mean.png
deleted file mode 100644
index 4cf3a801..00000000
Binary files a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/share_false_40k_400_qos2_p1024_1mps/mean.png and /dev/null differ
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/share_false_40k_400_qos2_p1024_1mps/p99.png b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/share_false_40k_400_qos2_p1024_1mps/p99.png
deleted file mode 100644
index 5478afb8..00000000
Binary files a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/share_false_40k_400_qos2_p1024_1mps/p99.png and /dev/null differ
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/share_false_40k_400_qos2_p1024_1mps/qps.png b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/share_false_40k_400_qos2_p1024_1mps/qps.png
deleted file mode 100644
index d6beb8e6..00000000
Binary files a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/share_false_40k_400_qos2_p1024_1mps/qps.png and /dev/null differ
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/share_true_40k_400_qos2_p1024_1mps/max.png b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/share_true_40k_400_qos2_p1024_1mps/max.png
deleted file mode 100644
index 3bc86414..00000000
Binary files a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/share_true_40k_400_qos2_p1024_1mps/max.png and /dev/null differ
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/share_true_40k_400_qos2_p1024_1mps/mean.png b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/share_true_40k_400_qos2_p1024_1mps/mean.png
deleted file mode 100644
index a901d10e..00000000
Binary files a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/share_true_40k_400_qos2_p1024_1mps/mean.png and /dev/null differ
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/share_true_40k_400_qos2_p1024_1mps/p99.png b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/share_true_40k_400_qos2_p1024_1mps/p99.png
deleted file mode 100644
index d7267523..00000000
Binary files a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/share_true_40k_400_qos2_p1024_1mps/p99.png and /dev/null differ
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/share_true_40k_400_qos2_p1024_1mps/qps.png b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/share_true_40k_400_qos2_p1024_1mps/qps.png
deleted file mode 100644
index e43d4c19..00000000
Binary files a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/share_true_40k_400_qos2_p1024_1mps/qps.png and /dev/null differ
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/true_1.2k_1.2k_qos2_p32_50mps/max.png b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/true_1.2k_1.2k_qos2_p32_50mps/max.png
deleted file mode 100644
index c58b1266..00000000
Binary files a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/true_1.2k_1.2k_qos2_p32_50mps/max.png and /dev/null differ
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/true_1.2k_1.2k_qos2_p32_50mps/mean.png b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/true_1.2k_1.2k_qos2_p32_50mps/mean.png
deleted file mode 100644
index 5eb4c306..00000000
Binary files a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/true_1.2k_1.2k_qos2_p32_50mps/mean.png and /dev/null differ
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/true_1.2k_1.2k_qos2_p32_50mps/p99.png b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/true_1.2k_1.2k_qos2_p32_50mps/p99.png
deleted file mode 100644
index f2075f03..00000000
Binary files a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/true_1.2k_1.2k_qos2_p32_50mps/p99.png and /dev/null differ
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/true_1.2k_1.2k_qos2_p32_50mps/qps.png b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/true_1.2k_1.2k_qos2_p32_50mps/qps.png
deleted file mode 100644
index e84021a7..00000000
Binary files a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/true_1.2k_1.2k_qos2_p32_50mps/qps.png and /dev/null differ
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/true_100k_100k_qos0_p1024_1mps/max.png b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/true_100k_100k_qos0_p1024_1mps/max.png
deleted file mode 100644
index 17c05f34..00000000
Binary files a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/true_100k_100k_qos0_p1024_1mps/max.png and /dev/null differ
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/true_100k_100k_qos0_p1024_1mps/mean.png b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/true_100k_100k_qos0_p1024_1mps/mean.png
deleted file mode 100644
index 25737687..00000000
Binary files a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/true_100k_100k_qos0_p1024_1mps/mean.png and /dev/null differ
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/true_100k_100k_qos0_p1024_1mps/p99.png b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/true_100k_100k_qos0_p1024_1mps/p99.png
deleted file mode 100644
index e3e20aac..00000000
Binary files a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/true_100k_100k_qos0_p1024_1mps/p99.png and /dev/null differ
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/true_100k_100k_qos0_p1024_1mps/qps.png b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/true_100k_100k_qos0_p1024_1mps/qps.png
deleted file mode 100644
index 283f2999..00000000
Binary files a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/true_100k_100k_qos0_p1024_1mps/qps.png and /dev/null differ
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/true_100k_100k_qos1_p1024_1mps/max.png b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/true_100k_100k_qos1_p1024_1mps/max.png
deleted file mode 100644
index 4f2b2274..00000000
Binary files a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/true_100k_100k_qos1_p1024_1mps/max.png and /dev/null differ
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/true_100k_100k_qos1_p1024_1mps/mean.png b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/true_100k_100k_qos1_p1024_1mps/mean.png
deleted file mode 100644
index 96139a00..00000000
Binary files a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/true_100k_100k_qos1_p1024_1mps/mean.png and /dev/null differ
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/true_100k_100k_qos1_p1024_1mps/p99.png b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/true_100k_100k_qos1_p1024_1mps/p99.png
deleted file mode 100644
index 86f56bd0..00000000
Binary files a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/true_100k_100k_qos1_p1024_1mps/p99.png and /dev/null differ
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/true_100k_100k_qos1_p1024_1mps/qps.png b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/true_100k_100k_qos1_p1024_1mps/qps.png
deleted file mode 100644
index 4ce5e17e..00000000
Binary files a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/true_100k_100k_qos1_p1024_1mps/qps.png and /dev/null differ
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/true_1_1k_qos1_p32_1mps/max.png b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/true_1_1k_qos1_p32_1mps/max.png
deleted file mode 100644
index a4508a75..00000000
Binary files a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/true_1_1k_qos1_p32_1mps/max.png and /dev/null differ
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/true_1_1k_qos1_p32_1mps/mean.png b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/true_1_1k_qos1_p32_1mps/mean.png
deleted file mode 100644
index c69e43e4..00000000
Binary files a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/true_1_1k_qos1_p32_1mps/mean.png and /dev/null differ
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/true_1_1k_qos1_p32_1mps/p99.png b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/true_1_1k_qos1_p32_1mps/p99.png
deleted file mode 100644
index 5ad8a978..00000000
Binary files a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/true_1_1k_qos1_p32_1mps/p99.png and /dev/null differ
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/true_1_1k_qos1_p32_1mps/qps.png b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/true_1_1k_qos1_p32_1mps/qps.png
deleted file mode 100644
index 8cc4f9cf..00000000
Binary files a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/true_1_1k_qos1_p32_1mps/qps.png and /dev/null differ
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/true_2k_2k_qos1_p32_50mps/max.png b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/true_2k_2k_qos1_p32_50mps/max.png
deleted file mode 100644
index 9b77e212..00000000
Binary files a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/true_2k_2k_qos1_p32_50mps/max.png and /dev/null differ
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/true_2k_2k_qos1_p32_50mps/mean.png b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/true_2k_2k_qos1_p32_50mps/mean.png
deleted file mode 100644
index 103c3412..00000000
Binary files a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/true_2k_2k_qos1_p32_50mps/mean.png and /dev/null differ
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/true_2k_2k_qos1_p32_50mps/p99.png b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/true_2k_2k_qos1_p32_50mps/p99.png
deleted file mode 100644
index 38882d21..00000000
Binary files a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/true_2k_2k_qos1_p32_50mps/p99.png and /dev/null differ
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/true_2k_2k_qos1_p32_50mps/qps.png b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/true_2k_2k_qos1_p32_50mps/qps.png
deleted file mode 100644
index 18dabccb..00000000
Binary files a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/true_2k_2k_qos1_p32_50mps/qps.png and /dev/null differ
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/true_4k_4k_qos0_p32_50mps/max.png b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/true_4k_4k_qos0_p32_50mps/max.png
deleted file mode 100644
index 2aa9c032..00000000
Binary files a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/true_4k_4k_qos0_p32_50mps/max.png and /dev/null differ
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/true_4k_4k_qos0_p32_50mps/mean.png b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/true_4k_4k_qos0_p32_50mps/mean.png
deleted file mode 100644
index b9044dad..00000000
Binary files a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/true_4k_4k_qos0_p32_50mps/mean.png and /dev/null differ
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/true_4k_4k_qos0_p32_50mps/p99.png b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/true_4k_4k_qos0_p32_50mps/p99.png
deleted file mode 100644
index 66c85d52..00000000
Binary files a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/true_4k_4k_qos0_p32_50mps/p99.png and /dev/null differ
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/true_4k_4k_qos0_p32_50mps/qps.png b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/true_4k_4k_qos0_p32_50mps/qps.png
deleted file mode 100644
index a2a25ff5..00000000
Binary files a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/true_4k_4k_qos0_p32_50mps/qps.png and /dev/null differ
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/true_50k_50k_qos2_p1024_1mps/max.png b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/true_50k_50k_qos2_p1024_1mps/max.png
deleted file mode 100644
index 6daa5df4..00000000
Binary files a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/true_50k_50k_qos2_p1024_1mps/max.png and /dev/null differ
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/true_50k_50k_qos2_p1024_1mps/mean.png b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/true_50k_50k_qos2_p1024_1mps/mean.png
deleted file mode 100644
index 1ce6c93d..00000000
Binary files a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/true_50k_50k_qos2_p1024_1mps/mean.png and /dev/null differ
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/true_50k_50k_qos2_p1024_1mps/p99.png b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/true_50k_50k_qos2_p1024_1mps/p99.png
deleted file mode 100644
index 33da3286..00000000
Binary files a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/true_50k_50k_qos2_p1024_1mps/p99.png and /dev/null differ
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/true_50k_50k_qos2_p1024_1mps/qps.png b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/true_50k_50k_qos2_p1024_1mps/qps.png
deleted file mode 100644
index 8adda29a..00000000
Binary files a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-1.0.x/99_test_report/images/true_50k_50k_qos2_p1024_1mps/qps.png and /dev/null differ
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-2.0.0/00_Readme.md b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-2.0.0/00_Readme.md
deleted file mode 100644
index 1ee14898..00000000
--- a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-2.0.0/00_Readme.md
+++ /dev/null
@@ -1,29 +0,0 @@
----
-sidebar_position: 0
----
-
-# BifroMQ
-
-BifroMQ 是一个基于 Java 实现的高性能、分布式 MQTT Broker 消息中间件,无缝集成了原生的多租户支持。它旨在支持构建大规模的物联网设备连接和消息系统。
-
-BifroMQ 源自百度物联网团队多年技术积累,目前,它作为百度智能云[物联网核心套件 IoT Core](https://cloud.baidu.com/product/iot.html)的基础技术,这是一个公有云的 Serverless 服务。
-
-## 名称的由来
-
-BifroMQ 的名称灵感来自于北欧神话中的`Bifröst`,一座彩虹之桥,联接着人类的世界 Midgard 和神祇居住的世界 Asgard。Bifröst 作为两个世界间的坚实而灵活的通道,BifroMQ 同样旨在成为连接各种系统或应用的枢纽,通过消息传递实现它们之间的交流。这与 MQTT 中间件在分布式系统中扮演的角色,即处理和转发消息,极为相似。
-
-此外,Bifröst 的坚固性寓意着 BifroMQ 在稳定性和可靠性方面的卓越表现,而它的灵活性则象征着 BifroMQ 在可扩展性和适应性上的优势。总的来说,`BifroMQ` 是一个坚固、灵活的 MQTT 中间件,作为连接不同系统或应用的桥梁。
-
-## 讨论组
-
-### 微信群
-
-如果你对我们的项目感兴趣,你可以加入我们的微信群。
-
-[通过电子邮件](mailto:hello@bifromq.io) 向我们发送您的微信 ID,以及为什么您对 BifroMQ 感兴趣的更多信息(我们很乐意听到),我们将尽快邀请您加入我们的群组。
-
-### Discord
-
-或加入我们的 Discord 群组(英文)
-
-<a href="https://discord.gg/Pfs3QRadRB"><img src="https://img.shields.io/discord/1115542029531885599?logo=discord&logoColor=white" alt="BifroMQ Discord server" /></a>
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-2.0.0/01_intro/_category_.json b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-2.0.0/01_intro/_category_.json
deleted file mode 100644
index 010ca759..00000000
--- a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-2.0.0/01_intro/_category_.json
+++ /dev/null
@@ -1,8 +0,0 @@
-{
-  "label": "Introduction",
-  "position": 1,
-  "link": {
-    "type": "generated-index",
-    "description": "BifroMQ overview introduction, features list, system limitations, release log, etc."
-  }
-}
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-2.0.0/01_intro/features_list.md b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-2.0.0/01_intro/features_list.md
deleted file mode 100644
index 05a358a9..00000000
--- a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-2.0.0/01_intro/features_list.md
+++ /dev/null
@@ -1,15 +0,0 @@
----
-sidebar_position: 1
----
-
-# 功能列表
-
-* 完全支持 MQTT 3.1/3.1.1 的特性,包括 TCP/TLS/WS/WSS,即将支持 MQTT 5.0
-* 原生支持多租户资源共享和工作负载隔离
-* 内置存储引擎,针对关键负载定向优化,无第三方中间件依赖。
-* 扩展机制支持:
-    * 认证/授权 (Authentication/Authorization)
-    * 运行时设置 (Runtime Setting)
-    * 桥接 (Bridging)
-    * 事件 (Event)
-    * 系统/租户级别的监控 (System/Tenant-level Monitoring)
\ No newline at end of file
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-2.0.0/02_get_started/1_quick_install.md b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-2.0.0/02_get_started/1_quick_install.md
deleted file mode 100644
index b69edff4..00000000
--- a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-2.0.0/02_get_started/1_quick_install.md
+++ /dev/null
@@ -1,15 +0,0 @@
----
-sidebar_position: 1
-title: 安装BifroMQ
----
-
-# 安装BifroMQ
-
-## Docker
-```
-docker run -d --name bifromq -p 1883:1883 bifromq/bifromq:latest
-```
-
-## bash
-
-关于更多的安装选项,详情请见:[安装和部署](../../category/install--deploy/)章节。
\ No newline at end of file
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-2.0.0/02_get_started/2_connect_to.md b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-2.0.0/02_get_started/2_connect_to.md
deleted file mode 100644
index 65c8f21a..00000000
--- a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-2.0.0/02_get_started/2_connect_to.md
+++ /dev/null
@@ -1,35 +0,0 @@
----
-sidebar_position: 2
----
-
-# 连接到BifroMQ
-
-## 使用 MQTT Client 简单连接验证
-使用已有的第三方 MQTT 客户端工具,可以快速验证是否可以实现与 BifroMQ 提供的 MQTT 服务交流发送或者接收消息。
-
-免费的第三方 MQTT 客户端工具较多,常见的有 MQTT.fx、MQTTBox、MQTTLens、MQTTX等。这里以 MQTTX 为例。
-
-1. 访问 https://mqttx.app/ 下载 MQTTX 并安装。
-2. 打开 MQTTX,点击“New Connection”或者左侧边栏上的“+”,创建一个新的连接配置。
-
-![image.png](https://bce.bdstatic.com/doc/IOTSTACK/iotcore/image_4636166.png)
-
-3. 填入各项必填配置:
-
-    * Name:本配置的名字,可随意填写。
-    * ClientID:客户端ID,自行设置或使用右边的按钮随机生成。支持“a-z”,“0-9”,“_”,“-”字符且不能大于128bytes,UTF8编码,不可重名。
-    * Host:连接地址。前面的协议头可以自行选择,mqtt://、mqtts://、wss:// 分别对应 MQTT 连接中的 TCP、TLS/SSL、WSS 三种方式。后面域名请填写可以实际访问到 BifroMQ MQTT 服务的地址。
-    * Port:连接端口。根据选择的协议头确定对应的端口。端口默认:	TCP:1883、TLS/SSL:1884、WSS:443。
-    * Username & Password:您拥有的用户名和密码。
-    * MQTT Version:选择3.1.1
-
-4. 正确填写连接配置后,点击右上角 Connect 连接服务器。一切正常会提示Connect Successful,并转入消息收发界面。
-5. 订阅主题:点击左上的“New Subscription”按钮,并在弹出的对话框中填入主题Topic。请注意,必须填写您有订阅权限的主题,这里我们使用一个测试主题,对应此设备为$iot/device1/user/fortest,选择默认的QoS 0,点击右下的“Confirm”进行订阅操作。
-
-![image.png](https://bce.bdstatic.com/doc/IOTSTACK/iotcore/image_62a12ac.png)
-
-6. 发布消息:在消息收发界面右下填入主题Topic,这里我们依然填写刚才的测试主题,自己给自己发送一条消息。选择默认的QoS 0,填写消息内容后点击发送按钮完成发送。
-
-![image.png](https://bce.bdstatic.com/doc/IOTSTACK/iotcore/image_e3d5f14.png)
-
-7. 发送成功后,可以在右方看到已发送的消息。MQTT服务工作正常的话,已经订阅了该主题的我们可以收到该消息,也会展示在对话界面左边。
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-2.0.0/02_get_started/_category_.json b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-2.0.0/02_get_started/_category_.json
deleted file mode 100644
index 9397afae..00000000
--- a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-2.0.0/02_get_started/_category_.json
+++ /dev/null
@@ -1,8 +0,0 @@
-{
-  "label": "Get Started",
-  "position": 2,
-  "link": {
-    "type": "generated-index",
-    "description": "BifroMQ overview introduction, features list, system limitations, release log, etc."
-  }
-}
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-2.0.0/03_deploy/11_build_from_source.md b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-2.0.0/03_deploy/11_build_from_source.md
deleted file mode 100644
index 927e9409..00000000
--- a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-2.0.0/03_deploy/11_build_from_source.md
+++ /dev/null
@@ -1,33 +0,0 @@
----
-sidebar_position: 11
----
-
-# 从源码编译部署
-
-## 前提条件
-
-* JDK 17+
-* Maven 3.5.0+
-  
-## 编译构建
-
-克隆版本库到本地
-
-```
-cd <YOUR_WORKSPACE>
-git clone https://github.com/bifromqio/bifromq bifromq
-```
-
-执行以下命令,进入项目根目录,构建整个项目
-
-```
-cd bifromq
-mvn wrapper:wrapper
-./mvnw -U clean package
-```
-
-构建输出是两个 tar.gz 和一个 zip 文件,位于 `/build/build-bifromq-starters/target/`
-
-* bifromq-xxx-all.tar.gz // 适用于 Linux 和 macOS 的 standalone 集群部署 tar.gz 包
-* bifromq-xxx-standalone.tar.gz  // 适用于 Linux 和 macOS 的 standalone 部署 tar.gz 包
-* bifromq-xxx-windows-standalone.zip // 适用于 Windows 的 standalone 部署的 zip 包
\ No newline at end of file
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-2.0.0/03_deploy/1_deploy_with_docker.md b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-2.0.0/03_deploy/1_deploy_with_docker.md
deleted file mode 100644
index bd9950d5..00000000
--- a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-2.0.0/03_deploy/1_deploy_with_docker.md
+++ /dev/null
@@ -1,38 +0,0 @@
----
-sidebar_position: 1
----
-
-# 使用 Docker 部署
-
-## 前提条件
-
-* 已安装 [Docker](https://www.docker.com/)
-* 有对应端口使用权限且端口空闲,如无权限请更换端口
-
-## Docker 命令
-
-运行以下命令,会将 BifroMQ 以 linux 用户 `bifromq` 在容器中以 `standalone` 模式运行。
-
-```
-docker run -d --name bifromq -p 1883:1883 bifromq/bifromq:latest
-```
-
-
-
-### 内存限制
-
-默认情况下,BifroMQ进程在启动时会基于部署服务器的物理内存自动计算出相应的JVM参数。然而,在容器环境中启动时,会读取宿主机的物理内存,可能导致与Docker或容器内存限制发生冲突,从而引发容器被终止的情况。
-
-为避免此类问题,建议主动限制容器内存使用量,并以环境变量的形式传递给容器运行时,BifroMQ启动是会优先根据MEM_LIMIT计算JVM参数。具体示例如下:
-
-```
-docker run -d -m 10G -e MEM_LIMIT='10737418240' --name bifromq -p 1883:1883 bifromq/bifromq:latest
-```
-
-***注:MEM_LIMIT单位为bytes***
-
-更进一步,可以主动对JVM堆内存进行配置,并将其直接传递给容器运行时,以供BifroMQ使用。具体示例如下:
-
-```
-docker run -d -m 10G -e JVM_HEAP_OPTS='-Xms2G -Xmx4G -XX:MetaspaceSize=128m -XX:MaxMetaspaceSize=500m -XX:MaxDirectMemorySize=1G' --name bifromq -p 1883:1883 bifromq/bifromq:latest
-```
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-2.0.0/03_deploy/21_cluster.md b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-2.0.0/03_deploy/21_cluster.md
deleted file mode 100644
index 2ec432ad..00000000
--- a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-2.0.0/03_deploy/21_cluster.md
+++ /dev/null
@@ -1,49 +0,0 @@
----
-sidebar_position: 21
----
-
-# 部署 BifroMQ 集群
-
-## 前提条件
-* 确保您已安装 JDK 17+ 环境。
-* 从[GitHub](https://github.com/bifromqio/bifromq)获取BifroMQ的最新版本。
-
-## 安装步骤
-在本节中,我们将演示部署3节点的BifroMQ集群。与在[Linux](2_deploy_on_linux_mac.md)中部署类似,您可以首先解压已下载的tar文件。
-
-## 配置
-默认情况下,提供了一个配置文件,其中包含以下设置:
-```yaml
-bootstrap: true
-
-mqttServerConfig:
-  tcpListener:
-    port: 1883
-
-# 构建BifroMQ集群配置
-clusterConfig:
-  # 集群环境, 集群成员在相同环境下可以互通
-  env: "Test"
-  # 集群间通讯使用的主机地址,如果未填写,则会尝试获取该节点的Site-Local地址。
-  host:
-  # 用于集群内部节点信息的发送的端口号。如果未填写,则系统会找到一个未占用的端口号进行使用。
-  # 对于种子节点,推荐指定端口号来简化构建集群的过程
-  port:
-  # 使用DNS发现集群地址信息, 该配置适用于K8S环境下的部署
-  clusterDomainName:
-  # 逗号分割的<ADDRESS>:<PORT>列表,用于加入集群
-  seedEndpoints:
-```
-在设置集群之前,您需要以逗号分隔的`<ADDRESS>:<PORT>`格式指定`seedPoints`,例如`clusterConfig.port: ${PORT} 
-clusterConfig.seedEndpoints: N1:${PORT},N2:${PORT},N3:${PORT}`。有关详细的配置信息,请查看[此处](..%2F04_configuration%2F2_file_configs_manual.md)。
-## 设置Leader节点
-运行脚本`./bin/standalone.sh start`来启动leader节点。
-## 设置Follower节点
-* 对于跟随者,将`bootstrap`配置设置为`false`。
-* 运行脚本`./bin/standalone.sh start`来启动follower节点。
-## 检查集群部署
-运行完follower的启动脚本后,节点将形成一个集群,并在各自的机器上生成以下日志:`AgentHost joined seedEndpoint: ${seedEndpoints}`。
-## 部署约定
-不同版本之间的配置可能会有所不同。在部署 BifroMQ 时,您可以使用先前的配置进行设置,而不会中断 BifroMQ 的运行。然而,请注意这些配置可能不会生效。
-
-此外,在info.log的开头,打印完整的配置信息将被打印。
\ No newline at end of file
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-2.0.0/03_deploy/2_deploy_on_linux_mac.md b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-2.0.0/03_deploy/2_deploy_on_linux_mac.md
deleted file mode 100644
index e6d008c0..00000000
--- a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-2.0.0/03_deploy/2_deploy_on_linux_mac.md
+++ /dev/null
@@ -1,19 +0,0 @@
----
-sidebar_position: 1
----
-
-# 在 Linux 或者 macOS 部署
-
-## 前提条件
-
-* 安装 JDK 17+ 环境
-* 在 [bifromq_release](https://github.com/bifromqio/bifromq/releases) 获取 BifroMQ 的最新版本
-
-## Linux或者macOS
-
-运行以下命令即可运行 BifroMQ。
-
-```
-tar -zxvf bifromq-*-standalone.tar.gz --strip-components 1  -C /usr/share/bifromq/
-cd bifromq && ./bin/standalone.sh start
-```
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-2.0.0/03_deploy/3_deploy_on_windows.md b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-2.0.0/03_deploy/3_deploy_on_windows.md
deleted file mode 100644
index 8cf9a352..00000000
--- a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-2.0.0/03_deploy/3_deploy_on_windows.md
+++ /dev/null
@@ -1,20 +0,0 @@
----
-sidebar_position: 4
----
-
-# 在 Windows 部署 
-
-## 前提条件
-
-* 安装 JDK 17+ 环境
-* 在 [bifromq_release](https://github.com/bifromqio/bifromq/releases) 获取 BifroMQ 的最新版本
-
-## Windows
-
-打开命令行工具,运行以下命令即可运行 BifroMQ。
-
-```
-unzip -zxvf bifromq-*-standalone-windows.zip
-cd bifromq\bin
-standalone.bat start
-```
\ No newline at end of file
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-2.0.0/03_deploy/_category_.json b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-2.0.0/03_deploy/_category_.json
deleted file mode 100644
index 181c7b1d..00000000
--- a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-2.0.0/03_deploy/_category_.json
+++ /dev/null
@@ -1,8 +0,0 @@
-{
-  "label": "Install & Deploy",
-  "position": 3,
-  "link": {
-    "type": "generated-index",
-    "description": "Install And Deploy BifroMQ."
-  }
-}
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-2.0.0/04_configuration/1_configs_introduction.md b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-2.0.0/04_configuration/1_configs_introduction.md
deleted file mode 100644
index 6255d7af..00000000
--- a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-2.0.0/04_configuration/1_configs_introduction.md
+++ /dev/null
@@ -1,22 +0,0 @@
----
-sidebar_position: 1
----
-
-
-# 配置简介
-
-BifroMQ的系统参数主要通过配置文件进行设置,本章节会分别介绍这部分配置及其含义。
-
-
-## 配置文件介绍
-
-主配置文件名称为standalone.yml,位置位于:
-
-| 安装方式   | 文件位置                               |
-| :--------- | -------------------------------------- |
-| 压缩包解压 | ./conf/standalone.yml                  |
-| Docker容器 | /usr/share/bifromq/conf/standalone.yml |
-
-主配置文件包含了大部分必须的配置项,其余配置项如果没有在配置文件中明确指定,将使用默认配置。 所有可用的配置项及其说明见:[配置文件手册](2_file_configs_manual.md)
-
-
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-2.0.0/04_configuration/2_file_configs_manual.md b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-2.0.0/04_configuration/2_file_configs_manual.md
deleted file mode 100644
index 054f138f..00000000
--- a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-2.0.0/04_configuration/2_file_configs_manual.md
+++ /dev/null
@@ -1,354 +0,0 @@
----
-sidebar_position: 2
----
-
-# 配置文件手册
-
-## 简介
-本文描述了BifroMQ的配置参数。
-
-### bootstrap
-- 类型:Boolean
-- 默认值:false
-- 描述:如果节点负责集群引导,则该值应设置为true。否则,应设置为false。注意:在集群部署中,必须存在**仅一个**引导节点。
-
-### authProviderFQN
-- 类型:String
-- 默认值:null
-- 描述:指定要通过Pf4j加载的authProvider的名称。如果未配置,则将使用内置的DefaultAuthProvider。
-
-### settingProviderFQN
-- 类型:String
-- 默认值:null
-- 描述:指定要通过Pf4j加载的settingProvider的名称。如果未配置,则将使用内置的DefaultSettingProvider。
-
-### clusterConfig
-#### env
-- 类型:String
-- 默认值:null
-- 描述:集群环境。注意:具有不同环境的集群彼此之间相互依赖。此外,集群环境不能为null或空字符串。
-
-#### host
-- 类型:String
-- 默认值:null
-- 描述:主机地址
-
-#### port
-- 类型:Integer
-- 默认值:0
-- 描述:主机端口号。
-
-#### seedEndpoints
-- 类型:String
-- 默认值:null
-- 描述:用于消息扩散的种子节点(ip:port的形式)
-
-#### clusterDomainName
-- 类型:String
-- 默认值:null
-- 描述:代理主机集群的域名。
-
-### mqttServerConfig
-#### connTimeoutSec
-- 类型:Integer
-- 默认值:20
-- 描述:从建立TCP连接到完成连接操作的可容忍超时持续时间。如果超出此限制,服务器将主动断开连接。
-
-#### maxConnPerSec
-- 类型:Integer
-- 默认值:2000
-- 描述:每秒接受的Connect操作的最大频率。超出此限制的连接将通过令牌桶受限,并随后将断开连接。
-
-#### maxDisconnPerSec
-- 类型:Integer
-- 默认值:1000
-- 描述:每秒接受的Disconnect操作的最大频率,通过令牌桶控制。
-
-#### maxMsgByteSize
-- 类型:Integer
-- 默认值:256 * 1024
-- 描述:数据包的最大允许大小。
-
-#### maxResendTimes
-- 类型:Integer
-- 默认值:5
-- 描述:具有QoS1和QoS2的消息的最大重发次数。超过此限制后,消息将被丢弃。
-
-#### maxConnBandwidth
-- 类型:Integer
-- 默认值:512 * 1024
-- 描述:单个连接允许的最大带宽,分别计算入站和出站流量。
-
-#### defaultKeepAliveSec
-- 类型:Integer
-- 默认值:300
-- 描述:连接的默认保持活动持续时间。当客户端未主动设置时,使用此值。
-
-#### qos2ConfirmWindowSec
-- 类型:Integer
-- 默认值:5
-- 描述:用于QoS2消息内部缓存messageId的过期时间。
-
-#### bossELGThreads
-- 类型:Integer
-- 默认值:1
-- 描述:Netty中处理连接的线程数。
-
-#### workerELGThreads
-- 类型:Integer
-- 默认值:可用处理器数量的1/2,最小值为2。
-- 描述:处理通道的消息处理线程数。
-
-### tcpListener
-#### enable
-- 类型:Boolean
-- 默认值:true
-- 描述:是否在mqtt-server内建立TCP访问能力。
-
-#### host
-- 类型:String
-- 默认值:0.0.0.0
-- 描述:mqtt-server绑定的地址。用于提供外部mqtt访问点。
-
-#### port
-- 类型:Integer
-- 默认值:1883
-- 描述:mqtt-server绑定的端口,用于向外部公开mqtt TCP访问端口。
-
-### tlsListener
-#### enable
-- 类型:Boolean
-- 默认值:false
-- 描述:是否在mqtt-server内建立TLS访问能力。
-
-#### host
-- 类型:String
-- 默认值:0.0.0.0
-- 描述:mqtt-server绑定的地址,用于提供外部mqtt访问点。
-
-#### port
-- 类型:Integer
-- 默认值:1884
-- 描述:mqtt-server绑定的端口,用于向外部公开mqtt TLS访问端口。
-
-#### sslConfig
-##### certFile
-- 类型:String
-- 默认值:null
-- 描述:指定服务器在mqtt-server模块提供TLS和WSS功能时所使用的公钥证书文件名。它将尝试从“CONF_DIR”系统参数指定的目录加载,或者从当前classpath加载。
-
-##### keyFile
-- 类型:String
-- 默认值:null
-- 描述:指定服务器在mqtt-server模块提供TLS和WSS功能时所使用的私钥证书文件名。它将尝试从“CONF_DIR”系统参数指定的目录加载,或者从当前classpath加载。
-
-##### trustCertsFile
-- 类型:String
-- 默认值:null
-- 描述:指定服务器在mqtt-server模块提供TLS和WSS功能时所使用的根证书文件名。它将尝试从“CONF_DIR”系统参数指定的目录加载,或者从当前classpath加载。
-
-##### clientAuth
-- 类型:String
-- 默认值:OPTIONAL
-- 描述:指定在mqtt-server与客户端建立SSL连接时是否需要客户端身份验证。可能的值包括:
-* NONE:不需要验证
-* OPTIONAL:服务器请求客户端验证,但如果客户端不提供证书,则不会失败。
-* REQUIRE:服务器需要客户端验证,如果客户端不提供证书则会失败。
-
-### wsListener
-#### enable
-- 类型:Boolean
-- 默认值:true
-- 描述:是否在mqtt-server内建立WebSocket访问能力。
-
-#### host
-- 类型:String
-- 默认值:0.0.0.0
-- 描述:mqtt-server绑定的地址,用于提供外部mqtt访问点。
-
-#### port
-- 类型:Integer
-- 默认值:8080
-- 描述:mqtt-server绑定的端口,用于向外部公开WebSocket访问端口。
-
-#### wsPath
-- 类型:String
-- 默认值:/mqtt
-- 描述:mqtt-server中WebSocket和WSS的访问路径。
-
-### wssListener
-#### enable
-- 类型:Boolean
-- 默认值:false
-- 描述:是否在mqtt-server内建立WebSocket Secure (WSS)访问能力。
-
-#### host
-- 类型:String
-- 默认值:0.0.0.0
-- 描述:mqtt-server绑定的地址,用于提供外部mqtt访问点。
-
-#### port
-- 类型:Integer
-- 默认值:8443
-- 描述:mqtt-server绑定的端口,用于向外部公开WebSocket Secure (WSS)访问端口。
-
-#### wsPath
-- 类型:String
-- 默认值:/mqtt
-- 描述:mqtt-server中WebSocket和WSS的访问路径。
-
-#### sslConfig
-- 描述:与tlsListener.sslConfig相同。
-
-## rpcClientConfig
-### workerThreads
-- 类型:Integer
-- 默认值:可用处理器核心数的1/8,最小值为2。
-- 描述:RPC客户端中线程的数量。
-
-### sslConfig
-#### certFile
-- 类型:String
-- 默认值:null
-- 描述:指定用于RPC客户端的公钥证书文件名。
-
-#### keyFile
-- 类型:String
-- 默认值:null
-- 描述:指定用于RPC客户端的私钥证书文件名。
-
-#### trustCertsFile
-- 类型:String
-- 默认值:null
-- 描述:指定用于RPC客户端的根证书文件名。
-
-## rpcServerConfig
-### host
-- 类型:String
-- 默认值:与mqtt-server主机地址相同。
-- 描述:rpc-server的主机地址。
-### port
-- 类型:Integer
-- 默认值:0
-- 描述:rpc-server的端口。
-### workerThreads
-- 类型:Integer
-- 默认值:可用处理器核心数的1/4,最小值为2。
-- 描述:rpc-server中线程的数量。
-### sslConfig
-- 描述:与`tlsListener.sslConfig`具有相同的字段和含义。
-## baseKVRpcServerConfig
-- 描述:与`rpcServerConfig`具有相同的字段和含义。
-## stateStoreConfig
-### queryThreads
-- 类型:Integer
-- 默认值:可用处理器的1/3,最小值为2。
-- 描述:用于执行BaseKV存储的dist-worker、inbox-store和retain-store模块中的查询类型请求的核心线程和最大线程数。
-### tickerThreads
-- 类型:Integer
-- 默认值:可用处理器的1/20,最小值为1。
-- 描述:用于执行dist-worker、inbox-store和retain-store模块中的BaseKV存储周期性tick操作的核心线程和最大线程数。
-### bgWorkerThreads
-- 类型:Integer
-- 默认值:可用处理器的1/4,最小值为1。
-- 描述:用于执行后台操作的核心线程和最大线程数。
-### distWorkerConfig
-#### queryPipelinePerStore
-- 类型:Integer
-- 默认值:1000
-- 描述:每个`BaseKV store`中queryPipeline的数量。
-#### compactWALThreshold
-- 类型:Integer
-- 默认值:2000
-- 描述:在执行压缩操作之前的最大日志数。
-#### dataEngineConfig
-##### type
-- 类型:String
-- 默认值:rocksdb
-- 描述:指定在 dist-worker模块的BaseKV存储中使用的数据引擎类型。选项包括:
-* rocksDB:提供持久性功能,可以在重新启动后恢复状态。
-* memory:无持久性,重新启动后数据将丢失。
-##### gcIntervalInSec
-- 类型:Integer
-- 默认值:300
-- 描述:指定dist-worker模块中BaseKV的数据引擎执行垃圾回收的间隔(以秒为单位)。
-##### dataPathRoot
-- 类型:String
-- 默认值:null
-- 描述:当类型设置为`rocksDB`时有效。指定dist-worker模块的dataEngine存储数据文件的目录。如果配置为绝对路径,将直接加载;如果配置为相对路径,将尝试从由`DATA_DIR`和`user.dir`系统参数指定的目录加载。
-##### compactMinTombstoneKeys
-- 类型:String
-- 默认值:200,000
-- 描述:当`type`设置为`rocksDB`时有效。
-##### compactTombstonePercent
-- 类型:Double
-- 默认值:0.3
-- 描述:当`type`设置为`rocksDB`时有效。当数据引擎使用的rocksDB中特定范围内已删除的密钥数超过`compactMinTombstoneKeys`,并且已删除密钥占总数的比例超过`compactTombstonePercent`时,将对此范围执行压缩操作。
-##### asyncWALFlush
-- 类型:Boolean
-- 默认值:false
-- 描述:仅适用于WAL引擎,日志将以异步方式刷新。
-##### fsyncWAL
-- 类型:Boolean
-- 默认值:false
-- 描述:仅适用于WAL引擎。如果此标志为 true,写入速度会较慢。如果此标志为false,且机器崩溃,某些最近的写入可能会丢失。
-#### walEngineConfig
-- 描述:类似于数据引擎。对于rocksdb配置,`compactMinTombstoneKeys`的默认值为 10,000。
-#### balanceConfig
-##### scheduleIntervalInMs
-- 类型:Long
-- 默认值:5,000
-- 描述:BaseKV 范围平衡器的调度间隔。
-##### balancers
-- 类型:List of String
-- 默认值:com.baidu.bifromq.dist.worker.balance.ReplicaCntBalancerFactory
-- 描述:BaseKV Range Balancers的FQNs。
-### inboxStoreConfig
-#### purgeDelaySeconds
-- 类型:Integer
-- 默认值:180
-- 描述:为过期的inbox提供一些延迟。
-#### queryPipelinePerStore
-- 类型:Integer
-- 默认值:100
-- 描述:每个`BaseKV store`中queryPipeline的数量。
-#### 其他字段
-- 描述:其他字段具有与dist workers相同的含义。
-### retainStoreConfig
-- 描述:字段与dist workers具有相同的含义。
-## apiServerConfig
-### enable
-- 类型:Boolean
-- 默认值:true
-- 描述:是否在api-service中构建HTTP访问功能。
-### host
-- 类型:String
-- 默认值:与mqtt-server主机地址相同。
-- 描述:api-service的主机地址。
-### httpPort
-- 类型:整数
-- 默认值:8091
-- 描述:api-service的HTTP端口。
-### apiBossThreads
-- 类型:Integer
-- 默认值:1
-- 描述:Netty中处理连接的线程数。
-### apiWorkerThreads
-- 类型:Integer
-- 默认值:2
-- 描述:处理消息处理通道的线程数。
-### httpsListenerConfig
-#### enable
-- 类型:Boolean
-- 默认值:false
-- 描述:是否在api-service中构建HTTPS访问功能。
-#### host
-- 类型:String
-- 默认值:与mqtt-server主机地址相同。
-- 描述:api-service的主机地址。
-#### port
-- 类型:Integer
-- 默认值:8090
-- 描述:api-service的HTTPS端口。
-#### sslConfig
-- 描述:与 `tlsListener.sslConfig` 具有相同的字段和含义。
\ No newline at end of file
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-2.0.0/04_configuration/3_performance_tuning_linux.md b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-2.0.0/04_configuration/3_performance_tuning_linux.md
deleted file mode 100644
index d01c229c..00000000
--- a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-2.0.0/04_configuration/3_performance_tuning_linux.md
+++ /dev/null
@@ -1,57 +0,0 @@
----
-sidebar_position: 3
----
-
-# 系统参数调优(Linux)
-
-以下Kernel参数会影响BifroMQ所在机器能接受的最大连接数
-
-## 内存
-
-* vm.max_map_count: 限制一个进程可以拥有的VMA(虚拟内存区域)的数量, 可放大到221184
-
-## 最大打开文件数
-
-* nofile: 指单进程的最大打开文件数
-* nr_open: 指单个进程可分配的最大文件数,通常默认值为1024*1024=1048576
-* file-max: 系统内核一共可以打开的最大值,默认值是185745
-
-## NetFilter调优
-
-通过`sysctl -a | grep conntrack`查看当前的参数,以下几个参数决定了最大连接数:
-
-* net.netfilter.nf_conntrack_buckets: 记录连接条目的hashtable的bucket大小
-  * 修改命令:`echo 262144 > /sys/module/nf_conntrack/parameters/hashsize`
-* net.netfilter.nf_conntrack_max: hashtable最大的条目数,一般为nf_conntrack_buckets * 4
-* net.nf_conntrack_max: 同net.netfilter.nf_conntrack_max
-* net.netfilter.nf_conntrack_tcp_timeout_fin_wait: 默认 120s -> 30s
-* net.netfilter.nf_conntrack_tcp_timeout_time_wait: 默认 120s -> 30s
-* net.netfilter.nf_conntrack_tcp_timeout_close_wait: 默认 60s -> 15s
-* net.netfilter.nf_conntrack_tcp_timeout_established: 默认 432000 秒(5天)-> 300s
-
-
-以下sysctl参数会影响大压力下tcp channel性能表现
-
-## Server端及测试发压端TCP相关调优
-
-推荐使用centos7环境进行部署及压力测试。
-
-centos6环境需要进行系统参数调优:
-* net.core.wmem_max: 最大的TCP数据发送窗口大小(字节)
-  * 修改命令:`echo 'net.core.wmem_max=16777216' >> /etc/sysctl.conf`
-* net.core.wmem_default: 默认的TCP数据发送窗口大小(字节)
-  * 修改命令:`echo 'net.core.wmem_default=262144' >> /etc/sysctl.conf`
-* net.core.rmem_max: 最大的TCP数据接收窗口大小(字节)
-  * 修改命令:`echo 'net.core.rmem_max=16777216' >> /etc/sysctl.conf`
-* net.core.rmem_default: 默认的TCP数据接收窗口大小(字节)
-  * 修改命令:`echo 'net.core.rmem_default=262144' >> /etc/sysctl.conf`
-* net.ipv4.tcp_rmem: socket接收缓冲区内存使用的下限  警戒值  上限
-  * 修改命令:`echo 'net.ipv4.tcp_rmem= 1024 4096 16777216' >> /etc/sysctl.conf`
-* net.ipv4.tcp_rmem: socket发送缓冲区内存使用的下限  警戒值  上限
-  * 修改命令:`echo 'net.ipv4.tcp_wmem= 1024 4096 16777216' >> /etc/sysctl.conf`
-* net.core.optmem_max: 每个socket所允许的最大缓冲区的大小 (字节)
-  * 修改命令:`echo 'net.core.optmem_max = 16777216' >> /etc/sysctl.conf`
-* net.core.netdev_max_backlog: 网卡设备将请求放入队列的长度
-  * 修改命令:`echo 'net.core.netdev_max_backlog = 16384' >> /etc/sysctl.conf`
-
-修改完配置通过`sysctl -p`并重启服务器生效。
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-2.0.0/04_configuration/_category_.json b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-2.0.0/04_configuration/_category_.json
deleted file mode 100644
index db925eaf..00000000
--- a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-2.0.0/04_configuration/_category_.json
+++ /dev/null
@@ -1,8 +0,0 @@
-{
-  "label": "Configuration",
-  "position": 4,
-  "link": {
-    "type": "generated-index",
-    "description": "BifroMQ Configuration."
-  }
-}
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-2.0.0/05_user_guide/1_connect/1_connect.md b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-2.0.0/05_user_guide/1_connect/1_connect.md
deleted file mode 100644
index 47beb228..00000000
--- a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-2.0.0/05_user_guide/1_connect/1_connect.md
+++ /dev/null
@@ -1,22 +0,0 @@
----
-sidebar_position: 1
----
-
-# 连接到 BifroMQ
-
-BifroMQ 是一个标准的 MQTT 消息中间件,你可以使用支持 MQTT 3.1/3.1.1 的任何 Client 进行连接。
-
-## 连接地址
-
-使用启动服务对应的 IP 或域名,默认端口及用途如下。
-
-端口|用途
----|---
-IP或域名:1883|TCP连接
-IP或域名:1884|TLS连接
-IP或域名:80/mqtt|WS连接
-IP或域名:443/mqtt|WSS连接
-
-## 鉴权
-
-默认情况下未开启鉴权,可将用户名密码留空进行连接。如需认证鉴权,请参考[认证鉴权插件](../../06_plugin/2_auth_provider.md)。
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-2.0.0/05_user_guide/1_connect/2_pubsub.md b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-2.0.0/05_user_guide/1_connect/2_pubsub.md
deleted file mode 100644
index 49a60a30..00000000
--- a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-2.0.0/05_user_guide/1_connect/2_pubsub.md
+++ /dev/null
@@ -1,41 +0,0 @@
----
-sidebar_position: 2
----
-
-# 发布/订阅
-
-根据MQTT协议按照消息发送和接收的角色可以分为发送方(Publisher)和订阅方(Subscriber),其基本模式如下图所示:
-
-![pub-sub-pattern](./images/pub-sub-pattern.png)
-
-* 发布消息。客户端可以通过连接向服务器发布消息。消息以主题(`topic`)为基础进行发布。主题是被订阅者感兴趣的通信内容的一种描述方式, 且具有层次结构(例如`home/bedroom/temperature`)。
-
-  客户端发布消息时需要指定主题,消息体中包含实际通信的内容。除此之外,发送方还需指定该条的QoS(Quality of Service),BifroMQ全量支持MQTT的所有QoS即QoS0/QoS1/QoS2。其具体含义如下:
-
-  | QoS  | 描述 |
-    | ---- | ---- |
-  | QoS0 | 至多一次传输 |
-  | QoS1 | 至少一次传输 |
-  | QoS2 | 正好一次传输 |
-
-* 订阅主题。在订阅中,订阅者的主题称为`topicFilter`。服务器端接收客户端发送的订阅请求,并记录该订阅。通常情况下,订阅可以分为非通配订阅(non-wildcard)和通配订阅(wildcard)。
-
-    * 对于非通配订阅:直接订阅特定的主题而不使用通配符,若订阅的主题为`home/bedroom/temperature`,则只能匹配主题为`home/bedroom/temperature`的消息。
-
-    * 对于通配订阅:订阅的主题中包含了通配符(`+`或`#`)。`+` 通配符匹配单级主题层级,`#` 通配符:匹配多级主题层级。下面是一些示例来说明如何使用通配符进行订阅: 
-
-      使用 `+` 通配符:  
-
-      * 订阅主题 `sensor/+/temperature`:匹配 `sensor/bedroom/temperature`、`sensor/kitchen/temperature` 等主题。
-      * 订阅主题 `home/+/light/+`:匹配 `home/livingroom/light/on`、`home/bedroom/light/off` 等主题。  
-
-      使用 `#` 通配符:  
-
-      * 订阅主题 `home/bedroom/#`:匹配 `home/bedroom/light/on`、`home/bedroom/temperature` 等主题及其子主题。
-      * 订阅主题 `home/+/#`:匹配 `home/bedroom/light/on`、`home/kitchen/temperature` 等主题及其子主题。
-      * 订阅主题 `#`:匹配所有主题。  
-
-      需要注意的是,通配符订阅可能会导致订阅的主题数量庞大,因此在使用通配符订阅时,应谨慎考虑性能和资源消耗。  
-
-      除此之外,与发布主题一样,订阅主题时还需要制定该主题的QoS。需要注意的是,BifroMQ在进行消息转发时,根据MQTT协议将取对应发送消息主题的QoS与订阅主题QoS的较小值,
-      即:`Min(PublishQoS, SubscribeQoS)`。因此即便订阅方订阅的主题为QoS2,依然有可能收到QoS0的对应消息。
diff --git a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-2.0.0/05_user_guide/1_connect/3_shared_sub.md b/i18n/zh-Hans/docusaurus-plugin-content-docs/version-2.0.0/05_user_guide/1_connect/3_shared_sub.md
deleted file mode 100644
index 2dab7154..00000000
--- a/i18n/zh-Hans/docusaurus-plugin-content-docs/version-2.0.0/05_user_guide/1_connect/3_shared_sub.md
+++ /dev/null
... 32968 lines suppressed ...