Do you have a firewall in play between the two sites? I had a similar issue with our Palo Alto firewall. In my case, deep packet inspection was slowing down file transfers.
On Fri, Oct 11, 2024 at 7:41 AM <[email protected]> wrote: > Hello, > > thanks all for your reply. > > After check if the iperf3 tools and confirm with the network guys, it > seems network infra issue. It is very slow, we got a bandwidth is 100 > bytes/seconds :) > > Thanks > > Minh > > > *Envoyé:* vendredi 11 octobre 2024 à 12:09 > *De:* "stephen.hindmarch.bt.com via users" <[email protected]> > *À:* [email protected] > *Objet:* RE: bandwidth with Site2site > > Minh, > > > > Have you checked the app log to see if there are any errors related to S2S? > > > > If this is a secure system I would > > > > - Set the protocol to HTTP as this will force the communications over > HTTPS. > - Remember the remote process group (RPG) is acting as a client and > the host with the remote port is acting as the server. > - Ensure both hosts can trust each other’s certificates. > - Check the client host exists as a user on the server host. The > client is identified by the full DN from their certificate. You can add > users to users.xml. > - Check that the client host is included in the global policy > “retrieve site-to-site details” on the server host. > - Check that the client host is included in the object policy > “send/receive data via site-to-site” on the remote port you are trying to > access. (send for an output port, receive for an input port). > - Check both the remote port and the remote process group are enabled. > - Check that you can access the “Refresh remote” and “Manage remote > ports” menus on the RPG and that you can see the remote ports in the manage > menu. > > > > The problems I encountered were firstly that the CA for the certificates > were not in the trust chain for the other host. You have to check this in > both directions. > > > > Secondly that the DN as recorded in users.xml did not match the DN on the > certificate. Even spaces, punctuation and case matter. For example if > users.xml says “…; DC=Foo; DC=Com” but the certificate says “…, DC=foo, > DC=com” then this will cause problems. Fix the values in users.xml to match > the certificate. > > > > *Regards* > > > > *Steve Hindmarch* > > > > *From:* [email protected] <[email protected]> > *Sent:* Thursday, October 10, 2024 2:58 PM > *To:* usersnifi.apache.org <[email protected]> > *Subject:* bandwidth with Site2site > > > > > > Hello, > > We have a lot flowfiles stucks in the connection before s2s (raw mode). > > We are not sure if it is network or NIFI issues. > > > The S2S uses tcp connection or wraps to https ? > > Do you know how it is possible to test the bandwidth without NIFI ? > Between server A and B, we have only NIFI port opened. > > If you have some tips, it will help me. > > > > Thanks > > Minh > > > >
