Hi @Andy LoPresto, Just want to follow up on ticket https://issues.apache.org/jira/browse/NIFI-3834 Is it prioritized for this year? Thanks. ... View more

Hi @Matt Clarke, Kubernetes master ip is different with nifi-0.svc, which is an external pod dns. So nifi-0.svc can't been access outside of Kubernetes. I feel that nifi.web.proxy.host may work for this case. Is there a way to disable the Request Header Check? Thanks. ... View more

Hi @Matt Clarke, Thank you for your clarification. Yes, I use the secure mode. In NiFi v1.4, I setup the two properties as below. nifi.web.https.host= nifi-0.svc nifi.web.https.port= 9443 Please note nifi-0.svc is the pod name of the first nifi node. Then, we have nifi-1.svc, nifi-2.svc in the setting of the other nifi nodes. Normally, if we want to access NiFi cluster outside of Kubernetes, we have to use the master node ip of Kubernetes. e.g. https://master-ip:9443/nifi/ Above worked perfectly before. Now my question is in NiFi v1.5. What should I set for nifi.web.https.host? 1. If I don't do any changes, it gives me "Invalid Host Header" error. 2. If I set it as nifi.web.https.host = master-ip in all three nifi nodes in the cluster. The error in log is: 2018-01-18 17:10:28,017 ERROR [NiFi logging handler] org.apache.nifi.StdErr Failed to start web server: Cannot assign requested address One thing confuses me is: I have three nifi nodes in a cluster. Should I set "nifi.web.https.host" in three nifi.property file to the same ip value? BTW, are we able to disable this request header check? Thanks. ... View more

Hi @Matt Clarke, Thank you for your response. Is it nifi.web.http(s).host or nifi.web.proxy.host? I have already put nifi.web.https.host = the-nifi-node-ip We deploy nifi cluster in Kubernete, What should I change it to? Thanks. ... View more

Hi @Benoit Rousseau, Thank you for your response. For the jmx_exporter option, my main trouble is where can I find or create the "nifi.yml". I found a couple of template for Kafka and Cassandra. But How do I know the existing jmx metrics in NiFi. I didn't find any documents on it. Would you please share a template? Thanks. ... View more

@Abdelkrim Hadjidj Perfect! Much clearer now. Thanks. ... View more

Hi @Abdelkrim Hadjidj Thank you for your response. Very helpful. I do have retrieve site-to-site details policy set for all nodes in the cluster. And the RPG can connect and refresh. However, the "Retrieve Data via site-to-site" item is grey and disabled for the Input Port. Then, I found below document. https://community.hortonworks.com/questions/67255/how-can-i-set-an-inputoutput-ports-for-a-remote-pr.html It says Input Port must be in the root level to enable S2S. I was wondering is it a limitation? How about I want to put my entire flow in a processor group? BTW, after S2S is enabled. I still find the file distribution is not even. One node processes more than the others. Is there a way to control the distribution? Thanks. ... View more

Hi @Matt Burgess Thank you for your response. I setup RPG and an Input Port. It seems RPG can connect the remote nifi instance. However, when I click Manage Remote Ports, it can't display the input port I added. BTW, I use a secured 3 node cluster with S2S enabled. Please see the attached screenshot. Did I miss anything? Thanks. ... View more