About zbz

MehulGain · ‎06-02-2020

To Introduce Myself: This is Mehul Desai - Executive Director at GainInsights driving Sales Globally. We are a Solution and Service provider for Data Related Value proposition to our customers. I have 25+ years IT experience all thought out sales and worked with organization like Wipro, BusinessObjects, SAP, Qlik and SAS.

Danny000 · ‎09-27-2019

Hi,I met the same issue with you,have you solved it?

zbz · ‎05-16-2019

I checked the failed job log and found that there was one such item, java.lang.NoSuchField Error: HBASE_CLIENT_PREFETCH. Then I look at the classpath of the failed job, find different versions of the jar package of HBase in hive. aux. jars. path, delete the jar package here, restart hiveserver2, and everything returns to normal.

Consult · ‎03-27-2019

Hello @zbz, It is nice to hear that. A side node: CM version 5.7.6 is a stable release for CM 5.7. If you don't plan to upgrade to next major release then you may want to consider to upgrade to CM 5.7.6 version atleast. Have a good day.

Harsh J · ‎03-05-2019

This may then be explained by open HDFS writer files perhaps, as those would've closed during a restart. Next time this occurs, try checking the count of open files via fsck '-openforwrite'? What is your configured block size for HDFS files. There were a few issues in past such as https://issues.apache.org/jira/browse/HDFS-8072 (5.5+) and https://issues.apache.org/jira/browse/HDFS-9038 (5.10+) that may be relevant to the issue observed here and an upgrade can help address these.

zbz · ‎01-23-2019

Hi ，when you look at the error ' Caused by: java.io.IOException: Cannot obtain block length for LocatedBlock{BP-19720802xxxxxxxxxx-xxxx-xxxx1:blk_1326223979_253064188 ' run those cmd : 1. hdfs fsck -blockId blk_1326223979 then you will see one file path that bock belong. 2. hdfs debug recoverLease -path theFilePath retries 3 and all is ok.

javicacheiro · ‎12-10-2018

One easy option in old CDH versions is just to change the shebang at the beginning of the script to: #!/usr/bin/env python2 Actually this will be more precise than the default, because the script is actually a python 2 script and ... python 3 is coming ... so it is good to be specific about the given version of the interpreter the script needs. We could be even more explicit and require python2.7.

manuroman · ‎11-21-2018

Hi @zbz, Good!! Thanks for the informatons tips. Regards, Manu.

zbz · ‎10-22-2018

Thank you so munch！ I change the group of '/tmp/logs' to hadoop , and restart the JobHistoryServer role, everything being OK. So happy !

bgooley · ‎10-08-2018

@JoaoBarreto, It is possible to do so, but it is not something we document or test exactly. The closest steps would be only doing the Cloudera Manager steps here: https://www.cloudera.com/documentation/enterprise/5-15-x/topics/install_singleuser_reqts.html#concept_ivr_lng_2v Since the agent runs as "root" by default, you shouldn't need to do any of the agent-specific steps there. Also, the Management Service "System User" and "System Group" are "cloudera-scm" by default. You may need to do a little trial and error to get everything working, but I don't think it would be too bad.

Online	Offline
Last Visited	‎07-09-2019 03:07 AM

Date Registered	‎10-07-2018 10:55 PM
Last Visited	‎07-09-2019 03:07 AM
Total Messages Posted	16

Re: INTRODUCE YOURSELF: Please Reply here to tell ...

Re: How to disable Hive CLI

Re: beeline hive on hbase error

Re: nodemanager can not start with error 'Conflict...

Re: DFS Remaining is not same to disk remain size

Re: Cannot obtain block length - error not persist...

Re: topology.py not Python 3 compatible

Re: some hosts of DataNode need reinstall linux O...

Re: Yarn Aggregate Log Retention Setting

Re: Changing installation username from "cloudera-...