-
Notifications
You must be signed in to change notification settings - Fork 450
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] Error for using graphscope in “hosts”mode. #2887
Comments
As could be seen in the pic, |
The reason you said I have considered. I have checked the pod 2379, it is free. And I run the programmer in a docker container. So the address is free. |
But I couldn't see any other reasons that could cause the address already in use error 😂
Hope you could try the above ways and share the results. |
I test |
@Pomelochen Try: graphscope.set_option(etcd_listening_client_port=2479)
graphscope.set_option(etcd_listening_peer_port=2480) |
Unfortunately, I try to change the port as you said. And other ports, the same bug address already in use. |
Can you please paste the error message you have? |
I have made some changes to reduce the dependency of analytical engine on etcd in #2889, which is expected to be available in tomorrow's nightly build. By then, you could upgrade your graphscope installation by pip3 install -U grpahscope --pre -i https://pypi.org/simple and try again (the nightly build will be available tomorrow, not today). |
Ok, I will try it. If possible. You can try to make a image with ubuntu20.04, and pip graphscope. And run the image on a machine with os readhat7.5,use graphscope on hosts. You may have the same bug. I have try several machine, meet the same bug. |
It's available now. |
When I try to install the new graphscope, I meet another bug |
Describe the bug
A clear and concise description of what the bug is.
When I try to create a session in local mode, I meet an error, here is the debug log :
Screenshots
Environment (please complete the following information):
-python:3.10
Additional context
We don’t meet the same bug in k8s mode.
The text was updated successfully, but these errors were encountered: