[ 
https://issues.apache.org/jira/browse/KAFKA-4527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15762372#comment-15762372
 ] 

ASF GitHub Bot commented on KAFKA-4527:
---------------------------------------

GitHub user shikhar opened a pull request:

    https://github.com/apache/kafka/pull/2277

    KAFKA-4527: task status was being updated before actual pause/resume

    h/t @ewencp for pointing out the issue

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/shikhar/kafka kafka-4527

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/kafka/pull/2277.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 #2277
    
----
commit 9911f25e2b06a02c56deadf7c586b5c263a08027
Author: Shikhar Bhushan <shik...@confluent.io>
Date:   2016-12-19T21:32:26Z

    KAFKA-4527: task status was being updated before actual pause/resume
    
    h/t @ewencp for pointing out the issue

----


> Transient failure of ConnectDistributedTest.test_pause_and_resume_sink where 
> paused connector produces messages
> ---------------------------------------------------------------------------------------------------------------
>
>                 Key: KAFKA-4527
>                 URL: https://issues.apache.org/jira/browse/KAFKA-4527
>             Project: Kafka
>          Issue Type: Bug
>          Components: KafkaConnect, system tests
>            Reporter: Ewen Cheslack-Postava
>            Assignee: Shikhar Bhushan
>              Labels: system-test-failure, system-tests
>             Fix For: 0.10.2.0
>
>
> {quote}
> ====================================================================================================
> test_id:    
> kafkatest.tests.connect.connect_distributed_test.ConnectDistributedTest.test_pause_and_resume_sink
> status:     FAIL
> run time:   40.164 seconds
>     Paused sink connector should not consume any messages
> Traceback (most recent call last):
>   File 
> "/var/lib/jenkins/workspace/system-test-kafka/kafka/venv/local/lib/python2.7/site-packages/ducktape-0.6.0-py2.7.egg/ducktape/tests/runner_client.py",
>  line 123, in run
>     data = self.run_test()
>   File 
> "/var/lib/jenkins/workspace/system-test-kafka/kafka/venv/local/lib/python2.7/site-packages/ducktape-0.6.0-py2.7.egg/ducktape/tests/runner_client.py",
>  line 176, in run_test
>     return self.test_context.function(self.test)
>   File 
> "/var/lib/jenkins/workspace/system-test-kafka/kafka/tests/kafkatest/tests/connect/connect_distributed_test.py",
>  line 257, in test_pause_and_resume_sink
>     assert num_messages == len(self.sink.received_messages()), "Paused sink 
> connector should not consume any messages"
> AssertionError: Paused sink connector should not consume any messages
> {quote}
> See one case here: 
> http://confluent-kafka-system-test-results.s3-us-west-2.amazonaws.com/2016-12-12--001.1481535295--apache--trunk--62e043a/report.html
>  but it has also happened before, e.g. 
> http://confluent-kafka-system-test-results.s3-us-west-2.amazonaws.com/2016-12-06--001.1481017508--apache--trunk--34aa538/report.html
> Thinking about the test, one simple possibility is that our approach to get 
> the number of messages produced/consumed during the test is flawed -- I think 
> we may not account for additional buffering between the connectors and the 
> process reading their output to determine what they have produced. However, 
> that's just a theory -- the minimal checking on the logs that I did didn't 
> reveal anything obviously wrong.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to