Member since
02-12-2015
56
Posts
7
Kudos Received
0
Solutions
11-08-2023
04:03 AM
1 Kudo
Hello Vidya, would you support me in this as well? regards, Mahrous Badr
... View more
03-02-2021
10:08 PM
I had a similar issue in CDH 6.21 and doing this worked . rm -rf /var/lib/cloudera-scm-agent/cm_guid
... View more
04-15-2019
03:04 AM
Thank you very much for your answer. Then it's almost the same to add a HDFS role of gateway respect an HDFS role of NFS gateway? It seems, in my case, that it's working properly. Many thanks in advance Steve
... View more
11-21-2016
07:39 AM
1 Kudo
Hi Neelesh, It seems you missed the leading "/" from the destination path, so it should be in your home directory. Can you please run "hdfs dfs -ls" as the same user? It should be there.
... View more
11-18-2016
02:37 AM
No. See doc for usage: http://archive.cloudera.com/cdh5/cdh/5/hbase/book.html#_export
... View more
11-03-2016
03:58 PM
Hello Neelesh, For encryption, you will need a license key to leverage this feature. I would like to point out is that you have the ablitily to deploy HDFS Transparent Encryption, Cloudera Navigator Encrypt, and the Key Trustee Server in an automated way with Cloudera Manager. The HDFS Transparent Encryption will allow you to data at rest encrypt your HDFS data. The Cloudera Navigator Encrypt allows you to encrypt additional filesystems on your linux systems that hold your metadata and logs. (/var/log & /opt/mysql) The Key Trustee Server allows you to centerally manage your keys to keep them secure and not left laying around on all of the servers that are using the Encryption. Look for Encryption & Key Management (Cloudera Navigator Encrypt & Key Trustee) in http://www.cloudera.com/content/dam/www/marketing/resources/datasheets/cloudera-enterprise-datasheet.pdf.landing.html Thanks, Brandon
... View more
10-28-2016
02:27 PM
It's commonly found on the host where you have installed the cloudera-manager-server-db2 package, and physical location is /var/lib/cloudera-scm-server-db/data
... View more
10-24-2016
01:08 PM
17 Kudos
Howdy, Thanks for your question. It can be quite jarring to see two columns in your output when du normally only has one column, but fear not, there is an explanation for everything. 🙂 I found a similar post discussing this topic. From looking at it, it's clear that it took some digging to get to the bottom of this, but if you look towards the bottom, you'll see a link to the source code explaining the output format. Eureka! Anywho, the output states that the first two columns are formatted like this: [size] [disk space consumed] but what does this mean? the "size" field is the base size of the file or directory before replication. As we know, HDFS replicates files, so the second field(disk space consumed) is included to show you how much total disk space that file or directory takes up after it's been replicated. Under the default replication factor of three, the first two columns of a 1MB file would theoretically look like this. 1 3 M The fun part is that we can actually use this info to infer the replication factor HDFS is using for these particular files, or at least the amount of replication the file is curently at. If you look at the first line of your output, you'll see the initial size as 816 and the disk space usage as 1.6 K. Divide 1.6K by 816 bytes, and you get 2 (roughly), which would indicate a replication factor of two, and you'll notice this math is consistent with the other entries in the output. Good times. Armed with this knowledge, you can now use du tool to its full potential, both for informative and troubleshooting purposes. Let me know if this info was helpful or if you have any other questions. 🙂 Cheers
... View more
10-24-2016
03:18 AM
Harsh, Could you clarify answer for point no.1 1. Whether hbase snapshot make another copy of the table or not.
... View more
08-14-2016
04:01 PM
1 Kudo
Try stopping all roles and restarting your CM agent on just this host and ensure you do not use the init.d script directly, and that instead you use the recommended service command approach: ~> service cloudera-scm-agent restart (i.e., never do this: "~> /etc/init.d/cloudera-scm-agent restart")
... View more