About MattWho

MattWho · ‎05-09-2017

@Sunil Neurgaonkar As a side note: No need to configure any of the TLS properties in your login-identity-providers.xml file. Since your authentication strategy is set to "SIMPLE", those property are all ignored and only the Manger DN and password are being used to connect to your LDAP.

MattWho · ‎05-09-2017

@Sunil Neurgaonkar It looks like you manually created your users.xml file rather then letting NiFi create it for you. Or you originally had teh initial admin identity configured as "cn=admin,dc=example, dc=org". Once the users.xml and authorizations.xml files are created the first time, changes to NiFi config files will not trigger any updates to these files. NiFi is trying to authorize your user "cn=admin,dc=example,dc=com"; however, this user does not exist in yoru users.xml file, so you are seeing the following error: 2017-05-0915:41:57,250 INFO [NiFiWebServer-17] o.a.n.w.a.c.AccessDeniedExceptionMapper cn=admin,dc=example,dc=com does not have permission to access the requested resource.ReturningForbidden response. A close look at your users.xml file provided above shows your user as: <useridentifier="99412284-acd9-3945-931b-362691f189ff"identity="cn=admin,dc=example,dc=org"/> Their is a mismatch between your ldap user DN and the DN of the user in the users.xml file. dc=com vs dc=org. You can simply manually correct this mismatch in the users.xml file and restart NiFi to fix your authorization issue. Thanks, Matt

MattWho · ‎05-08-2017

@Ninad Patkhedkar Was I able to address you question? Unfortunately there is no work around other then using FetchSFTP to actually pull the file content so that fileSize is updated; however, that is a complete waste of resources if you don't need to ingest the data. If you found this response helpful, please accept the answer. Thank you, Matt

MattWho · ‎05-08-2017

@HAR MAT You can also use NiFi's rest-api to start and stop processors using a script. https://nifi.apache.org/docs/nifi-docs/rest-api/

MattWho · ‎05-08-2017

@uttam kumar Where either of the above answers able to resolve your template issue? If you found either helpful, please accept the answer. Thank you, Matt

MattWho · ‎05-08-2017

@Gaurav Jain I don't know that i have any links that lead to exactly what you are looking for in just one tutorial. Here are series of links that may be helpful to you.... https://community.hortonworks.com/articles/16120/how-do-i-distribute-data-across-a-nifi-cluster.html https://community.hortonworks.com/articles/7882/hdfnifi-best-practices-for-setting-up-a-high-perfo.html https://community.hortonworks.com/questions/65360/can-someone-help-me-with-apache-nifis-basic-workin.html https://community.hortonworks.com/articles/97773/how-to-retrieve-files-from-a-sftp-server-using-nif.html Thanks, Matt

MattWho · ‎05-08-2017

@Gaurav Jain Each node in a cluster is responsible for working on its own FlowFiles. Each node is unaware of what FlowFiles other nodes are working on. If a NiFi processor component is working on a FlowFile at the time the Node goes down, the transformation work will start over once that the node is running again. A node disconnecting will not cause processing of FlowFiles to stop on the disconnected node. Processors that do transformation of FlowFile content will produce a new FlowFile once the transformation is complete. So if failure exists mid processing, the original remains on the incoming queue to the processor and the intermediate work is lost. This is how NiFi ensures no data loss occurs in unexpected failures. That being said Data plane High Availability (HA) is one of NiFi's roadmap items. Thanks, Matt

MattWho · ‎05-08-2017

@Gaurav Jain Please explain what you mean when you say "complete workflow not working". Screenshots may help if you can provide them.

MattWho · ‎05-08-2017

@Gaurav Jain When you find an answer that address your question, please accept that answer to benefit other who come to this forum for help. Thank you, Matt

MattWho · ‎05-08-2017

@Gaurav Jain The flow.xml.gz file contains everything (Processors, connections, controller services, etc. that make up your dataflow(s) on your canvas. If you try to make a change to a dataflow which has a disconnected node, you will get a response from Nifi that says changes are not allowed while a node is disconnected. You can take manual steps to delete the disconnected node from the cluster via the cluster UI. This will return control, but the node you deleted will not be able to rejoin cluster later (because flows will not match) without doing additional manual steps. Matt

Online	Offline
Last Visited	‎12-18-2025 12:23 AM

Member Since	‎07-30-2019 10:41 AM
Last Visited	‎12-18-2025 12:23 AM
Posts	3,406
Kudos received	1617

Cloudera Community

Re: Error importing NiFi workflow template from ve...

Re: Error importing NiFi workflow template from ve...

Re: How to elevate a default nifi user to admin - ...

Re: NiFi EnvokeHTTP - putting current date on HTTP...

Re: Invoking Nifi rest api in Data Flow

Re: Nifi not authorising the user

Re: Nifi not authorising the user

Re: ListSFTP processor not fetching file size

Re: How to configure a processor to run only once

Re: template upload issue

Re: Nifi Cluster setup for NIFI 1.1.2

Re: Nifi Cluster with Remote Process Group

Re: Nifi Cluster setup for NIFI 1.1.2

Re: Nifi Cluster setup for NIFI 1.1.2

Re: Nifi Cluster setup for NIFI 1.1.2