You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Apache Spark (JIRA)" <ji...@apache.org> on 2015/01/20 11:20:34 UTC
[jira] [Commented] (SPARK-5333) [Mesos] MesosTaskLaunchData occurs
BufferUnderflowException
[ https://issues.apache.org/jira/browse/SPARK-5333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14283669#comment-14283669 ]
Apache Spark commented on SPARK-5333:
-------------------------------------
User 'jongyoul' has created a pull request for this issue:
https://github.com/apache/spark/pull/4119
> [Mesos] MesosTaskLaunchData occurs BufferUnderflowException
> -----------------------------------------------------------
>
> Key: SPARK-5333
> URL: https://issues.apache.org/jira/browse/SPARK-5333
> Project: Spark
> Issue Type: Bug
> Components: Mesos
> Reporter: Jongyoul Lee
> Priority: Blocker
>
> MesosTaskLaunchData occurs exception when MesosExecutorBackend launches task because serializedTask.remaining is 0.
> {code}
> Exception in thread "Thread-6" java.nio.BufferUnderflowException
> at java.nio.Buffer.nextGetIndex(Buffer.java:498)
> at java.nio.HeapByteBuffer.getInt(HeapByteBuffer.java:355)
> at org.apache.spark.scheduler.cluster.mesos.MesosTaskLaunchData$.fromByteString(MesosTaskLaunchData.scala:46)
> at org.apache.spark.executor.MesosExecutorBackend.launchTask(MesosExecutorBackend.scala:81)
> {code}
> I've checked this bug with fine-grained mode. This is because MesosTaskLaunchData.toByteString doesn't rewind byteBuffer after they put data.
--
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