2

There are some details:

  • nebula version is 3.5.0.
  • Deployment method is stand-alone.
  • Installation method is RPM.
  • CPU and memory information are 16c and 32g

The operation is that the backup command is executed./br restore full --meta "127.0.0.1:9559" --storage "local:///root/database/nebula-graph/backup/" --name BACKUP_2023_06_20_11_06_43; After successful the execution, SHOW HOSTS displays node status is "OFFLINE"

The log is as follows:

+----------------------------+---------------------+-----------------------------+-------------+------------+
[root@bogon nebula-graph]# ./br restore full --meta "127.0.0.1:9559" --storage "local:///root/database/nebula-graph/backup/" --name BACKUP_2023_06_20_11_06_43
{"level":"info","meta address":"127.0.0.1:9559","msg":"Try to connect meta service.","time":"2023-06-20T11:18:05.086Z"}
{"level":"info","meta address":"127.0.0.1:9559","msg":"Connect meta server successfully.","time":"2023-06-20T11:18:05.087Z"}
{"level":"info","meta address":"127.0.0.1:9559","msg":"Try to connect meta service.","time":"2023-06-20T11:18:05.087Z"}
{"level":"info","meta address":"127.0.0.1:9559","msg":"Connect meta server successfully.","time":"2023-06-20T11:18:05.088Z"}
{"host info":"map[127.0.0.1:127.0.0.1:9779[STORAGE]: (data: /root/database/nebula-graph/3.5.0/data/storage, root: /root/database/nebula-graph/3.5.0) | 127.0.0.1:8888[AGENT]: (data: , root: ) | 127.0.0.1:9669[GRAPH]: (data: , root: /root/database/nebula-graph/3.5.0) | 127.0.0.1:9559[META]: (data: /root/database/nebula-graph/3.5.0/data/meta, root: /root/database/nebula-graph/3.5.0)]","level":"info","msg":"Get cluster topology from the nebula.","time":"2023-06-20T11:18:05.088Z"}
{"backup":"BACKUP_2023_06_20_11_06_43","level":"info","msg":"Check backup dir successfully.","time":"2023-06-20T11:18:05.088Z","uri":"local:///root/database/nebula-graph/backup/BACKUP_2023_06_20_11_06_43"}
{"dir":"/root/database/nebula-graph/3.5.0","host":"127.0.0.1","level":"info","msg":"Stop services.","role":"STORAGE","time":"2023-06-20T11:18:05.089Z"}
{"dir":"/root/database/nebula-graph/3.5.0","host":"127.0.0.1","level":"info","msg":"Stop services.","role":"GRAPH","time":"2023-06-20T11:18:05.119Z"}
{"dir":"/root/database/nebula-graph/3.5.0","host":"127.0.0.1","level":"info","msg":"Stop services.","role":"META","time":"2023-06-20T11:18:05.137Z"}
{"backup":"BACKUP_2023_06_20_11_06_43","level":"info","msg":"Stop cluster successfully.","time":"2023-06-20T11:18:05.159Z"}
{"addr":"127.0.0.1:9779","backup path":"/root/database/nebula-graph/3.5.0/data/storage/nebula_old_1687231085","level":"info","msg":"Backup origin storage data path successfully.","origin path":"/root/database/nebula-graph/3.5.0/data/storage/nebula","time":"2023-06-20T11:18:05.159Z"}
{"addr":"127.0.0.1:9559","backup path":"/root/database/nebula-graph/3.5.0/data/meta/nebula_old_1687231085","level":"info","msg":"Backup origin meta data path successfully.","origin path":"/root/database/nebula-graph/3.5.0/data/meta/nebula","time":"2023-06-20T11:18:05.159Z"}
{"backup":"BACKUP_2023_06_20_11_06_43","level":"info","msg":"Backup origin cluster data successfully.","time":"2023-06-20T11:18:05.159Z"}
{"level":"info","msg":"Download meta data to cluster successfully.","time":"2023-06-20T11:18:05.169Z"}
{"addr":"127.0.0.1:9779","external":"local:///root/database/nebula-graph/backup/BACKUP_2023_06_20_11_06_43/data/127.0.0.1:9779/data0/","level":"info","local":"/root/database/nebula-graph/3.5.0/data/storage/nebula","msg":"Download storage data successfully.","time":"2023-06-20T11:18:16.990Z"}
{"level":"info","msg":"Download storage data to cluster successfully.","time":"2023-06-20T11:18:16.990Z"}
{"addr":"127.0.0.1:9559","level":"info","msg":"Start meta service successfully.","time":"2023-06-20T11:18:17.027Z"}
{"level":"info","msg":"Start meta service successfully.","time":"2023-06-20T11:18:20.029Z"}
{"level":"info","meta address":"127.0.0.1:9559","msg":"Try to connect meta service.","time":"2023-06-20T11:18:20.030Z"}
{"level":"info","meta address":"127.0.0.1:9559","msg":"Connect meta server successfully.","time":"2023-06-20T11:18:20.031Z"}
{"addr":"127.0.0.1:9559","level":"info","msg":"Restore backup in this metad successfully.","time":"2023-06-20T11:18:21.582Z"}
{"level":"info","msg":"Restore meta service successfully.","time":"2023-06-20T11:18:21.582Z"}
{"addr":"127.0.0.1:9779","level":"info","msg":"Start storaged by agent successfully.","time":"2023-06-20T11:18:21.613Z"}
{"addr":"127.0.0.1:9669","level":"info","msg":"Start graphd by agent successfully.","time":"2023-06-20T11:18:21.642Z"}
{"level":"info","msg":"Start storage and graph services successfully.","time":"2023-06-20T11:18:21.642Z"}
{"addr":"127.0.0.1:9559","level":"info","msg":"Remove meta origin data successfully.","path":"/root/database/nebula-graph/3.5.0/data/meta/nebula_old_1687231085","time":"2023-06-20T11:18:21.643Z"}
{"addr":"127.0.0.1:9779","level":"info","msg":"Remove storage origin data successfully.","path":"/root/database/nebula-graph/3.5.0/data/storage/nebula_old_1687231085","time":"2023-06-20T11:18:21.676Z"}
{"level":"info","msg":"Cleanup origin data successfully.","time":"2023-06-20T11:18:21.677Z"}
**Restore succeed.**
[root@bogon nebula-graph]# ./nebula-console  -addr  127.0.0.1  -port  9669 -u root  -p  er

