Skip to content
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

when the zookeeper host can't resolve, the error message isn't intuitive to why #80

Closed
joestein opened this issue Jul 18, 2015 · 4 comments

Comments

@joestein
Copy link
Contributor


050-6268-0001/executors/kafka-inbound.67626d94-2cd8-11e5-a715-56847afe9799/runs/49652666-b2a7-4723-8501-483cfc781fd8
2015-07-17 23:06:12,049:25739(0x7fd0bbf41700):ZOO_INFO@zookeeper_init@786: Initiating client connection, host=host:2181 sessionTimeout=10000 watcher=0x7fd11d8281e0 sessionId=0 sessionPasswd=<null> context=0x7fd094000930 flags=0
2015-07-17 23:06:22,097:25739(0x7fd0bbf41700):ZOO_ERROR@getaddrs@599: getaddrinfo: No such file or directory

F0717 23:06:22.097390 25816 zookeeper.cpp:113] Failed to create ZooKeeper, zookeeper_init: No such file or directory [2]
*** Check failure stack trace: ***
    @     0x7fd11dad15cd  google::LogMessage::Fail()
    @     0x7fd11dad330c  google::LogMessage::SendToLog()
    @     0x7fd11dad11bc  google::LogMessage::Flush()
    @     0x7fd11dad13c9  google::LogMessage::~LogMessage()
    @     0x7fd11dad2332  google::ErrnoLogMessage::~ErrnoLogMessage()
    @     0x7fd11d828b81  ZooKeeperProcess::initialize()
    @     0x7fd11da7e541  process::ProcessManager::resume()
    @     0x7fd11da7e7ac  process::schedule()
    @     0x7fd1e7a34df3  start_thread
    @     0x7fd1e713901d  __clone

@joestein
Copy link
Contributor Author

We should capture this and explain to the user that the issue is that the dns isn't resolving and to check the host being used please.

@vidhyaarvind
Copy link

Similar note - there is a issue with external zookeeper ip not getting resolved and scheduler getting killed without any errors

@joestein
Copy link
Contributor Author

That could hang for a bit on retries, makes sense. So maybe 2-3 things. We
should log more, will add that to the metrics issue. Thanks!
On Jul 19, 2015 1:28 PM, "Vidhya Arvind" notifications@github.com wrote:

Similar note - there is a issue with external zookeeper ip not getting
resolved and scheduler getting killed without any errors


Reply to this email directly or view it on GitHub
#80 (comment).

@dmitrypekar
Copy link
Contributor

It seems that this is known Mesos issue: https://issues.apache.org/jira/browse/MESOS-2186
Closing for now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants