[GEARPUMP-359] The premature OutputWatermark advancing logic in Subscription is not right

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.8.5
• Assignee: Huafeng Wang
• Reporter: Huafeng Wang
• Created: 26/Oct/17 05:49
• Updated: 26/Oct/17 22:38
• Resolved: 26/Oct/17 22:36

Description

Subscription will update processingWatermark when sending a message and update outputWatermark when receiving an Ack message. It will cause prematurely updating the outputWatermark in such scenario: the Subscription already sent 200 messages to downstream and now the processingWatermark is 200th message's watermark, then it receives the first 100 messages' Ack and it will advance the outputWatermark to 200th message's watermark, not the 100th one, which is wrong.

Issue Links

• is blocked by: GEARPUMP-350 the app Clock is not started
• links to: GitHub Pull Request #234