diff --git a/docs-2.0/4.deployment-and-installation/1.resource-preparations.md b/docs-2.0/4.deployment-and-installation/1.resource-preparations.md index b1ea6e7236c..1299acb71a5 100644 --- a/docs-2.0/4.deployment-and-installation/1.resource-preparations.md +++ b/docs-2.0/4.deployment-and-installation/1.resource-preparations.md @@ -210,7 +210,7 @@ Users can estimate the memory, disk space, and partition number needed for a Neb | Resource |Unit| How to estimate |Description| |:--- |:---|:--- |:---| | Disk space for a cluster |Bytes| `the_sum_of_edge_number_and_vertex_number` * `average_bytes_of_properties` * 6 * 120% |-| -| Memory for a cluster |Bytes| [`the_sum_of_edge_number_and_vertex_number` * 15 + `the_number_of_RocksDB_instances` * (`write_buffer_size` * `max_write_buffer_number` + `rocksdb_block_cache`)] * 120% |`write_buffer_size` and `max_write_buffer_number` are RocksDB parameters. For more information, see [MemTable](https://github.com/facebook/rocksdb/wiki/MemTable). For details about `rocksdb_block_cache`, see [Memory usage in RocksDB](https://github.com/facebook/rocksdb/wiki/Memory-usage-in-RocksDB#block-cache).| +| Memory for a cluster |Bytes| [`the_sum_of_edge_number_and_vertex_number` * 16 + `the_number_of_RocksDB_instances` * (`write_buffer_size` * `max_write_buffer_number` + `rocksdb_block_cache`)] * 120% |`write_buffer_size` and `max_write_buffer_number` are RocksDB parameters. For more information, see [MemTable](https://github.com/facebook/rocksdb/wiki/MemTable). For details about `rocksdb_block_cache`, see [Memory usage in RocksDB](https://github.com/facebook/rocksdb/wiki/Memory-usage-in-RocksDB#block-cache).| | Number of partitions for a graph space |-| `the_number_of_disks_in_the_cluster` * `disk_partition_num_multiplier` |`disk_partition_num_multiplier` is an integer between 2 and 10 (both including). Its value depends on the disk performance. Use 2 for HDD.| * Question 1: Why do we multiply the disk space and memory by 120%? diff --git a/docs-2.0/4.deployment-and-installation/3.upgrade-nebula-graph/upgrade-nebula-graph-to-latest.md b/docs-2.0/4.deployment-and-installation/3.upgrade-nebula-graph/upgrade-nebula-graph-to-latest.md index 314665e4251..06e47dc00f9 100644 --- a/docs-2.0/4.deployment-and-installation/3.upgrade-nebula-graph/upgrade-nebula-graph-to-latest.md +++ b/docs-2.0/4.deployment-and-installation/3.upgrade-nebula-graph/upgrade-nebula-graph-to-latest.md @@ -1,14 +1,19 @@ -# Upgrade Nebula Graph to v{{nebula.release}} +# Upgrade Nebula Graph from version 2.x to {{nebula.release}} -The legacy versions of Nebula Graph refer to the versions lower than Nebula Graph v2.0.0-GA. This topic describes how to upgrade Nebula Graph to v{{nebula.release}}. +This topic describes how to upgrade Nebula Graph from version 2.x to {{nebula.release}}, taking upgrading from version 2.6.1 to {{nebula.release}} as an example. -!!! note +## Applicable source versions - To upgrade Nebula Graph v2.0.0-GA or later versions to v{{nebula.release}}, see [Nebula Graph v2.0.x to v{{nebula.release}}](upgrade-nebula-from-200-to-latest.md). +This topic applies to upgrading Nebula Graph from 2.0.0 and later 2.x versions to {{nebula.release}}. It does not apply to historical versions earlier than 2.0.0, including the 1.x versions. + +To upgrade Nebula Graph from historical versions to {{nebula.release}}: + +1. Upgrade it to the latest 2.x version according to the docs of that version. +2. Follow this topic to upgrade it to {{nebula.release}}. ## Limitations -* Rolling Upgrade is not supported. You must stop the Nebula Graph services before the upgrade. +* Rolling Upgrade is not supported. You must stop all the Nebula Graph services before the upgrade. * There is no upgrade script. You have to manually upgrade each server in the cluster. @@ -16,313 +21,165 @@ The legacy versions of Nebula Graph refer to the versions lower than Nebula Grap * You must upgrade the old Nebula Graph services on the same machines they are deployed. **DO NOT** change the IP addresses, configuration files of the machines, and **DO NOT** change the cluster topology. -* The hard disk space of each machine should be **three times** as much as the space taken by the original data directories. +* The hard disk space of each machine should be **more than three times** as much as the space taken by the original data directories. * Known issues that could cause data loss are listed on [GitHub known issues](https://github.com/vesoft-inc/nebula-graph/issues/857). The issues are all related to altering schema or default values. -* To connect to Nebula Graph 2.0.0, you must upgrade all the Nebula Graph clients. The communication protocols of the old versions and the latest versions are not compatible. - -* The upgrade takes about 30 minutes in [this test environment](#appendix_1_test_environment). - * **DO NOT** use soft links to switch the data directories. * You must have the sudo privileges to complete the steps in this topic. -## Installation paths - -### Old installation path - -By default, old versions of Nebula Graph are installed in `/usr/local/nebula/`, hereinafter referred to as `${nebula-old}`. The default configuration file path is `${nebula-old}/etc/`. - -* Storaged data path is defined by the `--data_path` option in the `${nebula-old}/etc/nebula-storaged.conf` file. The default path is `data/storage`. - -* Metad data path is defined by the `--data_path` option in the `${nebula-old}/etc/nebula-metad.conf` file. The default path is `data/meta`. - -!!! note - - The actual paths in your environment may be different from those described in this topic. You can run the Linux command `ps -ef | grep nebula` to locate them. - -### New installation path - -`${nebula-new}` represents the installation path of the new Nebula Graph version, such as `/usr/local/nebula-new/`. - -``` -# mkdir -p ${nebula-new} -``` - -## Upgrade steps - -1. **Stop all client connections**. You can run the following commands on each Graph server to turn off the Graph Service and avoid dirty write. - - ``` - # ${nebula-old}/scripts/nebula.service stop graphd - [INFO] Stopping nebula-graphd... - [INFO] Done - ``` +## Upgrade influences -2. Run the following commands to stop all services of the old version Nebula Graph. - - ``` - # ${nebula-old}/scripts/nebula.service stop all - [INFO] Stopping nebula-metad... - [INFO] Done - [INFO] Stopping nebula-graphd... - [INFO] Done - [INFO] Stopping nebula-storaged... - [INFO] Done - ``` - - The `storaged` process needs about 1 minute to flush data. Wait 1 minute and then run `ps -ef | grep nebula` to check and make sure that all the Nebula Graph services are stopped. - - !!! Note - - If the services are not fully stopped in 20 minutes, **stop upgrading** and go to the [Nebula Graph community](https://discuss.nebula-graph.io/) for help. - -3. Install the new version of Nebula Graph on each machine. - - 1. Install the new binary file. - - - To install with RPM/DEB packages, download the installation package of the corresponding operating system from [release page](https://github.com/vesoft-inc/nebula-graph/releases). - - ``` - # sudo rpm --force -i --prefix=${nebula-new} ${nebula-package-name.rpm} # for centos/redhat - # sudo dpkg -i --instdir==${nebula-new} ${nebula-package-name.deb} # for ubuntu - ``` - - For detailed steps, see [Install Nebula Graph with RPM or DEB package](../2.compile-and-install-nebula-graph/2.install-nebula-graph-by-rpm-or-deb.md). - - - To install with the source code, follow the substeps. For detailed steps, see [Install Nebula Graph by compiling the source code](../2.compile-and-install-nebula-graph/1.install-nebula-graph-by-compiling-the-source-code.md). Some key commands are as follows. - - - Clone the source code. +- Data swelling - ``` - # git clone --branch {{nebula.branch}} https://github.com/vesoft-inc/nebula-graph.git - ``` - - - Configure CMake. - - ``` - # cmake -DCMAKE_INSTALL_PREFIX=${nebula-new} -DENABLE_TESTING=OFF -DCMAKE_BUILD_TYPE=Release .. - ``` - - 2. Copy the configuration files from the old path to the new path. - - ``` - # cp -rf ${nebula-old}/etc ${nebula-new}/ - ``` - -4. Follow the substeps to prepare the Meta servers (usually 3 of them in a cluster). - - - Locate the old Meta data path and copy the data files to the new path. - - Find the `--data_path` option in `${nebula-old}/etc/nebula-metad.conf`. The default value is `data/meta`. - - - If the legacy versions **has not changed** the `--data_path` item, run the following command to copy the meta data to the new directory. - - ``` - # mkdir -p ${nebula-new}/data/meta/ - # cp -r ${nebula-old}/data/meta/* ${nebula-new}/data/meta/ - ``` - - - If the legacy versions change the default metad directory, copy it according to the actual directory. + The Nebula Graph 3.x version expands the original data format with one more key per vertex, so the data takes up more space after the upgrade. + + The format of the new key is: + + Type (1 byte) + Partition ID (3 bytes) + VID (size depends on the data type). + + The value of the new key is empty. The extra space taken can be calculated based on the number of vertices and the data type of the VID. For example, if there are 100 million vertices in the dataset and the VIDs are INT64, the new key will take 100 million x (1 + 3 + 8) = 1.2 billion bytes, i.e., about 1.2 GB. - - Modify the new Meta configuration files. +- Client compatibility - - Edit the new metad configuration file. + After the upgrade, you will not be able to connect to Nebula Graph from old clients. You will need to upgrade all clients to a version compatible with Nebula Graph {{nebula.release}}. - ``` - # vim ${nebula-new}/nebula-metad.conf - ``` +- Configuration changes - - [Optional]Add the following parameters in the Meta configuration files if you need them. + A few configuration parameters have been changed. For more information, see the release notes and configuration docs. - `--null_type=false`: Disables the support for using [`NULL`](../../3.ngql-guide/3.data-types/5.null.md).**The default value is `true`**. When set to `false`, you must specify a [default value](../../3.ngql-guide/10.tag-statements/1.create-tag.md) when altering tags or edge types, otherwise, data reading fails. +!!! caution - `--string_index_limit=32`: Specifies the [index length](../../3.ngql-guide/14.native-index-statements/1.create-native-index.md) for string values as 32. The default length is 64. + There may be other undiscovered influences. Before the upgrade, we recommend that you read the release notes and user manual carefully, and keep an eye on the [posts](https://discuss.nebula-graph.io/) on the forum and [issues](https://github.com/vesoft-inc/nebula/issues) on Github. - !!! Note +## Preparations before the upgrade - You must make sure that this step is applied on every Meta server. +- Download the TAR file of Nebula Graph {{nebula.release}} according to your operating system and system architecture. You need the binary files during the upgrade. Find the TAR file on [the download page](https://nebula-graph.io/download/). -5. Prepare the Storage configuration files on each Storage server. + !!! note + You can also get the new binaries from the source code or the RPM/DEB package. - + [Optional]If the old Storage data path is not the default setting `--data_path=data/storage`, modify it. +- Locate the data files based on the value of the `data_path` parameters in the Storage and Meta configurations, and backup the data files. The default paths are `nebula/data/storage` and `nebula/data/meta`. - ``` - # vim ${nebula-new}/nebula-storaged.conf - ``` - Change the value of `--data_path` as the new data path. +- Backup the configuration files. - + Create the new Storage data directories. +- Collect the statistics of all graph spaces before the upgrade. After the upgrade, you can collect again and compare the results to make sure that no data is lost. To collect the statistics: - ``` - # mkdir -p ${nebula-new}/data/storage/ - ``` + 1. Run `SUBMIT JOB STATS`. + 2. Run `SHOW JOBS` and record the result. - If the `--data_path` default value has been modified, create the Storage data directories according to the modification. +## Upgrade steps -6. Start the new Meta Service. +1. Stop all Nebula Graph services. - - Run the following command on each Meta server. + ``` + /scripts/nebula.service stop all + ``` - ``` - # ${nebula-new}/scripts/nebula.service start metad - [INFO] Starting nebula-metad... - [INFO] Done - ``` + `nebula_install_path` indicates the installation path of Nebula Graph. - - Check if every nebula-metad process is started normally. + The storaged progress needs around 1 minute to flush data. You can run `nebula.service status all` to check if all services are stopped. For more information about starting and stopping services, see [Manage services](../manage-service.md). - ``` - # ps -ef |grep nebula-metad - ``` + !!! note - - Check if there is any error information in the Meta logs in `${nebula-new}/logs`. - - !!! Note + If the services are not fully stopped in 20 minutes, stop upgrading and ask for help on [the forum](https://discuss.nebula-graph.io/) or [Github](https://github.com/vesoft-inc/nebula/issues). - If any nebula-metad process cannot start normally, **stop upgrading, start the Nebula Graph services from the old directories**, and take the error logs to the [Nebula Graph community](https://discuss.nebula-graph.io/) for help. +2. In the target path where you unpacked the TAR file, use the binaries in the `bin` directory to replace the old binaries in the `bin` directory in the Nebula Graph installation path. -7. Run the following commands to upgrade the Storage data format. + !!! note + Update the binary of the corresponding service on each Nebula Graph server. - ``` - # ${nebula-new}/bin/db_upgrader \ - --src_db_path= \ - --dst_db_path= \ - --upgrade_meta_server=:[,:,...] \ - --upgrade_version= \ - ``` +3. Modify the following parameters in all Graph configuration files to accommodate the value range of the new version. If the parameter values are within the specified range, skip this step. - The parameters are described as follows. + - Set a value in [1,604800] for `session_idle_timeout_secs`. The recommended value is 28800. + - Set a value in [1,604800] for `client_idle_timeout_secs`. The recommended value is 28800. - - `--src_db_path`: Specifies the absolute path of the **OLD** Storage data directories. Separate multiple paths with commas, without spaces. + The default values of these parameters in the 2.x versions are not within the range of the new version. If you do not change the default values, the upgrade will fail. For detailed parameter description, see [Graph Service Configuration](../../5.configurations-and-logs/1.configurations/3.graph-config.md). - - `--dst_db_path`: Specifies the absolute path of the **NEW** Storage data directories. Separate multiple paths with commas, without spaces. The paths must correspond to the paths set in `--src_db_path` one by one. +4. Start all Meta services. - - `--upgrade_meta_server`: Specifies the addresses of the new Meta servers that you started in step 6. + ``` + /scripts/nebula-metad.service start + ``` - - `--upgrade_version`: If the old Nebula Graph version is v1.2.0, set the parameter value to `1`. If the old version is v2.0.0-RC1, set the value to `2`. Do not set the value to other numbers. + Once started, the Meta services take several seconds to elect a leader. - !!! danger + To verify that Meta services are all started, you can start any Graph server, connect to it through Nebula Console, and run [`SHOW HOSTS meta`](../../3.ngql-guide/7.general-query-statements/6.show/6.show-hosts.md) and [`SHOW META LEADER`](../../3.ngql-guide/7.general-query-statements/6.show/19.show-meta-leader.md). If the status of Meta services are correctly returned, the services are successfully started. - Do not mix up the order of `--src_db_path` and `--dst_db_path`. Otherwise, the old data will be damaged during the upgrade. + !!! note + If the operation fails, stop the upgrade and ask for help on [the forum](https://discuss.nebula-graph.com.cn/) or [GitHub](https://github.com/vesoft-inc/nebula/issues). - For example, upgrade from v1.2.x: +5. Use the new db_upgrader file in the `bin` directory to upgrade the format of old data. - ``` - # /usr/local/nebula_new/bin/db_upgrader \ - --src_db_path=/usr/local/nebula/data/storage/data1/,/usr/local/nebula/data/storage/data2/ \ - --dst_db_path=/usr/local/nebula_new/data/storage/data1/,/usr/local/nebula_new/data/storage/data2/\ - --upgrade_meta_server=192.168.*.14:45500,192.168.*.15:45500,192.168.*.16:45500 \ - --upgrade_version=1 - ``` + !!! caution + This step backs up the Storage data. But to prevent backup failures and data loss, before executing this step, make sure that you have followed the **Preparations before the upgrade** section and backed up the Meta data and Storage data. - For example, upgrade from v2.0.0-RC1: + Command syntax: - ``` - # /usr/local/nebula_new/bin/db_upgrader \ - --src_db_path=/usr/local/nebula/data/storage/ \ - --dst_db_path=/usr/local/nebula_new/data/storage/ \ - --upgrade_meta_server=192.168.*.14:9559,192.168.*.15:9559,192.168.*.16:9559 \ - --upgrade_version=2 - ``` + ``` + /bin/db_upgrader \ + --src_db_path= \ + --dst_db_path= \ + --upgrade_meta_server=:[, : ...] \ + --upgrade_version=2:3 + ``` - !!! Note - - - If anything goes wrong, **Stop upgrading, stop all the Meta servers, and start the Nebula Graph services from the old directories.** - - Make sure that all the Storage servers have finished the upgrade. + - `old_storage_data_path` indicates the path of the Storage data. It is defined by the `data_path` parameter in the Storage configuration files. + - `data_backup_path` indicates a custom path for data backup. + - `meta_server_ip` and `port` indicate the IP address and port number of a Meta server. + - `2:3` indicates that the upgrade is from version 2.x to 3.x. -8. Start the new Storage Service on each Storage server. + Example for the test in this topic: - ``` - # ${nebula-new}/scripts/nebula.service start storaged - # ${nebula-new}/scripts/nebula.service status storaged - ``` + ``` + /bin/db_upgrader \ + --src_db_path=/usr/local/nebula/data/storage \ + --dst_db_path=/home/vesoft/nebula/data-backup \ + --upgrade_meta_server=192.168.8.132:9559 \ + --upgrade_version=2:3 + ``` !!! note - If this step goes wrong on any server, Take the logs in `${nebula-new}/logs/` to the [Nebula Graph community](https://discuss.nebula-graph.io/) for help. **Stop upgrading. Stop all the Meta servers and Storage servers. Start the Nebula Graph services from the old directories.** - -9. Start the new Graph Service on each Graph server. + If the operation fails, stop the upgrade and ask for help on [the forum](https://discuss.nebula-graph.com.cn/) or [GitHub](https://github.com/vesoft-inc/nebula/issues). - ``` - # ${nebula-new}/scripts/nebula.service start graphd - # ${nebula-new}/scripts/nebula.service status graphd - ``` +6. Start all the Graph and Storage services. !!! note + If the operation fails, stop the upgrade and ask for help on [the forum](https://discuss.nebula-graph.com.cn/) or [GitHub](https://github.com/vesoft-inc/nebula/issues). - If this step goes wrong on any server, take the logs in `${nebula-new}/logs/` to the [Nebula Graph community](https://discuss.nebula-graph.io/) for help. **Stop upgrading. Stop all the Meta servers, Storage servers, and Graph servers. Start the Nebula Graph services from the old directories.** - -10. Connect to Nebula Graph with the new versions of [Nebula Console](https://github.com/vesoft-inc/nebula-console). Verify if the Nebula Graph services are available and if the data can be accessed normally. Make sure that the command parameters, including the IP address and port of the Graph Service, are the same as the old one. - - ```ngql - nebula> SHOW HOSTS; - nebula> SHOW SPACES; - nebula> USE - nebula> SHOW PARTS; - nebula> SUBMIT JOB STATS; - nebula> SHOW STATS; - ``` +7. Connect to the new version of Nebula Graph to verify that services are available and data are complete. For how to connect, see [Connect to Nebula Graph](../connect-to-nebula-graph.md). - !!! Note + Currently, there is no official way to check whether the upgrade is successful. You can run the following reference statements to test the upgrade: - The old releases of Nebula Console may have compatibility issues. + ```ngql + nebula> SHOW HOSTS; + nebula> SHOW HOSTS storage; + nebula> SHOW SPACES; + nebula> USE + nebula> SHOW PARTS; + nebula> SUBMIT JOB STATS; + nebula> SHOW STATS; + nebula> MATCH (v) RETURN v LIMIT 5; + ``` -11. Upgrade other Nebula Graph clients. - - You must upgrade all other clients to corresponding Nebula Graph v{{nebula.release}}. The clients include but are not limited to [Python](https://github.com/vesoft-inc/nebula-python), [Java](https://github.com/vesoft-inc/nebula-java), [go](https://github.com/vesoft-inc/nebula-go), [C++](https://github.com/vesoft-inc/nebula-cpp), [Flink-connector](https://github.com/vesoft-inc/nebula-flink-connector), [Algorithm](https://github.com/vesoft-inc/nebula-algorithm), [Exchange](https://github.com/vesoft-inc/nebula-exchange), [Spark-connector](https://github.com/vesoft-inc/nebula-spark-connector), and [Nebula Bench](https://github.com/vesoft-inc/nebula-bench). Find the v{{nebula.release}} branch for each client. - - !!! Note - - Communication protocols of v{{nebula.release}} are not compatible with that of the old releases. To upgrade the clients, compile the v{{nebula.release}} source code of the clients or download corresponding binaries. - - Tip for maintenance: The data path after the upgrade is `${nebula-new}/`. Modify relative paths for hard disk monitor systems, log, or ELK, etc. + You can also test against [new features]((../../20.appendix/releasenote.md)) in version {{nebula.release}}. ## Upgrade failure and rollback -If the upgrade fails, stop all Nebula Graph services of the new version, and start the services of the old version. - -All Nebula Graph clients in use must be switched to the **old version**. +If the upgrade fails, stop all Nebula Graph services of the new version, recover the old configuration files and binaries, and start the services of the old version. -## Appendix 1: Test Environment - -The test environment for this topic is as follows: - -* Machine specifications: 32 CPU cores, 62 GB memory, and SSD. - -* Data size: 100 GB of Nebula Graph 1.2.0 LDBC test data, with 1 graph space, 24 partitions, and 92 GB of data directory size. - -* Concurrent configuration: `--max_concurrent=5`, `--max_concurrent_parts=24`, and `--write_batch_num=100`. - -The upgrade cost **21 minutes** in all, including 13 minutes of compaction. The descriptions are as follows. - -|Parameter|Default value| -|:---|:---| -|`--max_concurrent`|5| -|`--max_concurrent_parts`|10| -|`--write_batch_num`|100| - -## Appendix 2: Nebula Graph V2.0.0 code address and commit ID - -| Code address | Commit ID | -|:---|:---| -| [graphd](https://github.com/vesoft-inc/nebula-graph/releases/tag/v2.0.0) | 91639db | -| [storaged and metad](https://github.com/vesoft-inc/nebula-storage/tree/v2.0.0) | 761f22b | -| [common](https://github.com/vesoft-inc/nebula-common/tree/v2.0.0) | b2512aa | +All Nebula Graph clients in use must be switched to the old version. ## FAQ ### Can I write through the client during the upgrade? -A: No. The state of the data written during this process is undefined. - -### Can I upgrade other old versions except for v1.2.x and v2.0.0-RC to v{{nebula.release}}? - -A: Upgrading from other old versions is not tested. Theoretically, versions between v1.0.0 and v1.2.0 could adopt the upgrade approach for v1.2.x. v2.0.0-RC nightly versions cannot apply the solutions in this topic. +A: No. You must stop all Nebula Graph services during the upgrade. ### How to upgrade if a machine has only the Graph Service, but not the Storage Service? -A: Upgrade the Graph Service with the corresponding binary or rpm package. +A: You only need to update the configuration files and binaries of the Graph Service. ### How to resolve the error `Permission denied`? @@ -330,12 +187,24 @@ A: Try again with the sudo privileges. ### Is there any change in gflags? -A: Yes. For more information, see [github issues](https://github.com/vesoft-inc/nebula/issues/2501). +A: Yes. For more information, see the release notes and configuration docs. -### What are the differences between deleting data then installing the new version and upgrading according to this topic? +### Is there a tool or solution for verifying data consistency after the upgrade? -A: The default configurations for v2.x and v1.x are different, including the ports used. The upgrade solution keeps the old configurations, and the delete-and-install solution uses the new configurations. +A: No. But if you only want to check the number of vertices and edges, run `SUBMIT JOB STATS` and `SHOW STATS` after the upgrade, and compare the result with the result that you recorded before the upgrade. -### Is there a tool or solution for verifying data consistency after the upgrade? +### How to solve the issue that Storage is `OFFLINE` and `Leader count` is `0`? + +A: Run the following statement to add the Storage hosts into the cluster manually. + +```ngql +ADD HOSTS :[, : ...]; +``` + +For example: + +```ngql +ADD HOSTS 192.168.10.100:9779, 192.168.10.101:9779, 192.168.10.102:9779; +``` -A: No. +If the issue persists, ask for help on [the forum](https://discuss.nebula-graph.com.cn/) or [GitHub](https://github.com/vesoft-inc/nebula/issues). diff --git a/mkdocs.yml b/mkdocs.yml index e0fe9e6e7ca..3eb158e6300 100755 --- a/mkdocs.yml +++ b/mkdocs.yml @@ -309,8 +309,8 @@ nav: - Connect to Service: 4.deployment-and-installation/connect-to-nebula-graph.md # - Manage zone: 4.deployment-and-installation/5.zone.md - Upgrade: - - Upgrade Nebula Graph to the current version: 4.deployment-and-installation/3.upgrade-nebula-graph/upgrade-nebula-graph-to-latest.md - - Upgrade Nebula Graph from v2.0.x to the current version: 4.deployment-and-installation/3.upgrade-nebula-graph/upgrade-nebula-from-200-to-latest.md + - Upgrade Nebula Graph to the latest version: 4.deployment-and-installation/3.upgrade-nebula-graph/upgrade-nebula-graph-to-latest.md +# - Upgrade Nebula Graph from v2.0.x to the current version: 4.deployment-and-installation/3.upgrade-nebula-graph/upgrade-nebula-from-200-to-latest.md - Uninstall Nebula Graph: 4.deployment-and-installation/4.uninstall-nebula-graph.md - Configurations and logs: @@ -549,6 +549,8 @@ plugins: - spark-connector/* - nebula-operator/* - 4.deployment-and-installation/5.zone.md + - 4.deployment-and-installation/3.upgrade-nebula-graph/upgrade-nebula-from-200-to-latest.md + # Exclude the file with the following file name. # - abc.md # Exclude files with regular expressions (regexes)