flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-7343) Kafka010ProducerITCase instability
Date Wed, 02 Aug 2017 08:59:00 GMT

    [ https://issues.apache.org/jira/browse/FLINK-7343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16110577#comment-16110577

ASF GitHub Bot commented on FLINK-7343:

Github user NicoK commented on the issue:

    yes, seems like it was changed from `-Xmx800m` to `-Xmx1536m` by FLINK-6128 and again
to `-Xmx2048m` by FLINK-7004 without changing it here. The question should rather be whether
we need the specialised options anyway or whether we can remove them.
    I tested the latter (removing the `<argLine>...</argLine>` lines but keeping
the `<forkCount>1</forkCount>`) and then the root pom's values are inherited which
may be a better solution anyway.

> 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

View raw message