Home | About | Sematext search-lucene.com search-hadoop.com
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB
 Search Hadoop and all its subprojects:

Switch to Threaded View
Kafka >> mail # dev >> [jira] [Updated] (KAFKA-772) System Test Transient Failure on testcase_0122


Copy link to this message
-
[jira] [Updated] (KAFKA-772) System Test Transient Failure on testcase_0122

     [ https://issues.apache.org/jira/browse/KAFKA-772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

John Fung updated KAFKA-772:
----------------------------

    Attachment: testcase_0125.tar.gz
    
> System Test Transient Failure on testcase_0122
> ----------------------------------------------
>
>                 Key: KAFKA-772
>                 URL: https://issues.apache.org/jira/browse/KAFKA-772
>             Project: Kafka
>          Issue Type: Bug
>    Affects Versions: 0.8
>            Reporter: John Fung
>            Assignee: Sriram Subramanian
>              Labels: kafka-0.8, p1
>         Attachments: testcase_0122.tar.gz, testcase_0125.tar.gz
>
>
> * This test case is failing randomly in the past few weeks. Please note there is a small % data loss allowance for the test case with Ack = 1. But the failure in this case is the mismatch of log segment checksum across the replicas.
> * Test description:
> 3 brokers cluster
> Replication factor = 3
> No. topic = 2
> No. partitions = 3
> Controlled failure (kill -15)
> Ack = 1
> * Test case output
> _test_case_name  :  testcase_0122
> _test_class_name  :  ReplicaBasicTest
> arg : auto_create_topic  :  true
> arg : bounce_broker  :  true
> arg : broker_type  :  leader
> arg : message_producing_free_time_sec  :  15
> arg : num_iteration  :  3
> arg : num_partition  :  3
> arg : replica_factor  :  3
> arg : sleep_seconds_between_producer_calls  :  1
> validation_status  :
>      Leader Election Latency - iter 1 brokerid 3  :  377.00 ms
>      Leader Election Latency - iter 2 brokerid 1  :  374.00 ms
>      Leader Election Latency - iter 3 brokerid 2  :  384.00 ms
>      Leader Election Latency MAX  :  384.00
>      Leader Election Latency MIN  :  374.00
>      Unique messages from consumer on [test_1] at simple_consumer_test_1-0_r1.log  :  1750
>      Unique messages from consumer on [test_1] at simple_consumer_test_1-0_r2.log  :  1750
>      Unique messages from consumer on [test_1] at simple_consumer_test_1-0_r3.log  :  1750
>      Unique messages from consumer on [test_1] at simple_consumer_test_1-1_r1.log  :  1750
>      Unique messages from consumer on [test_1] at simple_consumer_test_1-1_r2.log  :  1750
>      Unique messages from consumer on [test_1] at simple_consumer_test_1-1_r3.log  :  1750
>      Unique messages from consumer on [test_1] at simple_consumer_test_1-2_r1.log  :  1500
>      Unique messages from consumer on [test_1] at simple_consumer_test_1-2_r2.log  :  1500
>      Unique messages from consumer on [test_1] at simple_consumer_test_1-2_r3.log  :  1500
>      Unique messages from consumer on [test_2]  :  5000
>      Unique messages from consumer on [test_2] at simple_consumer_test_2-0_r1.log  :  1714
>      Unique messages from consumer on [test_2] at simple_consumer_test_2-0_r2.log  :  1714
>      Unique messages from consumer on [test_2] at simple_consumer_test_2-0_r3.log  :  1680
>      Unique messages from consumer on [test_2] at simple_consumer_test_2-1_r1.log  :  1708
>      Unique messages from consumer on [test_2] at simple_consumer_test_2-1_r2.log  :  1708
>      Unique messages from consumer on [test_2] at simple_consumer_test_2-1_r3.log  :  1708
>      Unique messages from consumer on [test_2] at simple_consumer_test_2-2_r1.log  :  1469
>      Unique messages from consumer on [test_2] at simple_consumer_test_2-2_r2.log  :  1469
>      Unique messages from consumer on [test_2] at simple_consumer_test_2-2_r3.log  :  1469
>      Unique messages from producer on [test_2]  :  4900
>      Validate for data matched on topic [test_1] across replicas  :  PASSED
>      Validate for data matched on topic [test_2]  :  FAILED
>      Validate for data matched on topic [test_2] across replicas  :  FAILED
>      Validate for merged log segment checksum in cluster [source]  :  FAILED
>      Validate leader election successful  :  PASSED

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

 
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB