Member since
12-11-2015
199
Posts
29
Kudos Received
30
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
237 | 08-14-2024 06:24 AM | |
1231 | 10-02-2023 06:26 AM | |
1140 | 07-28-2023 06:28 AM | |
7233 | 06-02-2023 06:06 AM | |
593 | 01-09-2023 12:20 PM |
02-09-2020
06:10 PM
1 Kudo
The tuning of this property totally depends on your use case. yarn.scheduler.capacity.<queue-path>.maximum-am-resource-percent: Queue level AMshare For instance lets say your cluster is primarily used for oozie. For each oozie action [except sshaction] you will have a oozie launcher application(map-only job which will start the jobs) and an external application which actually does the job. In this case you will have a requirement to run lots of application and inturn lots of application master. In such cases if you want to achieve more parallelism you will create a dedicated queue for launcher application[oozie.launcher.mapred.job.queue.name can be used to direct all launcher application to this dedicated queue] and another another queue for the external application. You can then set 0.5 to launcher queue which has a single AM and single Mapper so equal distribution is rational setting. At cluster level yarn.scheduler.capacity.maximum-am-resource-percent - lets say you have the capacity to run 1000 containers and each of your application on an average runs 10 mapper. Then setting this value to 10% would allow you to run, 100 application in parallel (100 application master and 900 mappers). If you set this to 20% then you get a chance to run 200 application in parallel (200 application master and 800 mapper container) - each application will run short of 2 containers and will wait for other application to finish and the average throughput of your application will be little longer.
... View more
04-08-2019
11:45 PM
1 Kudo
yes you have to upgrade to cdh6.1.0 or higher to use impala-3.1.0 - Its not possible to selectively upgrade impala alone https://www.cloudera.com/documentation/enterprise/6/release-notes/topics/rg_cdh_61_packaging.html
... View more
02-12-2019
10:02 PM
What exact command you used for impala-shell? Can you try impala-shell -i <haproxy-host> and let us know if it works. Also do you have any overrides in hue.ini, hue_safety_valve.ini hue_safety_valve_server.ini If yes what values are under [impala] tag? Also Is there any reason behind having ELB and also Haproxy?
... View more
02-12-2019
01:32 AM
<td> <samp>principal (string)</samp></td> <td><samp>impala/master2-impala-20.yodlee.com@YODLEEINSIGHTS.COM</samp></td> Impalad will expect the client to use this SPN while client tries to connect to it. This is why it failed when you put host fqdn as haproxy When you enable haproxy in CM > Impala > Configuration > Impalad Load Balancer name then CM will prepare a merged keytab consisting of SPN of the loadbalancer and also changes this principal field in impalad configuration to haproxy spn, After which you will be able to connect to impalad.
... View more
02-11-2019
09:36 PM
What value are you noticing for principal in the impalad-webui varz page? https://<impalad-hostname>:25000/varz Did you add the ELB or Haproxy details in the CM > Impala > Configuration > Impala Daemons Load Balancer ?
... View more
02-07-2019
07:09 PM
Impala relies on hivemetastore for persisting table metadata. HMS inturn uses db to persist metadata. So if the db's filesystem is out of space, request from hms to persist metadata will be denied and yes if the space on the db is not freed up then request from hms will be failed and eventually impala also fails the query
... View more
05-16-2018
11:59 PM
Is the issue reported in this thread happened in UAT or in PROD? From UAT configs, the default timeouts are around 5 minutes and overridden timeouts are around 1 hr. Is the error that you posted happens for long running jdbc application maintaining a single connection ? Can you check if you increase the timeouts[lets say 2hr] further, the issue still happens?
... View more
05-16-2018
11:33 PM
Can you paste the haproxy.cfg here. Just want to have a look at the connection timeout configured The error you see happens if the connection between client and impalad gets broken. having a lower connection timeout on haproxy can potentially cause this
... View more
05-16-2018
11:22 PM
Is there any loadbalancer inbetween the client and impalad? if yes, try to increase the conntimeout on the LB
... View more
03-05-2017
03:20 AM
Command to test reverse resolution is described in this link http://linuxcommando.blogspot.in/2008/07/how-to-do-reverse-dns-lookup.html
... View more