flink-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From AJ Heller ...@drfloob.com>
Subject Re: ResourceManager not using correct akka URI in standalone cluster (?)
Date Thu, 15 Sep 2016 21:20:05 GMT
More information:

>From the master node, I cannot `telnet localhost 6123` nor `telnet <PUBLIC
IP> 6123` while the cluster is apparently running. Connection refused
immediately. `netstat -n | grep 6123` is empty. There's no server
listening. But the processes are running on all machines.

Does it matter that I don't have hadoop or HDFS installed? It is optional,
right? To be clear, this fails at startup, long before I'm able to run any

On Amazon EC2, the machines know of their private IPs, but not their public
IPs. I've instructed the cluster to operate over the public network because
I couldn't get the private IP scenario working.

Running `./bin/start-local.sh` shows non-zero counts in the Flink
Dashboard. Cluster setups show zero-counts all around.


On Thu, Sep 15, 2016 at 12:41 PM, AJ Heller <aj@drfloob.com> wrote:

> I'm running a standalone cluster on Amazon EC2. Leader election is
> happening according to the logs, and the Flink Dashboard is up and running,
> accessible remotely. The issue I'm having is that the SocketWordCount
> example is not working, the local connection is being refused!
> In the Flink Dashboard, 0 task managers are being reported. And in the
> jobmanager logs, the last line indicates "leader session null". All other
> akka URIs in the log file begin "akka.tcp://flink@PUBLIC_IP/...", but the
> Resourse Manager URI indicated "akka://flink/...".
> jobmanager log:
> http://pastebin.com/VWJM8XvW
> client log:
> http://pastebin.com/ZrWsbcwa
> flink-conf.yaml:
> http://pastebin.com/xy2tz7WS
> master and slave files are populated with public ips as well.

View raw message