Github user gyfora commented on the pull request:
https://github.com/apache/flink/pull/1305#issuecomment-153307495
@aljoscha
1. I was initially using the MockEnvironments but I added the
DummyEnvironment for several reasons: I wanted control over the JobId and the
number of subtasks for which I would have changed the MockEnvironment. Also I
wanted to avoid having to clean up the memorymanager and other resources as I
really don't need them
2. I don't really understand what you mean here, the recovery timestamp is
only used for cleanup on restore
3. Imagine a scenario where 2 task are restoring . 1 restores quickly and
starts writing new timestamps. If we call cleanup on the other task it will
remove the new states if we don't bound by recovery timestamp. This can happen
easily.
I don't know about the allOrNothingState :/
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
