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-10110) Harden e2e Kafka shutdown
Date Thu, 16 Aug 2018 07:55:00 GMT

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

ASF GitHub Bot commented on FLINK-10110:
----------------------------------------

tillrohrmann commented on issue #6531: [release-1.6][FLINK-10110][tests] Harden Kafka component
shut down for E2E tests
URL: https://github.com/apache/flink/pull/6531#issuecomment-413458673
 
 
   Merged via 17eeb5aa665b8fa8ae49e6d7179af67136f377bd

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


> 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)

Mime
View raw message