Hi NIFI Team, I am reaching out to you for the information regarding Remote process group. Please find the below details about NIFI and system setup we are using: NIFI version: 1.21.0 Environment details: 3 NIFI clusters for 2 NIFI servers and one NIFI client with 1TB storage. Each cluster have 3 instances of NIFI.
use case: * We are having three NIFI clusters, where remote process group is running in one cluster which is RDC site(site-to-site NIFI client), SiteA (site-to-site NIFI server 1) and SiteB (site-to-site nifi server 2). * From SiteA and SiteB, only one NIFI server is reachable. If one goes down the other will starts working. Here SiteA NIFI server is currently running and RDC NIFI client is able to do data transmission between RDC NIFI client and SiteA nifi server. * When SiteA NIFI server goes down we are trying to update the SiteB nifi server URLs to expect site-to-site communication between RDC NIFI client and SiteB NIFI server. Problem statement: * Unable to stop the remote process group manually from NIFI UI to update the URLs of SiteB. * Observed once SiteA is not reachable, the remote process group in RDC NIFI client were not accepting any request ie., stop, edit, delete. Note: Three NIFI clusters are in three different environments. * Observed once we start SiteA NIFI server process we can able to stop the remote process group running in RDC client and able to update the URLs with SiteB NIFI server URLs. * If SiteA NIFI is not reachable then we are observing this issue in RDC NIFI client where unable to remote process group to update URLs. Expectation: User should able to stop, edit or delete the Remote process group running in RDC NIFI client when the NIFI server which is communicating with RDC NIFI client becomes unreachable. Please find the attachments of Remote process group highlighting the state of it. Apologise if there is any confusion created in the explanation. Need inputs to understand more to resolve the above issue. Please let us know if there is any other information needed. Thaks & Regards, Dharani Tirumanyam.
