[KAFKA-12867] Trogdor ConsumeBenchWorker quits prematurely with maxMessages config

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 3.0.0
• Assignee: Kowshik Prakasam
• Reporter: Kowshik Prakasam
• Reviewer: Rajini Sivaram
• Created: 31/May/21 07:53
• Updated: 02/Jun/21 18:33
• Resolved: 02/Jun/21 18:33

Description

The trogdor ConsumeBenchWorker has a bug. If one of the consumption tasks completes executing successfully due to maxMessages being consumed, then, the consumption task notifies the doneFuture causing the ConsumeBenchWorker to halt. This becomes a problem when more than 1 consumption task is running in parallel, because the successful completion of 1 of the tasks shuts down the entire worker while the other tasks are still running. When the worker is shut down, it kills all the active consumption tasks, which is not the desired behavior.

The fix is to not notify the doneFuture when 1 of the consumption tasks complete without error. Instead, we should defer the notification to the CloseStatusUpdater thread.

Issue Links

• links to: GitHub Pull Request #10797