Replies: 6 comments 6 replies
-
i have the same issue, Is this problem solved? |
Beta Was this translation helpful? Give feedback.
-
NO,I give up.
…---Original---
From: ***@***.***>
Date: Mon, Nov 14, 2022 23:43 PM
To: ***@***.***>;
Cc: ***@***.******@***.***>;
Subject: Re: [alibaba/GraphScope] Coordinator pod start successful but can'tconnecting to service ... (Discussion #1707)
i have the same issue, Is this problem solved?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
/cc @lidongze0629 |
Beta Was this translation helpful? Give feedback.
-
any luck ? |
Beta Was this translation helpful? Give feedback.
-
@rahulvramesh It works fine with 0.23.0 GraphScope on the Aliyun ACK cluster. If you have any problems, could you please give more error messages here? We will take a look asap. Thanks! Here is my test code: In [28]: import graphscope
In [29]: graphscope.__version__
Out[29]: '0.23.0'
In [30]: graphscope.set_option(show_log=True)
In [31]: sess = graphscope.session(cluster_type="k8s")
2023-07-20 17:57:52,969 [INFO][cluster:545]: Coordinator pod start successful with address 192.168.0.174:31243, connecting to service ...
2023-07-20 17:57:52,974 [INFO][rpc:69]: GraphScope coordinator service connected. |
Beta Was this translation helpful? Give feedback.
-
@rahulvramesh Thanks very much, there's something wrong happened to get the gremlin |
Beta Was this translation helpful? Give feedback.
-
when I create session, I miss the error
sess = gs.session()
2022-06-11 11:16:02,303 [INFO][cluster:303]: Launching coordinator...
2022-06-11 11:16:05,349 [INFO][utils:182]: coordinator-qrgbuf-849984d654-rndlr: Successfully assigned gs-eonbnu/coordinator -qrgbuf-849984d654-rndlr to ubuntu8
2022-06-11 11:16:05,350 [INFO][utils:182]: coordinator-qrgbuf-849984d654-rndlr: Container image "registry.cn-hongkong.aliyu ncs.com/graphscope/graphscope:0.13.0" already present on machine
2022-06-11 11:16:05,350 [INFO][utils:182]: coordinator-qrgbuf-849984d654-rndlr: Created container coordinator
2022-06-11 11:16:05,350 [INFO][utils:182]: coordinator-qrgbuf-849984d654-rndlr: Started container coordinator
2022-06-11 11:17:04,267 [INFO][cluster:695]: Launching etcd ...
2022-06-11 11:17:05,308 [INFO][cluster:906]: Etcd created, endpoint is 10.104.223.35:58576
2022-06-11 11:17:05,309 [INFO][cluster:927]: Creating interactive engine service...
2022-06-11 11:17:05,309 [INFO][cluster:855]: Launching zetcd proxy service ...
2022-06-11 11:17:05,309 [INFO][cluster:867]: zetcd cmd /home/graphscope/.local/lib/python3.8/site-packages/graphscope.runti me/bin/zetcd --zkaddr 0.0.0.0:2181 --endpoints http://gs-etcd-service-qrgbuf:58576,http://gs-etcd-qrgbuf-0:58576
Running zetcd proxy
Version: Version not provided (use make instead of go build)
SHA: SHA not provided (use make instead of go build)
2022-06-11 11:17:06,318 [INFO][cluster:896]: ZEtcd is ready, endpoint is 10.244.3.34:2181
2022-06-11 11:17:06,318 [INFO][cluster:934]: Creating engine replicaset...
2022-06-11 11:17:06,318 [INFO][cluster:534]: Launching GraphScope engines pod ...
2022-06-11 11:17:06,611 [INFO][cluster:987]: [gs-engine-qrgbuf-6jzgc]: Successfully assigned gs-eonbnu/gs-engine-qrgbuf-6jz gc to ubuntu21
2022-06-11 11:17:07,550 [INFO][cluster:987]: [gs-engine-qrgbuf-6jzgc]: Container image "registry.cn-hongkong.aliyuncs.com/g raphscope/graphscope:0.13.0" already present on machine
2022-06-11 11:17:07,616 [INFO][cluster:987]: [gs-engine-qrgbuf-qqfgs]: Successfully assigned gs-eonbnu/gs-engine-qrgbuf-qqf gs to ubuntu21
2022-06-11 11:17:07,888 [INFO][cluster:987]: [gs-engine-qrgbuf-qqfgs]: Container image "registry.cn-hongkong.aliyuncs.com/g raphscope/graphscope:0.13.0" already present on machine
2022-06-11 11:17:08,014 [INFO][cluster:987]: [gs-engine-qrgbuf-qqfgs]: Created container engine
2022-06-11 11:17:08,253 [INFO][cluster:987]: [gs-engine-qrgbuf-qqfgs]: Started container engine
2022-06-11 11:17:08,349 [INFO][cluster:987]: [gs-engine-qrgbuf-qqfgs]: Created container vineyard
2022-06-11 11:17:08,560 [INFO][cluster:987]: [gs-engine-qrgbuf-qqfgs]: Started container vineyard
2022-06-11 11:17:10,780 [INFO][cluster:987]: [gs-engine-qrgbuf-6jzgc]: Created container engine
2022-06-11 11:17:10,781 [INFO][cluster:987]: [gs-engine-qrgbuf-6jzgc]: Started container engine
2022-06-11 11:17:10,783 [INFO][cluster:987]: [gs-engine-qrgbuf-6jzgc]: Created container vineyard
2022-06-11 11:17:10,784 [INFO][cluster:987]: [gs-engine-qrgbuf-6jzgc]: Started container vineyard
2022-06-11 11:17:19,167 [INFO][cluster:987]: [gs-engine-qrgbuf-6jzgc]: Readiness probe failed:
2022-06-11 11:17:20,172 [INFO][cluster:987]: [gs-engine-qrgbuf-qqfgs]: Readiness probe failed:
2022-06-11 11:16:23,522 [INFO][utils:182]: coordinator-qrgbuf-849984d654-rndlr: Readiness probe failed: dial tcp 10.244.3.3 4:59262: connect: connection refused
2022-06-11 11:17:36,063 [DEBUG][cluster:1019]: vineyard rpc runs on 10.175.123.21:30332
2022-06-11 11:17:36,064 [INFO][cluster:1025]: GraphScope engines pod is ready.
2022-06-11 11:17:36,066 [INFO][cluster:1172]: Engines pod name list: ['gs-engine-qrgbuf-6jzgc', 'gs-engine-qrgbuf-qqfgs']
2022-06-11 11:17:36,066 [INFO][cluster:1173]: Engines pod ip list: ['10.244.4.32', '10.244.4.33']
2022-06-11 11:17:36,066 [INFO][cluster:1174]: Engines pod host ip list: ['10.175.123.21', '10.175.123.21']
2022-06-11 11:17:36,066 [INFO][cluster:1175]: Vineyard service endpoint: 10.175.123.21:30332
2022-06-11 11:17:36,066 [INFO][cluster:1049]: Starting GAE rpc service on 10.244.4.32:56053 ...
2022-06-11 11:17:36,670 [DEBUG][utils:1777]: Resolve mpi cmd prefix: /home/graphscope/.local/lib/python3.8/site-packages/gr aphscope.runtime/openmpi/bin/mpirun --allow-run-as-root -n 2 -host gs-engine-qrgbuf-6jzgc:1.0,gs-engine-qrgbuf-qqfgs:1.0
2022-06-11 11:17:36,670 [DEBUG][utils:1778]: Resolve mpi env: {"OMPI_MCA_btl_vader_single_copy_mechanism": "none", "OMPI_MC A_orte_allowed_exit_without_sync": "1", "OMPI_MCA_odls_base_sigkill_timeout": "0", "OMPI_MCA_plm_rsh_agent": "/home/graphsc ope/.local/lib/python3.8/site-packages/graphscope.runtime/bin/kube_ssh"}
2022-06-11 11:17:36,681 [INFO][cluster:1095]: Analytical engine launching command: /home/graphscope/.local/lib/python3.8/si te-packages/graphscope.runtime/openmpi/bin/mpirun --allow-run-as-root -n 2 -host gs-engine-qrgbuf-6jzgc:1.0,gs-engine-qrgbu f-qqfgs:1.0 /home/graphscope/.local/lib/python3.8/site-packages/graphscope.runtime/bin/grape_engine --host 0.0.0.0 --port 5 6053 --vineyard_shared_mem 4Gi -v 10 --vineyard_socket /tmp/vineyard_workspace/vineyard.sock
2022-06-11 11:17:36,694 [INFO][coordinator:197]: Java initial class path set to: /home/graphscope/.local/lib/python3.8/site -packages/graphscope.runtime/lib/grape-runtime-0.1-shaded.jar
2022-06-11 11:17:36,697 [INFO][coordinator:1587]: Coordinator server listen at 0.0.0.0:59262
10.244.4.32 gs-engine-qrgbuf-6jzgc
10.244.4.33 gs-engine-qrgbuf-qqfgs
I0611 12:09:52.000000 108 /work/analytical_engine/core/grape_instance.cc:59] Workers of grape-engine initialized.
I0611 12:09:52.000000 111 /work/analytical_engine/core/server/analytical_server.cc:36] Analytical server is listening on 0.0.0.0:56053
2022-06-11 11:16:43,728 [INFO][cluster:571]: Coordinator pod start successful with address 10.175.123.8:31337, connecting t o service ...
Traceback (most recent call last):
File "/home/yuenyu/python/venv/lib/python3.9/site-packages/graphscope/client/rpc.py", line 68, in waiting_service_ready
self._stub.HeartBeat(request)
File "/home/yuenyu/python/venv/lib/python3.9/site-packages/grpc/_channel.py", line 946, in call
return _end_unary_response_blocking(state, call, False, None)
File "/home/yuenyu/python/venv/lib/python3.9/site-packages/grpc/_channel.py", line 849, in _end_unary_response_blocking
raise _InactiveRpcError(state)
grpc._channel._InactiveRpcError: <_InactiveRpcError of RPC that terminated with:
status = StatusCode.UNAVAILABLE
details = "failed to connect to all addresses"
debug_error_string = "{"created":"@1654918004.522083028","description":"Failed to pick subchannel","file":"src/core /ext/filters/client_channel/client_channel.cc","file_line":3217,"referenced_errors":[{"created":"@1654918004.522081306","de scription":"failed to connect to all addresses","file":"src/core/lib/transport/error_utils.cc","file_line":165,"grpc_status ":14}]}"
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/home/yuenyu/PycharmProjects/graph/graphscope/pagerank.py", line 10, in
sess = gs.session()
File "/home/yuenyu/python/venv/lib/python3.9/site-packages/graphscope/client/utils.py", line 357, in wrapper
return_value = func(*args, **kwargs)
File "/home/yuenyu/python/venv/lib/python3.9/site-packages/graphscope/client/session.py", line 715, in init
self._connect()
File "/home/yuenyu/python/venv/lib/python3.9/site-packages/graphscope/client/session.py", line 1047, in _connect
self._grpc_client.waiting_service_ready(
File "/home/yuenyu/python/venv/lib/python3.9/site-packages/graphscope/client/rpc.py", line 78, in waiting_service_ready
raise ConnectionError(f"Connect coordinator timeout, {msg}")
ConnectionError: Connect coordinator timeout, code: UNAVAILABLE, details: failed to connect to all addresses
Beta Was this translation helpful? Give feedback.
All reactions