hbase-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sumit Nigam <sumit_o...@yahoo.com.INVALID>
Subject hbase.client.retries.number
Date Fri, 27 Nov 2015 04:42:33 GMT
Hi,
Need some help/ inputs.
I have set hbase.client.retries.number as 40. Double checked this to make sure it is 40 and
not 400 as reported below!
However, I notice following in my logs:
2015-11-19 16:35:02,687 WARN  [htable-pool5-t1] client.AsyncProcess: #3, table=ldmns:indx_parameterstore,
attempt=401/400 failed 2 ops, last exception: java.net.ConnectException: Connection refused
on ip-172-31-23-41.us-west-2.compute.internal,44031,1447969471426, tracking started Thu Nov
19 14:23:54 PST 2015 - FAILED, NOT RETRYING ANYMORE
Not sure why 400 attempts are being made. The problem is that it seems to show 2+ hours of
time taken to fail because of these 400 attempts.
Then, I am also not sure why just a little later another thread succeeds (again after 2 hours!!
):
2015-11-19 16:35:21,921 INFO  [htable-pool6-t3] client.AsyncProcess: #4, table=ldmns:indx_parameterstore,
attempt=402/400 SUCCEEDED on ip-172-31-23-41.us-west-2.compute.internal,46620,1447971819216,
tracking started Thu Nov 19 14:23:54 PST 2015
What surprises me is that it seems to have even gone beyond 400 attempts. That seems like
a bug to me. It seems it would have kept trying beyond 400 attempts until it succeeded. Or
am I missing something? Also, where is this 400 coming from if not from hbase.client.retries.number?
This is with Hbase 0.98.14.
Thanks,Sumit


Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message