You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2018/08/07 08:19:00 UTC
[jira] [Commented] (IGNITE-9193) ML TF Integration: Python process
still running after node sigkill shutdown
[ https://issues.apache.org/jira/browse/IGNITE-9193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16571250#comment-16571250 ]
ASF GitHub Bot commented on IGNITE-9193:
----------------------------------------
GitHub user dmitrievanthony opened a pull request:
https://github.com/apache/ignite/pull/4491
IGNITE-9193 Stop child python processes on parent stop.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-9193
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/4491.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 #4491
----
commit ce4622f822336de6e820a302d310a2e7ba7a1a2a
Author: Anton Dmitriev <dm...@...>
Date: 2018-08-07T08:15:54Z
IGNITE-9193 Add watcher that kills python process on parent completes.
----
> ML TF Integration: Python process still running after node sigkill shutdown
> ---------------------------------------------------------------------------
>
> Key: IGNITE-9193
> URL: https://issues.apache.org/jira/browse/IGNITE-9193
> Project: Ignite
> Issue Type: Bug
> Components: ml
> Affects Versions: 2.7
> Reporter: Stepan Pilschikov
> Assignee: Anton Dmitriev
> Priority: Major
> Labels: tf-integration
>
> 1. Running gird
> 2. Fill caches with training data
> 3. Run python script
> 4. Gird run several python processes on each node
> 5. Kill SIGNKILL one node
> Processes restore on other nodes
> Script is doing rerun
> But python processes which was created by killed node are still running
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)