Welcome to Nebula Graph!

(root@nebula) [(none)]> SHOW HOSTS;
+-------------+------+-----------+--------------+----------------------+------------------------+---------+
| Host        | Port | Status    | Leader count | Leader distribution  | Partition distribution | Version |
+-------------+------+-----------+--------------+----------------------+------------------------+---------+
| "127.0.0.1" | 9779 | "OFFLINE" | 0            | "No valid partition" | "basketballplayer:15"  |         |
+-------------+------+-----------+--------------+----------------------+------------------------+---------+
Got 1 rows (time spent 965µs/1.498815ms)

Tue, 20 Jun 2023 11:20:30 CST

(root@nebula) [(none)]>

Then I restart all services, query again, but the display is alsoADD HOSTS

[root@bogon ~]# sudo /root/database/nebula-graph/3.5.0/scripts/nebula.service status   all
[WARN] The maximum files allowed to open might be too few: 1024
[INFO] nebula-metad(18fd7b1): Running as 1687, Listening on 9559
[INFO] nebula-graphd(18fd7b1): Running as 1878, Listening on 9669
[WARN] nebula-storaged after v3.0.0 will not start service until it is added to cluster.
[WARN] See Manage Storage hosts:ADD HOSTS in https://docs.nebula-graph.io/
[INFO] nebula-storaged(18fd7b1): Running as 1819, Listening on 9779
[root@bogon ~]# sudo /root/database/nebula-graph/3.5.0/scripts/nebula.service restart    all
[WARN] The maximum files allowed to open might be too few: 1024
[INFO] Stopping nebula-metad...
[INFO] Done
[INFO] Starting nebula-metad...
[INFO] Done
[INFO] Stopping nebula-graphd...
[INFO] Done
[INFO] Starting nebula-graphd...
[INFO] Done
[INFO] Stopping nebula-storaged...
[INFO] Done
[INFO] Starting nebula-storaged...
[INFO] Done
[root@bogon ~]# sudo /root/database/nebula-graph/3.5.0/scripts/nebula.service status   all
[WARN] The maximum files allowed to open might be too few: 1024
[INFO] nebula-metad(18fd7b1): Running as 2080, Listening on 9559
[INFO] nebula-graphd(18fd7b1): Running as 2190, Listening on 9669
[WARN] nebula-storaged after v3.0.0 will not start service until it is added to cluster.
[WARN] See Manage Storage hosts:ADD HOSTS in https://docs.nebula-graph.io/
[INFO] nebula-storaged(18fd7b1): Running as 2328, Listening on 9779

0 Answers0