while I'm still trying to find anything useful in the logs, my question is why isn't HBase self managing this? In my 2-3 decades of using databases i had never had to stop a write operation to do anything such as compactions or whatever. The only time a write would fail would be if the db runs out of physical storage. The client could slowness due to many writes but throwing exceptions was unheard of.
________________________________ From: jeff saremi <[email protected]> Sent: Friday, May 19, 2017 8:18:59 PM To: [email protected] Subject: Re: What is the cause for RegionTooBusyException? Thanks Ted. I will look deeper as you suggested ________________________________ From: Ted Yu <[email protected]> Sent: Friday, May 19, 2017 4:18:12 PM To: [email protected] Subject: Re: What is the cause for RegionTooBusyException? Have you checked region server log ? Please take a look at the following method in HRegion: private void checkResources() throws RegionTooBusyException { ... if (this.memstoreDataSize.get() > this.blockingMemStoreSize) { blockedRequestsCount.increment(); requestFlush(); throw new RegionTooBusyException("Above memstore limit, " + Which hbase release are you using ? Cheers On Fri, May 19, 2017 at 3:59 PM, jeff saremi <[email protected]> wrote: > We're getting errors like this. Where should we be looking into to solve > this? > > > Failed 69261 actions: RegionTooBusyException: 12695 times, > RemoteWithExtrasException: 56566 times > > thanks > > Jeff > >
