About Guru007

Guru007 · ‎06-07-2017

Hi I was able to fix the issue. We have a dedicated switch for Hadoop Cluster and I configured ntp server to sync with switch. It works all fine now 🙂 Not sure if everyone can do this, I would suggest you guys to try configuring ntp server for accurate time sync. Or you might setup a ntp server for Hadoop Cluster. Usually, ntp sync should work fine with domain controllers. [root@blrrndaclxx ~]# ntpq -p remote refid st t when poll reach delay offset jitter ============================================================================== *ntpbigdata.rnd. 172.xx.xx.111 4 u 574 1024 377 0.931 -0.790 3.597

Guru007 · ‎06-07-2017

Hi, Please make sure all java packages are uninstalled from your machine (reboot the machine) and later choose to install recommended java in Cloudera Manager wizard. Once you uninstall java from your machine, execute "yum clean" command. Also, no output is received when you execute command "update-alternatives --config java" Hope, this would solve the issue.

Guru007 · ‎12-11-2015

I found the fix for my issue. As after format of namenode, checkpointing on snn was not happening bcoz of old namespace and blockpoolID on VERSION file. After deleting the files under /data/dfs/snn. I restart the namenode and snn, later found it working fine.

Guru007 · ‎11-16-2015

Hi, I had same issue on one of the 10 node cluster built using VMware hypervisor, so all 10 VM's running on hypervisor. I actually did not face clock offset issue when I built cloudera cluster on a physical machines without using hypervisor. I feel there is latency issue with time sync of 3 minutes while on hypervisor. Please let us know if it is recommended to have hadoop cluster over hypervisor or not.

Guru007 · ‎11-02-2015

Please use below command to chang ethe replication factor for existing data on Hadoop FS $ hadoop fs -setrep -R -w 2 / Note: You may mention number according to your requirement to have the replication factor. $ hdfs fsck / -delete

Guru007 · ‎08-21-2015

Issue fixed with below steps I performed. Download derby derby client from db-derby-10.11.1.1-bin.zip Extract and copy derby.jar and derbyclient.jar from zip file to /var/lib/sqoop2 Copy derby.jar to /opt/cloudera/parcels/CDH-<version>/jars/ as well Delete /opt/cloudera/parcels/CDH-<version>/lib/sqoop2/webapps/sqoop/WEB-INF/lib/derby-<version>.jar soft link. Make /opt/cloudera/parcels/CDH-<version>/lib/sqoop2/webapps/sqoop/WEB-INF/lib/derby.jar to /opt/cloudera/parcels/CDH-<version>/jars/derby.jar Command for soft link: ln -s /opt/cloudera/parcels/CDH-5.4.0-1.cdh5.4.0.p0.27/lib/sqoop2/webapps/sqoop/WEB-INF/lib/derby.jar /opt/cloudera/parcels/CDH-5.4.0-1.cdh5.4.0.p0.27/jars/derby.jar

Guru007 · ‎08-04-2015

It seems like HA settings are enabled. Please check if HDFS>Configuration>"Filesystem Checkpoint Age Monitoring Thresholds" is specified. If specified then change it to never as shown below. Save the settings you will not get the message again.

Guru007 · ‎07-22-2015

If the above step doesn't fix your issue then the postgresql is not running to identitfy it try to run command service postgresql restart if above command fails then you have to check in /etc/hosts if loopback address is missing 127.0.0.1 localhost Add line 127.0.0.1 localhost save it, then try starting the postgresql service service postgresql start Hope this will help Guruveer

Guru007 · ‎05-20-2015

Yes, permission all fine. Checked jar file is placed in /var/lib/sqoop path. I am using Debain Wheezy build with CDH5.3.3 parcels version. I do not see only sqoop as it shows sqoop 2 alone as in screen shoft below. However, it is doesn't work.

Guru007 · ‎05-13-2015

Please let me know if anything to be taken care in configuration files...such as hdfs setup or Hive.....namenode format CDH5 on Debain linux OS Expecting the sqoop to import oracle data into HDFS. Please suggest

Online	Offline
Last Visited	‎07-31-2019 07:05 AM

Member Since	‎05-12-2015 09:05 PM
Last Visited	‎07-31-2019 07:05 AM
Posts	26
Kudos received	4

Cloudera Community

Re: Checkpoint Status on name node

Re: Unable to use sqoop on cloudera CDH5

Re: Cloudera 5.4.x cluster randomly reports "Clock...

Re: Cloudera Manager 5.11 stuck at Distributed o...

Re: Checkpoint Status on name node

Re: Cloudera 5.4.x cluster randomly reports "Clock...

Re: Percentage under replicated blocks: 100.00%

Re: Unable to use sqoop on cloudera CDH5

Re: Checkpoint Status on name node

Re: cloudera-scm-server is dead and pid file exist...

Re: Unable to use sqoop on cloudera CDH5

Re: Unable to use sqoop on cloudera CDH5