@krishnaraj_v13    The error output is telling you that your NiFi node(s) have not been granted the proxy policy in your NiFi Registry.  Your NiFi-Registry policies are managed locally within NiFi-Registry. Your NiFi is setup to use Ranger ti handle authorizations and i see you mentioned you granted your NiFi nodes /proxy in Ranger, but these policies only apply for NiFi and not NiFi-Registry. Based on the authorizers.xml shared from NiFi-Registry, I can see you defined your NiFi nodes as local users in the file-user-group-provider, but did not also configure those nodes in the file-access-provider.  The file-access-provider actually created the initial policies in the authorizations.xml file and assigns users to those created policies. Note: Both NiFi and NiFi-Registry will only create the users.xml and authorizations.xml files if they do not already exist.  So modifications to these providers in the authorizers.xml file will not result in modifications to these files if they already exist. To resolve the error you are seeing you need to login to your NiFi-Registry with your initial admin user and grant your NiFi nodes the the following policies: 1. "Can proxy user requests".  (solves current error) 2. "Can Manage buckets" --> Read.  (allows NiFi nodes to read buckets to see if new flow versions have been committed) Hope this helps, Matt ... View more

Hi @Krishnaraj V! I'm not sure if I get it, but are you trying to kill the consumer that you're creating right? If so, then I'd try to grep the kafka.tools.ConsoleConsumer + the topic name. Would be like: sleep 0.5m for line in $(cat /root/backup/listtopics.txt) do echo $line sleep 1m ps -ef | grep -i kafka.tools.ConsoleConsumer | grep -i $line| grep -v grep | awk '{print $2}' | xargs kill - 9 done Hope this helps! ... View more