We're using docker, and in our failover scenario the machine is rebooted and/or the docker system is restarted.
We're currently volume mapping the following : - /srv/nifi/flow/archive:/opt/nifi/nifi-1.2.0/conf/archive:Z - /srv/nifi/flows:/opt/nifi/nifi-1.2.0/conf/flows:Z - /srv/nifi/content_repository:/opt/nifi/nifi-1.2.0/content_repository:Z - /srv/nifi/database_repository:/opt/nifi/nifi-1.2.0/database_repository:Z - /srv/nifi/flowfile_repository:/opt/nifi/nifi-1.2.0/flowfile_repository:Z - /srv/nifi/provenance_repository:/opt/nifi/nifi-1.2.0/provenance_repository:Z - /srv/nifi/work:/opt/nifi/nifi-1.2.0/work:Z - /srv/nifi/logs:/opt/nifi/nifi-1.2.0/logs:Z Are you referring to the local state management provider value (default /opt/nifi/nifi-1.2.0/state/local) ? If so I guess volume mapping that folder should fix it ? Would that be the right thing to do ? -- View this message in context: http://apache-nifi-users-list.2361937.n4.nabble.com/Nifi-clusters-duplicate-nodes-shown-in-cluster-overview-tp1966p1972.html Sent from the Apache NiFi Users List mailing list archive at Nabble.com.