[jira] [Created] (FLINK-23772) Double check if non-keyed FullyFinishedOperatorState can be mixed up with non finished OperatorState on recovery

["Piotr Nowojski (Jira)" <ji...@apache.org>]

Piotr Nowojski created FLINK-23772:
--------------------------------------

             Summary: Double check if non-keyed FullyFinishedOperatorState can be mixed up with non finished OperatorState on recovery
                 Key: FLINK-23772
                 URL: https://issues.apache.org/jira/browse/FLINK-23772
             Project: Flink
          Issue Type: Sub-task
          Components: Runtime / Checkpointing
    Affects Versions: 1.14.0
            Reporter: Piotr Nowojski
             Fix For: 1.14.0


I'm not sure if with non-keyed state we have an issue that it can be reshuffled to different operators during recovery. Are there any guarantees that if subtask 1 has state A, while subtask 2 has B, that after recovery it won’t be rotated?
# is this an issue?
# if so, if we have partially finished tasks with some operators having, {{FullyFinishedOperatorState}}, what prevents {{VerticesFinishedCache.calculateIfFinished}} from failing if the {{FullyFinishedOperatorState}} gets assigned to an operator chain with non finished operator?

For example an operator chain with parallelism of two, non-keyed, before recovery:
{noformat}
src1 (finished state) -> foo1 (finished state)
src2 -> foo2
{noformat}
Can we end up after recovery with:
{noformat}
src1 (finished state) -> foo2
src2 -> foo1 (finished state)
{noformat}
?



--
This message was sent by Atlassian Jira
(v8.3.4#803005)