Hello sbpothineni,   Based on the limited log snippet, it appears you may need to increase the heap size for your NodeManager.   You can increase the NodeManager's heap size by doing the following:   1. In CM UI, go to YARN -> Configuration -> NodeManager ->  Java Heap Size of NodeManager in Bytes.   2. Change the value.   3. Save changes and redeploy configuration. ... View more

Hello Saayak,   The only impact in moving your MySQL instance to another server is that if you do not update your CM/CDH configuration to point to the new MySQL instance.   After you stop your cluster, export and import the MySQL databases, you will need to make the following configration changes: 1. For Cloudera Manager:   a. Go to /etc/cloudera-scm-server/   b. Backup the following file:   - db.properties   c. In the db.properties file, change the following attribute to point to your new MySQL host:   - com.cloudera.cmf.db.host= 2. For Hive Metastore:   a. In Cloudera Manager, go to Hive -> Configuration.   b. Search for the following property: "Hive Metastore Database Host"   c. Change the value for "Hive Metastore Database Host" to your new host's fully qualified domain name.   d. Save changes.   3. For Oozie:   a. In Cloudera Manager, go to Oozie -> Configuration.   b. Search for the following property: "Oozie Server Database Host"   c. Change the value for "Oozie Server Database Host" to your new host's fully qualified domain name   d. Save changes.   4. Cloudera Navigator:   a. In Cloudera Manager, go to Cloudera Management Service -> Configuration.   b. Search for the following property: Navigator Audit Server Database Hostname   c. Change the value for "Navigator Audit Server Database Hostname" to your new host's fully qualified domain name.   d. Search for the following property: "Navigator Metadata Server Database Hostname"   e. Change the value for "Navigator Metadata Server Database Hostname" to your new host's fully qualified domain name.   f. Save changes.     5. For Sentry:   a. In Cloudera Manager, go to Sentry -> Configuration.   b. Search for the following property: "Sentry Server Database Host"   c. Change the value for "Sentry Server Database Host" to your new host's fully qualified domain name   d. Save changes. 6. For Hue:   a. In Cloudera Manager, go to Hue -> Configuration.   b. Search for the following property: "Hue Database Hostname"   c. Change the value for "Hue Database Hostname" to your new host's fully qualified domain name   d. Save changes.   ... View more

Hello Hrishi,   Since Cloudera Navigator cannot authenticate this specific user, the issue may lie with its inability to find the user in Active Directory.   You should compare the location of the user in Active Directory with Navigator's External Authenication "LDAP User Search Base" property.   The user's AD location may not be within the scope of the "LDAP User Search Base" property. If that is the case, you may need to widen the property's scope. ... View more

Hello Nukala,   When configured correctly, lineage diagrams for Spark and Yarn should be visible under Navigator's Search Tab -> Source Type -> Spark -> (Select Yarn application number) -> (Select Lineage Tab).   If you do not see the Spark Source Type, then check to see if Spark is configured to allow Navigator auditing by doing the following:   1. Go to Cloudera UI.   2. Select Spark Service -> Configuration -> Cloudera Navigator.   3. For the "Enable Lineage Collection" property, select the checkbox to enable the property. ... View more

Hello Jwood,   The audit sources for the Navigator audit data is as follows:   OS File System:   Each service has audit data in the OS file system, under the following path:   /var/log/<service>/audit   For example, the HDFS audit data would be located in the following path:   /var/log/hadoop-hdfs/audit   From there you would view the "hdfs-audit.log" file.     MySQL:   The audit data is propagated from the aforementioned audit files to Navigator Audit Server's underlying database.   The data is located in the following tables:   <SERVICENAME>_AUDIT_EVENTS   For example, the can find the HBASE, HDFS, and HUE audit data in the following tables:   - HBASE_AUDIT_EVENTS - HDFS_AUDIT_EVENTS - HUE_AUDIT_EVENTS ... View more

Hello Vitali1,   The file count by directory can be accessed in Cloudera Navigator via the HDFS Analytics feature.   To access HDFS Analytics, please do the following:   1. From the Cloudera Navigator main menu, go to Analytics -> HDFS.   2. On the HDFS Analytics page, select the "Size" chart.   3. After selecting the Size chart, under the HDFS Files, select the "By Directory" option/radio button.   4. The results will sort by "Directory" and "Number of Files" in decending order. ... View more

For the worknodes (e.g., datanodes), it would be better to add a larger EC2 instance to the cluster, replicate the data to the instance and add, (or transfer) any roles.  Once the smaller EC2 instance is no longer needed, simply decommision/remove it.    ... View more

Hello,   To replace an EC2 instance with a more powerful instance, do either of the following:   1. Power down the EC2 instance. 2. In the EC2 management console, right click the instance and choose "Change Instance Type."   OR   1. Create an image (AMI) of the EC2 instance. 2. Launch an instance from the AMI.   OR   1. Create a snapshot of the EC2 instance's volume. 2. Create a volume from the snapshot. 3. Provision a larger EC2 instance. 4. Power down the EC2 instance. 5. Delete volume from the EC2 instance. 6. Attach the volume, provisioned from the snapshot, to the EC2 instance. ... View more

You are welcome. ... View more

Since this is a single node, can you perform the following edits?:   1. Edit the /etc/hosts file:   Change the entry from:   127.0.0.1 localhost.hadoopdomain localhost   to   127.0.0.1 localhost localhost.hadoopdomain 2. Edit the /etc/cloudera-scm-agent/config.ini file by either confirming or changing the entry (third line from the top) to the following:   server_host=localhost   ... View more

Hello,   I have downloaded the quickstart VM and imported it into a running instance of Virtualbox.  Initially, I saw nothing wrong.   I was able to reproduce the error by disabling networking in the VM, and changing networking in Virtualbox.   Check the following:   1. In the Quickstart VM, check the status of your networking by viewing the network icon in the upper right area, next to the speaker icon.  Right-click the icon to see if Enable Networking is checked.  If it is unchecked, check the box.   2. If Networking is already enabled, go to Virtualbox Manager, and do the following:       a. Right-click the Quickstart VM and select Settings.       b. In the Settings window, select Network.       c. The configuration that works for me is the following:           i. Attached to: NAT           ii. Cable Connected: checked   ... View more