we are getting inundated with RPC exceptions in Thrift server. Is anyone here
that could point us to where the problem is?
According to the Master UI everything is good, no regions in transition, no
FAILED_CLOSE, no red tasks or anything like that, no Offline regions, nothing
__
You must have some stack trace once all the retries are exhausted (tries=36,
retries=35). can you please share that.
On Mon, Aug 7, 2017 at 11:53 PM, jeff saremi wrote:
> Just checked
>
> THe keys are URLs. The region name has that and also the intended lookup
> key is a URL. So I think they are
Hi everyone,
Does anyone know of a ycdb option that will allow the following read request
distribution:
1. 90% of the material read was inserted in the last 24 hours.2. 97% in the
last 2 hours.
The only options i see for request distribution is "latest", "zipfian" and
"uniform"
Is there anyway
You were right, moving to 2.6.1 solved my problem, thanks a lot for your help
!
--
View this message in context:
http://apache-hbase.679495.n3.nabble.com/HBase-connection-expiration-on-kerberized-cluster-tp4089493p4089611.html
Sent from the HBase User mailing list archive at Nabble.com.
