Hi Chang,
I think there is a JIRA[1] aimed at harden this case.
In fact Flink create this directory on started and without other warnings,
we can assume that it has been created. So it might be deleted by
some clean up processes(by Flink or by the fs).
Best,
tison.
[1] https://issues.apache.org
Hi,
Till is the release manager for 1.7, so ping him here.
Best,
tison.
Hao Sun 于2018年11月14日周三 上午3:07写道：
> Sorry I mean the scala-2.12 version is missing
>
> On Tue, Nov 13, 2018 at 10:58 AM Hao Sun wrote:
>
>> I can not find the jar here:
>>
>> https://repository.apache.org/content/reposito
Hi,
Yet Flink does not support auto-scaling. However, there is an umbrella JIRA
issue[1]
to cover the discussion about it. And I think the design doc(draft)
attached[2] could help.
Best,
tison.
[1] https://issues.apache.org/jira/browse/FLINK-10407
[2]
https://docs.google.com/document/d/1XKDXnrp8
+1 to drop it.
It seems few people use it. Commits history of an experimental
module sparse often means that there is low interest.
Best,
tison.
远远 于2018年9月29日周六 下午2:16写道：
> +1， it‘s time to drop it😂
>
> Zhijiang(wangzhijiang999) 于2018年9月29日周六
> 下午1:53写道：
>
>> Very agree with to drop it. +1
Hi Julio,
If the single JobManager lost temporarily and reconnected later, it could
be regranted leadership. And if you use Flink on Yarn, the Yarn RM
(according to configuration) would start a new ApplicationMaster to act as
a take-over JobManager.
Best,
tison.
Julio Biason 于2018年9月28日周五 上午3:
Hi Averell,
As Till pointed out, currently Flink doesn't provide such a flexible
schedule strategy.
However, our team internally implemented a mechanism that allow user-define
schedule plugin(flexible schedule strategy). It could fit your case by
setting a timer on schedule start and trigger (1)
