[KAFKA-12668] MockScheduler is not safe to use in concurrent code.

• Type: Improvement
• Status: Patch Available
• Priority: Major
• Resolution: Unresolved
• Component/s: unit tests
• Labels: newbie
• Assignee: Maksim Iakunin
• Reporter: Jose Armando Garcia Sancio
• Reviewer: Jose Armando Garcia Sancio
• Created: 14/Apr/21 17:16
• Updated: 06/Oct/21 15:04

Description

The current implementation of MockScheduler executes tasks in the same stack when schedule is called. This violates Log's assumption since Log calls schedule while holding a lock. This can cause deadlock in tests.

One solution is to change MockSchedule schedule method so that tick is not called. tick should be called by a stack (thread) that doesn't hold any locks.

Issue Links

• links to: GitHub Pull Request #10775