GitHub user ijuma opened a pull request:
https://github.com/apache/kafka/pull/2298
KAFKA-4528: Fix failure in
ProducerTest.testAsyncSendCanCorrectlyFailWithTimeout
I was able to reproduce the failure in less than 10 runs before the change.
With the change,
the test passed 70 times consecutively with the change.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ijuma/kafka
kafka-4528-fix-test-async-send-timeout
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/kafka/pull/2298.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #2298
----
commit 29d456cd21d8f3430d52db50a8fd17cc8d700f36
Author: huxi <[email protected]>
Date: 2016-12-31T10:45:47Z
KAFKA-4351; MirrorMaker with new consumer should support comma-separated
regex
This makes it consistent with MirrorMaker with the old consumer.
Author: huxi <[email protected]>
Author: amethystic <[email protected]>
Reviewers: Vahid Hashemian <[email protected]>, Ismael Juma
<[email protected]>
Closes #2072 from
amethystic/kafka-4351_Regex_behavior_change_for_new_consumer
commit 6f09bcb59cd42521152cd8439df94606036ad85f
Author: Vahid Hashemian <[email protected]>
Date: 2016-12-31T18:49:27Z
KAFKA-4480: Report an error in 'kafka-configs' command if the config to be
removed does not exist
Author: Vahid Hashemian <[email protected]>
Reviewers: Guozhang Wang <[email protected]>
Closes #2218 from vahidhashemian/KAFKA-4480
commit 24dce1229dbcf10ff027ed7ca40985473abaf437
Author: Ismael Juma <[email protected]>
Date: 2017-01-03T11:02:12Z
KAFKA-4528: Fix failure in
ProducerTest.testAsyncSendCanCorrectlyFailWithTimeout
commit d6f10937026ce819b95e61f100247eed261fd515
Author: Ismael Juma <[email protected]>
Date: 2017-01-03T11:02:45Z
Minor clean-ups in `ProducerTest`
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
