Dear All .   Below is my data format in pig output file but $1 column contains name :-       name                 dob      gender                 address (LACTE^MIRAM,19659802,F,4395 NOREY AVE^^ATTIC CITY^N9J^09901) (JSON^MAW,19820309,M,COUNTRY CLUB DR^^NORELD^NJ^99225)   but want like below:- firstname  lastname  dob     gender         address (LACTE,MIRAM,19659802,F,4395 NOREY AVE^^ATTIC CITY^N9J^09901) (JSON,MAW,19820309,M,COUNTRY CLUB DR^^NORELD^NJ^99225)         Thanks HadoopHelp ... View more

I'm having same issue. customized local parcels stored under /opt/cloudera/parcel-repo are not listing under CM- Parcels   I even tried below 1. copied exising parcel which is visible in CM 2. untar parcel to some temp location 3. rename dir (untar) 4. generate parcel/ tar by only replacing parcel name in parcel.json 5. generated sha file 6. Copied parcel and sha files under /opt/cloudera/parcel-repo 7. Restarted cloudera manager server. But no luck   Any suggestion? ... View more

  I am just sharing the relevant part of the linked docs, as they contain the instructions on how to enable the hbase balancer via hbase shell:   Load Balancer It is assumed that the Region Load Balancer is disabled while the graceful_stop script runs (otherwise the balancer and the decommission script will end up fighting over region deployments). Use the shell to disable the balancer: hbase(main):001:0> balance_switch false true 0 row(s) in 0.3590 seconds This turns the balancer OFF. To reenable, do: hbase(main):001:0> balance_switch true false 0 row(s) in 0.3590 seconds The graceful_stop will check the balancer and if enabled, will turn it off before it goes to work. If it exits prematurely because of error, it will not have reset the balancer. Hence, it is better to manage the balancer apart from graceful_stopreenabling it after you are done w/ graceful_stop. ... View more

The simple answer is to open up the ports in a bidirectional manner on all the hosts.  For instance:   on each node in cluster A:  Allow connectivity to 1004 (or 50010 without Kerberos) and 50020 on each datanode in cluster B. As well as 8020 to namenodes in Cluster B.   on each node in cluster B: Allow connectivity to 1004 (or 50010 without Kerberos) and 50020 on each datanode in cluster A. As well as 8020 to namenodes in Cluster A.   However... You are right, where the distcp is executed will determine the source/destination.  Executing distcp on Cluster A will cause a mapreduce job to run on cluster A.  Each datanode will(may) run a task that will connect to the namenode(s) on cluster B for block locations and then datanodes on cluster B for transfer.  I'm not sure if the node the distcp is executed on will need access as well.  So I generally run the distcp on one of the datanodes. ... View more

Installation is not able to locate the oozie shared library tar gip file. I even didn't find in any other locations.    Error: gzip: /usr/lib/oozie/oozie-sharelib-yarn.tar.gz: No such file or directory tar: This does not look like a tar archive tar: Exiting with failure status due to previous errors I'm running with    Version: Cloudera Enterprise Data Hub Edition Trial 5.11.1 CDH 5.0.0 ... View more

Thanks . That got me a bit closer.   I discovered that there was no core created on solrserver2, which i just did and restarted  both servers.   now i am getting Node: solrserver2:8983_solr is not live !   but i see it started in the manager , and no logs either. What am I missing !!   Your help probably saved couple days of reading and frustration ! ... View more

Renaming the .sha1 file to .sha was successful. Thanks for your help Gautam. Kevin ... View more