Field Name | Description |
Session Name ID | Unique identifier for the session. Sessions created by the SuperSQL job engine only have a Session ID. Session ID rule: livy-session-uuid. Sessions created by the standard engine or Spark engine User-submitted Notebook, auto-generated by the platform. User-submitted batch SQL, auto-generated by the platform. |
Spark App Name / ID | Sessions created by the SuperSQL job engine only have a Spark App ID. The Spark App ID prefixed with spark. Sessions created by the standard Spark engine: User-submitted Notebook : Spark App Name : Spark application name specified by the user when creating the kernel; defaults to the prefix sparkapp. Spark App ID : prefixed with spark. Unique identifier for the Spark app. User-submitted batch SQL : Spark App Name : prefixed with temporary-rg. Spark App ID : prefixed with spark. Unique identifier for the Spark app. |
Status | State of the current session, can be divided into not_started: The session has not been started. This status indicates that the session request has been accepted, but the session has not yet started for some reason (for example, insufficient resources or configuration problems). Users need to check related configurations or resource status to start the session. Starting: The session is starting. This status means Livy is allocating resources and initializing the environment for a new Spark session. idle: The session has started successfully and is in idle state. At this point, you can submit Spark jobs. The Livy session is ready to process requests. busy: The session is processing one or more jobs. This status indicates that the session is executing tasks and cannot accept new job requests until the current job is completed. shutting down: The session is deactivating. This status means the user has requested to stop the session, and Livy is performing clearing and resource release operations. The session may stay in this status for a period of time until all running jobs are completed and resources are released. error: The session encounters an error during startup or execution. This status usually means the session is unable to function normally, possibly due to insufficient resources, configuration errors, or other problems. dead: The session has died and cannot be recovered. killed: The session is forcefully terminated. This status means the user has actively terminated the session, possibly because the session is no longer needed or there are problems with the ongoing jobs. A killed session cannot be recovered. success: The session has been successfully completed. This status usually indicates that all jobs in the session have been successfully executed and completed. The session can be considered successful in this status, and users can view the results or output. |
Engine | Computing engine. |
Resource Group | Standard Spark Engine : The resource group used when mounting the compute engine. For batch SQL submitted by users, ephemeral resources are used by default, and the resource group is displayed as --. SuperSQL: The resource group column is not shown. |
Kind | Session type Spark PySpark SQL Machine Learning Python MLlib |
Creator | The user who creates a session. |
Startup Time | The time when the session was started. |
End Time | The time when the session dead or was killed. |
Operation | Supports the kill action to manually close the session. |
Was this page helpful?
You can also Contact sales or Submit a Ticket for help.
Help us improve! Rate your documentation experience in 5 mins.
Feedback