DataFactory DataFlow Activity ManageVnet dataflow cluster is not started

Question

Hi All,

we are unable to start the azure data factory data flow cluster . we are using Mange Vent IR in itally north region

when we start the cluster in Debug Mode we get message-The startup of the cluster is taking longer than expected , we recommend to wait more while the cluster finishes to startup

when we run the pipeline we get dataflow fail with error message- Error: Error code: 135 Failure type: System ErrorDetails Internal Server Error:Failed to submit job on instance pool. Integration Runtime 'integrationRuntime12345', ActivityId: '97c61d76-b012-459a-a8e6-e63972b953c4'.

i have check tag no special character

Answer 1

Hi manish verma ,

Glad that the issue has been resolved and thank you for posting your solution so that others experiencing the same thing can easily reference this! Since the Microsoft Q&A community has a policy that "The question author cannot accept their own answer. They can only accept answers by others ", I'll repost your solution in case you'd like to "Accept " the answer.

Deploying the ADB cluster in other region , in this case, North Europe, helped resolve the issue.

Kindly accept the answer by clicking on Accept answer button so that the solution reaches the community in case anyone is facing similar issue. Thankyou.

Answer 2

Hello @manish verma

Let's try to troubleshoot the issue together. Firstly, have you tried waiting for a longer period of time for the cluster to start up?

The message you received suggests that the startup process is taking longer than expected, so it might be worth waiting a bit longer to see if the cluster eventually starts up. If waiting doesn't work, there are a few other things you can try.

One possible cause of the issue could be that the integration runtime you are using is not configured correctly. You mentioned that you are using a Managed Virtual Network integration runtime in the initial North region.

Have you checked that the integration runtime is properly configured and has the necessary permissions to access the resources it needs?

Another possible cause of the issue could be that there is an issue with the data flow itself. Have you checked the data flow for any errors or issues?

You can try running the data flow in debug mode to see if any errors are reported. Finally, the error message you received suggests that there was an internal server error when trying to submit the job on the instance pool.

This could be caused by a number of issues, including network connectivity issues or problems with the Azure infrastructure.

I hope this helps.