Hi @Sudheend,   Pseudo-distributed mode means each of the separate processes run on the same server, rather than multiple servers in a cluster.    In CDH6/7, "start-hbase.sh" is not existing anymore, and "service hbase-master start/stop" is also not working anymore. Instead, Cloudera Manager will use multiple scripts to do this. You can check how a HBase role is started in CM by expanding steps and check stderr.log of the running commands.    So the best way is to use Cloudera Manager to install HBase service, you can choose same host to install Master role, RegionServer role. Then you could stop/start the HBase roles via CM > HBase > Instances > Select role > Actions > Stop/Start.   Then use jps or ps -ef to check the running processes: For example: # jps 7251 DataNode 8019 NodeManager 7253 NameNode 15238 HMaster 11384 HRegionServer 16105 Jps 7085 QuorumPeerMain   Regards, Will If the answer helps, please accept as solution and click thumbs up. ... View more

Hi @ighack, Please search keywords "JvmPauseMonitor" in that RegionServer log to see if there are GC pause and determine is it GC or Non-GC. - For GC pause general step is to increase heap size.  Please go through the setting of "Java Heap Size of HBase RegionServer in Bytes" in CM > HBase > Configuration. If the current setting is small please increase it. Please check this KB for the heap size tuning concept. https://community.cloudera.com/t5/Community-Articles/Tuning-Hbase-for-optimized-performance-Part-1/ta-p/248137 - For Non-GC pause you will need to check if: Kernel blocking the process due to: hardware issues blocking I/O page allocation failures due to heavy memory utilization etc… Look into kernel messages for clues dmsg /var/log/messages   Regards, Will If the answer helps, please accept as solution and click thumbs up. ... View more

Hi @shean    It looks like the hdfs pathname is wrong, you should use double "/" after "hdfs:": hdfs://localnode2:8020/user/hue/oozie/workspaces/hue-oozie-1630559728.5  Please check your command or configurations for this wrong path setting and correct it.   Regards, Will If the answer helps, please accept as solution and click thumbs up. ... View more

Hello @AnuradhaV, Thanks for raising questions in community. We usually don't suggest to put files with special characters in file name to hdfs. If you have to do this you should replace the special characters with URL encoding. For example, below characters should be encoded as:    # encoded as %23 ? encoded as %3F = encoded as %3D ; encoded as %3B   A full list of URL encoding characters: https://www.degraeve.com/reference/urlencoding.php To help you test it out, I created these files in my local and then put them to hdfs:   # ls 900-0314-Slide#2.vsi abc.html?C=S;O=A # hdfs dfs -put 900-0314-Slide%232.vsi /tmp/ # hdfs dfs -put abc.html%3FC%3DS%3BO%3DA /tmp/ # hdfs dfs -ls /tmp Found 2 items -rw-r--r-- 3 hdfs supergroup 0 2021-09-03 07:07 /tmp/900-0314-Slide#2.vsi -rw-r--r-- 3 hdfs supergroup 0 2021-09-03 07:15 /tmp/abc.html?C=S;O=A   Thanks, Will If the answer helps, please accept as solution and click thumbs up. ... View more

Hi @vciampa,   You can refer to this doc for migrating data from secured HDP to secured CDP: https://docs.cloudera.com/cdp-private-cloud-upgrade/latest/data-migration/topics/rm-migrate-securehdp-securecdp-distcp.html   For question 2) I think it says about to set hadoop configuration file location to Destination cluster if you use HFTP(refer to HFTP for explanation), if not using HFTP, you should set it to Source cluster. But I think this link is kinda confusing it looks like HDP documents not CDP documents. There are different HADOOP_CONF location between HDP and CDP. https://docs.cloudera.com/cdp-private-cloud-base/7.1.6/concepts/topics/cm-server-client-configuration.html For example, In HDP, HADOOP_CONF location is /etc/hadoop/conf, it contains both service/client sides configuration files. In CDP, Cloudera manager separate the client and server configurations: Client configurations located at /etc/hadoop/conf/hdfs-site.xml Server configurations located in the latest process directory of each role: under /var/run/cloudera-scm-agent/process/<latest_pid>-hdfs-NAMENODE/hdfs-site.xml   As for question 1) please follow the answer of @vidanimegh in the previous post. As for question 2) please just ignore this step and Follow the first link I provided in this post.   Thanks, Will   If the answer helps, please accept as solution and click thumbs up. ... View more

Hi Roshan,   Thanks for raise question in Cloudera community ! Firstly you need to check what is the current kudu version.  Notes: Use the kudu-spark_2.10 artifact if using Spark with Scala 2.10. Note that Spark 1 is no longer supported in Kudu starting from version 1.6.0. So in order to use Spark 1 integrated with Kudu, version 1.5.0 is the latest to go to. And please refer to below articles for some code examples. [1] CDP 7.2.10 documents: https://docs.cloudera.com/runtime/7.2.10/kudu-development/topics/kudu-integration-with-spark.html [2] Kudu official site: https://kudu.apache.org/docs/developing.html#_kudu_integration_with_spark   If it helps please accept the solution and click thumbs up. ... View more