Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[release-1.6][FLINK-10110][tests] Harden Kafka component shut down for E2E tests #6531

Conversation

tillrohrmann
Copy link
Contributor

What is the purpose of the change

Instead of only calling kafka-server-stop.sh and zookeeper-server-stop.sh which can fail
due to KAFKA-4931 we also use jps to kill the Kafka and ZooKeeper processes.

Does this pull request potentially affect one of the following parts:

  • Dependencies (does it add or upgrade a dependency): (no)
  • The public API, i.e., is any changed class annotated with @Public(Evolving): (no)
  • The serializers: (no)
  • The runtime per-record code paths (performance sensitive): (no)
  • Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (no)
  • The S3 file system connector: (no)

Documentation

  • Does this pull request introduce a new feature? (no)
  • If yes, how is the feature documented? (not applicable)

Instead of only calling kafka-server-stop.sh and zookeeper-server-stop.sh which can fail
due to KAFKA-4931 we also use jps to kill the Kafka and ZooKeeper processes.
@tillrohrmann tillrohrmann changed the title [FLINK-10110][tests] Harden Kafka component shut down for E2E tests [release-1.6][FLINK-10110][tests] Harden Kafka component shut down for E2E tests Aug 9, 2018
@tillrohrmann
Copy link
Contributor Author

Merged via 17eeb5a

@tillrohrmann tillrohrmann deleted the hardenE2EKafkaShutDown-16 branch August 16, 2018 08:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants