You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Robert Metzger (JIRA)" <ji...@apache.org> on 2019/02/28 13:37: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 ]
Robert Metzger updated FLINK-10110:
-----------------------------------
Component/s: (was: Tests)
Connectors / Kafka
> Harden e2e Kafka shutdown
> -------------------------
>
> Key: FLINK-10110
> URL: https://issues.apache.org/jira/browse/FLINK-10110
> Project: Flink
> Issue Type: Improvement
> Components: Connectors / Kafka
> 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)