About Bildervic

Bildervic · ‎01-18-2021

hello, try to find your log4j.properties file ( my case /etc/hadoop/conf.cloudera.hdfs/log4j.properties) and add these two lines : log4j.appender. RFA =org.apache.log4j.ConsoleAppender log4j.appender. RFA .layout=org.apache.log4j.PatternLayout good luck

Bildervic · ‎01-18-2021

hello Michael, I had a similar issue with my CDH bases cluster, solved by a stupid-like solution. What I did is that first I turned the replication factor into 2 instead of 3, /*under replicated blocks notice should appear */ run the rebalance (by Blockpool then by Datanode to make some shuffles between data nodes ) , then reconfigure the replication factor to 3, then I noticed some major changes. Not sure if that gonna work for you but just wanted to share my experience if want to try it. Good luck

Bildervic · ‎01-18-2021

hello, So to have a clearer vision of what you're seeking can you tell us if you're willing to connect your host to an already installed cluster or you just want to install Hadoop on a single machine (standalone )? On another side, your server needs repositories to install from the components (you have to configure your local repository on your server or any other server that can connect to it via a private IP for example )

Bildervic · ‎09-21-2020

I have tested the backup/restore solution and seems to be working like charm with spark : -First, check and record the names as given in the list of the kudu_master (or the primary elected master in case of multi masters ) http://Master1:8051/tables -Download the kudu-backupX.X.jar in case you can't find it in /opt/cloudera/parcels/CDH-X.Xcdh.XX/lib/ and put it there -In kuduMasterAddresses you put the name of your Kudu_master or the names of your three masters separated by ',' -Backup : sudo -u hdfs spark2-submit --class org.apache.kudu.backup.KuduBackup /opt/cloudera/parcels/CDH-X.Xcdh.XX/lib/kudu-backup2_2.11-1.13.0.jar --kuduMasterAddresses MASTER1(,MASTER2,..) --rootPath hdfs:///PATH_HDFS impala::DB.TABLE -COPY : sudo -u hdfs hadoop distcp -i - hdfs:///PATH_HDFS/DB.TABLE hdfs://XXX:8020/kudu_backups/ -Restore: sudo -u hdfs spark2-submit --class org.apache.kudu.backup.KuduRestore /opt/cloudera/parcels/CDH-X.Xcdh.XX/lib/kudu-backup2_2.11-1.13.0.jar --kuduMasterAddresses MASTER1(,MASTER2,..) --rootPath hdfs:///PATH_HDFS impala::DB.TABLE finally INVALIDATE METADATA

Bildervic · ‎09-19-2020

hi @Harish19 there is a solution I'm going to test mentioned in https://kudu.apache.org/docs/administration.html and https://docs.cloudera.com/cdp/latest/data-migration/topics/cdp-data-migration-restoring-kudu-data.html the main idea is to create a backup with spark move it with distcp then restore your backup good luck

Bildervic · ‎03-24-2020

HI Rosa, Sorry I gave up that time because It was an urgent matter , so I just took the short way and used hive to hash my data and put it in a table , where I can run my queries later with Impala , I'll come back for it later for sure since hive is a bit slow while having java based functions. I'd recommend you to try with C language ,it's suitable for impala tho it will work faster . So please If you came up with anything share it with us , otherwise I'll post for sure my solution once it's done . best luck Bilal

Bildervic · ‎03-11-2020

hello how about when you change " http://ip-10-189-107-50.eu-west 1.compute.internal" with the IP address/domain of your host that contains the ResourceManager role?

Bildervic · ‎02-14-2020

