-
Notifications
You must be signed in to change notification settings - Fork 100
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
Multi-node setup w/ coordinator as worker - fatal error #370
Comments
I did exclude the coordinator from the worker list:
But still getting the same error:
This means that prestoadmin must be started from outside the cluster? I am running it from the coordinator. |
I do not think it should matter. What version are using? |
What do you have in Here you have some docs where you could find these files: https://prestodb.io/presto-admin/docs/current/installation/presto-configuration.html# |
HI kokosing, Many thansk for the reply. a) Packages being installed are b) My config.json file follows:
I had the coordinator as a worker too, but tried taking it out to see if it works, but it did not. |
I am sorry, but I did not ask for presto-admin |
Dear @kokosing we found the issue. In fact config.properties under /worker and /coordinator nodes where the discovery.uri field was set to . We replaced it with the real IP and it worked. We algo could accumulate the coordinator and worker job in the same node. Thanks! |
Hello,
I have the following config.json setup:
But I get this error:
Fatal error: [172.17.233.164] discovery.uri should not be localhost in a multi-node cluster, but found http://localhost:8080. You may have encountered this error by choosing a coordinator that is localhost and a worker that is not. The default discovery-uri is http://<coordinator>:8080
After that I get some error messages from the workers:
Fatal error: [172.17.233.xxx] sudo() received nonzero return code 1 while executing!
Why is that? Can´t the coordinator share the worker status in a multi-node cluster?
The text was updated successfully, but these errors were encountered: