What do you think about reverting this change (FLINK-8696), because it is
really hard to debug for users? A problem would be if people now rely on
the second argument being the hostname.
An alternative could be to filter out `cluster` and `local` if they should
appear as second argument. This
Yes, that would be a good idea. I think it should go into the release
notes. Will add it.
On Wed, Sep 26, 2018 at 10:24 AM Fabian Hueske wrote:
> Should we add a warning to the release announcements?
>
> Fabian
>
> Am Mi., 26. Sep. 2018 um 10:22 Uhr schrieb Robert Metzger <
>
Should we add a warning to the release announcements?
Fabian
Am Mi., 26. Sep. 2018 um 10:22 Uhr schrieb Robert Metzger <
rmetz...@apache.org>:
> Hey Jamie,
>
> we've been facing the same issue with dA Platform, when running Flink
> 1.6.1.
> I assume a lot of people will be affected by this.
>
>
Hey Jamie,
we've been facing the same issue with dA Platform, when running Flink 1.6.1.
I assume a lot of people will be affected by this.
On Tue, Sep 25, 2018 at 11:18 PM Till Rohrmann wrote:
> Hi Jamie,
>
> thanks for the update on how to fix the problem. This is very helpful for
> the
Hi Jamie,
thanks for the update on how to fix the problem. This is very helpful for
the rest of the community.
The change of removing the execution mode parameter (FLINK-8696) from the
start up scripts was actually released with Flink 1.5.0. That way, the host
name became the 2nd parameter. By
Update on this:
The issue was the command being used to start the jobmanager:
`jobmanager.sh start-foreground cluster`. This was a command leftover in
our automation that used to be the correct way to start the JM -- however
now, in Flink 1.5.4, that second parameter, `cluster`, is being
Anybody else seen this and know the solution? We're dead in the water with
Flink 1.5.4.
On Sun, Sep 23, 2018 at 11:46 PM alex wrote:
> We started to see same errors after upgrading to flink 1.6.0 from 1.4.2. We
> have one JM and 5 TM on kubernetes. JM is running on HA mode. Taskmanagers
>
We started to see same errors after upgrading to flink 1.6.0 from 1.4.2. We
have one JM and 5 TM on kubernetes. JM is running on HA mode. Taskmanagers
sometimes are loosing connection to JM and having following error like you
have.
*2018-09-19 12:36:40,687 INFO
Anybody else seen this? I'm running both the JM and TM on the same host in
this setup. This was working fine w/ Flink 1.5.3.
On the TaskManager:
00:31:30.268 INFO o.a.f.r.t.TaskExecutor - Could not resolve
ResourceManager address akka.tcp://flink@localhost:6123/user/resourcemanager,
retrying
