About Jaraxal

Jaraxal · ‎02-23-2017

@Oriane Unfortunately the Sandbox has a minimum requirement of 8GB of RAM. It tends to run better with 10-12GB. Given that your computer only has 8GB of RAM total, you are going to have issues trying to run the Sandbox. As @Sandeep Nemuri mentioned, you can try to turn off HDP components that you don't need to use. This will save some memory, but I believe you'll still have issues.

Jaraxal · ‎09-28-2016

@Robbert Naastepad No worries!

Jaraxal · ‎02-21-2016

You can download configuration scripts which will provide you recommended settings based on the number of cores and memory of your servers. Download Companion Files

Jaraxal · ‎02-01-2016

I discovered several posts via Google that suggested the problem was hbase.rpc.timeout. When I changed the value of this via Ambari, it had no effect. As I responded below, the problem seemed to be that I was missing the HBASE_CONF_DIR environment variable so it was using the default settings instead of the Ambari configured settings.

Jaraxal · ‎02-01-2016

This was the issue. Well more specifically HBASE_CONF_DIR. Running phoenix_utils.py showed HBASE_CONF_PATH and HBASE_CONF_DIR as equal to ".". I set my HBASE_CONF_DIR environment variable to to use "/etc/hbase/conf" and now the query seems to work ok.

Jaraxal · ‎02-01-2016

I tried that already, as I indicated in my original post. It did not work.

Jaraxal · ‎02-01-2016

I have a table in HBase created via Phoenix. The table has approxmiately 20 million records. I'm connecting to Phoenix via: phoenix-sqlline.py hbasemaster:2181:/hbase-unsecure I'm trying to run a count as follows: select count(columnname) from tablename; When I run that SQL, Phoenix reports a timeout org.apache.phoenix.exception.PhoenixIOException: org.apache.phoenix.exception.PhoenixIOException: Failed after attempts=36, exceptions: java.net.SocketTimeoutException: callTimeout=60000, callDuration=60317: row .... I've tried changing the hbase.rpc.timeout via Ambari, but that doesn't seem to be the issue. The default timeout in Ambari was set to 1m30s and I changed it to 2m. The timeout reported by Phoenix is 60s before and after the change, so I don't think that's the culprit anyway. What setting do I need to change to allow for longer running queries? Is there something else that I should be looking at?

Jaraxal · ‎01-30-2016

@Josh Elser Thank you for the clarification regarding the clients. I didn't expect to see difference in terms of how the sql worked. Using the thin client did help to identify there was a difference between the two.

Jaraxal · ‎01-30-2016

I had an issue with ZK. I stopped HBase via Ambari. I ran "hbase clean --cleanZk". I then started HBase via Ambari. Now the Pig script is loading data. @Neeraj Sabharwal @Josh ElserThanks for helping to resolve the issue via another post.

Jaraxal · ‎01-30-2016

@Neeraj Sabharwal Good catch! Running "hbase clean --cleanZk" fixed the problem. Now the thick and thin client are working similarly.

Online	Offline
Last Visited	‎09-05-2014 03:20 PM

Member Since	‎08-21-2014 01:36 PM
Last Visited	‎09-05-2014 03:20 PM
Posts	23
Kudos received	14

Cloudera Community

Re: spark shell - lack of memory

Re: is there any script that I can run to get the ...

Re: SolR and Banana

Re: spark shell - lack of memory

Re: I need help with the riskfactor pig script fro...

Re: is there any script that I can run to get the ...

Re: Phoenix - Query Timeout

Re: Phoenix - Query Timeout

Re: Phoenix - Query Timeout

Phoenix - Query Timeout

Re: Phoenix - Create Table Question

Re: Phoenix Storage in Pig

Re: Phoenix - Create Table Question