Hi Ben, From the error, it appears the HTTPS handshake (to identify the endpoint) is successful but the communication over the RAW transport is failing.
Can you share the approximate size of your flowfiles being transmitted between the two endpoints? If the contents are large, it may require increasing the timeout to a value like 300 seconds to allow the socket transmission to complete. You may also want to investigate changing the transport protocol from RAW to HTTP, which will allow for slightly different communication (RAW = HTTP(S) handshake, socket transport; HTTP = HTTP(S) for both). Do you have any network traffic monitoring (Wireshark, etc.) where you can evaluate the actual data being transmitted between the nodes? If you see data transfer simply not completing by the time the timeout occurs, you basically have two options - raise the timeout or perform a split on the content within the transmitting NiFi and reassemble at the receiving end. Koji Kawamura put some detailed diagrams explaining the various transport protocols on the wiki [1]. Hopefully this helps or at least leads you down the right path. With additional details we may be able to offer further assistance. [1] https://cwiki.apache.org/confluence/display/NIFI/Support+HTTP%28S%29+as+a+transport+mechanism+for+Site-to-Site <https://cwiki.apache.org/confluence/display/NIFI/Support+HTTP(S)+as+a+transport+mechanism+for+Site-to-Site> Andy LoPresto alopre...@apache.org alopresto.apa...@gmail.com PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B 2F7D EF69 > On Feb 6, 2020, at 4:22 PM, Fullarton, Ben MR <ben.fullar...@defence.gov.au> > wrote: > > UNCLASSIFIED > > Hi Apache NiFi Team, > > Hoping you can help with an error Im getting with our NiFi1.8.0 Site-to-Site > running over a low bandwidth network. > > Basically we are testing the performance of NiFi over poor networks . Our 2 > NiFi servers are built on Windows 2016 servers with site-to-site > communications enabled and secured with SSL certificates. We have configured > the servers as follows; > > Sender (Client) NiFi Server > OS: Windows Server 2016 standard > NiFi Version: 1.8.0 > NiFi.Properties: > # Site to Site properties: > nifi.remote.input.host=senderhostname > nifi.remote.input.secure=true > nifi.remote.input.socket.port=8888 > nifi.remote.input.http.enabled=true > nifi.remote.input.http.transaction.ttl=600 sec > nifi.remote.contents.cache.expiration=10 secs > Remote Process Group details: > URLs: https://Destinationhostname:8443/nifi/ > Transport Protocol: RAW > Communication Timeout: 60 sec > Yield Duration: 1 sec > > Destination (Server) NiFi Server > OS: Windows Server 2016 standard > NiFi Version: 1.8.0 > NiFi.Properties: > # Site to Site properties: > nifi.remote.input.host=destinationhostname > nifi.remote.input.secure=true > nifi.remote.input.socket.port=8888 > nifi.remote.input.http.enabled=true > nifi.remote.input.http.transaction.ttl=600 sec > nifi.remote.contents.cache.expiration=10 secs > > > So far, sending files between the servers via remote port group is fine under > normal conditions. However when we restrict the network link throughput > (channel capacity) via our network emulator (iTrinegy INE) to 100kbps the > NiFi client (sender) fails to transfer data and provides the following error > message [sensitive details have been reacted]; > > RemoteGroupPort[name=senderhostname,targets=https://destinationhostname.fqdn:8443/nifi/] > failed to communicate with remote NiFi instance due to java.io.IOException: > Failed to confirm transaction with Peer[url=nifi://destinationhostname:8888] > due to java.net.SocketTimeoutException: Timed out reading from socket > connected to destinationhostname:8888 > > Consequently, the files stop transmitting to the destination NiFi server. > > Can you please advise on how we can fix this error whilst maintaining a > network link throughput (channel capacity) less than or equal to (≤) 100 > Kbps? Perhaps we may be able to change some aspect of the Nifi configuration > or underlying configuration files. > > If you are able to provide any additional guidance about configuring NiFi to > work over low throughput, high latency and high packet loss links it would be > greatly appreciated. > > If not able to provide us advice, are you able to suggest someone who may > assist us? > > Many thanks > > > Kind Regards, > > Ben Fullarton > Systems Engineer > Contractor to Defence > Ph: 02 6265 0158 > Mob: 0427 800 745 > email: ben.fullar...@defence.gov.au<mailto:ben.fullar...@defence.gov.au> > IMPORTANT: This email remains the property of the Department of Defence. > Unauthorised communication and dealing with the information in the email may > be a serious criminal offence. If you have received this email in error, you > are requested to contact the sender and delete the email immediately. > >
