Return-Path: X-Original-To: apmail-spark-issues-archive@minotaur.apache.org Delivered-To: apmail-spark-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id ED73A18F32 for ; Mon, 19 Oct 2015 22:42:27 +0000 (UTC) Received: (qmail 34863 invoked by uid 500); 19 Oct 2015 22:42:27 -0000 Delivered-To: apmail-spark-issues-archive@spark.apache.org Received: (qmail 34815 invoked by uid 500); 19 Oct 2015 22:42:27 -0000 Mailing-List: contact issues-help@spark.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@spark.apache.org Received: (qmail 34797 invoked by uid 99); 19 Oct 2015 22:42:27 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 19 Oct 2015 22:42:27 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id AF55D2C0451 for ; Mon, 19 Oct 2015 22:42:27 +0000 (UTC) Date: Mon, 19 Oct 2015 22:42:27 +0000 (UTC) From: "Tathagata Das (JIRA)" To: issues@spark.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Resolved] (SPARK-11063) Spark TaskSetManager doesn't use Receiver's scheduling executors MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/SPARK-11063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tathagata Das resolved SPARK-11063. ----------------------------------- Resolution: Fixed Assignee: Shixiong Zhu Fix Version/s: 1.5.2 The fix for 1.5.2 and master is to set preferred location as only the host name of the executor the receiver is assigned to. It may so happen that the receiver gets scheduled on an executor that is on the same host as the desired executor, but not the desired executor. In that case, the receiver will be restarted, until it gets scheduled on the desired executor. So in a environment where there are more than 1 executor in the same host, this can cause some delay in launching of all the executors. But this delay is considered acceptable as in the long run it will ensure that the receivers are always evenly distributed among the executors. > Spark TaskSetManager doesn't use Receiver's scheduling executors > ---------------------------------------------------------------- > > Key: SPARK-11063 > URL: https://issues.apache.org/jira/browse/SPARK-11063 > Project: Spark > Issue Type: Bug > Components: Streaming > Affects Versions: 1.5.0, 1.5.1 > Reporter: Shixiong Zhu > Assignee: Shixiong Zhu > Priority: Critical > Fix For: 1.5.2 > > > The format of RDD's preferredLocations must be hostname but the format of Streaming Receiver's scheduling executors is hostport. So it doesn't work. -- This message was sent by Atlassian JIRA (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org For additional commands, e-mail: issues-help@spark.apache.org