Partition level HDFS directory disk usage is not avaible since this works on gievn direceoty path only and not at the disk level.  Thank you        ... View more

This is not a permission issue at this point but more of an issue between NameNode and DataNode. I would request you start a new thread for HDFS. Thank you  ... View more

PublishKafka writes messages only to those Kafka nodes that are leaders for a given topic: partition. Now it's Kafka internal job to keep the In-Sync Replicas in sync with its leader. So with respect to your question: When the Publisher client is set to run ,client sends a (read/write) request the bootstrap server, listed in the configuration bootstrap.servers to get the metadata info about topic: partition details, that's how the client knows who are all leaders in given topic partitions and the Publisher client writes into leaders of topic: partition  With "Guarantee single node" and if kafka broker node goes down which was happen to be a leader for topic: partition then Kafka will assign a new leader from ISR list  for topic: partition and through Kafka client setting metadata.max.age.ms producer refreshed its metadata information will get to know who is next leader to produce.   If you found this response assisted with your issue, please take a moment and click on "Accept as Solution" below this post. Thank you ... View more

This error has to do with the schema used in Record Writer controllers used by ExecuteSQLRecord. I would validate the provided schema and check if it is in the correct Avro format as it Avro schema parser is complaining about an illegal character in the provided schema.    If you found this response assisted with your issue, please take a moment and click on "Accept as Solution" below this post. Thank you ... View more

At a minimum, this is required in NiFi to connect to the Hdfs service secured by Kerberos. 1. Copy of core-site.xml and hdfs-site.xml file from hdfs cluster needs to be placed on nifi host to be able to configure in for Hadoop Configuration Resources property  2. Kerberos user principal and copy of keytab file on each nifi node to able to use by KeytabCredentialsService or directly configured in processor. 3. From NiFi hosts, the user who is running the nifi application "by default is nifi " should be able to obtain Kerberos tickets by using the user principal and keytab file configured in processor at  step2 ,  from KDC server which is used by HDFS Service, so krb5.conf Kerberos client file needs to be updated to respective kdc realm details.    If you found this response assisted with your issue, please take a moment and click on "Accept as Solution" below this post. Thank you ... View more