[
https://issues.apache.org/jira/browse/SPARK-17350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15453826#comment-15453826
]
Apache Spark commented on SPARK-17350:
--------------------------------------
User 'JoshRosen' has created a pull request for this issue:
https://github.com/apache/spark/pull/14906
> 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: [email protected]
For additional commands, e-mail: [email protected]
