Cannot connect to discovery server for announce: Announcement failed for http://hadoop102:8881

简介: linux下启动Presto报错:Cannot connect to discovery server for announce: Announcement failed for http://hadoop102:8881

在虚拟机hadoop103启动时报错

[lqs@hadoop103 presto]$ bin/launcher run

报错内容如下:

hadoop103:34966
2021-12-01T12:59:12.646+0800    ERROR    Discovery-0    io.airlift.discovery.client.CachingServiceSelector    Cannot connect to discovery server for refresh (presto/general): Lookup of presto failed for http://hadoop102:8881/v1/service/presto/general
2021-12-01T12:59:12.809+0800    ERROR    Discovery-4    io.airlift.discovery.client.CachingServiceSelector    Cannot connect to discovery server for refresh (collector/general): Lookup of collector failed for http://hadoop102:8881/v1/service/collector/general

对应图片:
报了这个错后,后面持续循环输出一下信息
报了这个错后,后面持续循环输出一下信息

2021-12-01T12:59:30.212+0800    ERROR    Announcer-0    io.airlift.discovery.client.Announcer    Cannot connect to discovery server for announce: Announcement failed for http://hadoop102:8881
2021-12-01T12:59:30.215+0800    ERROR    Announcer-0    io.airlift.discovery.client.Announcer    Service announcement failed after 71.59ms. Next request will happen within 0.00s
2021-12-01T12:59:30.232+0800    ERROR    Announcer-1    io.airlift.discovery.client.Announcer    Service announcement failed after 8.78ms. Next request will happen within 1.00ms
2021-12-01T12:59:30.239+0800    ERROR    Announcer-1    io.airlift.discovery.client.Announcer    Service announcement failed after 3.46ms. Next request will happen within 2.00ms
2021-12-01T12:59:30.245+0800    ERROR    Announcer-3    io.airlift.discovery.client.Announcer    Service announcement failed after 1.71ms. Next request will happen within 4.00ms
2021-12-01T12:59:30.257+0800    ERROR    Announcer-2    io.airlift.discovery.client.Announcer    Service announcement failed after 2.22ms. Next request will happen within 8.00ms
2021-12-01T12:59:30.278+0800    ERROR    Announcer-1    io.airlift.discovery.client.Announcer    Service announcement failed after 4.38ms. Next request will happen within 16.00ms
2021-12-01T12:59:30.314+0800    ERROR    Announcer-3    io.airlift.discovery.client.Announcer    Service announcement failed after 2.77ms. Next request will happen within 32.00ms
2021-12-01T12:59:30.381+0800    ERROR    Announcer-2    io.airlift.discovery.client.Announcer    Service announcement failed after 2.12ms. Next request will happen within 64.00ms
2021-12-01T12:59:30.512+0800    ERROR    Announcer-1    io.airlift.discovery.client.Announcer    Service announcement failed after 1.85ms. Next request will happen within 128.00ms
2021-12-01T12:59:30.771+0800    ERROR    Announcer-3    io.airlift.discovery.client.Announcer    Service announcement failed after 1.73ms. Next request will happen within 256.00ms
2021-12-01T12:59:31.286+0800    ERROR    Announcer-2    io.airlift.discovery.client.Announcer    Service announcement failed after 3.23ms. Next request will happen within 512.00ms
2021-12-01T12:59:32.288+0800    ERROR    Announcer-1    io.airlift.discovery.client.Announcer    Service announcement failed after 1.36ms. Next request will happen within 1000.00ms
2021-12-01T12:59:33.290+0800    ERROR    Announcer-3    io.airlift.discovery.client.Announcer    Service announcement failed after 1.41ms. Next request will happen within 1000.00ms
2021-12-01T12:59:34.292+0800    ERROR    Announcer-2    io.airlift.discovery.client.Announcer    Service announcement failed after 1.30ms. Next request will happen within 1000.00ms
2021-12-01T12:59:35.297+0800    ERROR    Announcer-1    io.airlift.discovery.client.Announcer    Service announcement failed after 4.38ms. Next request will happen within 1000.00ms
2021-12-01T12:59:36.301+0800    ERROR    Announcer-3    io.airlift.discovery.client.Announcer    Service announcement failed after 2.88ms. Next request will happen within 1000.00ms
2021-12-01T12:59:37.304+0800    ERROR    Announcer-2    io.airlift.discovery.client.Announcer    Service announcement failed after 1.98ms. Next request will happen within 1000.00ms
2021-12-01T12:59:38.308+0800    ERROR    Announcer-1    io.airlift.discovery.client.Announcer    Service announcement failed after 3.81ms. Next request will happen within 1000.00ms
2021-12-01T12:59:39.310+0800    ERROR    Announcer-3    io.airlift.discovery.client.Announcer    Service announcement failed after 1.51ms. Next request will happen within 1000.00ms

