Re: after region split, client didnt get result after timeout setting,so the cachedLocation didnot update, client still query the old region id

so it is very wired that in parts of my servers, I didnot get the error and so the cache was not cleaned. 2012/8/10 N Keywal > If it's a single row, I would expect the server to return the error > immediately. Then you will have the sleep I was mentioning previously, > but the cache should be cl

Re: after region split, client didnt get result after timeout setting,so the cachedLocation didnot update, client still query the old region id

If it's a single row, I would expect the server to return the error immediately. Then you will have the sleep I was mentioning previously, but the cache should be cleaned before the sleep... On Fri, Aug 10, 2012 at 1:32 PM, deanforwever2010 wrote: > hi, Keywal > my hbase version is 0.94, > my que

Re: after region split, client didnt get result after timeout setting,so the cachedLocation didnot update, client still query the old region id

hi, Keywal my hbase version is 0.94, my query is just to get limited columns of a row, I make a callable task of 1.5 seconds, so maybe it didnot fail but canceled by my process,so the region cache didnot clear after many requests happened. my question is why should it take so long time for failure

Re: after region split, client didnt get result after timeout setting,so the cachedLocation didnot update, client still query the old region id

Hi, What are your queries exactly? What's the HBase version? The mechanism is: - There is a location cache, per HConnection, on the client - The client first tries the region server in its cache - if it fails, the client removes this entry from the cache and enters the retry loop - there is a lim