Details
-
Improvement
-
Status: In Progress
-
Major
-
Resolution: Unresolved
-
None
-
None
Description
Today whenever we are closing-dirty a task, we always wipe out the state stores if we are under EOS. But when the closing task was a RESTORING active, or a RUNNING standby, we may actually not need to wipe out the stores since we know that upon resuming, we would still continue restoring the task before transit to processing ever (assuming the LEO offset would not be truncated), i.e. when they resumes it does not matter if the same records gets applied twice during the continued restoration.
Attachments
Issue Links
- relates to
-
KAFKA-13350 Handle task corrupted exception on a per state store basis
- Open
- links to