报错截图如下:
在这里插入图片描述

原因分析:

这是因为我们没有启动第一个对应节点的原因,这里启动的是第二个节点,为此我们只需要在第一个节点启动,然后再来这个节点启动就可以了

解决方案:

第一个节点启动成功信息如下

2021-12-01T13:12:43.701+0800    INFO    main    com.facebook.presto.metadata.StaticCatalogStore    -- Added catalog hive using connector hive-hadoop2 --
2021-12-01T13:12:43.702+0800    INFO    main    com.facebook.presto.execution.resourceGroups.InternalResourceGroupManager    -- Loading resource group configuration manager --
2021-12-01T13:12:43.703+0800    INFO    main    com.facebook.presto.execution.resourceGroups.InternalResourceGroupManager    -- Loaded resource group configuration manager legacy --
2021-12-01T13:12:43.703+0800    INFO    main    com.facebook.presto.security.AccessControlManager    -- Loading system access control --
2021-12-01T13:12:43.704+0800    INFO    main    com.facebook.presto.security.AccessControlManager    -- Loaded system access control allow-all --
2021-12-01T13:12:43.754+0800    INFO    main    com.facebook.presto.server.PrestoServer    ======== SERVER STARTED ========

出现以上内容表示第一节点启动成功(接图如下:)
在这里插入图片描述

第二个节点启动成功信息如下:

2021-12-01T13:15:20.798+0800    INFO    main    Bootstrap    hive.allow-add-column                              false          false                      Allow Hive connector to add column
2021-12-01T13:15:20.798+0800    INFO    main    Bootstrap    hive.allow-drop-column                             false          false                      Allow Hive connector to drop column
2021-12-01T13:15:20.798+0800    INFO    main    Bootstrap    hive.allow-drop-table                              false          false                      Allow Hive connector to drop table
2021-12-01T13:15:20.798+0800    INFO    main    Bootstrap    hive.allow-rename-column                           false          false                      Allow Hive connector to rename column
2021-12-01T13:15:20.798+0800    INFO    main    Bootstrap    hive.allow-rename-table                            false          false                      Allow Hive connector to rename table
2021-12-01T13:15:20.798+0800    INFO    main    Bootstrap    hive.security                                      legacy         legacy
2021-12-01T13:15:21.821+0800    INFO    main    com.facebook.presto.metadata.StaticCatalogStore    -- Added catalog hive using connector hive-hadoop2 --
2021-12-01T13:15:21.824+0800    INFO    main    com.facebook.presto.security.AccessControlManager    -- Loading system access control --
2021-12-01T13:15:21.824+0800    INFO    main    com.facebook.presto.security.AccessControlManager    -- Loaded system access control allow-all --
2021-12-01T13:15:21.872+0800    INFO    main    com.facebook.presto.server.PrestoServer    ======== SERVER STARTED ========

启动成功截图如下:

在这里插入图片描述

