Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 6F4862009C6 for ; Tue, 31 May 2016 17:57:04 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 6DD12160A44; Tue, 31 May 2016 15:57:04 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id B41B51609AD for ; Tue, 31 May 2016 17:57:03 +0200 (CEST) Received: (qmail 12505 invoked by uid 500); 31 May 2016 15:57:02 -0000 Mailing-List: contact user-help@flink.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@flink.apache.org Delivered-To: mailing list user@flink.apache.org Received: (qmail 12495 invoked by uid 99); 31 May 2016 15:57:02 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 31 May 2016 15:57:02 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 73E3C180481 for ; Tue, 31 May 2016 15:57:02 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.313 X-Spam-Level: * X-Spam-Status: No, score=1.313 tagged_above=-999 required=6.31 tests=[RCVD_IN_DNSWL_NONE=-0.0001, URI_HEX=1.313] autolearn=disabled Received: from mx2-lw-us.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id gs7h99TwIHjq for ; Tue, 31 May 2016 15:56:58 +0000 (UTC) Received: from mwork.nabble.com (mwork.nabble.com [162.253.133.43]) by mx2-lw-us.apache.org (ASF Mail Server at mx2-lw-us.apache.org) with ESMTP id 6979D5F474 for ; Tue, 31 May 2016 15:56:58 +0000 (UTC) Received: from mjoe.nabble.com (unknown [162.253.133.57]) by mwork.nabble.com (Postfix) with ESMTP id D403F309E4AA for ; Tue, 31 May 2016 08:56:54 -0700 (MST) Date: Tue, 31 May 2016 08:19:20 -0700 (PDT) From: jganoff To: user@flink.apache.org Message-ID: <1464707960321-7291.post@n4.nabble.com> In-Reply-To: References: Subject: Re: Executing detached data stream programs MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit archived-at: Tue, 31 May 2016 15:57:04 -0000 Hi Robert, Thanks for the suggestion. Threading out a blocking RemoteStreamEnvironment.execute() call and polling the monitoring REST API will work for now. Once the job transitions to running I will kill the thread and monitor the job through the REST API. As for metrics, accumulators, and other job state I think I can get away with monitoring jobs through a combination of my own metrics system and the data exposed through the Flink Monitoring REST APIs [0]. I didn't find any JIRA issues related to my original request for being able to easily submit detached jobs through an ExecutionEnvironment. Does that sound like something the Flink team would be open to discussing? Thanks! [0] https://ci.apache.org/projects/flink/flink-docs-master/internals/monitoring_rest_api.html -- View this message in context: http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/Executing-detached-data-stream-programs-tp7268p7291.html Sent from the Apache Flink User Mailing List archive. mailing list archive at Nabble.com.