1) Update hbase.rpc.timeout : 120 in client side hbase-site.xml
Bad idea. 20 min of timeout?
Check RS log files for unusual GC activity (always run hbase with GC stats
on). That is probably what is going on in there.
On Thu, Apr 9, 2015 at 11:27 AM, Samarth Jain samarth.j...@gmail.com
The phoenix.query.timeoutMs property should be set on the
hbase-site.xml of the client (in the phoenix/bin) directory, not the
server hbase-site.xml. See
https://github.com/forcedotcom/phoenix/wiki/Tuning . Did you try just
setting it on the client side config before starting sqlline and
running
I have to mention I also tried changing these properties on HBase side :
hbase.regionserver.lease.period : 12
hbase.rpc.timeout : 120
I am running on Hortonworks 2.2.0
Phoenix 4.2.0
HBase 0.98.4
From: PERNOLLET Martin (EXT) ItecCttDir
Sent: Thursday 9 April 2015 17:52
To:
Looking at the exception java.lang.RuntimeException:
org.apache.phoenix.exception.PhoenixIOException:
org.apache.phoenix.exception.PhoenixIOException: Failed after attempts=36,
exceptions:
Thu Apr 09 16:49:33 CEST 2015, null,
java.net.SocketTimeoutException: callTimeout=6, callDuration=62366
