hi @PrathapKumar  thanks for the answer! 😉 but, I had already seen this KB from fixed CVE 😊 ... View more

Hi @Abdul @lwang @rar59b  We have a know issue with the javax.security.sasl.SaslException: DIGEST-MD5: IO error acquiring password. Which is not yet fixed in any current CDP versions. https://issues.apache.org/jira/browse/HDFS-16332 Are we seeing any jobs failures when we have this issue? What values we set for the below parameters. dfs.data.transfer.protection = hadoop.rpc.protection = dfs.encrypt.data.transfer = ... View more

Hi @kkanchu  Can you please accept the answer if the above steps helps to change the log level of the HBase daemon on the fly without any restart. ... View more

Hello @PrathapKumar Thank you for your response It seems zookeeper is losing the hbase:meta table on docker restart.  Before restart: Run the ZooKeeper shell hbase zkcli In the shell run ls /hbase/table Result:    [hbase:meta, personal, hbase:namespace After restart the result is empty []. I wonder how I can persist the data on docker restart ... View more

Hi @rahuledavalath  We can use the HBase replication process for the data copy between the two CDP clusters, like production to DR. We have multiple open documents for the setting Hbase replication please follow the docs for setting the replication between two cluster to synchronise the data. https://docs.cloudera.com/cdp-private-cloud-base/7.1.6/hbase-backup-dr/topics/hbase-replication.html https://blog.cloudera.com/apache-hbase-replication-overview/     ... View more

See, thank you. ... View more

@arunpoy  If we are using the CDH/CDP both timeout parameters(hbase.rpc.timeout & hbase.client.scanner.timeout.period) need to be added in both server-side and client-side in the below paths from the HBase configuration. HBase Service Advanced Configuration Snippet (Safety Valve) for hbase-site.xml HBase Client Advanced Configuration Snippet (Safety Valve) for hbase-site.xml   Bothe the time-out parameters need to be added on the server and client-side and RPC(hbase.rpc.timeout) time-out needs to be set a bit higher than the client scanner time-out (hbase.client.scanner.timeout.period). ... View more

Hello @Ma_FF    Kindly let us know if the Post was Helpful to Identify the RegionServer Thread spiking the CPU Usage of the RegionServer JVM. If Yes, Please mark the Post as Solved.    Regards, Smarak ... View more

Hi, @kras Thank you for writing back with your observation. Can you please check the below details as well? 1) When the Region Server JVM reports High CPU, Open "top" Command for the Region Server PID, 2) Use "Shift H" to open the Thread View of the PID. This would show the Threads within the Region Server JVM with CPU Usage, 3) Monitor the Thread View & Identify the Thread hitting the Max CPU Usage, 4) Take Thread Dump | JStack of Region Server PID & Compare the Thread with the "top" Thread View consuming the Highest CPU. 5) Check the CUP usage of the other services that are hosted on the Region Server host.   The above Process would allow you to identify the Thread contributing towards the CPU Usage. Compare the same with other Region Server & your Team can make a Conclusive Call to identify the reasoning for CPU Utilization. Howsoever Logs are reviewed, Narrowing the Focus of JVM review would assist in identifying the Cause. Review shared Link for additional reference.   Ref:  https://www.infoworld.com/article/3336222/java-challengers-6-thread-behavior-in-the-jvm.html  https://blogs.manageengine.com/application-performance-2/appmanager/2011/02/09/identify-java-code-co...  https://blog.jamesdbloom.com/JVMInternals.html   Thanks & Regards, Prathap Kumar. ... View more