Skip to main content

Spark 2 Application Errors & Solutions

Exception - 

Exception in thread "broadcast-exchange-0" java.lang.OutOfMemoryError: Not enough memory to build and broadcast

This is Driver Exception and can be solved by 

  • setting spark.sql.autoBroadcastJoinThreshold to -1
  • Or, increasing --driver-memory

Exception - 
Container  is running beyond physical memory limits.
Current usage: X GB of Y GB physical memory used; X GB of Y GB virtual memory used. Killing container

YARN killed container as it was exceeding memory limits.
  • Increase 
  • --driver-memory
  • --executor-memory
  •  
Exception -
ERROR Executor: Exception in task 600 in stage X.X (TID 12345)
java.lang.OutOfMemoryError: GC overhead limit exceeded

This means that Executor JVM was spending more time in Garbage collection than actual execution. 
  • This JVM feature can be disabled by adding -XX:-UseGCOverheadLimit
  • Increasing Executor memory may help --executor-memory
  • Make data more distributed so that it is not skewed to one executor.
  • Might use parallel GC -XX:+UseParallelGC or -XX:+UseConcMarkSweepGC
Exception -

org.apache.spark.shuffle.FetchFailedException: failed to allocate 65536 byte(s) of direct
memory (used: 1073699840, max: 1073741824)
at org.apache.spark.storage.ShuffleBlockFetcherIterator.throwFetchFailedException(ShuffleBlockFetcherIterator.scala:442)

This means that executor went out of memory .

  • Can increase executor memory --executor-memory
  • Make data more distributed so that it is not skewed to one executor.
  • Increase shuffle partitions  --spark.sql.shuffle.partitions
Exception -
ExecutorLostFailure (executor 525 exited unrelated to the running tasks) Reason: Container container_1495825717937_0056_01_000916 on host: 10.0.0.14 was preempted.

This means you were running above YARN queue capacity assigned to your Job. 
  • Ask for more YARN resources, or schedule Job when resources are available to you.
Exception - 
WARN TaskSetManager: Lost task 49.2 in stage 6.0 (TID xxx, xxx.xxx.xxx.compute.internal): ExecutorLostFailure (executor 16 exited caused by one of the running tasks) Reason: Container killed by YARN for exceeding memory limits. 10.4 GB of 10.4 GB physical memory used. Consider boosting spark.yarn.executor.memoryOverhead.

This means that executor is running out of memory as assigned by YARN
  • Can increase spark.yarn.executor.memoryOverhead
  • can increase --executor-memory
  • Can try reducing number of cores for an executor --executor-cores
Exception- 
org.apache.spark.SparkException: Job aborted due to stage failure: Total size of serialized results of 16 tasks (1048.5 MB) is bigger than spark.driver.maxResultSize (1024.0 MB)

This means that total size of results is greater than the Spark Driver Max Result Size value. This not necessarily means that you are doing a collect causing results to be accumulated on driver. It may be the case that your Job is huge and resulting in large number of tasks, as tasks are serialized to executors by driver. 
  • Consider boosting spark.driver.maxResultSize
  • Or, may be break your job in to multiple sub jobs.
Exception - 
Caused by: org.apache.spark.shuffle.FetchFailedException: Too large frame: 5454002341

When the size of the shuffle data blocks exceeds the limit of 2 GB, which spark can handle, 
  • Identify and re-partition the dataframe 
  • increase parallelism spark.sql.shuffle.partitions
Exception - 
Caused by: java.lang.RuntimeException: Unsupported data type NullType.
at scala.sys.package$.error(package.scala:27)

This might be resulted because of SQL in place. In some cases, it is required to select NULL value(s). For example : Select NULL as col1 from Table1. Spark will not be able to determine data type for NULL value. Thus, our job fails with above error.
  • please try to update the query and cast the NULL to appropriate data type . For example – cast (NULL as String) as col1
Exception - 
Caused by: org.apache.spark.sql.AnalysisException: Cannot overwrite table XXX that is also being read from;


Exception - 
java.lang.NoClassDefFoundError: Could not initialize class org.xerial.snappy.Snappy
        at org.apache.parquet.hadoop.codec.SnappyDecompressor.decompress(SnappyDecompressor.java:62)

OR 

Caused by: java.lang.UnsatisfiedLinkError: /tmp/snappy-1.1.2-d5273c94-b734-4a61-b631-b68a9e859151-libsnappyjava.so: /tmp/snappy-1.1.2-d5273c94-b734-4a61-b631-b68a9e859151-libsnappyjava.so: failed to map segment from shared object: Operation not permitted
        at java.lang.ClassLoader$NativeLibrary.load(Native Method)

It is because that /tmp doesn't have execute permissions.
  • Set temporary directory: --conf "spark.driver.extraJavaOptions=-Djava.io.tmpdir=/a/b/ctmp" --conf "spark.executor.extraJavaOptions=-Djava.io.tmpdir=/a/b/ctmp"
