[BEAM-1674] Flink user state GC depends on order of timer firing

• Type: Bug
• Status: Resolved
• Priority: P0
• Resolution: Fixed
• Affects Version/s: 0.5.0
• Fix Version/s: 0.6.0
• Component/s: runner-flink
• Assignee: Aljoscha Krettek
• Reporter: Aljoscha Krettek
• Created: 09/Mar/17 15:13
• Updated: 24/Jul/20 20:15
• Resolved: 13/Mar/17 20:24

Description

The newly added ParDoTest.testEventTimeTimerMultipleKeys() fails because the DoFn sets a timer for window.maxTimestamp() which also happens to be the GC timer for the user state. The Flink Runner uses timers to schedule GC, the user-set timer and the GC timer have a different timer id, so they don't clash. However, if the GC timer is being processed before the user timer then the user doesn't have a chance to access the state anymore because it will already be cleared out by the time the user timer is being processed.

Issue Links

• links to: GitHub Pull Request #2210
• links to: GitHub Pull Request #2215
• links to: GitHub Pull Request #2217