Hi Till,
I will have to test it with flink 1.7.1 and get back to you. Thanks!
Best,
Ethan
> On Feb 15, 2019, at 4:01 AM, Till Rohrmann wrote:
>
> Hi Ethan,
>
> can you observe a similar behaviour with Flink 1.7.1? Flink 1.4.2 is no
> longer supported by the community.
>
> Cheers,
> Till
>
Hi Ethan,
can you observe a similar behaviour with Flink 1.7.1? Flink 1.4.2 is no
longer supported by the community.
Cheers,
Till
On Thu, Feb 14, 2019 at 5:06 PM Ethan Li wrote:
> The related job manager log is
> https://gist.github.com/Ethanlm/86a10e786ad9025ddaa27c113c536da8
>
> On Feb 14, 2
The related job manager log is
https://gist.github.com/Ethanlm/86a10e786ad9025ddaa27c113c536da8
> On Feb 14, 2019, at 9:40 AM, Ethan Li wrote:
>
> Hello,
>
> I have a standalone flink-1.4.2 cluster with one JobManager, one TaskManager,
> and zookeeper. I first started JM and TM and waited fo
Hello,
I have a standalone flink-1.4.2 cluster with one JobManager, one TaskManager,
and zookeeper. I first started JM and TM and waited for them to be stable.
Then I restarted JM. It’s when the TM got confused.
TM got notified that Leader node has changed and it tried to register to the
new
