Sorry @Neil_1992 where could I find nifi.service file, to add this property ? ... View more

Thinks for all your suggestion.  By increasing HEAP size issue resloved. Thanks, Suryakant ... View more

Thank you. ... View more

Hey! Can you please explain more how to create an apache NIFI template?!  Actually I need to know is it possible to generate an Apache NiFi template using JAVA ?? ... View more

Want to add some clarity to this last comment: ListenHTTP requires 2-way TLS when enabled if a SSLContextService has been configured with a truststore.  The truststore is used to trust the client certificate presented by the client, for the purpose of authentication, connecting to this secured ListenHTTP processor.     If only a keystore and no truststore is configured in the SSLContext service, the ListenHTTP will not require that clients present a client certificate. The server certificate from the keystore will be presented to the client so the client can verify that it trusts the server (NiFI listenHTTP jetty server) that it is connecting with. ... View more

@MattWho I've been trying these steps and somehow the SAN keeps getting removed when I import/export to JKS. How do I get the SAN extension to be with the key inside of the keystore file? I'm totally stuck! ... View more

Hi Anand,   I just saw your post about NiFi to GCP. I repeated the same process and the ControllerService showed errors to me:    Failed to invoke@OnEnabled method due to org.apache.nifi.reporting.InitializationException: java.io.lOException: Error reading credentials from stream, 'type' field not specified .java.io.lOException: Error reading credentials from stream, 'type' field not specified   Do you have 'type' field on your credentials json file? Thanks.   ... View more

The error message was not very clear but it works for HDF 1.9.2. Thanks a lot! ... View more

@mayki wogno It is very possible the slow responses are the result of a very high number of http requests coming in to your NiFi nodes. - The main contributor to high number of requests are Remote Process Groups (RPG). It is very common for users to design dataflows that use many RPGs throughout their canvas to redistribute FlowFiles across their cluster. Each RPG is pinging the target http Nifi instance for the current Site-To-Site (S2S) details. Assume you have a 5 node cluster with 20 RPGs all pointing back to same cluster as an example. That means that every RPG on every node is requesting S2S details every 30 seconds. That alone is 100 HTTP request every 30 seconds. There is a improvement implemented through https://issues.apache.org/jira/browse/NIFI-4598 (fixed in NiFi 1.5) to improve how RPGs work in this scenario. - Additionally NiFi 1.2 is hardcoded to allow only 100 concurrent http requests which can lead to temporary unavailable of the http endpoint. This was resolved in an improvement covered via https://issues.apache.org/jira/browse/NIFI-4143 (fixed in NiFi 1.4) which allows users to increase the number of allowed concurrent http requests. - Another suggestion to improve http endpoint performance would be to make sure your RPGs are configured to use the "RAW" transport instead of "HTTP". While S2S details are still retrieved over http, the transfer of FlowFiles would be sent over a dedicated socket port instead of over http port. - Upgrading to Apache NiFi 1.5 will include both of the fixes above. HDF 3.1 is based off Apache NIFi 1.5. - Thank you, Matt - If you found this answer addressed your question, please take a moment to login and click "accept". ... View more

In Apache NiFi 1.5.0 (not yet released at the time of this writing), SelectHiveQL (via NIFI-4473) will have a property to Normalize Names for Avro, so you won't have to do the alias. ... View more