Mark, There are some improvements which can be made in a clustering setup. Maybe this one is related? https://issues.apache.org/jira/browse/NIFI-1190?filter=-2
Andrew From: Mark Payne <marka...@hotmail.com<mailto:marka...@hotmail.com>> Reply-To: "users@nifi.apache.org<mailto:users@nifi.apache.org>" <users@nifi.apache.org<mailto:users@nifi.apache.org>> Date: Friday, April 29, 2016 at 11:09 AM To: "users@nifi.apache.org<mailto:users@nifi.apache.org>" <users@nifi.apache.org<mailto:users@nifi.apache.org>> Subject: Re: NiFi Clustering Issue Chris, Under the hood, NiFi is using an embedded Jetty Server to handle HTTP Requests. The documentation in the web server indicates: The network interface this connector binds to as an IP address or a hostname. If null or 0.0.0.0, then bind to all interfaces. So if not specified, it should be binding to all interfaces. If this is not what you are experiences, then I do believe that it is a bug that should be addressed. Thanks -Mark On Apr 29, 2016, at 11:02 AM, Christopher Wilson <wilson...@gmail.com<mailto:wilson...@gmail.com>> wrote: I spent some time over the past few days attempting to cluster 3 NiFi nodes. I thought I had the nifi.properties file properly configured, but kept getting "unexpected error occurs" from the UI. Long story short, you have to specifically set the nifi.web.http.host setting equal to your hostname or IP address and not empty, which defaults to localhost. Does anyone feel this is a bug or is this behavior intended? I was thinking if nifi.cluster.is.node=true then nifi.web.http.host should equal `hostname`, gethostbyname/gethostbyaddr, or something other than localhost. Happy to create a bug if the consensus is "yes, it's a bug" or at least update the docs to reflect that this setting must not be empty. -Chris
