Chris Egerton

It turns out that the `testReplication` flakiness persisted in Jenkins, and was not solved by increasing timeouts. Instead, the root of the problem was a change in the Connect framework's...

This was proposed in the original PR for MM2, but decided against: https://github.com/apache/kafka/pull/6295#discussion_r290372816 I was on the fence about adding something now that we're changing the logic. At `TRACE` level...

@clolov are you planning on revisiting this one?

The single test failure is unrelated; merging...

@vvcephei @cadonna would either of you have time to double-check this quick Scalafmt bump?

Converting to draft until upstream PRs are reviewed.

I ran the tests locally when I first wrote them, repeatedly (believe I ran everything in a loop overnight and made sure it all came out green). In the year...

I've been able to get one green run of the test locally, but all other attempts have failed with timeouts, even when bumping the permitted duration for worker startup from...

I've started seeing this worker startup error in the logs for my local runs: ``` [2022-07-15 22:29:48,073] ERROR Stopping due to error (org.apache.kafka.connect.cli.ConnectDistributed) org.apache.kafka.connect.errors.ConnectException: Unable to initialize REST server at...

I made a small adjustment to the shutdown logic for the tests, which ensures that the worker process is actually dead before trying to bring up a new one. This...