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 25C2110762 for ; Sun, 3 May 2015 16:56:06 +0000 (UTC) Received: (qmail 45237 invoked by uid 500); 3 May 2015 16:56:06 -0000 Delivered-To: apmail-spark-issues-archive@spark.apache.org Received: (qmail 45205 invoked by uid 500); 3 May 2015 16:56:06 -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 45194 invoked by uid 99); 3 May 2015 16:56:06 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 03 May 2015 16:56:06 +0000 Date: Sun, 3 May 2015 16:56:05 +0000 (UTC) From: "Josh Rosen (JIRA)" To: issues@spark.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (SPARK-6026) Eliminate the bypassMergeThreshold parameter and associated hash-ish shuffle within the Sort shuffle code 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-6026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Josh Rosen updated SPARK-6026: ------------------------------ Component/s: Shuffle > Eliminate the bypassMergeThreshold parameter and associated hash-ish shuffle within the Sort shuffle code > --------------------------------------------------------------------------------------------------------- > > Key: SPARK-6026 > URL: https://issues.apache.org/jira/browse/SPARK-6026 > Project: Spark > Issue Type: Bug > Components: Shuffle, Spark Core > Affects Versions: 1.3.0 > Reporter: Kay Ousterhout > > The bypassMergeThreshold parameter (and associated use of a hash-ish shuffle when the number of partitions is less than this) is basically a workaround for SparkSQL, because the fact that the sort-based shuffle stores non-serialized objects is a deal-breaker for SparkSQL, which re-uses objects. Once the sort-based shuffle is changed to store serialized objects, we should never be secretly doing hash-ish shuffle even when the user has specified to use sort-based shuffle (because of its otherwise worse performance). > [~rxin][~adav], masters of shuffle, it would be helpful to get agreement from you on this proposal (and also a sanity check that I've correctly characterized the issue). -- 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