[LIVY-280] Livy session leakage issue when app submission timeout

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.3
• Fix Version/s: 0.3
• Component/s: Core
• Assignee: Jeff Zhang
• Reporter: Jeff Zhang
• Created: 17/Dec/16 03:13
• Updated: 12/Jan/17 06:27
• Resolved: 12/Jan/17 06:27

Description

Sometimes we see no yarn app tagged exception. This is due to it takes a little long time to launch the yarn app (cluster is not busy). But the yarn app finally is still launched. That means the livy session is leaked.

java.lang.Exception: No YARN application is tagged with livy-session-1-sfqqmw85.
com.cloudera.livy.utils.SparkYarnApp.com$cloudera$livy$utils$SparkYarnApp$$getAppIdFromTag(SparkYarnApp.scala:131) com.cloudera.livy.utils.SparkYarnApp$$anonfun$1$$anonfun$4.apply(SparkYarnApp.scala:195) com.cloudera.livy.utils.SparkYarnApp$$anonfun$1$$anonfun$4.apply(SparkYarnApp.scala:192) scala.Option.getOrElse(Option.scala:120) com.cloudera.livy.utils.SparkYarnApp$$anonfun$1.apply$mcV$sp(SparkYarnApp.scala:192) com.cloudera.livy.Utils$$anon$1.run(Utils.scala:95)