You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by apurvam <gi...@git.apache.org> on 2017/06/12 22:54:12 UTC
[GitHub] kafka pull request #3308: KAFKA-5437: Always send a sig_kill when cleaning t...
GitHub user apurvam opened a pull request:
https://github.com/apache/kafka/pull/3308
KAFKA-5437: Always send a sig_kill when cleaning the message copier
When the message copier hangs (like when there is a bug in the client), it ignores the sigterm and doesn't shut down. this leaves the cluster in an unclean state causing future tests to fail.
In this patch we always send SIGKILL when cleaning the node if the process isn't already dead. This is consistent with the other services.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/apurvam/kafka KAFKA-5437-force-kill-message-copier-on-cleanup
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/kafka/pull/3308.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #3308
----
commit 5364c4830f5f97fbbfbefbf2c92e1d7230490ebf
Author: Apurva Mehta <ap...@confluent.io>
Date: 2017-06-12T22:52:45Z
Always send a sig_kill when cleaning the message copier
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] kafka pull request #3308: KAFKA-5437: Always send a sig_kill when cleaning t...
Posted by asfgit <gi...@git.apache.org>.
Github user asfgit closed the pull request at:
https://github.com/apache/kafka/pull/3308
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---