About Johnny_Bach

Johnny_Bach · ‎06-28-2019

Hi @BiggieSmalls Yes , i did happen to got the issue resolved , it's been quite an while ago , let me get back to you on monday

Johnny_Bach · ‎02-26-2019

i'm currently using cloudera community editition 5.15.0 from past 90 days I had External authentication configured over the Cloudera community edition , after few days of utilization i'm noticing that external authentication is not avaliable under the Administrattion-> Security Options Does External Authentication comes only will limited period of time ? please advice

Johnny_Bach · ‎11-21-2018

@Tomas79, Thank you for the inputs

Johnny_Bach · ‎11-20-2018

i'm not sure what's going wrong out here ,ideally it should not happen but , when i happen to execute the below query when HDFS service is down , i would notice the partition being dropped despite of below error Query: alter table fenet5_dev.dw_malicious_events drop partition (occurred_month = 201808) purge ERROR: ImpalaRuntimeException: Error making 'dropPartition' RPC to Hive Metastore: CAUSED BY: MetaException: Got exception: java.net.ConnectException Call From hpc143 to hpc123:8020 failed on connection exception: java.net.ConnectException: Connection refused; For more details see: http://wiki.apache.org/hadoop/ConnectionRefused

Johnny_Bach · ‎10-09-2018

@EricL, i had an impression that MEM_LIMIT only poses an soft limit of memory resource and helps in attaining concurrency but the reality is that it's an hard limit and query would fail exceeding beyond the mem_limit value, so after setting the memory limit to greater value query ran fine with the peak utilization of 27GB.

Johnny_Bach · ‎09-30-2018

@Tim Armstrong, i have an follow-up question on this , can an given query exceed the memory consumption specified as Default minimum memory (MEM_LIMIT) Let's suppose , Default memory limit is set to 20g and if a given query require more than 20g can impalad process allocate the additional memory without cancelling it . so far, we have noticed , Default memory limit is setting an hard limit on the memory utilization thus canceling the query and each time we had to set the mem_limit to higher value and re-run although OS has sufficient amount of memory to allocate. Version : CDH5.8.2

Johnny_Bach · ‎09-27-2018

