Hi guys It was upgrade time again on our side, we just upgraded from 1.19.1 to 1.20.0. Since 1.20.0 we do see significantly more SSH Connection Timeout errors on the PutSFTP processor…
PutSFTP Processor ERROR: 2023-02-16 07:44:07,905 ERROR [Timer-Driven Process Thread-50] o.a.nifi.processors.standard.PutSFTP PutSFTP[id=12563431-c40a-1af7-b09b-16de27d887b7] Unable to transfer StandardFlowFileRecord[uuid=a1adadb1-61f9-414f-99e5-aad4331165ef,claim=StandardContentClaim [resourceClaim=StandardResourceClaim[id=1676529847583-196507, container=default, section=923], offset=0, length=6582249],offset=0,name=myfile.avro.gz,size=6582249] to remote host nas.local.com due to org.apache.nifi.processors.standard.socket.ClientConnectException: SSH Client connection failed [nas.local.com:22]: net.schmizz.sshj.transport.TransportException: Timeout expired: 30000 MILLISECONDS; routing to failure net.schmizz.sshj.transport.TransportException: Timeout expired: 30000 MILLISECONDS I know that David Handermann implemented a fix (https://issues.apache.org/jira/browse/NIFI-9989) for SSHJ, but I don’t know if it really is related. May be it’s just a configuration issue (number of allowed concurrent connections?) on the SFTP Server side. Let’s make an example, let’s say we do have 50 PutSFTP processors to the same destination and all of them are getting data in an interval of 15min. Does NiFi keep the SSH connection established for this 50 processors or will it be closed after each flow has been transferred? If it isn’t closed after each flow, how can we influence the timeout? I see only the two timeouts below, which let me assume that it’s closed after each flow… But may be one of you guys can bring some light into the dark. [Background pattern Description automatically generated with low confidence] Cheers Josef
smime.p7s
Description: S/MIME Cryptographic Signature
