Mac环境Java客户端StorageClient连不上服务端

问答 问题
1
  • nebula 版本：v2.5.0
  • 部署方式 ：Docker
    -Java环境：java8
    -电脑：Macbook

Docker部署的nebula，console正常，GraphClient连接正常，Storage连接报错。

 public static void main(String[] args) {
        // input params are the metad's ip and port
        StorageClient client = new StorageClient("172.17.44.67", 9559);
        try {
            client.connect();//报错
        } catch (Exception e) {
            LOGGER.error("storage client connect error, ", e);
            client.close();
            System.exit(1);
        }
        scanVertex(client);
        scanEdge(client);

        client.close();
    }

报错日志

ERROR [main] - storage client connect error, 
com.facebook.thrift.transport.TTransportException: java.net.ConnectException: Connection refused (Connection refused)
	at com.facebook.thrift.transport.TSocket.open(TSocket.java:175)
	at com.vesoft.nebula.client.storage.GraphStorageConnection.open(GraphStorageConnection.java:40)
	at com.vesoft.nebula.client.storage.StorageClient.connect(StorageClient.java:79)
	at nebula.StorageClientExample.main(StorageClientExample.java:32)
Caused by: java.net.ConnectException: Connection refused (Connection refused)
	at java.net.PlainSocketImpl.socketConnect(Native Method)
	at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
	at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
	at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
	at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
	at java.net.Socket.connect(Socket.java:589)
	at com.facebook.thrift.transport.TSocket.open(TSocket.java:170)
	... 3 more

Process finished with exit code 1

docker 容器ps

CONTAINER ID   IMAGE                           COMMAND                  CREATED      STATUS                PORTS                                                                                                  NAMES
9de378216149   vesoft/nebula-graphd:v2.5.0     "/usr/local/nebula/b…"   4 days ago   Up 4 days (healthy)   0.0.0.0:56879->9669/tcp, 0.0.0.0:56877->19669/tcp, 0.0.0.0:56878->19670/tcp                            nebula-docker-compose_graphd2_1
cc48d28257e3   vesoft/nebula-graphd:v2.5.0     "/usr/local/nebula/b…"   4 days ago   Up 4 days (healthy)   0.0.0.0:9669->9669/tcp, :::9669->9669/tcp, 0.0.0.0:56880->19669/tcp, 0.0.0.0:56881->19670/tcp          nebula-docker-compose_graphd_1
e018b5672dd0   vesoft/nebula-graphd:v2.5.0     "/usr/local/nebula/b…"   4 days ago   Up 4 days (healthy)   0.0.0.0:56884->9669/tcp, 0.0.0.0:56882->19669/tcp, 0.0.0.0:56883->19670/tcp                            nebula-docker-compose_graphd1_1
4450db20822d   vesoft/nebula-storaged:v2.5.0   "/usr/local/nebula/b…"   4 days ago   Up 4 days (healthy)   9777-9778/tcp, 9780/tcp, 0.0.0.0:56871->9779/tcp, 0.0.0.0:56872->19779/tcp, 0.0.0.0:56873->19780/tcp   nebula-docker-compose_storaged0_1
f802b93b8ab3   vesoft/nebula-storaged:v2.5.0   "/usr/local/nebula/b…"   4 days ago   Up 4 days (healthy)   9777-9778/tcp, 9780/tcp, 0.0.0.0:56876->9779/tcp, 0.0.0.0:56874->19779/tcp, 0.0.0.0:56875->19780/tcp   nebula-docker-compose_storaged1_1
42ac2739a7c5   vesoft/nebula-storaged:v2.5.0   "/usr/local/nebula/b…"   4 days ago   Up 4 days (healthy)   9777-9778/tcp, 9780/tcp, 0.0.0.0:56869->9779/tcp, 0.0.0.0:56870->19779/tcp, 0.0.0.0:56868->19780/tcp   nebula-docker-compose_storaged2_1
8606e27b8fc2   vesoft/nebula-metad:v2.5.0      "/usr/local/nebula/b…"   4 days ago   Up 4 days (healthy)   9560/tcp, 0.0.0.0:56865->9559/tcp, 0.0.0.0:56866->19559/tcp, 0.0.0.0:56867->19560/tcp                  nebula-docker-compose_metad2_1
e3eb7bf6b176   vesoft/nebula-metad:v2.5.0      "/usr/local/nebula/b…"   4 days ago   Up 4 days (healthy)   9560/tcp, 0.0.0.0:56864->9559/tcp, 0.0.0.0:56862->19559/tcp, 0.0.0.0:56863->19560/tcp                  nebula-docker-compose_metad1_1
17545d9feb2c   vesoft/nebula-metad:v2.5.0      "/usr/local/nebula/b…"   4 days ago   Up 4 days (healthy)   9560/tcp, 0.0.0.0:56860->9559/tcp, 0.0.0.0:56861->19559/tcp, 0.0.0.0:56859->19560/tcp                  nebula-docker-compose_metad0_1
1791f6157ad6   nginx:alpine                    "/docker-entrypoint.…"   5 days ago   Up 5 days             80/tcp, 0.0.0.0:7001->7001/tcp, :::7001->7001/tcp                                                      nebula-graph-studio-v3_nginx_1
a9834fe4bbe7   vesoft/nebula-graph-studio:v3   "docker-entrypoint.s…"   5 days ago   Up 5 days             0.0.0.0:64193->7001/tcp                                                                                nebula-graph-studio-v3_web_1
e30885a3d2c2   vesoft/nebula-http-gateway:v2   "./nebula-http-gatew…"   5 days ago   Up 5 days             0.0.0.0:64192->8080/tcp                                                                                nebula-graph-studio-v3_client_1
89435eb3ac07   vesoft/nebula-importer:v2       "nebula-importer --p…"   5 days ago   Up 5 days             0.0.0.0:64191->5699/tcp                                                                                nebula-graph-studio-v3_importer_1

请问需要配置什么东西吗？我telnet试了一下，9559连不上，9669、7001啥的正常。
此外，请问StorageClient和GraphClient主要区别是什么啊

2

连接不上的话。就是跨容器访问的问题，你可以试试下面回复的方法（和下面的帖子是一个问题），然后更新下进度

3

Nebula 分为 graphd、metad 和 storaged 三个服务，可以具体看下这个文档 https://docs.nebula-graph.com.cn/2.5.1/1.introduction/3.nebula-graph-architecture/1.architecture-overview/ 了解下三个服务各自是干嘛的

4

请问一下，scanVertex和scanEdge一般可以用来干嘛啊？返回结果的话感觉GraphClient也能做到啊。是返回结果效率更高吗？

5

:thinking: 我的理解是，去捞数据，graph 是去计算，但是原材料是由 storage 那边供给的

6

此话题已在最后回复的 7 天后被自动关闭。不再允许新回复。