-
Notifications
You must be signed in to change notification settings - Fork 5.3k
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
Cannot connect to discovery server for announce: Announcement failed with status code 404 #7768
Comments
Can you SSH into d2 and verify you can curl the discovery URL on d1?
|
I found that all the discover services provided by the visit can not visit, has been reported 404, even if the machine is their visit to the d1 is also the wrong 404, which is why? Does the discover server have a normal boot and work,How to make the discover normal service start? |
I found that there is a lot of 404 logs on the machine d1 http-request.log, most and / v1 / announcement / related, as follows: `2017-04-07T10:54:42.922+08:00 10.2.19.55 GET /v1/service/collector/general null 9b552087-6da5-4fbb-9871-c39e11cd851f 404 0 260 1 a703e1a4079f4d3b99cca6b8f378561b0000007769 2017-04-07T10:54:42.922+08:00 10.2.19.55 GET /v1/service/presto/general null 9b552087-6da5-4fbb-9871-c39e11cd851f 404 0 257 1 a703e1a4079f4d3b99cca6b8f378561b000000776a 2017-04-07T10:54:42.923+08:00 10.2.19.55 PUT /v1/announcement/9b552087-6da5-4fbb-9871-c39e11cd851f null 9b552087-6da5-4fbb-9871-c39e11cd851f 404 0 0 0 a703e1a4079f4d3b99cca6b8f378561b000000776b 2017-04-07T10:54:43.922+08:00 10.2.19.56 GET /v1/service/collector/general null fedc0e99-d7d5-45ef-ae73-cd7969b12337 404 0 260 1 a703e1a4079f4d3b99cca6b8f378561b000000776d 2017-04-07T10:54:43.923+08:00 10.2.19.56 GET /v1/service/presto/general null fedc0e99-d7d5-45ef-ae73-cd7969b12337 404 0 257 0 a703e1a4079f4d3b99cca6b8f378561b000000776f 2017-04-07T10:54:43.923+08:00 10.2.19.57 GET /v1/service/presto/general null 50354782-afc5-4f70-9eb8-a845e9881f52 404 0 257 1 a703e1a4079f4d3b99cca6b8f378561b0000007770 2017-04-07T10:54:43.923+08:00 10.2.19.57 PUT /v1/announcement/50354782-afc5-4f70-9eb8-a845e9881f52 null 50354782-afc5-4f70-9eb8-a845e9881f52 404 0 0 1 a703e1a4079f4d3b99cca6b8f378561b0000007771 2017-04-07T10:54:43.922+08:00 10.2.19.57 GET /v1/service/collector/general null 50354782-afc5-4f70-9eb8-a845e9881f52 404 0 260 1 a703e1a4079f4d3b99cca6b8f378561b000000776e 2017-04-07T10:54:43.922+08:00 10.2.19.56 PUT /v1/announcement/fedc0e99-d7d5-45ef-ae73-cd7969b12337 null fedc0e99-d7d5-45ef-ae73-cd7969b12337 404 0 0 1 a703e1a4079f4d3b99cca6b8f378561b000000776c 2017-04-07T10:54:43.924+08:00 10.2.19.55 GET /v1/service/collector/general null 9b552087-6da5-4fbb-9871-c39e11cd851f 404 0 260 1 a703e1a4079f4d3b99cca6b8f378561b0000007772 2017-04-07T10:54:43.924+08:00 10.2.19.55 PUT /v1/announcement/9b552087-6da5-4fbb-9871-c39e11cd851f null 9b552087-6da5-4fbb-9871-c39e11cd851f 404 0 0 1 a703e1a4079f4d3b99cca6b8f378561b0000007774 2017-04-07T10:54:43.924+08:00 10.2.19.55 GET /v1/service/presto/general null 9b552087-6da5-4fbb-9871-c39e11cd851f 404 0 257 1 a703e1a4079f4d3b99cca6b8f378561b0000007773` I have read these requests are: io.airlift.discovery.client.HttpDiscoveryAnnouncementClient.announce issued. jar version: discovery-0.142 So now the point of view, is not understood as d1 on the Discovery service problems? |
I was inspired by the following technical blog, built a separate discover server node, found three nodes normal! technical blog site: Prestodb install document Just wonder why the built-in discovering server can not function properly. Thank you @electrum ,If you have the idea of this problem, please give a reply, thank you ~ |
All the 404s lead me to believe the embedded discovery server is not enabled or fails to start. When the server starts, it prints all the config properties. Please check for these lines:
The last two lines come from the Another thing is to look for a thread created by the discovery server. Run the |
There's another way. Hit this endpoint: http://10.2.19.55:8081/application.wadl You should see |
I found in the independent discover service node: / v1 / announcement /, the current cluster has been used. By the way, you provide wadl address is great, whether to consider this written to the user documentation, to give other enthusiasts to reduce some of the exploration time. In addition, the separate build discover service is also recommended to put the user documentation, because I also spent more time to find this solution, I wish you lucky :) 👍 |
@electrum #Hi, i get one problem similar to this when i run presto-0.155 on Centos7,can you give me a device to fix it.Thanks...
4 errors
|
In your configuration file using ip, or ip and host relationship configuration /etc/hosts inside to try again. @yakcy |
Thank you very much. It is solved by configuration /etc/hosts @BillLucky |
@BillLucky Hello, I encountered a similar problem when using centos7 to build Presto cluster. How do I solve this problem? |
@BillLucky I do not understand what changes do we need to make to |
@sbmaggarwal Did you find out how to utilize |
In a Java program, when your program reports an error that a host domain name cannot be recognized, you will usually see an error like "java.net.UnknownHostException" in the log. This means that the program cannot identify the specific IP through DNS, so you can configure /etc/hosts on your local computer or server for mapping to help your program correctly find the IP behind it, and it will work normally. for example: @sbmaggarwal The following quoted links are information that may be useful to you. |
Presto version:
This version of the code is released after 0.167, but 0.168 not released when the master pulled down, based on the custom development of some of the permissions function, but the discovery of the relevant code module did not move.
My development environment:
3 machines:
10.2.19.55 d1
10.2.19.56 d2
10.2.19.57 d3
ps:
d1 --> coordinator + worker
d2 --> worker
d3 --> worker
Expected situation: three workers available
Current situation: only one worker is available
But found d2 / d3 has been unable to join the cluster, the configuration is as follows:
d1 configuration file:
config.properties
coordinator = true
node-scheduler.include-coordinator = true
http-server.http.port = 8081
query.max-memory = 5GB
query.max-memory-per-node = 1GB
discovery-server.enabled = true
discovery.uri = http://10.2.19.55:8081
node.properties
node.environment=test
node.id=9b552087-6da5-4fbb-9871-c39e11cd851f
node.data-dir=/opt/app/presto-server-0.168-dp-SNAPSHOT/data/
d2 configuration file:
config.properties
coordinator = false
http-server.http.port = 8081
query.max-memory = 5GB
query.max-memory-per-node = 1GB
discovery.uri = http://10.2.19.55:8081
node.properties
node.environment=test
node.id=fedc0e99-d7d5-45ef-ae73-cd7969b12337
node.data-dir=/opt/app/presto-server-0.168-dp-SNAPSHOT/data/
d3 configuration file:
config.properties
coordinator = false
http-server.http.port = 8081
query.max-memory = 5GB
query.max-memory-per-node = 1GB
discovery.uri = http://10.2.19.55:8081
node.properties
node.environment=test
node.id=50354782-afc5-4f70-9eb8-a845e9881f52
node.data-dir=/opt/app/presto-server-0.168-dp-SNAPSHOT/data/
server.log
2017-04-06T17:05:53.113+0800 INFO main com.facebook.presto.server.PrestoServer ======== SERVER STARTED ========
5781 2017-04-06T17:05:53.113+0800 ERROR Announcer-0 io.airlift.discovery.client.Announcer Cannot connect to discovery server for announce: Announcement failed with status code 404:
5782 2017-04-06T17:05:53.113+0800 ERROR Announcer-0 io.airlift.discovery.client.Announcer Service announcement failed after 16.74ms. Next request will happen within 0.00s
5783 2017-04-06T17:05:53.122+0800 ERROR Announcer-1 io.airlift.discovery.client.Announcer Service announcement failed after 3.68ms. Next request will happen within 1.00ms
5784 2017-04-06T17:05:53.130+0800 ERROR Announcer-1 io.airlift.discovery.client.Announcer Service announcement failed after 5.99ms. Next request will happen within 2.00ms
5785 2017-04-06T17:05:53.140+0800 ERROR Announcer-0 io.airlift.discovery.client.Announcer Service announcement failed after 5.62ms. Next request will happen within 4.00ms
5786 2017-04-06T17:05:53.151+0800 ERROR Announcer-4 io.airlift.discovery.client.Announcer Service announcement failed after 3.14ms. Next request will happen within 8.00ms
5787 2017-04-06T17:05:53.174+0800 ERROR Announcer-1 io.airlift.discovery.client.Announcer Service announcement failed after 6.52ms. Next request will happen within 16.00ms
5788 2017-04-06T17:05:53.213+0800 ERROR Announcer-0 io.airlift.discovery.client.Announcer Service announcement failed after 5.99ms. Next request will happen within 32.00ms
5789 2017-04-06T17:05:53.286+0800 ERROR Announcer-4 io.airlift.discovery.client.Announcer Service announcement failed after 8.19ms. Next request will happen within 64.00ms
5790 2017-04-06T17:05:53.420+0800 ERROR Announcer-1 io.airlift.discovery.client.Announcer Service announcement failed after 6.30ms. Next request will happen within 128.00ms
5791 2017-04-06T17:05:53.683+0800 ERROR Announcer-0 io.airlift.discovery.client.Announcer Service announcement failed after 6.27ms. Next request will happen within 256.00ms
5792 2017-04-06T17:05:54.204+0800 ERROR Announcer-4 io.airlift.discovery.client.Announcer Service announcement failed after 8.27ms. Next request will happen within 512.00ms
5793 2017-04-06T17:05:55.210+0800 ERROR Announcer-1 io.airlift.discovery.client.Announcer Service announcement failed after 5.88ms. Next request will happen within 1000.00ms
5794 2017-04-06T17:05:56.219+0800 ERROR Announcer-0 io.airlift.discovery.client.Announcer Service announcement failed after 8.04ms. Next request will happen within 1000.00ms
5795 2017-04-06T17:05:57.226+0800 ERROR Announcer-4 io.airlift.discovery.client.Announcer Service announcement failed after 6.85ms. Next request will happen within 1000.00ms
5796 2017-04-06T17:05:58.234+0800 ERROR Announcer-1 io.airlift.discovery.client.Announcer Service announcement failed after 6.63ms. Next request will happen within 1000.00ms
5797 2017-04-06T17:05:59.243+0800 ERROR Announcer-0 io.airlift.discovery.client.Announcer Service announcement failed after 8.06ms. Next request will happen within 1000.00ms
5798 2017-04-06T17:06:00.251+0800 ERROR Announcer-4 io.airlift.discovery.client.Announcer Service announcement failed after 7.70ms. Next request will happen within 1000.00ms
5799 2017-04-06T17:06:01.255+0800 ERROR Announcer-1 io.airlift.discovery.client.Announcer Service announcement failed after 3.36ms. Next request will happen within 1000.00ms
5800 2017-04-06T17:06:02.259+0800 ERROR Announcer-0 io.airlift.discovery.client.Announcer Service announcement failed after 4.17ms. Next request will happen within 1000.00ms
5801 2017-04-06T17:06:03.264+0800 ERROR Announcer-4 io.airlift.discovery.client.Announcer Service announcement failed after 4.13ms. Next request will happen within 1000.00ms
5802 2017-04-06T17:06:04.269+0800 ERROR Announcer-1 io.airlift.discovery.client.Announcer Service announcement failed after 4.25ms. Next request will happen within 1000.00ms
5803 2017-04-06T17:06:05.272+0800 ERROR Announcer-0 io.airlift.discovery.client.Announcer Service announcement failed after 2.76ms. Next request will happen within 1000.00ms
5804 2017-04-06T17:06:06.277+0800 ERROR Announcer-4 io.airlift.discovery.client.Announcer Service announcement failed after 3.98ms. Next request will happen within 1000.00ms
5805 2017-04-06T17:06:07.281+0800 ERROR Announcer-1 io.airlift.discovery.client.Announcer Service announcement failed after 3.99ms. Next request will happen within 1000.00ms
Cluster available nodes, has always been only one, d2 / d3 of the workers have been unable to join the cluster?
curl d1:8081/v1/cluster | json_reformat
{
"runningQueries": 0,
"blockedQueries": 0,
"queuedQueries": 0,
"activeWorkers": 1,
"runningDrivers": 0,
"reservedMemory": 0.0,
"rowInputRate": 0.0,
"byteInputRate": 0.0,
"cpuTimeRate": 0.0
}
@electrum
Read a lot on the Internet you answer to this question, mainly in the following solutions:
Which of the above solutions does not seem to solve this problem for me?
Relevant questions answered address:
1.Presto server - Cannot connect to discovery server for announce
2.prestodb Cannot connect to discovery server for refresh
Thank you for reading, hoping to get your help.
The text was updated successfully, but these errors were encountered: