You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Chesnay Schepler (JIRA)" <ji...@apache.org> on 2018/03/21 22:41:00 UTC

[jira] [Closed] (FLINK-7343) Kafka010ProducerITCase instability

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

Chesnay Schepler closed FLINK-7343.
-----------------------------------
    Resolution: Fixed

master: b87e660ac64bebbd9a0a6aa4334a68736140053f
1.5: 0fa76e50f06e84da8764089f36227ed26a2c2765

> Kafka010ProducerITCase instability
> ----------------------------------
>
>                 Key: FLINK-7343
>                 URL: https://issues.apache.org/jira/browse/FLINK-7343
>             Project: Flink
>          Issue Type: Bug
>          Components: Kafka Connector
>            Reporter: Piotr Nowojski
>            Assignee: Piotr Nowojski
>            Priority: Blocker
>              Labels: test-stability
>             Fix For: 1.5.0
>
>
> As reported by [~till.rohrmann] in https://issues.apache.org/jira/browse/FLINK-6996 there seems to be a test instability with `Kafka010ProducerITCase>KafkaProducerTestBase.testOneToOneAtLeastOnceRegularSink`
> https://travis-ci.org/tillrohrmann/flink/jobs/258538641
> It is probably related to log.flush intervals in Kafka, which delay flushing the data to files and potentially causing data loses on killing Kafka brokers in the tests.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)