@Tarek Elgamal Assuming you are referring to settings for "Max Timer Driven Thread count"? That setting controls the max number of threads that can execute at one time. Does not guarantee any order to the execution of threads. NiFi's controller in the back ground does not operate under this thread pool. Both processors will be scheduled to run based on their configured run schedule. Those concurrent tasks then get stacked in a request queue waiting on one of the threads from that pool to service them. This way, every processor is eventually going to get a chance to run thier code. Also keep in mind that some processors work on batches of FlowFiles while others process one FlowFile per task. Also hard to say that each processed FlowFile will take same amount of time to complete an operation. Really depends on processor and what it is designed to do. Thanks, Matt ... View more

@Veerendra Nath Jasthi Glad to hear we got this all worked out... 🙂 Please take a moment to login and click the "accept" link for this answer to close out the thread. - Thank you, Matt ... View more

@Veerendra Nath Jasthi The screenshot you just attached shows a non secure NiFi running over HTTP on port 9090. There is no user authentication that will occur for a unsecured NiFi. User authentication and authorization will only occur for a secured NiFi running over https. Thanks, Matt ... View more

@Veerendra Nath Jasthi *** Forum Tip: Please try to avoid responding to an existing Answer by starting a new Answer. This makes following multiple response threads difficult. Instead use "add comment" to respond to a posted answer. - The attached image shows that the user who is currently logged in as ""CN=niifiadmin, OU=HORTONWORKS". Your comment says you expect to see this and that is what is being shown, so I am little confused. Sorry if I am missing something here. - Are you saying that you expected the UI to instead show ""CN=niifiadmin, OU=CLOUD.HORTONWORKS.COM"? - The UI is only going to display what is presented in the certificate being used for authentication. Try performing a verbose listing on your client certificate to see what the actual DN is. - Sharing your nifi-users.log, authorizers.xml, users.xml, and authorizations.xml files may shed some light on what is going on here. also sharing the verbose output of your client cert would help. - Thanks, Matt ... View more

@Mustafa Ali Qizilbash *** Forum Tip: please try to avoid responding to an existing answer by starting a new answer. Instead use "add comment" to respond an answer. - The Firefox version you are trying to use is to old. https://wiki.mozilla.org/Release_Management/Calendar - Firefox 17.0.10 was released back on October 29, 2013. The developer tools are very likely going to show some JS issues here. You need to upgrade to a newer version of Firefox or switch to a new version of another browser like Chrome. - Thank you, Matt ... View more

@Prakhar Agrawal Then your issue is going to be the backend validation that is going on. How much validation that is occurring depends on what you are doing. Shu's recommendation for disabling processors that are not running should help a great deal. - There is no such thing as "Max Cron Driven Thread Count". I am going to assume you meant "Max Event Driven Thread count." There is nothing you will add to your canvas that will use the "Event Driven" scheduling strategy. You physically need to change the configuration on a component to use "Event Driven". Event Driven is consider experimental and deprecated in favor of advance made with the Timer driven Scheduling strategy. By setting "Max Event Driven Thread count" to 50 you are creating a pool of 50 reserved threads. I recommend not using "Event Driven" Scheduling strategy anywhere and reducing the max Event Driven thread count setting to "1". Reducing the "Max Event driven thread count" setting will require a NiFi restart. ... View more

@David Miller Sorry for leaving out some of the details. The ListSFTP and FetchSFTP processors where originally developed and added to NiFi back in Apache NiFi 0.4.0. The 0.x versions of NiFi did not use zookeeper for cluster or state. ZK was introduced with the major redesign work that went into Apache NIFi 1.x. - To avoid issues for users upgrading from 0.x to 1.x+ versions of NiFi, the distributedMapCache properties remained in all the state keeping processors created prior to 1.x release. NiFi 1.x and newer version will automatically store state in ZK. Having the DistributeMapCache configured gives users who had state previously stored in a cache server to be read and NiFi would then write that state to ZK moving forward. - So in newer versions (NiFi 1.x +), there is no need to use the distributeMapCache property. - Thanks, Matt ... View more