Hi Paul,
you're analysis is right. The JobManager does not wait for pending
operation results to be properly served. See
https://issues.apache.org/jira/browse/FLINK-10309 for more details. I think
a way to solve it is to wait for some time if the RestServerEndpoint still
has some responses to serv
Hi Paul,
As far as writing programs are they are a few lines of code:
*CompletableFuture savepointPath = client.triggerSavepoint();*
*savepointPath.get(); //block until the savepoint completed*
*client.cancel();*
*Please note that this is just an example, not a real program, and there
may be de
Hi vino,
Thank you for the helpful information!
One more question, are these operations supposed to run concurrently to ensure
JobManager receives the cancel request before the savepoint is completed?
Best,
Paul lam
> 在 2018年9月14日，11:48，vino yang 写道：
>
> Hi Paul,
>
> It does not affect any
Hi Paul,
It does not affect anything. It simply splits the two operations that can
be connected together into two separate operations.
The cancel operation will not be triggered until the savepoint operation is
completed.
Thanks, vino.
Paul Lam 于2018年9月14日周五 上午11:12写道：
> Hi Devin,
>
> Thanks f
Hi Devin,
Thanks for the reply! It seems like I missed an important thread.
@vino mentioned a solution that is splitting the cancel-with-savepoint
operation into two separated operations, and I wonder if it breaks the end to
end exactly-once semantics in case of a at-least-once sink? Thanks a
