[SAMZA-2122] Fix the task caught-up logic which doesn't handle no incoming messages

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.1
• Assignee: Xinyu Liu
• Reporter: Xinyu Liu
• Created: 06/Mar/19 01:05
• Updated: 07/Mar/19 01:07
• Resolved: 07/Mar/19 01:07

Description

Currently the TaskInstance.checkCaughtUp() logic has a bug that if there is no incoming messages for a partition, it will not mark the ssp to be caught up. Instead, it should mark ssp to be caught up if the starting offset is already the upcoming offset for a ssp, meaning it has consumed all the messages in this partition and waiting for the future incoming messages. This indicates the ssp is fully caught up.

Issue Links

• links to: GitHub Pull Request #939