Member since
04-22-2014
8
Posts
4
Kudos Received
2
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
11585 | 11-09-2016 09:51 AM | |
1543 | 06-27-2014 08:01 AM |
11-29-2016
02:36 PM
2 Kudos
Hi, Can you try restarting CM agent using the following cmd: # service cloudera-scm-agent restart Then restart NM from CM. Let me know if that works. Note: do not start CM agent using /etc/init.d script directly
... View more
11-09-2016
10:38 AM
Hi, Instructions on yum repo installation can be found here [1]. You can get the repo file for example for RHEL 7 from here for example [2]. [1] - https://www.cloudera.com/documentation/enterprise/latest/topics/cdh_ig_cdh5_install.html#topic_4_4_1__p_32 [2] - https://archive.cloudera.com/cdh5/redhat/7/x86_64/cdh/cloudera-cdh5.repo?_ga=1.8210228.728334008.1433982308
... View more
11-09-2016
10:27 AM
Hi, the reason for this has to do with the fact that you need to upgrade CM to 5.5. CM will not allow you to upgrade CDH to 5.5 until you upgrade CM to 5.5 first. Per the documentation [1]: "The Cloudera Manager minor version must always be equal to or greater than the CDH minor version because older versions of Cloudera Manager may not support features in newer versions of CDH. For example, if you want to upgrade to CDH 5.4.8 you must first upgrade to Cloudera Manager 5.4 or higher." [1] - http://www.cloudera.com/documentation/enterprise/5-5-x/topics/cm_mc_upgrading_cdh.html#cmig_topic_10
... View more
11-09-2016
09:51 AM
2 Kudos
Hi Kartik, Have you tried following these steps: http://www.cloudera.com/documentation/enterprise/5-4-x/topics/admin_nn_migrate_roles.html?scroll=concept_w3h_m2l_2r_unique_1 Otherwise, if you can bring down HDFS, you can do the following: 1. Stop HDFS service 2. Copy over JN edits from a (good) JN to the (bad) JN. Make sure you get all edits from all dirs ( dfs.journalnode.edits.dir) 3. Start HDFS service Let me know if that works for you.
... View more
06-27-2014
08:01 AM
Bommuraj, you can set it in CM under HDFS service. It's a service wide setting. So under Services click on HDFS service, then click on Configuration -> View/Edit. Then click on the drop-down for Service-Wide and it's under the Performance section. -Hazem
... View more
04-28-2014
02:18 PM
So just to clarify: 1. You have a vm host which you have VirtualBox installed. 2. You setup an Ubuntu vm guest and placed the CM installation file on that Ubuntu vm guest 3. You were able to run the installer successfully (./cloudera-manager-installer.bin) from the command line 4. You then opened a browser and went to what URL (http://hostname:7180)? Which hostname/IP did you point to? Also, make sure your DNS resolution is working fine. -Hazem
... View more
04-25-2014
12:18 PM
What error do you see when you put your ip address in the wizard on your browser? Also, make sure iptables is turned off. You can also check your /var/log/cloudera-scm-server/cloudera-scm-server.log log file. You will see attempts to SSH into your vm guest when you click Search. Below is a snippet of how mine looks when I hit search: -Hazem 2014-04-25 12:17:09,163 INFO [454338303@scm-web-5:node.NodeScannerService@287] Request 2 contains 1 nodes 2014-04-25 12:17:09,163 INFO [454338303@scm-web-5:node.NodeScannerService@383] Existing scan of node 10.7.0.175 is too old, rescanning 2014-04-25 12:17:09,163 INFO [454338303@scm-web-5:node.NodeScannerService@291] Finished submitting request 2 2014-04-25 12:17:09,168 INFO [NodeScannerThread-2:node.NodeScanner@219] Beginning scan of node 10.7.0.175 and port 22 2014-04-25 12:17:09,172 INFO [NodeScannerThread-2:node.NodeScanner@243] Canonical hostname is 10.7.0.175 2014-04-25 12:17:09,172 INFO [NodeScannerThread-2:node.NodeScanner@256] Connecting to remote host 2014-04-25 12:17:09,173 INFO [NodeScannerThread-2:node.NodeScanner@277] Disconnecting from remote host 2014-04-25 12:17:09,173 INFO [NodeScannerThread-2:node.NodeScanner@293] Connecting to ssh service on remote host 2014-04-25 12:17:09,174 INFO [454338303@scm-web-5:node.NodeScannerService@124] Request 2 returning 0/1 scans 2014-04-25 12:17:09,177 INFO [NodeScannerThread-2:transport.TransportImpl@152] Client identity string: SSH-2.0-SSHJ_0_8 2014-04-25 12:17:09,187 INFO [NodeScannerThread-2:transport.TransportImpl@161] Server identity string: SSH-2.0-OpenSSH_5.3 2014-04-25 12:17:09,189 INFO [NodeScannerThread-2:transport.KeyExchanger@195] Sending SSH_MSG_KEXINIT 2014-04-25 12:17:09,190 INFO [reader:transport.KeyExchanger@357] Received SSH_MSG_KEXINIT 2014-04-25 12:17:09,214 INFO [reader:kex.DHG14@110] Sending SSH_MSG_KEXDH_INIT 2014-04-25 12:17:09,217 INFO [reader:transport.KeyExchanger@370] Received kex followup data 2014-04-25 12:17:09,217 INFO [reader:kex.DHG14@120] Received SSH_MSG_KEXDH_REPLY 2014-04-25 12:17:09,241 INFO [reader:transport.KeyExchanger@203] Sending SSH_MSG_NEWKEYS 2014-04-25 12:17:09,241 INFO [reader:transport.KeyExchanger@385] Received SSH_MSG_NEWKEYS 2014-04-25 12:17:09,243 INFO [NodeScannerThread-2:node.CmfSSHClient@686] Key exchange took 0.053 seconds 2014-04-25 12:17:09,243 INFO [NodeScannerThread-2:node.NodeScanner@315] Disconnecting from ssh service on remote host 2014-04-25 12:17:09,243 INFO [NodeScannerThread-2:node.NodeScanner@208] Connected to SSH on node 10.7.0.175 with port 22 (latency PT0.001S) 2014-04-25 12:17:09,245 INFO [NodeScannerThread-2:node.NodeScannerService@175] Request 2 observed finished scan of node 10.7.0.175 2014-04-25 12:17:10,196 INFO [454338303@scm-web-5:node.NodeScannerService@124] Request 2 returning 1/1 scans
... View more