相关文章
|
4月前
|
机器学习/深度学习 前端开发 JavaScript
源映射错误:Error: request failed with status 404 源 URL:http://localhost:8080/bootstrap/js/axios-0.18.0.js
源映射错误:Error: request failed with status 404 源 URL:http://localhost:8080/bootstrap/js/axios-0.18.0.js
118 0
源映射错误:Error: request failed with status 404 源 URL:http://localhost:8080/bootstrap/js/axios-0.18.0.js
|
1月前
|
Web App开发 监控 UED
如何解决Angular中的Error: HTTP request failed, call timeout问题
在Angular应用中,遇到HTTP请求超时错误`Error: HTTP request failed, call timeout`时,可通过多种途径解决。首先,可增加请求超时时间,Angular默认无超时限制,设置合理的超时时间如5秒有助于避免长时间等待无响应。其次,检查服务器响应时间,利用开发者工具监控网络请求,优化服务器端代码或调整超时值。最后,确认网络连接稳定性,使用`navigator.onLine`检测网络状态,并在不同网络环境中测试。这些策略共同作用,能够有效提升应用的稳定性和用户体验。
102 1
|
30天前
|
缓存 运维 Serverless
函数计算产品使用问题之怎么优化HTTP Server的启动速度
函数计算产品作为一种事件驱动的全托管计算服务,让用户能够专注于业务逻辑的编写,而无需关心底层服务器的管理与运维。你可以有效地利用函数计算产品来支撑各类应用场景,从简单的数据处理到复杂的业务逻辑,实现快速、高效、低成本的云上部署与运维。以下是一些关于使用函数计算产品的合集和要点,帮助你更好地理解和应用这一服务。
|
1月前
|
iOS开发 MacOS Python
【Mac 系统】解决已有清华镜像但出现CondaHTTPError: HTTP 000 CONNECTION FAILED for url
在尝试使用清华镜像创建conda环境时遇到下载超时问题,通过删除原有镜像并添加针对Mac OS的清华镜像解决了该问题。
77 3
|
1月前
|
Python
【Azure 应用服务】Azure Function HTTP Trigger 遇见奇妙的500 Internal Server Error: Failed to forward request to http://169.254.130.x
【Azure 应用服务】Azure Function HTTP Trigger 遇见奇妙的500 Internal Server Error: Failed to forward request to http://169.254.130.x
|
3月前
|
网络协议 PHP
Swoole 源码分析之 Http Server 模块
想要了解到 `Http Server` 的全貌,其实只要把那张整体的实现图看懂就足以了。但是,如果想要有足够的深度,那么就还需要深入 `Swoole` 的源代码中,就着源码自行分析一遍。同时,也希望这一次的分析,能够给大家带来对 `Swoole` 更多的一些了解。并不要求要深刻的掌握,因为,很多的事情都不可能一蹴而就。从自己的实力出发,勿忘初心。
71 0
Swoole 源码分析之 Http Server 模块
|
3月前
|
小程序
Failed to load local image resource Xx the server responded with a status of of 500 (HTTP/1.1 500)
Failed to load local image resource Xx the server responded with a status of of 500 (HTTP/1.1 500)
100 4
|
2月前
|
JavaScript 网络架构
vue-router.mjs:3252 TypeError: Cannot use ‘in‘ operator to search for ‘validateStatus‘ in http://loc
vue-router.mjs:3252 TypeError: Cannot use ‘in‘ operator to search for ‘validateStatus‘ in http://loc
|
3月前
svn: E175002: Commit failed (details follow): svn: E175002: Unexpected HTTP status 502Bad Gateway on
svn: E175002: Commit failed (details follow): svn: E175002: Unexpected HTTP status 502Bad Gateway on
100 1
|
3月前
|
资源调度 分布式计算 Hadoop
实时计算 Flink版产品使用问题之yarn session模式中启动的任务链接是http IP,想把IP映射为主机hadoop,该怎么操作
实时计算Flink版作为一种强大的流处理和批处理统一的计算框架,广泛应用于各种需要实时数据处理和分析的场景。实时计算Flink版通常结合SQL接口、DataStream API、以及与上下游数据源和存储系统的丰富连接器,提供了一套全面的解决方案,以应对各种实时计算需求。其低延迟、高吞吐、容错性强的特点,使其成为众多企业和组织实时数据处理首选的技术平台。以下是实时计算Flink版的一些典型使用合集。

相关实验场景

更多