Forum Discussion
Unable to connect to HDInsight Spark Status code 502
I am getting the following error when trying to connect to my HDInsight Spark instance:
Details: "ODBC: ERROR [HY000] [Microsoft][ThriftExtension] (14) Unexpected response from server during a HTTP connection: Bad Status: Unrecognized response with no error message header. Status code: 502."
I've just updated Power BI Desktop.
The process is start new report > Get data > Azure HDInsight Spark > enter server as per the overview (see image below) > enter password set during cluster creation. The error appears.
I can connect via SSH and this has happened on two seperate networks. It's the first time I've used HDInsight so I've never had it working and I can't find anything related to this error (everything similar is related to databricks). The only post that came close suggested long passwords are an issue so I reduced the p/w size to the minimum 10 and it still has the same error.
- Anonymous5 years ago
The fix was to rebuild the cluster twice. The first rebuild had the same problem, the second rebuild worked.
4 Replies
- AnonymousNot applicable
Hi Anonymous
Does HDInsight Spark work well in Azure portal? Could you connect to other HDInsight Spark successfully?
The URL you used was correct. Please check whether the username and password is correct in this cluster.
Please update your Desktop version to the lastest one by this link: Download
Here I found some blog and I hope they could help you.
Blogs: Configure Apache Spark settings
Tutorial: Analyze Apache Spark data using Power BI in HDInsight
Best Regards,
Rico Zhou
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
- AnonymousNot applicable
Hi Rico,
I have already logged a support ticket and had someone contact me. It appears there is an issue with the Spark connector itself.
- AnonymousNot applicable
Hi Anonymous
I hope your issue could be solved soon. Please share the workaround with us after your issue has been solved. This will help other users who have the same issue.
Best Regards,
Rico Zhou
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
- AnonymousNot applicable
The fix was to rebuild the cluster twice. The first rebuild had the same problem, the second rebuild worked.