You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/data-factory/data-factory-troubleshoot-guide.md
+10-8Lines changed: 10 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -663,16 +663,18 @@ The following table applies to Azure Batch.
663
663
664
664
-**Recommendation**: For 502 error, most of the time this is because your Ambari Server process was shut down. You can restart the Ambari Services by rebooting the head node.
665
665
666
-
1. Connect to one of your node on Hdinsight using SSH.
667
-
2. Identify your active head node host by running “ping headnodehost”.
668
-
3. Connect to your active head node as Ambari Server sits on the active head node using SSH.
669
-
4. Reboot the active head node.
666
+
1. Connect to one of your node on Hdinsight using SSH.
667
+
2. Identify your active head node host by running “ping headnodehost”.
668
+
3. Connect to your active head node as Ambari Server sits on the active head node using SSH.
669
+
4. Reboot the active head node.
670
670
671
-
For more information: Look through Azure HDInsight troubleshooting documentation, for example:
671
+
For more information: Look through Azure HDInsight troubleshooting documentation, for example:
-[Scenario: RpcTimeoutException for Apache Spark thrift server in Azure HDInsight](https://docs.microsoft.com/azure/hdinsight/spark/apache-spark-troubleshoot-rpctimeoutexception).
675
-
-[Troubleshooting bad gateway errors in Application Gateway](https://docs.microsoft.com/azure/application-gateway/application-gateway-troubleshooting-502).
- [Scenario: RpcTimeoutException for Apache Spark thrift server in Azure HDInsight](https://docs.microsoft.com/azure/hdinsight/spark/apache-spark-troubleshoot-rpctimeoutexception).
675
+
- [Troubleshooting bad gateway errors in Application Gateway](https://docs.microsoft.com/azure/application-gateway/application-gateway-troubleshooting-502).
676
+
677
+
<br>
676
678
677
679
-**Cause**: When error message contains a message similar to 'Unable to service the submit job request as templeton service is busy with too many submit job requests' or 'Queue root.joblauncher already has 500 applications, cannot accept submission of application', this means that too many jobs are being submitted to HDInsight at the same time.
0 commit comments