Let do a separate JIRA, not overload this already tough pull request...
On Fri, Nov 13, 2015 at 10:44 AM, Matthias J. Sax wrote:
> I was thinking about this issue too and wanted to include it in my
> current PR (I just about to rebase it to the current master...
> https://github.com/apache/flink
I was thinking about this issue too and wanted to include it in my
current PR (I just about to rebase it to the current master...
https://github.com/apache/flink/pull/750).
Or should be open a new JIRA for it and address it after Stop signal is
available?
-Matthias
On 11/12/2015 11:47 AM, Maxim
+1 for the proposed changes. But why not always create a snapshot on
shutdown? Does that break any assumptions in the checkpointing
interval? I see that if the user has checkpointing disabled, we can
just create a fake snapshot.
On Thu, Nov 12, 2015 at 9:56 AM, Gyula Fóra wrote:
> Yes, I agree wi
Yes, I agree with you.
Once we have the graceful shutdown we can make this happen fairly simply
with the mechanism you described :)
Gyula
Stephan Ewen ezt írta (időpont: 2015. nov. 11., Sze,
15:43):
> I think you are touching on something important here.
>
> There is a discussion/PullRequest a
I think you are touching on something important here.
There is a discussion/PullRequest about graceful shutdown of streaming jobs
(like stop
the sources and let the remainder of the streams run out).
With the work in progress to draw external checkpoint, it should be easy do
checkpoint-and-close.
Hey guys,
With recent discussions around being able to shutdown and restart streaming
jobs from specific checkpoints, there is another issue that I think needs
tackling.
As far as I understand when a streaming job finishes the tasks are not
notified for the last checkpoints and also jobs don't ta
