Member since
10-23-2017
4
Posts
0
Kudos Received
0
Solutions
10-02-2019
07:52 AM
It is absolutely possible to do this. However somethings need to be considered: With a multi node Nifi cluster, the local storage must be a single location usually the primary node. This data will not be local to the rest of the cluster nodes. The location should be separate from OS partition and the required nifi repository partitions. This is to avoid corrupting these partitions in the chance local storage consumes all available space. In past projects I have used primary node, with a separate partition to storing files local to NiFi Primary Node. These files are then used outside of NiFi for other purposes. In some projects these files are picked up in NiFi in separate flows, and then re-distributed into the cluster for processing across all nodes. The primary use case here was audit received files directly to disk by Team 1. Some time later Team 2 access files for processing. In this sample Team 1 and Team 2 are completely separate with Security Group based access to nifi (they cannot see each others flows).
... View more
07-30-2018
01:59 PM
@Sri Bet When a node attempts to join an existing cluster there are 3 files that are checked to make sure they match between the node connecting and the cluster: 1. flow.xml.gz (Contains everything you have configured/added via the NiFi UI.) 2. users.xml (Contains all users added via the NiFI UI. This file will not exist if you are not using NiFi's default file based authorizer. Also will not exist if NiFi is not running secured) 3. authorizations.xml (Contains all authorization policies which have been granted to above users added via the NiFI UI. This file will not exist if you are not using NiFi's default file based authorizer. Also will not exist if NiFi is not running secured) - I am not sure why one of your nodes had a mismatch in your authorizations.xml file. Perhaps while this node was not in the cluster a new policy was granted to a user? - Deleting the users.xml and authorizations.xml files is not the best resolution. When these files do not exist, NiFi will create on the basic authorizations for the initial admin identity and nodes defined in the authorizers.xml file. deleting these files will result in loss of any other authorizations that ay have been granted later. - The best fix is to copy the users.xml and authorizations.xml from another node to the node having issues. - Thank you, Matt
... View more