org.apache.spark.SparkException

Yarn application has already ended! It might have been killed or unable to launch application master.


Samebug tips1

Change the queue name to hadoop

Don't give up yet. Our experts can help. Paste your full stack trace to get a solution.


Solutions on the web1870

Solution icon of github
Yarn application has already ended! It might have been killed or unable to launch application master.

Solution icon of stackoverflow
via Stack Overflow by Ravi
, 1 year ago
Yarn application has already ended! It might have been killed or unable to launch application master.

Solution icon of stackoverflow
Yarn application has already ended! It might have been killed or unable to launch application master.

Solution icon of stackoverflow
Yarn application has already ended! It might have been killed or unable to launch application master.

Solution icon of web
via blogspot.com by Unknown author, 1 year ago
Yarn application has already ended! It might have been killed or unable to launch application master.

Solution icon of stackoverflow
via Stack Overflow by Ashesh Nair
, 1 year ago
Yarn application has already ended! It might have been killed or unable to launch application master.

Solution icon of stackoverflow
via Stack Overflow by Anand Agrawal
, 1 year ago
Yarn application has already ended! It might have been killed or unable to launch application master.

Solution icon of stackoverflow
via Stack Overflow by Pedro Rosanes
, 1 year ago
Yarn application has already ended! It might have been killed or unable to launch application master.

Solution icon of stackoverflow
Yarn application has already ended! It might have been killed or unable to launch application master.

Solution icon of stackoverflow
Yarn application has already ended! It might have been killed or unable to launch application master.

Stack trace

  • org.apache.spark.SparkException: Yarn application has already ended! It might have been killed or unable to launch application master. at org.apache.spark.scheduler.cluster.YarnClientSchedulerBackend.waitForApplication(YarnClientSchedulerBackend.scala:85) at org.apache.spark.scheduler.cluster.YarnClientSchedulerBackend.start(YarnClientSchedulerBackend.scala:62) at org.apache.spark.scheduler.TaskSchedulerImpl.start(TaskSchedulerImpl.scala:156) at org.apache.spark.SparkContext.<init>(SparkContext.scala:509) at org.apache.spark.SparkContext$.getOrCreate(SparkContext.scala:2313) at org.apache.spark.sql.SparkSession$Builder$$anonfun$6.apply(SparkSession.scala:868) at org.apache.spark.sql.SparkSession$Builder$$anonfun$6.apply(SparkSession.scala:860) at scala.Option.getOrElse(Option.scala:121) at org.apache.spark.sql.SparkSession$Builder.getOrCreate(SparkSession.scala:860) at org.apache.spark.repl.Main$.createSparkSession(Main.scala:95)

Write tip

You have a different solution? A short tip here would help you and many other users who saw this issue last week.

Users with the same issue

Samebug visitor profile picture
Unknown user
Once, 3 weeks ago
Samebug visitor profile picture
Unknown user
Once, 3 weeks ago
3 times, 5 months ago
Once, 1 year ago
Samebug visitor profile picture
Unknown user
Once, 1 year ago
3 more bugmates