Return-Path: X-Original-To: apmail-spark-dev-archive@minotaur.apache.org Delivered-To: apmail-spark-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id F340019097 for ; Thu, 14 Apr 2016 10:19:02 +0000 (UTC) Received: (qmail 46919 invoked by uid 500); 14 Apr 2016 10:19:01 -0000 Delivered-To: apmail-spark-dev-archive@spark.apache.org Received: (qmail 46809 invoked by uid 500); 14 Apr 2016 10:19:01 -0000 Mailing-List: contact dev-help@spark.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list dev@spark.apache.org Received: (qmail 46799 invoked by uid 99); 14 Apr 2016 10:19:00 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 14 Apr 2016 10:19:00 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 7C71AC0DAB for ; Thu, 14 Apr 2016 10:19:00 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -0.302 X-Spam-Level: X-Spam-Status: No, score=-0.302 tagged_above=-999 required=6.31 tests=[HTML_MESSAGE=2, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id RP1m6aQm3JKR for ; Thu, 14 Apr 2016 10:18:59 +0000 (UTC) Received: from mail4.ugr.es (mail4.ugr.es [150.214.243.4]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 73E6F5FB07 for ; Thu, 14 Apr 2016 10:18:58 +0000 (UTC) Received: from smtp4.ugr.es (smtp4.ugr.es [150.214.220.64]) by mail4.ugr.es (Postfix) with ESMTP id CE3317D2 for ; Thu, 14 Apr 2016 12:18:51 +0200 (CEST) Received: from [10.100.8.63] (unknown [156.17.137.68]) by smtp4.ugr.es (Postfix) with ESMTPSA id AAC887F6F for ; Thu, 14 Apr 2016 12:18:51 +0200 (CEST) To: "dev@spark.apache.org" From: =?UTF-8?Q?Sergio_Ram=c3=adrez?= Subject: [Streaming] Infinite delay when stopping the context Message-ID: <570F6E8A.90006@ugr.es> Date: Thu, 14 Apr 2016 12:18:50 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.4.0 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="------------010508080802090900040606" --------------010508080802090900040606 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Hello: I use the stop method in my streaming programs to finish the executions of my experiments. However, despite of getting these messages: / //16/04/14 12:03:39 INFO JobGenerator: Stopping JobGenerator immediately// //16/04/14 12:03:39 INFO RecurringTimer: Stopped timer for JobGenerator after time 1460628219000// //16/04/14 12:03:39 INFO JobGenerator: Stopped JobGenerator// //16/04/14 12:03:39 INFO ReceivedBlockTracker: Deleting batches ArrayBuffer() /The thread associated to this app never ends completely. If I look for this process in the OS, I can see that it is still running. I get the same problem with both version of the stop function (gracefully and abrupt). The spark version used is 1.6.1. Any clue about this problem? Regards, Sergio R. --------------010508080802090900040606 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 7bit Hello:

I use the stop method in my streaming programs to finish the executions of my experiments. However, despite of getting these messages:

16/04/14 12:03:39 INFO JobGenerator: Stopping JobGenerator immediately
16/04/14 12:03:39 INFO RecurringTimer: Stopped timer for JobGenerator after time 1460628219000
16/04/14 12:03:39 INFO JobGenerator: Stopped JobGenerator
16/04/14 12:03:39 INFO ReceivedBlockTracker: Deleting batches ArrayBuffer()

The thread associated to this app never ends completely. If I look for this process in the OS, I can see that it is still running. I get the same problem with both version of the stop function (gracefully and abrupt). The spark version used is 1.6.1.

Any clue about this problem?

Regards,

Sergio R.
--------------010508080802090900040606--