hmm. While there is /technically/ no guarantee that
notifyCheckpointComplete is called, it virtually always is,
especially in local setups.
Is it possible for you to share more code (or all of it)? (you can also
send it to me directly)
On 07.11.2017 11:58, Rinat wrote:
Yes, but
Yes, but notifyCheckpointComplete callback doesn’t called on await completion,
I do the same, as in specified test template :
ActorGateway jobManager = (ActorGateway)
Await.result(cluster.leaderGateway().future(), DEADLINE.timeLeft());
Future savepointResultFuture =
Do you verify that savepointResult is a
JobManagerMessages.TriggerSavepointSuccess? It could also be
JobManagerMessages.TriggerSavepointFailure. (instanceof check)
On 02.11.2017 19:11, Rinat wrote:
Chesnay, thanks for your reply, it was very helpful, but I took logic
from this test template
Chesnay, thanks for your reply, it was very helpful, but I took logic from this
test template and tried to reuse it in my IT case, but found one more issue.
I’ve registered an accumulator in my source function, and for it’s value, as
specified in the specified example.
When accumulator has an
You could trigger a savepoint, which from the viewpoint of
sources/operators/sinks is the same thing as a checkpoint.
How to do this depends a bit on how your test case is written, but you
can take a look at the SavepointMigrationTestBase#executeAndSavepoint
which is all about running josb
