I think then you have to either reconfigure your cluster environment or
wait until we bump the Akka version to 2.4.x which supports having an
internal and external IP address.
Cheers,
Till
On Fri, Apr 15, 2016 at 6:36 PM, star jlong
wrote:
> Hi Till/Ned,
>
> Soory I thought this was my post.
>
Hi Till/Ned,
Soory I thought this was my post.
Le Vendredi 15 avril 2016 17h28, ned dogg a écrit :
Hi Till/Jstar,
Thanks for the the reply.
Well I'm facing the same issue as Jstar. Here is my scenarios, I have app that
is creating flink cluster on VMs for users. This app cannot create
Hi Till,
Thanks for the reply.
The idea of ssh of the instance is a good one. I thought of that but in my case
it is not applicable because I setting up a cluster some employees of a
company. And ssh the instance by employees will mean giving them the instance's
key-pair, which I can not. Matte
Hi Ned,
what you also could do is to ssh to your remote cluster and submit the job
using the private IP address which is reachable from within your cluster. I
don't know whether that would be applicable to your use case.
Cheers,
Till
On Fri, Apr 15, 2016 at 9:22 AM, Till Rohrmann wrote:
> The
The log says: Unable to allocate on port 6123, due to error: Cannot assign
requested address
Thus, I would assume that something with your cluster configuration is not
entirely correct. Could you check that?
On Thu, Apr 14, 2016 at 11:19 AM, ned dogg wrote:
> Here a try that I given. As first I
Here a try that I given. As first I was configuring my cluster with private
ip and it was starting properly.
So to avoid this akka issue, I decided to configure my cluster with public
address but with this configuration, my cluster is not starting at all.
Here is the logs that I get
2016-04-14 09:0
Thanks Till for the reply.
But according to you how can I address that?
Thanks,
Ned
On Thu, Apr 14, 2016 at 9:56 AM, Till Rohrmann
wrote:
> Hi Ned,
>
> I think you are facing the issue described in this JIRA issue [1]. The
> problem is that you have a private and a public IP address and that A
Hi Ned,
I think you are facing the issue described in this JIRA issue [1]. The
problem is that you have a private and a public IP address and that Akka
binds to the private IP address. Since the registered IP of an ActorSystem
and the target IP address of a request to this ActorSystem have to be
m
2016-04-14 08:23:51,900 INFO
org.apache.flink.runtime.jobmanager.JobManager-
2016-04-14 08:23:51,902 INFO
org.apache.flink.runtime.jobmanager.JobManager- Starting
JobManager (Version:
I'm referring to the jobmanager.log file not the client log file. You can
find it in the `/log` directory.
Cheers,
Till
On Thu, Apr 14, 2016 at 9:56 AM, ned dogg wrote:
> Hi Till
>
> Thanks for the prompt reply.
>
> The logs say that Please make sure that the actor is running and its port
> is
Hi Till
Thanks for the prompt reply.
The logs say that Please make sure that the actor is running and its port
is reachable.
And it is actaully reachable because I can ping that address.
Ned.
On Thu, Apr 14, 2016 at 8:43 AM, Till Rohrmann
wrote:
> Hi Ned,
>
> what does the logs of the JobMana
Hi Ned,
what does the logs of the JobManager say?
Cheers,
Till
On Apr 14, 2016 9:19 AM, "ned dogg" wrote:
> Hi everybody,
>
> I'm Ned, a young and passionte developer of apache technologies. I have
> been playing with apache flink lastly.
>
> This is what I wanted to do submit a flink topology
Hi everybody,
I'm Ned, a young and passionte developer of apache technologies. I have
been playing with apache flink lastly.
This is what I wanted to do submit a flink topology to a remote flink
cluster. The following are the steps that I did.
- Install flink as a cluster indicated on the link
h
13 matches
Mail list logo
