developster opened a new pull request, #15080: URL: https://github.com/apache/kafka/pull/15080
*Description of the change* Changed StandaloneHerder to always synchronize on itself before invoking any methods on MemoryConfigBackingStore. This helped the situation as the order of acquiring locks is always the same. First on the herder and then on the config backing store. *Testing strategy* Manually tested StandaloneHerder from Kafka 2.6.3 and Kafka 3.6.1 and both have the same issue. 9 times out of 10 startup ends in deadlock. Tested after fixing (3.8.0-SNAPSHOT) and the deadlock is not happening anymore. ### Committer Checklist (excluded from commit message) - [ ] Verify design and implementation - [ ] Verify test coverage and CI build status - [ ] Verify documentation (including upgrade notes) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: jira-unsubscr...@kafka.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
