Data Factory - Internal Server Error and AzureResourceProviderThrottling errors

Quinn, Katie 1 Reputation point
2021-04-14T19:24:52.8+00:00

We had multiple Data Factory pipelines fail over the last few days (4/11-4/13) with several intermittent errors.

One example of the Internal Server Error we saw:
87880-image.png

The internal server errors were on pipeline steps that were transforming the data and not moving data from a source to a sink. Is there a way to diagnose Internal Server Errors within Data Factory?

Another error we were seeing was specific to an Azure Resource Provider Throttling error. The following error message appeared:

Unexpected failure while waiting for the cluster (0412-081827-waxen351) to be ready.Cause Unexpected state for cluster (0412-081827-waxen351): AZURE_RESOURCE_PROVIDER_THROTTLING(CLOUD_FAILURE): azure_error_code:AzureResourceProviderThrottling,azure_error_message:Encountered Azure Resource Provider throttling. Please try again later. Details: ,databricks_error_message:Error code: AzureResourceProviderThrottling, error message: Encountered Azure Resource Provider throttling. Please try again later.

Is there a reason why we would be seeing an Azure Resource Provider Throttling error message? Was there an outage or planned maintenance with databricks?

The errors were intermittent, however, we saw enough instances of these errors across our pipelines to be concerned.

Azure Data Factory
Azure Data Factory
An Azure service for ingesting, preparing, and transforming data at scale.
11,623 questions
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. KranthiPakala-MSFT 46,642 Reputation points Microsoft Employee Moderator
    2021-04-14T20:12:00.097+00:00

    Hi @Quinn, Katie ,

    Welcome to Microsoft Q&A forum and sorry for your experience.

    We usually notice the internal server error when there is an issue with the ADF dependent service Databricks.
    As per my conversation with internal team, there was an outage reported by Databricks service on 4/13 probably that could be the reason you are seeing these errors. But the issue is resolved now.

    In case if you still continue to receive these errors please do share the latest pipeline and activity runID's for the failed ones so that we can escalate to product team to have a deeper analysis.

    You can also check the status of databricks from the status page here: https://status.azuredatabricks.net/
    This page also contains info about the planned maintenance.

    Hope this info helps. Please do share the pipeline and activity runID's if you ever notice these errors.

    Thank you

    ----------

    Please don’t forget to Accept Answer and Up-Vote wherever the information provided helps you, this can be beneficial to other community members.


Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.