Synapse - Sftp linked service authentication timeout

Kenny, Craig (EthosEnergy) 1 Reputation point
2022-06-14T11:49:50.887+00:00

I'm trying to connect to a sftp site that takes around 90 seconds to authenticate against
Tested this with a tool like WinSCP it works fine from the VM my integration runtime exists on and once authenticated it responds quickly.

However when trying to connect to it using a SFTP linked service in synapse - it times out after 30 seconds

ErrorCode=SftpNetworkIssue,'Type=Microsoft.DataTransfer.Common.Shared.HybridDeliveryException,Message=Meet network issue when connect to Sftp server 'x.x.x.x', SocketErrorCode: 'TimedOut'.,Source=Microsoft.DataTransfer.ClientLibrary.SftpConnector,''Type=System.Net.Sockets.SocketException,Message=A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond,Source=Renci.SshNet

How can I set the connection timeout to something longer than 30 seconds?

Azure Synapse Analytics
Azure Synapse Analytics
An Azure analytics service that brings together data integration, enterprise data warehousing, and big data analytics. Previously known as Azure SQL Data Warehouse.
5,138 questions
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. MartinJaffer-MSFT 26,211 Reputation points
    2022-06-15T16:49:02.257+00:00

    Hello and welcome to Microsoft Q&A @Kenny, Craig (EthosEnergy) .

    So, do I understand correctly, that your authentication alone takes 90 seconds, on average, no matter what you connect with? I can certainly see how this would cause a timeout in Synapse and many other applications.

    I ask, because taking more than a minute to authenticate is, well, so far beyond the norm as to be unreasonable in all the cases I can think of. I am not blaming you or anything, but I am concerned. I could look into whether there is a way to increase connection timeout, but I worry that your authentication provider has something bad happening, and ignoring the cause might make it worse.

    Imagine trying to log into your email, and waiting 2 minutes before even getting to load. As an end user, I would have pressed reload button after 25 seconds, thinking something broke.

    Modern applications would have done multiple retries by 30 seconds, for comparison.


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.