Hello Community, A red-flagged error message appeared suddenly in the Zookeeper section of my Cloudera Manager Interface "Bad : Maximum request latency: 102,477 ms. Maximum client-negotiable session timeout: 50,000 ms. Percentage of maximum client-negotiable session timeout: 204.95%. Critical threshold: 100.00%" . I have noticed that those values "102,477", "204.95%" are static and don't change at all in that message. how to get rid of the message? it's corrupt the beauty of my CM (the view of all working fine in my cluster ) I've tried the restart solution mentioned in : https://community.cloudera.com/t5/Support-Questions/zookeeper-test-Maximum-Request-Latency-is-failing-How-to-fix/m-p/27509#M32397 also tried to clean the logs but no change any help or indication would be appreciated. CDH :5.14.2 CM :Cloudera Express 5.14.1

Bildervic · ‎01-30-2020

After some researches I did, it seems that Impala does not support GenericUDFs yet. https://issues.apache.org/jira/browse/IMPALA-7877 https://issues.apache.org/jira/browse/IMPALA-8369 so I'll just try to create my own function for Impala.

Bildervic · ‎01-29-2020

Hi all, I'm trying to create a function to use in imapla. my function is simply re-using hive's sha2() function. the creation of the function goes smoothly : create function to_sha2(string,int) returns string location 'user/hive/hive.jar' symbol='org.apache.hadoop.hive.ql.udf.generic.GenericUDFSha2' ; but when I try to use it doesn't work launching this warning : select to_sha2('test',256); Query State: EXCEPTION Query Status: ClassCastException: class org.apache.hadoop.hive.ql.udf.generic.GenericUDFSha2 I have tried to search for UDFSha2 that doesn't contain the Generic word in the hive's jar but I couldn't find it. the original built-in function in hive : sha2(string/binary, len) - Calculates the SHA-2 family of hash functions (SHA-224, SHA-256, SHA-384, and SHA-512). | the other functions are working normally in impala (for example I have tried to create UDF MD5 function from hive's jar and it was working ). so my question is do I have to create my own UDF-Sha2 function? or there is a saving situation for my case, any help will be appreciated Impala version 2.9 Hive : 1.1.0 CDH : 5.12

Bildervic · ‎01-23-2020

works perfectly , thanks

Bildervic · ‎11-25-2019

hi all, when I check my Kudu log (warnings) a warning message that notifies about a connection problem between my master and 2 of my tablet servers (nodes ) keeps showing W1125 15:37:41.447703 71781 leader_election.cc:219] T 164547348c3247909aa8686f9ecab142 P 616c11aaad4e48e2b127f29cf3e420ad [CANDIDATE]: Term 7 pre-election: Was unable to construct an RPC proxy to peer 4346c5a6d387436389f1c5653207c207: Network error: unable to resolve address for node55.n0 : Name or service not known. Counting it as a 'NO' vote. the problem is that those two nodes do not exist in my hosts files nor the CM, because they were decomissionned a long time ago. even after checking with: sudo kudu tserver list those two nodes are not present in any related rpc-addresse did I miss a must-check for kudu? any help or guidance will be appreciable , greetings .

Bildervic · ‎08-06-2019

hi @eMazarakis as far as I know Impala does not support HDFS Impersonation . (security reasons I guess ) means you can't delete hdfs files using hue user cheers !

Bildervic · ‎08-05-2019

hi @Harish19 check here : https://community.cloudera.com/t5/forums/forumtopicprintpage/board-id/Questions/message-id/13133/print-single-message/true/page/1

Bildervic · ‎08-05-2019

@Amritha as I have checked some Kudu manuals, Chrony is not fully tested with KUDU for network time synchronization. " Kudu releases are only tested with NTP. Other time synchronization providers like Chrony may or may not work." so you can either try to install NTP. or just try this tip I've found : "In order to use chrony for synchronization (for KUDU), chrony.conf must be configured with the rtcsync option" good luck

Bildervic · ‎08-02-2019

hello @GopiG , have you tried setting the executor's and the driver's params in spark-defaults.conf ? spark.driver.extraJavaOptions -Duser.timezone=UTC spark.executor.extraJavaOptions -Duser.timezone=UTC you can set the default time zone UTC or any example you want like GMT+8 etc... cheers.

