Yes, value 1 for "hbase.client.retries.number" is the root cause of above
exception.
General guideline/formulae could be(not official):-
(time taken for region movement in your cluster + timeout of zookeeper) /
hbase.client.pause
Or with intuition, you can set to at least 10.
On Fri, Jul 14,
Thanks Josh for the quick reply
So we are not getting the Exception transiently, but it get thrown out our
application code wrapped in an SQLException from Phoenix layer.
For now, we have written kind of a backoff retry logic which re-tries the
query after some time again but looking for a more
On 7/13/17 1:48 PM, Tanujit Ghosh wrote:
Hi All,
We are facing a problem in our cluster as stated below.
We have a long running java process which does various select on
underlying Phoenix/HBASE table structure and return data. This process
gets requests from other upstream apps and
Hi All,
We are facing a problem in our cluster as stated below.
We have a long running java process which does various select on underlying
Phoenix/HBASE table structure and return data. This process gets requests
from other upstream apps and responds with results from Phoenix/HBASE.
We are
