Re: NiFi 1.4 Clustering Error: Cannot Replicate Request GET /nifi-api/flow/current-user

Ah ok, I see that you have a deeper issue there that probably needs to be addressed within the web-framework in the main project. Afraid I can't help with that, but I wish you luck! On Tue, Jan 30, 2018 at 6:09 PM Ryan H wrote: > Hi Dan, > > Thanks for the

Re: NiFi 1.4 Clustering Error: Cannot Replicate Request GET /nifi-api/flow/current-user

Hi Dan, Thanks for the info on the changes you made to the Docker image. I am essentially doing the same thing as I have built our own Docker and have a wrapper script that provides the ability to configure the nifi.properties file based on env variables at run time. The problem I am facing is

Re: NiFi 1.4 Clustering Error: Cannot Replicate Request GET /nifi-api/flow/current-user

Hi Ryan, I have proposed a small change to the Docker image which may help you here - https://github.com/apache/nifi/pull/2439 Essentially it exposes the port and hostname to be used within nifi.properties as environment variables which you can pass in at runtime. Perhaps the approach used will

Re: NiFi 1.4 Clustering Error: Cannot Replicate Request GET /nifi-api/flow/current-user

Good deal, thanks for getting back to me about it. I think that I may make some changes and potentially open a PR depending on what comes of it (I'll have to take a look at the workflow and all of that good stuff first). Cheers, Ryan H On Mon, Jan 29, 2018 at 12:55 PM, Bryan Bende

Re: NiFi 1.4 Clustering Error: Cannot Replicate Request GET /nifi-api/flow/current-user

Ryan, I'm not that familiar with Docker and DCOS, but I think what you said is correct... The issue is that you currently can't leave nifi.web.http.host blank because that will cause the "node API address" of each node to be calculated as 'localhost', which then means replication of requests

Re: NiFi 1.4 Clustering Error: Cannot Replicate Request GET /nifi-api/flow/current-user

Hi Bryan, Yes that makes total sense, and it is what I figured was happening. So whatever is configured for nifi.web.http.host is where api calls will go to, but this is also what jetty will bind to, correct? So in my case, I would have to have the additional property mentioned in

Re: NiFi 1.4 Clustering Error: Cannot Replicate Request GET /nifi-api/flow/current-user

Ryan, I remember creating an issue for something that seems similar to what you are running into: https://issues.apache.org/jira/browse/NIFI-3642 Long story short, I believe you do need to specify a value for nifi.web.http.host because that will be used to replicate requests that come in to the

NiFi 1.4 Clustering Error: Cannot Replicate Request GET /nifi-api/flow/current-user

Dev Team, I am running into an interesting issue while trying to cluster NiFi in a containerized environment (Docker containers running on DC/OS cluster) and I am somewhat stuck with what to do. I am starting with getting just 2 NiFi nodes with a single external zookeeper instance (just to get