[
https://issues.apache.org/jira/browse/KAFKA-3513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15237505#comment-15237505
]
Ismael Juma commented on KAFKA-3513:
------------------------------------
We have had failures with various different parameters:
{code}
"""Module: kafkatest.tests.consumer_test
Class: OffsetValidationTest
Method: test_consumer_bounce
Arguments:
{
""bounce_mode"": ""all"",
""clean_shutdown"": true
}"
"Module: kafkatest.tests.client.consumer_test
Class: OffsetValidationTest
Method: test_broker_failure
Arguments:
{
""clean_shutdown"": false,
""enable_autocommit"": true
}"
"Module: kafkatest.tests.client.consumer_test
Class: OffsetValidationTest
Method: test_broker_failure
Arguments:
{
""clean_shutdown"": true,
""enable_autocommit"": false
}"
"""Module: kafkatest.tests.consumer_test
Class: OffsetValidationTest
Method: test_consumer_bounce
Arguments:
{
""bounce_mode"": ""rolling"",
""clean_shutdown"": true
}"
"Module: kafkatest.tests.client.consumer_test
Class: OffsetValidationTest
Method: test_consumer_bounce
Arguments:
{
""bounce_mode"": ""all"",
""clean_shutdown"": false
}"
{code}
> Transient failure of OffsetValidationTest
> -----------------------------------------
>
> Key: KAFKA-3513
> URL: https://issues.apache.org/jira/browse/KAFKA-3513
> Project: Kafka
> Issue Type: Bug
> Components: consumer, system tests
> Reporter: Ewen Cheslack-Postava
> Assignee: Jason Gustafson
>
> http://confluent-kafka-system-test-results.s3-us-west-2.amazonaws.com/2016-04-05--001.1459840046--apache--trunk--31e263e/report.html
> The version of the test fails in this case is:
> Module: kafkatest.tests.client.consumer_test
> Class: OffsetValidationTest
> Method: test_broker_failure
> Arguments:
> {
> "clean_shutdown": true,
> "enable_autocommit": false
> }
> and others passed. It's unclear if the parameters actually have any impact on
> the failure.
> I did some initial triage and it looks like the test code isn't seeing all
> the group members join the group (receive partition assignments), but it
> appears from the logs that they all did. This could indicate a simple timing
> issue, but I haven't been able to verify that yet.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
