You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2018/08/09 09:38:00 UTC

[jira] [Updated] (FLINK-10110) Harden e2e Kafka shutdown

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

ASF GitHub Bot updated FLINK-10110:
-----------------------------------
    Labels: pull-request-available  (was: )

> Harden e2e Kafka shutdown
> -------------------------
>
>                 Key: FLINK-10110
>                 URL: https://issues.apache.org/jira/browse/FLINK-10110
>             Project: Flink
>          Issue Type: Improvement
>          Components: Tests
>    Affects Versions: 1.6.0
>            Reporter: Till Rohrmann
>            Assignee: Till Rohrmann
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.6.1, 1.7.0
>
>
> Due to KAFKA-4931, the shutdown of Kafka components can fail if the output of {{ps}} is limited to 4096 characters. Therefore, it can happen that e2e tests which start Kafka don't properly shut it down. I suggest to fix this problem by hardening our {{stop_kafka_cluster}} in {{kafka-common.sh}}.



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