[
https://issues.apache.org/jira/browse/KAFKA-4558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15799448#comment-15799448
]
Apurva Mehta commented on KAFKA-4558:
-------------------------------------
That sounds like a good idea in general, to make metrics easier to gather from
a variety of clients. What metric would you add to the consumer to fix this
test? Number of partitions assigned or something else?
Another thought: the Throttling test strictly requires that consumer be started
and ready to go before the producer starts. The other tests using
`ProduceConsumeValidate` do not require this. One short term work around is to
revert [this patch to
ProduceConsumeValidate|https://github.com/apache/kafka/pull/1904/files#diff-70247099943a55f682e6e6e4f400334eL35]
. This way, we could keep the throttling test ignored until we have a more
reliable way to determine that the consumer is ready, but the other tests would
be good to go..
Thoughts?
> throttling_test fails if the producer starts too fast.
> ------------------------------------------------------
>
> Key: KAFKA-4558
> URL: https://issues.apache.org/jira/browse/KAFKA-4558
> Project: Kafka
> Issue Type: Bug
> Reporter: Apurva Mehta
> Assignee: Apurva Mehta
>
> As described in https://issues.apache.org/jira/browse/KAFKA-4526, the
> throttling test will fail if the producer in the produce-consume-validate
> loop starts up before the consumer is fully initialized.
> We need to block the start of the producer until the consumer is ready to go.
> The current plan is to poll the consumer for a particular metric (like, for
> instance, partition assignment) which will act as a good proxy for successful
> initialization. Currently, we just check for the existence of a process with
> the PID, which is not a strong enough check, causing the test to fail
> intermittently.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
