[
https://issues.apache.org/jira/browse/FLINK-7343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16116655#comment-16116655
]
ASF GitHub Bot commented on FLINK-7343:
---------------------------------------
Github user pnowojski commented on the issue:
https://github.com/apache/flink/pull/4470
Yes I also didn't like adding this new flag, but didn't have enough
motivation to change it. I have done some refactoring extracting those
dynamically set in `prepare` method to some `Config` class.
However it helps only a little bit. Those tests would need a more
comprehensive refactor in the future. I particularly don't like that this
`prepare` method exists, it should all be configured in the constructor and all
of those should be final fields.
> 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
> Labels: test-stability
>
> 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
(v6.4.14#64029)
