From 0dcc82f1af774cee5ecf16c33416311fb47578ea Mon Sep 17 00:00:00 2001 From: Abby <78209557+abby-cyber@users.noreply.github.com> Date: Fri, 27 May 2022 15:57:13 +0800 Subject: [PATCH] display error fix --- docs-2.0/nebula-explorer/12.query-visually.md | 10 +++++----- .../8.3.balance-data-when-scaling-storage.md | 2 +- 2 files changed, 6 insertions(+), 6 deletions(-) diff --git a/docs-2.0/nebula-explorer/12.query-visually.md b/docs-2.0/nebula-explorer/12.query-visually.md index 064b8823d73..ddc0713cb12 100644 --- a/docs-2.0/nebula-explorer/12.query-visually.md +++ b/docs-2.0/nebula-explorer/12.query-visually.md @@ -54,9 +54,9 @@ On the page, the descriptions of other icons are as follows. One vertex can have zero or multiple tags: - - When 0 tag is set, query the vertex without tags. - - When 1 tag is set, query the vertex with that tag. - - When multiple tags are set, query the vertex that has all the tags you set. + - When 0 tag is set, query the vertex without tags. + - When 1 tag is set, query the vertex with that tag. + - When multiple tags are set, query the vertex that has all the tags you set. - **Filter**: Add one or more sets of filter conditions, including vertex properties, operators, and property values. @@ -74,9 +74,9 @@ On the page, the descriptions of other icons are as follows. One edge have one and only one edge type: - - When one edge type is set, query the edge with that edge type. + - When one edge type is set, query the edge with that edge type. - - When multiple edge types are set, query the edge that has any of the edge types you set. + - When multiple edge types are set, query the edge that has any of the edge types you set. - **Direction**: Set the edge direction between two vertices, including Outgoing, Incoming, and Bidirect. diff --git a/docs-2.0/nebula-operator/8.custom-cluster-configurations/8.3.balance-data-when-scaling-storage.md b/docs-2.0/nebula-operator/8.custom-cluster-configurations/8.3.balance-data-when-scaling-storage.md index 5db5e886eb2..326d0d2cb27 100644 --- a/docs-2.0/nebula-operator/8.custom-cluster-configurations/8.3.balance-data-when-scaling-storage.md +++ b/docs-2.0/nebula-operator/8.custom-cluster-configurations/8.3.balance-data-when-scaling-storage.md @@ -6,7 +6,7 @@ After the Storage service is scaled out, you can decide whether to balance the data in the Storage service. -The scaling out of the Nebula Graph's Storage service is divided into two stages. In the first stage, the status of all pods is changed to `Ready`. In the second stage, the commands of `BALANCE DATA`和`BALANCE LEADER` are executed to balance data. These two stages decouple the scaling out process of the controller replica from the balancing data process, so that you can choose to perform the data balancing operation during low traffic period. The decoupling of the scaling out process from the balancing process can effectively reduce the impact on online services during data migration. +The scaling out of the Nebula Graph's Storage service is divided into two stages. In the first stage, the status of all pods is changed to `Ready`. In the second stage, the commands of `BALANCE DATA` and `BALANCE LEADER` are executed to balance data. These two stages decouple the scaling out process of the controller replica from the balancing data process, so that you can choose to perform the data balancing operation during low traffic period. The decoupling of the scaling out process from the balancing process can effectively reduce the impact on online services during data migration. You can define whether to balance data automatically or not with the parameter `enableAutoBalance` in the configuration file of the CR instance of the cluster you created.