From issues-return-128334-apmail-spark-issues-archive=spark.apache.org@spark.apache.org Thu Sep 1 00:09:20 2016 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 9DFCF19EC1 for ; Thu, 1 Sep 2016 00:09:20 +0000 (UTC) Received: (qmail 84111 invoked by uid 500); 1 Sep 2016 00:09:20 -0000 Delivered-To: apmail-spark-issues-archive@spark.apache.org Received: (qmail 84079 invoked by uid 500); 1 Sep 2016 00:09:20 -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 84070 invoked by uid 99); 1 Sep 2016 00:09:20 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Sep 2016 00:09:20 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 69E892C014F for ; Thu, 1 Sep 2016 00:09:20 +0000 (UTC) Date: Thu, 1 Sep 2016 00:09:20 +0000 (UTC) From: "Josh Rosen (JIRA)" To: issues@spark.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (SPARK-17350) Disable default use of KryoSerializer in Thrift Server MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Josh Rosen created SPARK-17350: ---------------------------------- Summary: Disable default use of KryoSerializer in Thrift Server Key: SPARK-17350 URL: https://issues.apache.org/jira/browse/SPARK-17350 Project: Spark Issue Type: Bug Components: SQL Reporter: Josh Rosen Assignee: Josh Rosen In SPARK-4761 (December 2014) we enabled Kryo serialization by default in the Spark Thrift Server. However, I don't think that the original rationale for doing this still holds as all Spark SQL serialization should now be performed via efficient encoders and our UnsafeRow format. In addition, the use of Kryo as the default serializer can introduce performance problems because the creation of new KryoSerializer instances is expensive and we haven't performed instance-reuse optimizations in several code paths (including DirectTaskResult deserialization). Given all of this, I propose to revert back to using JavaSerializer as the default serializer in the Thrift Server. -- 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