From 7a94c7db8aee2841467a09b8dd6bab18449f8d65 Mon Sep 17 00:00:00 2001 From: Abby <78209557+abby-cyber@users.noreply.github.com> Date: Thu, 31 Mar 2022 12:07:41 +0800 Subject: [PATCH] note for storaged port showing red --- docs-2.0/20.appendix/0.FAQ.md | 2 +- docs-2.0/reuse/source_manage-service.md | 4 ++++ 2 files changed, 5 insertions(+), 1 deletion(-) diff --git a/docs-2.0/20.appendix/0.FAQ.md b/docs-2.0/20.appendix/0.FAQ.md index a2fd7a7c3be..80b4f302533 100644 --- a/docs-2.0/20.appendix/0.FAQ.md +++ b/docs-2.0/20.appendix/0.FAQ.md @@ -187,7 +187,7 @@ Got 1 rows (time spent 1235/1934 us) - The second number `1934` shows the time spent from the client's perspective, that is, the time it takes for the client from sending a request, receiving a response, and displaying the result on the screen. -### Why does the port number of the `nebula-storaged` process keep showing red after connecting Nebula Graph? +### Why does the port number of the `nebula-storaged` process keep showing red after connecting to Nebula Graph? Because the `nebula-storaged` process waits for `nebula-metad` to add the current Storage service during the startup process. The Storage works after it receives the ready signal. Starting from Nebula Graph 3.0.0, the Meta service cannot directly read or write data in the Storage service that you add in the configuration file. The configuration file only registers the Storage service to the Meta service. You must run the `ADD HOSTS` command to enable the Meta to read and write data in the Storage service. For more information, see [Manage Storage hosts](../4.deployment-and-installation/manage-storage-host.md). diff --git a/docs-2.0/reuse/source_manage-service.md b/docs-2.0/reuse/source_manage-service.md index a98c9e8609d..d32dbcc0649 100644 --- a/docs-2.0/reuse/source_manage-service.md +++ b/docs-2.0/reuse/source_manage-service.md @@ -129,6 +129,10 @@ $ sudo /usr/local/nebula/scripts/nebula.service status all [INFO] nebula-storaged(02b2091): Running as 26709, Listening on 9779 ``` + !!! note + + After starting Nebula Graph, the port of the `nebula-storaged` process is shown in red. Because the `nebula-storaged` process waits for the `nebula-metad` to add the current Storage service during the startup process. The Storage works after it receives the ready signal. Starting from Nebula Graph 3.0.0, the Meta service cannot directly read or write data in the Storage service that you add in the configuration file. The configuration file only registers the Storage service to the Meta service. You must run the `ADD HOSTS` command to enable the Meta to read and write data in the Storage service. For more information, see [Manage Storage hosts](../4.deployment-and-installation/manage-storage-host.md). + * If the returned result is similar to the following one, there is a problem. You may also go to the [Nebula Graph community](https://discuss.nebula-graph.io/) for help. ```bash