[KAFKA-10218] DistributedHerder's canReadConfigs field is never reset to true

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0.0, 2.0.1, 2.1.0, 2.2.0, 2.1.1, 2.0.2, 2.3.0, 2.1.2, 2.2.1, 2.2.2, 2.4.0, 2.3.1, 2.2.3, 2.5.0, 2.3.2, 2.4.1, 2.6.0, 2.4.2, 2.5.1, 2.7.0, 2.5.2, 2.6.1
• Fix Version/s: 2.4.2, 2.7.0, 2.5.2, 2.6.1
• Component/s: connect
• Assignee: Chris Egerton
• Reporter: Chris Egerton
• Reviewer: Randall Hauch
• Created: 29/Jun/20 22:18
• Updated: 29/Sep/20 00:08
• Resolved: 29/Sep/20 00:08

Description

If the DistributedHerder encounters issues reading to the end of the config topic, it takes note of this fact by setting a field canReadConfigs to false and then acts accordingly at the start of its tick loop by trying again to read to the end of the config topic. However, if a subsequent attempt to read to the end of the config topic succeeds, the canReadConfigs field is never set back to true again, so no matter what, the herder will always attempt to read to the end of the config topic at the beginning of each tick.

Issue Links

• links to: GitHub Pull Request #8973