Forum Discussion
Timeout failures when using semantic-link for spark sql
Hi dbeavon3,
Thank you for reaching out in Microsoft Community Forum.
Since your primary tenant is in West US but your Fabric capacity (where the Spark pool runs) is in North Central US, some requests may still be routed through the tenant region, leading to timeouts.
java.net.SocketTimeoutException error related to SynapseML when running Spark notebooks in a scenario where your tenant and capacity are in different regions. This cross-region configuration can sometimes lead to network latency issues, especially with services like SynapseML.
please follow below steps to resolve the error;
1.Run ping or traceroute to check network delays and make sure no firewall or proxy restrictions are affecting connections.
2. Scale up Spark pool resources for better performance.
3.Identify any authentication or connection failures and Break large queries into smaller steps to improve performance.
Please continue using Microsoft community forum.
If you found this post helpful, please consider marking it as "Accept as Solution" and give it a 'Kudos'. if it was helpful. help other members find it more easily.
Regards,
Pavan.
- dbeavon31 year agoMemorable Member
Anonymous
I now have a ticket open with Mindtree.
Please reduce the amount of copy/paste answers from chat GPT. I would ask chat GPT the question if I wanted that sort of answer.This bug probably impacts every single multi-region customer in Fabric. Despite the wide impact, I'm still not likely to motivate this PG to fix it very quickly. I'm using Mindtree for support, and they seem to have a hard time escalating these bugs past the "SME". I'm not sure why it is so difficult...