@lv_antel Welcome to the Cloudera Community! As this is an older post, you would have a better chance of receiving a resolution by starting a new thread. This will also be an opportunity to provide details specific to your environment that could aid others in assisting you with a more accurate answer to your question. You can link this thread as a reference in your new post. Thanks. ... View more

I encountered the same error. After a few days of trying I decided to give up. Just go to Hbase config on Cloudera Manager UI and turn "hbase.security.authentication" to "simple" and "hbase.thrift.security.qop" to "none"   ... View more

add this in spark service in CM > Spark > Configuration >Spark Client Advanced Configuration Snippet (Safety Valve) for spark-conf/spark-env.sh =export HADOOP_CONF_DIR=/etc/hadoop/conf ... View more

Yes, we are currently stuck on 11.0.9 (rather than 11.0.9.1). But that is not really an acceptable solution in the longer term. We should be able to use the latest JDK 11 with all security patches etc, for current and future versions of the JDK. ... View more

@Boenu  Beginning with Apache NiFi 1.12 a change was implemented that changed the default anonymous access to static resources to false.  This was done as part of https://issues.apache.org/jira/browse/NIFI-7170. This change also added the ability to add an additional property to the nifi.properties file to restore the behavior to that of Apache NiFi 1.11 and older versions:  nifi.security.allow.anonymous.authentication=true   The above restores previous behavior while work is done to change the how NiFi handles access to these static endpoints.  The following Jiras cover that work: https://issues.apache.org/jira/browse/NIFI-7849 https://issues.apache.org/jira/browse/NIFI-7870   Hope this helps, Matt ... View more

Hi SherKhan, Based on the screenshot, you have two conditions configured for the warning trigger. The first one will trigger if the free space falls below 5GB, the second one will trigger once the disk utilization is higher than 50%. The disk belonging to master.ndctech.net has 55.53% of it's capacity used, and so the warning is triggered. If you consider this to be a false alarm, you should raise the warning threshold from 50% to 70% perhaps. Kind regards, Gyuszi ... View more

@rbloughThank you for the continued support.   2) The command is being run as the hdfs user.   1) The detailed output showed that there are 603,723 blocks in total. Looking at the HDFS UI, the Datanodes report having 586,426 blocks each.   3) hdfs fsck / -openforwrite says that there are 506,549 blocks in total.   The discrepancy in block count seems to be there still. Below are the summaries of the different fsck outputs.   hdfs fsck / -files -blocks -locations -includeSnapshots Status: HEALTHY Number of data-nodes: 3 Number of racks: 1 Total dirs: 64389 Total symlinks: 0 Replicated Blocks: Total size: 330079817503 B (Total open files size: 235302 B) Total files: 625308 (Files currently being written: 129) Total blocks (validated): 603723 (avg. block size 546740 B) (Total open file blocks (not validated): 122) Minimally replicated blocks: 603723 (100.0 %) Over-replicated blocks: 0 (0.0 %) Under-replicated blocks: 0 (0.0 %) Mis-replicated blocks: 0 (0.0 %) Default replication factor: 3 Average block replication: 3.0 Missing blocks: 0 Corrupt blocks: 0 Missing replicas: 0 (0.0 %) Blocks queued for replication: 0 Erasure Coded Block Groups: Total size: 0 B Total files: 0 Total block groups (validated): 0 Minimally erasure-coded block groups: 0 Over-erasure-coded block groups: 0 Under-erasure-coded block groups: 0 Unsatisfactory placement block groups: 0 Average block group size: 0.0 Missing block groups: 0 Corrupt block groups: 0 Missing internal blocks: 0 Blocks queued for replication: 0 FSCK ended at Wed Sep 30 12:23:06 CEST 2020 in 23305 milliseconds hdfs fsck / -openforwrite Status: HEALTHY Number of data-nodes: 3 Number of racks: 1 Total dirs: 63922 Total symlinks: 0 Replicated Blocks: Total size: 329765860325 B Total files: 528144 Total blocks (validated): 506549 (avg. block size 651004 B) Minimally replicated blocks: 506427 (99.975914 %) Over-replicated blocks: 0 (0.0 %) Under-replicated blocks: 0 (0.0 %) Mis-replicated blocks: 0 (0.0 %) Default replication factor: 3 Average block replication: 2.9992774 Missing blocks: 0 Corrupt blocks: 0 Missing replicas: 0 (0.0 %) Blocks queued for replication: 0 Erasure Coded Block Groups: Total size: 0 B Total files: 0 Total block groups (validated): 0 Minimally erasure-coded block groups: 0 Over-erasure-coded block groups: 0 Under-erasure-coded block groups: 0 Unsatisfactory placement block groups: 0 Average block group size: 0.0 Missing block groups: 0 Corrupt block groups: 0 Missing internal blocks: 0 Blocks queued for replication: 0 FSCK ended at Wed Sep 30 12:28:06 CEST 2020 in 11227 milliseconds    ... View more

There weren't any processor errors, but NiFi logs really helped figure out the problem with network permissions. Thanks, Julius! ... View more