Hi @noekmc , It is recommended to turn off Tuned on RHEL8 as its being used to set the processor c-state and act as a way to control power utilisation. So as far as recommendation goes, it's good to turn it off and the Doc needs to be updated to include RHEL8.   -- Was your question answered? Please take some time to click on “Accept as Solution” below this post. If you find a reply useful, say thanks by clicking on the thumbs up button. ... View more

Hi @KCJeffro ,   The best possible way would be to change the log level for the thread 'org.apache.hadoop.hdfs.server.blockmanagement.BlockPlacementPolicy' to 'ERROR'. Do the following: Navigate to Cloudera Manager > HDFS > Config > search for 'NameNode Logging Advanced Configuration Snippet (Safety Valve) log4j_safety_valve' Add the following property: log4j.logger.org.apache.hadoop.hdfs.server.blockmanagement.BlockPlacementPolicy=ERROR ... View more

Hi @Ben1978    Spark 3.3 will be a compatible with CDP 7.1.8 which is yet to be released. ... View more

Hi @BORDIN , Are you able to copy any other files to hdfs using hdfs dfs -put? Does this happen all the time?   This problem can be caused by the range of different issues that can cause the datanode block reports being delayed from reaching the namenode or the namenode being delayed when processing them.   Can you check the Namenode log for the same time when put was done for any WARN/ERRORS.   If the Namenode is busy, we can perform more retries and thereby more time for Namenode for the block write to complete.   - Go to Cloudera Manager -> HDFS -> Configuration -> HDFS Client Advanced Configuration Snippet (Safety Valve) for hdfs-site.xml and add an entry like following: <property> <name>dfs.client.block.write.locateFollowingBlock.retries</name> <value>10</value> </property> - Save changes - Restart the stale services and deploy the client configuration.      ... View more

Hi @yagoaparecidoti ,   Yes, as you are using Ambari to manage the cluster, you can add the property as follows :   Ambari -> HDFS -> Configs -> Advanced -> Custom hdfs-site -> Add Property dfs.client.block.write.replace-datanode-on-failure.policy=ALWAYS ... View more

Hi @noekmc    The alert saying "Requires Server Restart" for the config properties is expected to be there to help administrators to run the "systemctl restart cloudera-scm-server" on the CM host whenever they change the configs and even post changing the config and restarting the CM server. So, how are you validating that the config has not taken affect?   To confirm this, you can simply login to the CM database and run a select query on the "configs" table to check if the properties are there.   For eg, on my postgresDB,   # sudo -u postgres psql postgres=# \c scm scm=# select attr, value, host_id, service_id from configs where attr like 'ldap%'; attr | value | host_id | service_id --------------+--------+---------+------------ ldap_type | LDAP | | ldap_bind_pw | abcdef | | ldap_bind_dn | robin | | (3 rows)   So even after I have added some random values for LDAP in CM UI, the UI will show ""Requires Server Restart" for the already changed properties. ... View more