i'm receving the below error message on memory limit although there is enough default memory limit set on the resource pool and explan plan only shows 288 MB out of 18 nodes cluster which leads to 5184 MB of total memory consumption +-----------------------------------------------------------+ | Explain String | +-----------------------------------------------------------+ | Estimated Per-Host Requirements: Memory=288.00MB VCores=1 | | | | 01:EXCHANGE [UNPARTITIONED] | | | limit: 1 | | | | | 00:SCAN HDFS [fenet5.hmig_os_changes_details_malicious] | | partitions=1/25 files=3118 size=110.01GB | | predicates: job_id = 55451 | | limit: 1 | +-----------------------------------------------------------+ WARNINGS: Memory limit exceeded HdfsParquetScanner::ReadDataPage() failed to allocate 269074889 bytes for dictionary. Memory Limit Exceeded HDFS_SCAN_NODE (id=0) could not allocate 257.23 MB without exceeding limit. Query(294eb435fbf8fc63:f529602818758c80) Limit: Limit=20.00 GB Consumption=20.00 GB Fragment 294eb435fbf8fc63:f529602818758c8b: Consumption=20.00 GB HDFS_SCAN_NODE (id=0): Consumption=20.00 GB DataStreamSender: Consumption=1.45 KB Block Manager: Limit=16.00 GB Consumption=0 Memory Limit Exceeded HDFS_SCAN_NODE (id=0) could not allocate 255.63 MB without exceeding limit. Query(294eb435fbf8fc63:f529602818758c80) Limit: Limit=20.00 GB Consumption=20.00 GB Fragment 294eb435fbf8fc63:f529602818758c8b: Consumption=20.00 GB HDFS_SCAN_NODE (id=0): Consumption=20.00 GB DataStreamSender: Consumption=1.45 KB Block Manager: Limit=16.00 GB Consumption=0 Memory Limit Exceeded HDFS_SCAN_NODE (id=0) could not allocate 255.27 MB without exceeding limit. Query(294eb435fbf8fc63:f529602818758c80) Limit: Limit=20.00 GB Consumption=20.00 GB Fragment 294eb435fbf8fc63:f529602818758c8b: Consumption=20.00 GB HDFS_SCAN_NODE (id=0): Consumption=20.00 GB DataStreamSender: Consumption=1.45 KB Block Manager: Limit=16.00 GB Consumption=0 Memory Limit Exceeded HDFS_SCAN_NODE (id=0) could not allocate 255.39 MB without exceeding limit. Query(294eb435fbf8fc63:f529602818758c80) Limit: Limit=20.00 GB Consumption=20.00 GB Fragment 294eb435fbf8fc63:f529602818758c8b: Consumption=20.00 GB HDFS_SCAN_NODE (id=0): Consumption=20.00 GB DataStreamSender: Consumption=1.45 KB Block Manager: Limit=16.00 GB Consumption=0 Memory Limit Exceeded HDFS_SCAN_NODE (id=0) could not allocate 16.09 KB without exceeding limit. Query(294eb435fbf8fc63:f529602818758c80) Limit: Limit=20.00 GB Consumption=19.74 GB Fragment 294eb435fbf8fc63:f529602818758c8b: Consumption=19.74 GB HDFS_SCAN_NODE (id=0): Consumption=19.74 GB DataStreamSender: Consumption=1.45 KB Block Manager: Limit=16.00 GB Consumption=0 Memory Limit Exceeded HDFS_SCAN_NODE (id=0) could not allocate 15.20 KB without exceeding limit. Query(294eb435fbf8fc63:f529602818758c80) Limit: Limit=20.00 GB Consumption=19.64 GB Fragment 294eb435fbf8fc63:f529602818758c8b: Consumption=19.64 GB HDFS_SCAN_NODE (id=0): Consumption=19.64 GB DataStreamSender: Consumption=1.45 KB Block Manager: Limit=16.00 GB Consumption=0 Memory Limit Exceeded HDFS_SCAN_NODE (id=0) could not allocate 14.61 KB without exceeding limit. Query(294eb435fbf8fc63:f529602818758c80) Limit: Limit=20.00 GB Consumption=19.64 GB Fragment 294eb435fbf8fc63:f529602818758c8b: Consumption=19.64 GB HDFS_SCAN_NODE (id=0): Consumption=19.64 GB DataStreamSender: Consumption=1.45 KB Block Manager: Limit=16.00 GB Consumption=0 Memory Limit Exceeded HDFS_SCAN_NODE (id=0) could not allocate 257.11 MB without exceeding limit. Query(294eb435fbf8fc63:f529602818758c80) Limit: Limit=20.00 GB Consumption=19.47 GB Fragment 294eb435fbf8fc63:f529602818758c8b: Consumption=19.47 GB HDFS_SCAN_NODE (id=0): Consumption=19.47 GB DataStreamSender: Consumption=1.45 KB Block Manager: Limit=16.00 GB Consumption=0 Memory Limit Exceeded HDFS_SCAN_NODE (id=0) could not allocate 255.51 MB without exceeding limit. Query(294eb435fbf8fc63:f529602818758c80) Limit: Limit=20.00 GB Consumption=19.24 GB Fragment 294eb435fbf8fc63:f529602818758c8b: Consumption=19.24 GB HDFS_SCAN_NODE (id=0): Consumption=19.24 GB DataStreamSender: Consumption=1.45 KB Block Manager: Limit=16.00 GB Consumption=0 Memory Limit Exceeded HDFS_SCAN_NODE (id=0) could not allocate 255.32 MB without exceeding limit. Query(294eb435fbf8fc63:f529602818758c80) Limit: Limit=20.00 GB Consumption=19.24 GB Fragment 294eb435fbf8fc63:f529602818758c8b: Consumption=19.24 GB HDFS_SCAN_NODE (id=0): Consumption=19.24 GB DataStreamSender: Consumption=1.45 KB Block Manager: Limit=16.00 GB Consumption=0 Memory Limit Exceeded HDFS_SCAN_NODE (id=0) could not allocate 255.73 MB without exceeding limit. Query(294eb435fbf8fc63:f529602818758c80) Limit: Limit=20.00 GB Consumption=19.49 GB Fragment 294eb435fbf8fc63:f529602818758c8b: Consumption=19.49 GB HDFS_SCAN_NODE (id=0): Consumption=19.49 GB DataStreamSender: Consumption=1.45 KB Block Manager: Limit=16.00 GB Consumption=0 Memory Limit Exceeded HDFS_SCAN_NODE (id=0) could not allocate 255.29 MB without exceeding limit. Query(294eb435fbf8fc63:f529602818758c80) Limit: Limit=20.00 GB Consumption=19.49 GB Fragment 294eb435fbf8fc63:f529602818758c8b: Consumption=19.49 GB HDFS_SCAN_NODE (id=0): Consumption=19.49 GB DataStreamSender: Consumption=1.45 KB Block Manager: Limit=16.00 GB Consumption=0 Memory Limit Exceeded HDFS_SCAN_NODE (id=0) could not allocate 256.61 MB without exceeding limit. Query(294eb435fbf8fc63:f529602818758c80) Limit: memory limit exceeded. Limit=20.00 GB Consumption=20.00 GB Fragment 294eb435fbf8fc63:f529602818758c8e: Consumption=20.00 GB HDFS_SCAN_NODE (id=0): Consumption=20.00 GB DataStreamSender: Consumption=1.45 KB Block Manager: Limit=16.00 GB Consumption=0 Memory Limit Exceeded HDFS_SCAN_NODE (id=0) could not allocate 256.05 MB without exceeding limit. Query(294eb435fbf8fc63:f529602818758c80) Limit: Limit=20.00 GB Consumption=19.69 GB Fragment 294eb435fbf8fc63:f529602818758c8e: Consumption=19.69 GB HDFS_SCAN_NODE (id=0): Consumption=19.69 GB DataStreamSender: Consumption=1.45 KB Block Manager: Limit=16.00 GB Consumption=0 Memory Limit Exceeded HDFS_SCAN_NODE (id=0) could not allocate 255.35 MB without exceeding limit. Query(294eb435fbf8fc63:f529602818758c80) Limit: Limit=20.00 GB Consumption=17.97 GB Fragment 294eb435fbf8fc63:f529602818758c8e: Consumption=17.97 GB HDFS_SCAN_NODE (id=0): Consumption=17.72 GB DataStreamSender: Consumption=1.45 KB Block Manager: Limit=16.00 GB Consumption=0 Memory Limit Exceeded HDFS_SCAN_NODE (id=0) could not allocate 1.02 KB without exceeding limit. Query(294eb435fbf8fc63:f529602818758c80) Limit: Limit=20.00 GB Consumption=17.63 GB Fragment 294eb435fbf8fc63:f529602818758c8e: Consumption=17.63 GB HDFS_SCAN_NODE (id=0): Consumption=17.63 GB DataStreamSender: Consumption=1.45 KB Block Manager: Limit=16.00 GB Consumption=0 Memory Limit Exceeded HDFS_SCAN_NODE (id=0) could not allocate 1.01 KB without exceeding limit. Query(294eb435fbf8fc63:f529602818758c80) Limit: Limit=20.00 GB Consumption=16.94 GB Fragment 294eb435fbf8fc63:f529602818758c8e: Consumption=16.94 GB HDFS_SCAN_NODE (id=0): Consumption=16.68 GB DataStreamSender: Consumption=1.45 KB Block Manager: Limit=16.00 GB Consumption=0 Memory Limit Exceeded HDFS_SCAN_NODE (id=0) could not allocate 88.00 KB without exceeding limit. Query(294eb435fbf8fc63:f529602818758c80) Limit: Limit=20.00 GB Consumption=16.61 GB Fragment 294eb435fbf8fc63:f529602818758c8e: Consumption=16.61 GB HDFS_SCAN_NODE (id=0): Consumption=16.36 GB DataStreamSender: Consumption=1.45 KB Block Manager: Limit=16.00 GB Consumption=0 Memory Limit Exceeded HDFS_SCAN_NODE (id=0) could not allocate 255.23 MB without exceeding limit. Query(294eb435fbf8fc63:f529602818758c80) Limit: Limit=20.00 GB Consumption=16.30 GB Fragment 294eb435fbf8fc63:f529602818758c8e: Consumption=16.30 GB HDFS_SCAN_NODE (id=0): Consumption=16.30 GB DataStreamSender: Consumption=1.45 KB Block Manager: Limit=16.00 GB Consumption=0 Memory Limit Exceeded Query(294eb435fbf8fc63:f529602818758c80) Limit: Limit=20.00 GB Consumption=8.02 GB Fragment 294eb435fbf8fc63:f529602818758c8e: Consumption=8.02 GB HDFS_SCAN_NODE (id=0): Consumption=8.02 GB Block Manager: Limit=16.00 GB Consumption=0

Johnny_Bach · ‎09-25-2018

@mmm286- in-case your issue is resolved , could you please kindly update the details and mark as solved

Johnny_Bach · ‎09-20-2018

Could you verify the troublshooting steps mentioned in below link and see if you need to fix anything at your end https://community.cloudera.com/t5/Cloudera-Manager-Installation/Getting-quot-heartbeat-quot-errors-when-trying-to-install/ta-p/36843

Johnny_Bach · ‎09-20-2018

have you verified if 7182 port is open using telnet

Online	Offline
Last Visited	‎05-28-2020 04:26 AM

Member Since	‎03-19-2018 12:18 AM
Last Visited	‎05-28-2020 04:26 AM
Posts	47
Kudos received	2

Cloudera Community

Re: Hue RestException: bad handshake - certificate...

Does External Authentication comes only will limit...

Re: Hive partition getting dropped while HDFS serv...

Hive partition getting dropped while HDFS service ...

Re: Impala - Memory limit exceeded

Re: Error Impala admission control

Impala - Memory limit exceeded

Re: Configured Capacity 0

Re: Agent Heartbeat not working with error: Connec...

Re: Agent Heartbeat not working with error: Connec...