Exception-
org.apache.spark.sql.AnalysisException: Detected cartesian product for INNER join between logical plans

If source data has a static partition value than Spark will analyze execution plan thinking that it is a case wherein it should be a Cross join instead of Inner join.
  • set property - "set spark.sql.crossJoin.enabled=true;"

Comments

Popular posts

Spark MongoDB Connector Not leading to correct count or data while reading

  We are using Scala 2.11 , Spark 2.4 and Spark MongoDB Connector 2.4.4 Use Case 1 - We wanted to read a Shareded Mongo Collection and copy its data to another Mongo Collection. We noticed that after Spark Job successful completion. Output MongoDB did not had many records. Use Case 2 -  We read a MongoDB collection and doing count on dataframe lead to different count on each execution. Analysis,  We realized that MongoDB Spark Connector is missing data on bulk read as a dataframe. We tried various partitioner, listed on page -  https://www.mongodb.com/docs/spark-connector/v2.4/configuration/  But, none of them worked for us. Finally, we tried  MongoShardedPartitioner  this lead to constant count on each execution. But, it was greater than the actual count of records on the collection. This seems to be limitation with MongoDB Spark Connector. But,  MongoShardedPartitioner  seemed closest possible solution to this kind of situation. But, it per...




Scala Spark building Jar leads java.lang.StackOverflowError

  Exception -  [Thread-3] ERROR scala_maven.ScalaCompileMojo - error: java.lang.StackOverflowError [Thread-3] INFO scala_maven.ScalaCompileMojo - at scala.collection.generic.TraversableForwarder$class.isEmpty(TraversableForwarder.scala:36) [Thread-3] INFO scala_maven.ScalaCompileMojo - at scala.collection.mutable.ListBuffer.isEmpty(ListBuffer.scala:45) [Thread-3] INFO scala_maven.ScalaCompileMojo - at scala.collection.mutable.ListBuffer.toList(ListBuffer.scala:306) [Thread-3] INFO scala_maven.ScalaCompileMojo - at scala.collection.mutable.ListBuffer.result(ListBuffer.scala:300) [Thread-3] INFO scala_maven.ScalaCompileMojo - at scala.collection.mutable.Stack$StackBuilder.result(Stack.scala:31) [Thread-3] INFO scala_maven.ScalaCompileMojo - at scala.collection.mutable.Stack$StackBuilder.result(Stack.scala:27) [Thread-3] INFO scala_maven.ScalaCompileMojo - at scala.collection.generic.GenericCompanion.apply(GenericCompanion.scala:50) [Thread-3] INFO scala_maven.ScalaCompile...




MongoDB Chunk size many times bigger than configure chunksize (128 MB)

  Shard Shard_0 at Shard_0/xyz.com:27018 { data: '202.04GiB', docs: 117037098, chunks: 5, 'estimated data per chunk': '40.4GiB', 'estimated docs per chunk': 23407419 } --- Shard Shard_1 at Shard_1/abc.com:27018 { data: '201.86GiB', docs: 116913342, chunks: 4, 'estimated data per chunk': '50.46GiB', 'estimated docs per chunk': 29228335 } Per MongoDB-  Starting in 6.0.3, we balance by data size instead of the number of chunks. So the 128MB is now only the size of data we migrate at-a-time. So large data size per chunk is good now, as long as the data size per shard is even for the collection. refer -  https://www.mongodb.com/community/forums/t/chunk-size-many-times-bigger-than-configure-chunksize-128-mb/212616 https://www.mongodb.com/docs/v6.0/release-notes/6.0/#std-label-release-notes-6.0-balancing-policy-changes




AWS EMR Spark – Much Larger Executors are Created than Requested

  Starting EMR 5.32 and EMR 6.2 you can notice that Spark can launch much larger executors that you request in your job settings. For example - We started a Spark Job with  spark.executor.cores  =   4 But, one can see that the executors with 20 cores (instead of 4 as defined by spark.executor.cores) were launched. The reason for allocating larger executors is that there is a AWS specific Spark option spark.yarn.heterogeneousExecutors.enabled (exists in EMR only, does not exist in Open Source Spark) that is set to true by default that combines multiple executor creation requests on the same node into a larger executor container. So as the result you have fewer executor containers than you expected, each of them has more memory and cores that you specified. If you disable this option (--conf "spark.yarn.heterogeneousExecutors.enabled=false"), EMR will create containers with the specified spark.executor.memory and spark.executor.cores settings and will not co...




Hive Count Query not working

Hive with Tez execution engine -  count(*) not working , returning 0 results.  Solution -  set hive.compute.query.using.stats=false Refer -  https://cwiki.apache.org/confluence/display/Hive/Configuration+Properties hive.compute.query.using.stats Default Value:  false Added In: Hive 0.13.0 with  HIVE-5483 When set to true Hive will answer a few queries like min, max, and count(1) purely using statistics stored in the metastore. For basic statistics collection, set the configuration property  hive.stats.autogather   to true. For more advanced statistics collection, run ANALYZE TABLE queries.