Bildervic · ‎08-02-2019

hi @Amritha , when you're running the command ntpq -np , (ntp should be already installed I guess ) what does it give as result? greetings .

Bildervic · ‎05-06-2019

hi @MartinP , one way to do it is to build a new cluster in your CentOS platforme , then copy all your data to the new cluster as mentionned here : https://www.cloudera.com/documentation/enterprise/5-5-x/topics/cdh_admin_distcp_data_cluster_migrate.html just pay attention to the CDH distribution source and destination ,if they are supported for the migration or not . cheers,

Bildervic · ‎04-25-2019

hi @Harish19 , can you tell us what version of java,spark and CDH you're running ? otherwise try to add spark-assembly-XXX.jar to hdfs (copy from local to hdfs) then add that parameter : spark.yarn.jars hdfs://IP/spark/spark-assembly-XXX.jar to the file spark-defaults.conf and don't forget to restart yarn. I hope this will work for you ,

Bildervic · ‎04-24-2019

hi @DataMike , The Balancer role is normally added (by default) when the HDFS service is installed, so the "Balancer" Resides usally in your nameNode , but to make sure where it's assigned you can check HDFS->Instances then check the role Type , you'll find the role 'balancer' assigned to a host ( usally it's the nameNode ) . for your second question I guess it's better to use the nameNode just to maintain the architecture since we're talking about checking all the other DataNodes,moving blocks...

Bildervic · ‎04-24-2019

@bgooley , thank you for your feedback and your clear explanation , in fact the problem was resolved by removing the contents of /var/lib/hadoop-yarn/yarn-nm-recovery/ directory and then the Nodemanager role started successfully. the solution that I've found was from : https://community.cloudera.com/t5/Batch-Processing-and-Workflow/Yarn-NodeManager-fails-to-start-and-crashing-with-SIGBUS/m-p/66590#M3611

Bildervic · ‎04-23-2019

hello folks , the nodeManager has suddently stopped in a instance (while stille running for other nodes/intances ). so when I try to start/restart it -via cloudera manager - , an error is shown in the first step : Failed to start role. and I'm using CentOS release 6.10 (Final) please what do you suggest me to look or check in order to resolve this problem ? here's my stdout log : Tue Apr 23 10:18:56 PDT 2019 JAVA_HOME=/usr/java/jdk.1.8.0_144 using /usr/java/jdk.1.8.0_144 as JAVA_HOME using 5 as CDH_VERSION using /opt/cloudera/parcels/CDH-5.14.2-1.cdh5.14.2.p0.3/lib/hadoop-yarn as CDH_YARN_HOME using /opt/cloudera/parcels/CDH-5.14.2-1.cdh5.14.2.p0.3/lib/hadoop-mapreduce as CDH_MR2_HOME using /var/run/cloudera-scm-agent/process/23960-yarn-NODEMANAGER as CONF_DIR CONF_DIR=/var/run/cloudera-scm-agent/process/23960-yarn-NODEMANAGER CMF_CONF_DIR=/etc/cloudera-scm-agent # # A fatal error has been detected by the Java Runtime Environment: # # SIGBUS (0x7) at pc=0x00007f8c1fde51a1, pid=3004, tid=0x00007f8c4f44c700 # # JRE version: Java(TM) SE Runtime Environment (8.0_144-b01) (build 1.8.0_144-b01) # Java VM: Java HotSpot(TM) 64-Bit Server VM (25.144-b01 mixed mode linux-amd64 compressed oops) # Problematic frame: # C [libleveldbjni-64-1-8170950501904951615.8+0x491a1] leveldb::ReadBlock(leveldb::RandomAccessFile*, leveldb::ReadOptions const&, leveldb::BlockHandle const&, leveldb::BlockContents*)+0x191 # # Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again # and this is my log.out error : NodeManager Node Manager health check script is not available or doesn't have execute permission, so not starting the node health script runner. AsyncDispatcher Registering class org.apache.hadoop.yarn.server.nodemanager.containermanager.container.ContainerEventType for class org.apache.hadoop.yarn.server.nodemanager.containermanager.ContainerManagerImpl$ContainerEventDispatcher AsyncDispatcher Registering class org.apache.hadoop.yarn.server.nodemanager.containermanager.application.ApplicationEventType for class org.apache.hadoop.yarn.server.nodemanager.containermanager.ContainerManagerImpl$ApplicationEventDispatcher AsyncDispatcher Registering class org.apache.hadoop.yarn.server.nodemanager.containermanager.localizer.event.LocalizationEventType for class org.apache.hadoop.yarn.server.nodemanager.containermanager.localizer.ResourceLocalizationService AsyncDispatcher Registering class org.apache.hadoop.yarn.server.nodemanager.containermanager.AuxServicesEventType for class org.apache.hadoop.yarn.server.nodemanager.containermanager.AuxServices AsyncDispatcher Registering class org.apache.hadoop.yarn.server.nodemanager.containermanager.monitor.ContainersMonitorEventType for class org.apache.hadoop.yarn.server.nodemanager.containermanager.monitor.ContainersMonitorImpl AsyncDispatcher Registering class org.apache.hadoop.yarn.server.nodemanager.containermanager.launcher.ContainersLauncherEventType for class org.apache.hadoop.yarn.server.nodemanager.containermanager.launcher.ContainersLauncher

Bildervic · ‎02-13-2019

try to ping on that ip first (127.0.0.1 or for my case I had to add another bridge ip) suits well with port 22 as mentioned in @nauseous the port 22 sould be enabled in iptables (firewall) , and so for ssh ( /etc/ssh/sshd_config) check if the port is still commented with # (that means still on default port 22 ) otherwise try to add a new port of your own .

Bildervic · ‎02-11-2019

very helpful , thank you for your efforts

Bildervic · ‎02-07-2019

for my case I was just working on cloudera VM , I had to configure the node ip , => ifconfig LOCAL_NODE_IP eth1:2 netmask XXXX after that pinging to that ip is going well thanks a lot

Online	Offline
Last Visited	‎05-05-2021 09:09 AM

Date Registered	‎01-31-2019 01:50 AM
Last Visited	‎05-05-2021 09:09 AM
Total Messages Posted	25
Total Kudos Received	4

Re: IMPALA function 'hive generic UDF SHA2 '

Re: Kudu to HDFS data load timestamp issue.

Re: Which Host Should HDFS "Balancer" Role Reside?

Re: Failed to start role -YARN- NodeManager (n...

Re: getting ERROR when trying to start hadoop name...

Re: hadoop + how to rebalnce the hdfs

Re: install the Hadoop client components on a host...

Re: kudu tables migration from one cluster to anot...

Re: kudu tables migration from one cluster to anot...

Re: IMPALA function 'hive generic UDF SHA2 '

Re: Cannot display the history of a job

Zookeeper Maximum Latency Monitoring Thresholds

Re: IMPALA function 'hive generic UDF SHA2 '

IMPALA function 'hive generic UDF SHA2 '

Re: Failed to configure urlScheme property for Sol...

Network error: unable to resolve address for table...

Re: How to properly delete a hive table through HU...

Re: Impala ODBC connection fails with ssl errors.

Re: KUDU time sync error

Re: Kudu to HDFS data load timestamp issue.

Re: KUDU time sync error

Re: Migrating OS distribution

Re: can't access pyspark shell

Re: Which Host Should HDFS "Balancer" Role Reside?

Re: Failed to start role -YARN- NodeManager (n...

Failed to start role -YARN- NodeManager (node)

Re: unable to Ssh using putty from windows to clou...

Re: Tutorial exercise 3 explained in details

Re: data nodes can't reach name node