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 608CE10AF0 for ; Thu, 26 Feb 2015 21:13:14 +0000 (UTC) Received: (qmail 56995 invoked by uid 500); 26 Feb 2015 21:13:04 -0000 Delivered-To: apmail-spark-issues-archive@spark.apache.org Received: (qmail 56959 invoked by uid 500); 26 Feb 2015 21:13:04 -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 56947 invoked by uid 99); 26 Feb 2015 21:13:04 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 26 Feb 2015 21:13:04 +0000 Date: Thu, 26 Feb 2015 21:13:04 +0000 (UTC) From: "Ted Yu (JIRA)" To: issues@spark.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (SPARK-6045) RecordWriter should be checked against null in PairRDDFunctions#saveAsNewAPIHadoopDataset 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-6045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14339169#comment-14339169 ] Ted Yu commented on SPARK-6045: ------------------------------- The logic of CassandraHadoopMigrator.scala is unknown. With the current PR, user would be able to see exception earlier so that he / she can perform proper analysis. > RecordWriter should be checked against null in PairRDDFunctions#saveAsNewAPIHadoopDataset > ----------------------------------------------------------------------------------------- > > Key: SPARK-6045 > URL: https://issues.apache.org/jira/browse/SPARK-6045 > Project: Spark > Issue Type: Bug > Reporter: Ted Yu > > gtinside reported in the thread 'NullPointerException in TaskSetManager' with the following stack trace: > {code} > WARN 2015-02-26 14:21:43,217 [task-result-getter-0] TaskSetManager - Lost > task 14.2 in stage 0.0 (TID 29, devntom003.dev.blackrock.com): > java.lang.NullPointerException > org.apache.spark.rdd.PairRDDFunctions.saveAsNewAPIHadoopDataset(PairRDDFunctions.scala:1007) > com.bfm.spark.test.CassandraHadoopMigrator$.main(CassandraHadoopMigrator.scala:77) > com.bfm.spark.test.CassandraHadoopMigrator.main(CassandraHadoopMigrator.scala) > sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > java.lang.reflect.Method.invoke(Method.java:606) > org.apache.spark.deploy.SparkSubmit$.launch(SparkSubmit.scala:358) > org.apache.spark.deploy.SparkSubmit$.main(SparkSubmit.scala:75) > org.apache.spark.deploy.SparkSubmit.main(SparkSubmit.scala) > {code} > Looks like the following call in finally block was the cause: > {code} > writer.close(hadoopContext) > {code} > We should check writer against null before calling close(). -- 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