Return-Path: X-Original-To: apmail-hadoop-hdfs-user-archive@minotaur.apache.org Delivered-To: apmail-hadoop-hdfs-user-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id A93CC10161 for ; Mon, 1 Jul 2013 23:14:56 +0000 (UTC) Received: (qmail 82251 invoked by uid 500); 1 Jul 2013 23:14:52 -0000 Delivered-To: apmail-hadoop-hdfs-user-archive@hadoop.apache.org Received: (qmail 82157 invoked by uid 500); 1 Jul 2013 23:14:51 -0000 Mailing-List: contact user-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@hadoop.apache.org Delivered-To: mailing list user@hadoop.apache.org Received: (qmail 82149 invoked by uid 99); 1 Jul 2013 23:14:51 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 01 Jul 2013 23:14:51 +0000 X-ASF-Spam-Status: No, hits=2.2 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of john.lilley@redpoint.net designates 206.225.164.233 as permitted sender) Received: from [206.225.164.233] (HELO hub021-nj-8.exch021.serverdata.net) (206.225.164.233) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 01 Jul 2013 23:14:44 +0000 Received: from MBX021-E3-NJ-2.exch021.domain.local ([10.240.4.78]) by HUB021-NJ-8.exch021.domain.local ([10.240.4.117]) with mapi id 14.03.0123.003; Mon, 1 Jul 2013 16:14:23 -0700 From: John Lilley To: "user@hadoop.apache.org" Subject: YARN tasks and child processes Thread-Topic: YARN tasks and child processes Thread-Index: Ac52sIsHF9m/AhNURXu1Z+lylJgnXg== Date: Mon, 1 Jul 2013 23:14:22 +0000 Message-ID: <869970D71E26D7498BDAC4E1CA92226B658D59BF@MBX021-E3-NJ-2.exch021.domain.local> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [173.160.43.61] Content-Type: multipart/alternative; boundary="_000_869970D71E26D7498BDAC4E1CA92226B658D59BFMBX021E3NJ2exch_" MIME-Version: 1.0 X-Virus-Checked: Checked by ClamAV on apache.org --_000_869970D71E26D7498BDAC4E1CA92226B658D59BFMBX021E3NJ2exch_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Is it possible for a child process of a YARN task to persist after the task= is complete? I am looking at an alternative to a YARN auxiliary process t= hat may be simpler to implement, if I can have a task spawn a process that = persists for some time after the task finishes. Thanks, John --_000_869970D71E26D7498BDAC4E1CA92226B658D59BFMBX021E3NJ2exch_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Is it possible for a child process of a YARN task to= persist after the task is complete?  I am looking at an alternative t= o a YARN auxiliary process that may be simpler to implement, if I can have = a task spawn a process that persists for some time after the task finishes.

Thanks,

John=

 

--_000_869970D71E26D7498BDAC4E1CA92226B658D59BFMBX021E3NJ2exch_--