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

本文主要是介绍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 ========

启动成功截图如下:

在这里插入图片描述

这篇关于Cannot connect to discovery server for announce: Announcement failed for http://hadoop102:8881的文章就介绍到这儿,希望我们推荐的文章对编程师们有所帮助!



http://www.chinasem.cn/article/210765

相关文章

SQL Server跟踪自动统计信息更新实战指南

《SQLServer跟踪自动统计信息更新实战指南》本文详解SQLServer自动统计信息更新的跟踪方法,推荐使用扩展事件实时捕获更新操作及详细信息,同时结合系统视图快速检查统计信息状态,重点强调修... 目录SQL Server 如何跟踪自动统计信息更新:深入解析与实战指南 核心跟踪方法1️⃣ 利用系统目录

SQL Server 中的 WITH (NOLOCK) 示例详解

《SQLServer中的WITH(NOLOCK)示例详解》SQLServer中的WITH(NOLOCK)是一种表提示,等同于READUNCOMMITTED隔离级别,允许查询在不获取共享锁的情... 目录SQL Server 中的 WITH (NOLOCK) 详解一、WITH (NOLOCK) 的本质二、工作

SQL Server安装时候没有中文选项的解决方法

《SQLServer安装时候没有中文选项的解决方法》用户安装SQLServer时界面全英文,无中文选项,通过修改安装设置中的国家或地区为中文中国,重启安装程序后界面恢复中文,解决了问题,对SQLSe... 你是不是在安装SQL Server时候发现安装界面和别人不同,并且无论如何都没有中文选项?这个问题也

SQL server数据库如何下载和安装

《SQLserver数据库如何下载和安装》本文指导如何下载安装SQLServer2022评估版及SSMS工具,涵盖安装配置、连接字符串设置、C#连接数据库方法和安全注意事项,如混合验证、参数化查... 目录第一步:打开官网下载对应文件第二步:程序安装配置第三部:安装工具SQL Server Manageme

C#连接SQL server数据库命令的基本步骤

《C#连接SQLserver数据库命令的基本步骤》文章讲解了连接SQLServer数据库的步骤,包括引入命名空间、构建连接字符串、使用SqlConnection和SqlCommand执行SQL操作,... 目录建议配合使用:如何下载和安装SQL server数据库-CSDN博客1. 引入必要的命名空间2.

SQL Server配置管理器无法打开的四种解决方法

《SQLServer配置管理器无法打开的四种解决方法》本文总结了SQLServer配置管理器无法打开的四种解决方法,文中通过图文示例介绍的非常详细,对大家的学习或者工作具有一定的参考学习价值,需要的... 目录方法一:桌面图标进入方法二:运行窗口进入检查版本号对照表php方法三:查找文件路径方法四:检查 S

springboot如何通过http动态操作xxl-job任务

《springboot如何通过http动态操作xxl-job任务》:本文主要介绍springboot如何通过http动态操作xxl-job任务的问题,具有很好的参考价值,希望对大家有所帮助,如有错... 目录springboot通过http动态操作xxl-job任务一、maven依赖二、配置文件三、xxl-

SQL Server修改数据库名及物理数据文件名操作步骤

《SQLServer修改数据库名及物理数据文件名操作步骤》在SQLServer中重命名数据库是一个常见的操作,但需要确保用户具有足够的权限来执行此操作,:本文主要介绍SQLServer修改数据... 目录一、背景介绍二、操作步骤2.1 设置为单用户模式(断开连接)2.2 修改数据库名称2.3 查找逻辑文件名

SQL Server数据库死锁处理超详细攻略

《SQLServer数据库死锁处理超详细攻略》SQLServer作为主流数据库管理系统,在高并发场景下可能面临死锁问题,影响系统性能和稳定性,这篇文章主要给大家介绍了关于SQLServer数据库死... 目录一、引言二、查询 Sqlserver 中造成死锁的 SPID三、用内置函数查询执行信息1. sp_w

Maven 配置中的 <mirror>绕过 HTTP 阻断机制的方法

《Maven配置中的<mirror>绕过HTTP阻断机制的方法》:本文主要介绍Maven配置中的<mirror>绕过HTTP阻断机制的方法,本文给大家分享问题原因及解决方案,感兴趣的朋友一... 目录一、问题场景:升级 Maven 后构建失败二、解决方案:通过 <mirror> 配置覆盖默认行为1. 配置示