在AWS上preSTO服务器

本文介绍了在AWS上preSTO服务器 - 无法连接到发现服务器的处理方法，对大家解决问题具有一定的参考价值，需要的朋友们下面随着小编来一起学习吧！ 问题描述

试图运行preSTO协调服务器，发现服务器嵌入式AWS CDH4集群

Trying to run Presto coordinator server with discovery server embedded on AWS CDH4 cluster

config.properties：

config.properties:

coordinator=true datasources=jmx http-server.http.port=8000 presto-metastore.db.type=h2 presto-metastore.db.filename=var/db/MetaStore task.max-memory=1GB discovery-server.enabled=true discovery.uri=ip-10-0-0-11:8000

在服务器启动时，它无法与发现自身注册（相关日志）：

When server starts it can't register itself with discovery (relevant logs):

2013-11-08T19:38:38.193+0000 WARN main Bootstrap Warning: Configuration property 'discovery.uri' is deprecated and should not be used 2013-11-08T19:38:38.968+0000 INFO main Bootstrap discovery-server.enabled false true 2013-11-08T19:38:38.975+0000 INFO main Bootstrap discovery.uri null ip-10-0-0-11:8000 Discovery service base URI 2013-11-08T19:38:40.916+0000 ERROR Discovery-0 io.airlift.discovery.client.CachingServiceSelector Cannot connect to discovery server for refresh (collector/general): Lookup of collector failed for ip-10-0-0-11:8000/v1/service/collector/general 2013-11-08T19:38:42.556+0000 ERROR Discovery-1 io.airlift.discovery.client.CachingServiceSelector Cannot connect to discovery server for refresh (presto/general): Lookup of presto failed for ip-10-0-0-11:8000/v1/service/presto/general 2013-11-08T19:38:43.854+0000 INFO main org.eclipse.jetty.server.AbstractConnector Started SelectChannelConnector@0.0.0.0:8000

试过也独立运行发现服务器，同样的效果。看着已启动的侦听器注册尝试之后。

Tried to also run standalone Discovery server, same effect. Looks that listener is started after registration attempt is made.

推荐答案

我想知道是否有人会在日志中注意到这一点:)这其实不是一个问题。因为发现客户端启动发现服务器已准备好之前出现的错误。你会看到后不久，其中表明，它的工作日志成功的刷新。我们将解决这个日志消息，但最终它纯粹是一个表面问题。

I was wondering if someone would notice this in the logs :) It's actually not a problem. The error appears because the discovery client starts before the discovery server is ready. You'll see "succeeded for refresh" shortly after in the logs which shows that it's working. We will fix the log message eventually but it's purely a cosmetic issue.