-
Notifications
You must be signed in to change notification settings - Fork 312
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
Question(FQDN): how to connect to Pegasus cluster with FQDN pegasus version #2007
Comments
So I want to know what should I do , to deloy a peagsus cluster with FQDN now , and how to use tools control this cluster. Thanks a lot. @acelyc111 |
Hi, @ninsmiracle ! Is the Pegasus cluster deployed as a onebox in the docker container? Do the Pegasus shell tool and admin-cli run in the same docker container? |
When I deloyed as a onebox in my Docker container , cluster run as normal. However, if I deploy it on real node, cluster running but can not accept any RPC. |
It's because after the main FQDN patch has been merged, a new Thrift structure (i.e. host_port) has been introduced, but the admin-cli side dosen't know this type. You can check it in the admin-cli's shell.log, the error looks like:
The resolution is to update the admin-cli dependent go-client. However, we have to resolve #1917 at first. |
@ninsmiracle You can check if this patch could solve the issue: #2044 |
#2007 In servers, we assume that the remote IPs may can't be reverse resolved, in this case, warning or error messages are logged instead of crashing. But in tests, we assume that all the IPs can be reverse resolved.
…che#2044) apache#2007 In servers, we assume that the remote IPs may can't be reverse resolved, in this case, warning or error messages are logged instead of crashing. But in tests, we assume that all the IPs can be reverse resolved.
@ninsmiracle If it has been resolved, I'll close the issue. |
General Question
When I deploy master branch of pegasus to real cluster, I could not connect to peagsus via peagsus_shell.
./admin-cli -n aaa:25101,bbb:25101
,but returnfatal: failed to list nodes [context deadline exceeded]
nodes -d
,cluster crash.stdout(error log) in meta server:
172.17.0.1 is my pegasus-shell IP , which is in a docker. It looks like peagsus can not resolve this IP correctly, it's a bug?
I also fonud these coredump in replica servers.
The text was updated successfully, but these errors were encountered: