HI Matt, Thanks for all your valuable inputs, we configured the SAN disk to nifi cluster based on the above recommendations. Regards Girish V G ... View more

@Darryl  So the downstream system that putUDP is sending to is complaining the size of the datagram is too large when batch size is set to 50.   When using batching in ListenUDP processor each datagram is delimited by a new line character.  You could add a processor like splitText between ListenUDP and PutUDP to split these FlowFiles into smaller FlowFiles before sending to putUDP.  Since a batch size of 30 seemed to work well for you, I would try increasing Batch setting in ListenUDP to 60 and set the "lineSplit Count" in Split text to 30. As far as "When i tried bumping up the concurrent threads from 1 to 2, it caused the video to be extremely blurry", I am guessing maybe the multi-threading is resulting the packets out of order resulting in your extremely blurry video?  If that is the case, you'll need to keep your flow single treaded.  And if order of processing FlowFiles is important downstream connections should be configured with FirstInFirstOutPrioritizer prioritizer.  This does not mean you can then use multiple threads, but makes sure downstream processors take FlowFiles from upstream connections in this order. Please help our community grow and thrive. If you found any of the suggestions/solutions provided helped you with solving your issue or answering your question, please take a moment to login and click "Accept as Solution" on one or more of them that helped. Thank you, Matt ... View more

@AlokVenugopal  The "/nifi-api/access/token" endpoint is used by the ldap-provider or kerberos-provider NiFi login providers. Since you are using an OIDC (SSO) provider, you would need to obtain the token from that provider.     You can utilize the developer tools available in most browsers to capture the rest-api call being made to NiFi from you browser. While I do not have a setup utilizing Azure AD, I'd expect you should be able to see the redirect to the Azure endpoint to get the token. Please help our community grow. If you found any of the suggestions/solutions provided helped you with solving your issue or answering your question, please take a moment to login and click "Accept as Solution" on one or more of them that helped. Thank you, Matt   ... View more

Hi @Shelton Thanks so much for detailed information @MattWho  thanks much for the reply and apologies for short info.  based on above information was able to create SSL certificates and generate Keystore and trustore in jks format . initially i was not configured CA file into truststore so faced some issue 2. then i did not added nifi nodes entries as intial identity in autherizers.xml file so above issue occured . i followed cloudera blogs where you had informed https://community.cloudera.com/t5/Support-Questions/insufficient-permissions-untrusted-proxy/m-p/366443#M239582  based on these i was able to resolve and 3 node cluster with external zookeeper was able to up.  i appreciate your kind help and your time here . much thanks to both 🙂 ... View more

@MattWho  Hi Matt, I made changes in my test based on the description you provided and I've been able to get the Groovy code working in ExecuteScript also. Thanks very much for your help! Back to the counter now. 🙂 ... View more

@nifi-srinikr, Did the response help resolve your query? If it did, kindly mark the relevant reply as the solution, as it will aid others in locating the answer more easily in the future.  ... View more

@ajignacio  The PutMarkLogic processor is not a component bundled and shipped with Apache NiFi, so I am not familiar with it.  You may want to raise your issue directly with those who developed this connector and include your Apache NiFi version specifics as well: https://github.com/marklogic/nifi/issues Please help our community grow. If you found any of the suggestions/solutions provided helped you with solving your issue or answering your question, please take a moment to login and click "Accept as Solution" on one or more of them that helped. Thank you, Matt ... View more

@jirungaray  The DistributedMapCacheServer controller service sets up a cache server which will keep all cached objects in NiFi's JVM heap memory.  This cache is lost if the controller service is disabled/re-enabled or if NiFi were to restart unless the "Persistence Directory" is configured.  The persistence directory is some local disk directory where cache entries are persisted in addition to those cache entries also being in Heap memory.  The persistence to disk allows the in memory cache to be reloaded if the cache server is disabled/re-enabled or NiFi is restarted.  I assume this is the cache server you are currently using. Matt ... View more