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

2023-10-14 13:20
文章标签 http failed server connect cannot discovery announce announcement 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。

相关文章

BUUCTF靶场[web][极客大挑战 2019]Http、[HCTF 2018]admin

BUUCTF靶场[web][极客大挑战 2019]Http、[HCTF 2018]admin

目录   [web][极客大挑战 2019]Http 考点：Referer协议、UA协议、X-Forwarded-For协议 [web][HCTF 2018]admin 考点：弱密码字典爆破 四种方法：   [web][极客大挑战 2019]Http 考点：Referer协议、UA协议、X-Forwarded-For协议 访问环境 老规矩，我们先查看源代码
阅读更多...
【Linux】应用层http协议

【Linux】应用层http协议

一、HTTP协议 1.1 简要介绍一下HTTP        我们在网络的应用层中可以自己定义协议，但是，已经有大佬定义了一些现成的，非常好用的应用层协议，供我们直接使用，HTTP（超文本传输协议）就是其中之一。        在互联网世界中，HTTP（超文本传输协议）是一个至关重要的协议，他定义了客户端（如浏览器）与服务器之间如何进行通信，以交换或者传输超文本（比如HTML文档）。
阅读更多...
如何确定 Go 语言中 HTTP 连接池的最佳参数？

如何确定 Go 语言中 HTTP 连接池的最佳参数？

确定 Go 语言中 HTTP 连接池的最佳参数可以通过以下几种方式： 一、分析应用场景和需求 并发请求量： 确定应用程序在特定时间段内可能同时发起的 HTTP 请求数量。如果并发请求量很高，需要设置较大的连接池参数以满足需求。例如，对于一个高并发的 Web 服务，可能同时有数百个请求在处理，此时需要较大的连接池大小。可以通过压力测试工具模拟高并发场景，观察系统在不同并发请求下的性能表现，从而
阅读更多...
Anaconda 中遇到CondaHTTPError: HTTP 404 NOT FOUND for url的问题及解决办法

Anaconda 中遇到CondaHTTPError: HTTP 404 NOT FOUND for url的问题及解决办法

最近在跑一个开源项目遇到了以下问题，查了很多资料都大（抄）同（来）小（抄）异（去）的，解决不了根本问题，费了很大的劲终于得以解决，记录如下： 1、问题及过程： (myenv) D:\Workspace\python\XXXXX>conda install python=3.6.13 Solving environment: done.....Proceed ([y]/n)? yDownloa
阅读更多...
red5-server源码

red5-server源码

red5-server源码：https://github.com/Red5/red5-server
阅读更多...
构建高性能WEB之HTTP首部优化

构建高性能WEB之HTTP首部优化

0x00 前言 在讨论浏览器优化之前，首先我们先分析下从客户端发起一个HTTP请求到用户接收到响应之间，都发生了什么？知己知彼，才能百战不殆。这也是作为一个WEB开发者，为什么一定要深入学习TCP/IP等网络知识。 0x01 到底发生什么了？ 当用户发起一个HTTP请求时，首先客户端将与服务端之间建立TCP连接，成功建立连接后，服务端将对请求进行处理，并对客户端做出响应，响应内容一般包括响应
阅读更多...
ImportError: cannot import name ‘print_log‘ from ‘logging‘

ImportError: cannot import name ‘print_log‘ from ‘logging‘

mmcv升级到2.+后删除了很多 解决 查FAQ文档，找到 添加到mmcv.utils下即可
阅读更多...
Golang支持平滑升级的HTTP服务

Golang支持平滑升级的HTTP服务

前段时间用Golang在做一个HTTP的接口，因编译型语言的特性，修改了代码需要重新编译可执行文件，关闭正在运行的老程序，并启动新程序。对于访问量较大的面向用户的产品，关闭、重启的过程中势必会出现无法访问的情况，从而影响用户体验。 使用Golang的系统包开发HTTP服务，是无法支持平滑升级（优雅重启）的，本文将探讨如何解决该问题。 一、平滑升级（优雅重启）的一般思路 一般情况下，要实现平滑
阅读更多...
Java http请求示例

Java http请求示例

使用HttpURLConnection public static String httpGet(String host) {HttpURLConnection connection = null;try {URL url = new URL(host);connection = (HttpURLConnection) url.openConnection();connection.setReq
阅读更多...
vue 父组件调用子组件的方法报错，“TypeError: Cannot read property ‘subDialogRef‘ of undefined“

vue 父组件调用子组件的方法报错，“TypeError: Cannot read property ‘subDialogRef‘ of undefined“

vue 父组件调用子组件的方法报错，“TypeError: Cannot read property ‘subDialogRef’ of undefined” 最近用vue做的一个界面，引入了一个子组件，在父组件中调用子组件的方法时，报错提示： [Vue warn]: Error in v-on handler: “TypeError: Cannot read property ‘methods
阅读更多...

Copyright China编程 23002807@qq.com

沪ICP备2023033072号-2