GitHub user tdas opened a pull request:
https://github.com/apache/spark/pull/14361
[TEST][STREAMING] Fix flaky Kafka rate controlling test
## What changes were proposed in this pull request?
The current test is incorrect, because
- The expected number of messages does not take into account that the topic
has 2 partitions, and rate is set per partition.
- Also in some cases, the test ran out of data in Kafka while waiting for
the right amount of data per batch.
The PR
- Reduces the partitions to 1
- Adds more data to Kafka
- Runs with 0.5 second so that batches are created slowly
## How was this patch tested?
Ran many times locally, going to run it many times in Jenkins
(If this patch involves UI changes, please attach a screenshot; otherwise,
remove this)
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/tdas/spark kafka-rate-test-fix
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/spark/pull/14361.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 #14361
----
commit 52b5a209eab2b11565e0e9403b35b5eae6429e53
Author: Tathagata Das <[email protected]>
Date: 2016-07-26T02:28:55Z
Fixed rate controller test
----
---
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.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
