Azure Synapse Notebook - Livy Dead error (after upgrading Spark version from 3.3 to 3.4)

Question

Azure Synapse Notebook - Livy Dead error (after upgrading Spark version from 3.3 to 3.4)

Shenbahagomathi Gnanasambandan 10

Dear Team,

We are facing Synapse Livy Dead error after upgrading Spark version from 3.3 to 3.4.

Resource Location - East US

User's image

Thanks in advance!

phemanth 15,235 Reputation points Microsoft External Staff

2025-04-01T09:47:31.26+00:00
@Shenbahagomathi Gnanasambandan

Please Check the below steps and confirm us if issue persists

Enable Error Classification: Azure Synapse Analytics has an error classification feature that can help identify the root cause of the error. You can enable this by setting the Spark configuration livy.rsc.synapse.error-classification.enabled to true

Check Logs: Review the driver, executor, Spark Event, and Livy logs to pinpoint the exact cause of the failure. This can provide more detailed insights into what might be going wrong

Update Spark Pool Configuration: Sometimes, changing the Spark pool configuration in the notebook activity settings and then reverting it back can resolve version mismatch issues

Permissions: Ensure that all necessary permissions are correctly set, especially if your job interacts with Azure Data Lake Storage (ADLS) Gen2
Shenbahagomathi G 10 Reputation points

2025-04-01T09:59:37.2866667+00:00

Thanks for your response!

I could find the below from Livy logs

Exception in thread "main" org.apache.hadoop.fs.azure.AzureException: com.microsoft.azure.storage.StorageException: Server encountered an internal error. Please try again after some time.

There is no change recently to access level.
phemanth 15,235 Reputation points Microsoft External Staff

2025-04-03T07:42:36.4366667+00:00

@Shenbahagomathi Gnanasambandan Just checking in to see if the below answer helped. If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.

1 answer

Your answer

phemanth 15,235 Reputation points Microsoft External Staff

2025-04-01T09:47:31.26+00:00

@Shenbahagomathi Gnanasambandan

Please Check the below steps and confirm us if issue persists

Enable Error Classification: Azure Synapse Analytics has an error classification feature that can help identify the root cause of the error. You can enable this by setting the Spark configuration livy.rsc.synapse.error-classification.enabled to true

Check Logs: Review the driver, executor, Spark Event, and Livy logs to pinpoint the exact cause of the failure. This can provide more detailed insights into what might be going wrong

Update Spark Pool Configuration: Sometimes, changing the Spark pool configuration in the notebook activity settings and then reverting it back can resolve version mismatch issues

Permissions: Ensure that all necessary permissions are correctly set, especially if your job interacts with Azure Data Lake Storage (ADLS) Gen2
Shenbahagomathi G 10 Reputation points

2025-04-01T09:59:37.2866667+00:00

Thanks for your response!

I could find the below from Livy logs

Exception in thread "main" org.apache.hadoop.fs.azure.AzureException: com.microsoft.azure.storage.StorageException: Server encountered an internal error. Please try again after some time.

There is no change recently to access level.
phemanth 15,235 Reputation points Microsoft External Staff

2025-04-03T07:42:36.4366667+00:00

@Shenbahagomathi Gnanasambandan Just checking in to see if the below answer helped. If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.

Answer 1

phemanth 15,235 Microsoft External Staff

Please consider this additional step and let us know.

Retry the Operation: Sometimes, these errors are transient and retrying the operation after some time can resolve the issue.

Check Azure Service Health: Verify if there are any ongoing issues or maintenance activities in the East US region that might be affecting Azure Storage. You can check the Azure Service Health dashboard for updates.

Review Storage Account Configuration: Ensure that there are no recent changes to the storage account configuration that might be causing the issue. This includes checking for any throttling or quota limits.

Increase Timeout Settings: If the issue persists, consider increasing the timeout settings for your storage operations. This can sometimes help in scenarios where the server is taking longer to respond.

Shenbahagomathi G 10 Reputation points

2025-04-02T09:42:02.78+00:00

Thanks for your response @phemanth

We re-tried after some time as stated in the above message and the issue auto resolved.
phemanth 15,235 Reputation points Microsoft External Staff

2025-04-04T06:46:10.8366667+00:00

@Shenbahagomathi Gnanasambandan Following up to see if the above answer was helpful. If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.

Share via

Azure Synapse Notebook - Livy Dead error (after upgrading Spark version from 3.3 to 3.4)

1 answer

Your answer