Re: How do I determine a library mismatch between jdbc client and server?

you might just end up using your own heuristics. if the port is "alive" (ie. you can list it via netstat or telnet to it) but you can't connect... then you got yourself a problem. kinda like a bootstrapping problem, eh? you need to connect to get the version but you can't connect if you don't

How do I determine a library mismatch between jdbc client and server?

Hi, I'm trying to do development in an environment where we have a mixed bag of clusters. Some Cloudera, some Hortonworks, different versions of each, etc. (I don't know if we'll see this mix in the field but we need the variety for testing our software.) Sometimes the poor overworked developer

Re: Hive queries rejected under heavy load

gotta start by looking at the logs and run the local client to eliminate HS2. perhaps running hive as such: $ hive -hiveconf hive.root.logger=DEBUG,console do you see any smoking gun? On Wed, Sep 28, 2016 at 7:34 AM, Jose Rozanec wrote: > Hi, > > We have a

Re: how to dynamically find out hivesever2's host name?

One of the changes (HIVE-14063) which I have been working on can potentially solve your problem. The change essentially detects the hiveserver2 host from the hive-site.xml. The change is still in review and not yet available but you can do something similar. > On Sep 28, 2016, at 8:55 AM,

how to dynamically find out hivesever2's host name?

I am trying to use one set of scripts for different Hadoop clusters in different environments, for example DEV/QA/PROD environments with corresponding clusters. The difficulty I am facing is that the host name of hiveserver2 is a part of the connection url, which has to vary between

RE: How to obtain concurrent query executions

If you are using Hadoop 2.7 or newer, you can use mapreduce.job.running.map.limit and mapreduce.job.running.reduce.limit to restrict map and reduce tasks at each job level. Another way is to use Scheduler to limit queue size. From: Jose Rozanec [mailto:jose.roza...@mercadolibre.com] Sent:

Hive queries rejected under heavy load

Hi, We have a Hive cluster (Hive 2.1.0+Tez 0.8.4) which works well for most queries. Though for some heavy ones we observe that sometimes are able to execute and sometimes get rejected. We are not sure why we get a rejection instead of getting them enqueued and wait for execution until resources

hiveserver2 hostname

How do I dynamically get the configured hiveserver2 hostname for a cluster? Thanks, Shyla Access the Q2 2016 Digital Marketing Report for a fresh set of trends and benchmarks in digital marketing Download our latest report titled “The Case

Re: Configure hiveserver2 logs

Hi Kishore, Setting above 3 parameters enables query/operations logs. If you are looking for HiveServer2 process log, you'll need to configure it while launching HiveServer2 Process with following jvm params "-Dhive.log.dir= -Dhive.log.file=hive-server2.log" You can refer to "Hive Logging"

Re: Query consuming all resources

What Jörn said. We use the capacity scheduler to be able to give priority to some user groups over others. Regards /Pelle On Wednesday, September 28, 2016, Jörn Franke wrote: > You need to configure queues in yarn and use the fairscheduler. From your > use case it looks

Re: Query consuming all resources

You need to configure queues in yarn and use the fairscheduler. From your use case it looks like you need to also configure pre-emption > On 28 Sep 2016, at 00:52, Jose Rozanec wrote: > > Hi, > > We have a Hive cluster. We notice that some queries consume all