@sally sally The processor will only list the files which were not included in the first listing it created. ... View more

@Simon Jespersen Run this command on your keytab file: klist -kt /etc/security/keytabs/kafka.service.keytab Whatever is displayed should be your principal in the jaas-client.config file. ... View more

@Simon Jespersen Create a jaas-client.config file with the principal and keytab for NiFi to use to connect to the broker. Here is one I use for my NiFi: KafkaClient { com.sun.security.auth.module.Krb5LoginModule required useKeyTab=true storeKey=true keyTab="/etc/nifi/2.1.1.0-2/0/kafka.service.keytab" principal="kafka/hdp-24-03.openstacklocal@SMENIFI.COM"; }; Make sure to put it in a directory that the nifi user can access, mine is located in the /etc/nifi/2.1.1.0-2/0/ directory. Then add the highlighted property to the Advanced nifi-bootstrap-env section in Ambari This file must be on all of the nodes in your cluster. ... View more

@Simon Jespersen What version of NiFi are you using? ... View more

@Simon Jespersen You need to configure two additional properties in the processor: Change the Kerberos Service name to just kafka ... View more

@mayki wogno Did this resolve your issue? ... View more

@mayki wogno Are you still seeing this issue? ... View more

@haM@ In the GetFTP processor, you can change that property to use a different port. Try using 139 or 445 to see if it works? ... View more

@Wesley Bohannon Check these properties, the default values are 3 seconds, change them to 30 seconds and see if it helps nifi.zookeeper.connect.timeout nifi.zookeeper.session.timeout I would also check these properties, the default values are 5 seconds, change them to 30 seconds also nifi.cluster.node.connection.timeout nifi.cluster.node.read.timeout Finally, check this property, change it from the default of 10 to 40 or 50 nifi.cluster.node.protocol.threads ... View more