Site-to-site is much more versatile than multi-DC communications (though this is a great use case for this NiFi's feature). S2s can link multiple clusters (or standalone instances), can even connect a cluster to itself (for data re-distribution), as well as used for MiNiFi to NiFi communication. It's also bi-directional, meaning it can be push/pull in either direction. At the end of the day this means you will be able to communicate e.g. over a corporate HTTP proxy regardless of the inbound/outbound firewall rules, there's enough flexibility to accommodate these scenarios in s2s. Read up more here https://nifi.apache.org/docs/nifi-docs/html/user-guide.html#site-to-site ... View more

@Avijeet Dash Every Node in a NiFi cluster run with their own repositories, flow.xml.gz, and work with their own set of data. Nodes in a cluster are unaware of what data other nodes in the cluster are working on. Once a cluster coordinator is elected all nodes send heartbeats to that node. Nodes cannot share repositories. When you access the UI via any Node in the cluster, the UI will show the cumulative stats of the entire cluster to the user. The centralized management aspect comes in to play here. Any changes you make within NiFi (no matter which node UI you are logged into) will be replicated to all nodes in the cluster. Thanks, Matt ... View more

Hi Avijeet. This is currently not possible, but do take a look at the following proposal to understand where things are going in the future: https://cwiki.apache.org/confluence/display/NIFI/Configuration+Management+of+Flows ... View more