,,..And you can Pre-split yout Table... and give a random & uniform
property to your rowkey...
Then you can able to distribute your PUT operation load over different
region server...



On Tue, Feb 25, 2014 at 10:19 PM, Nicolas Liochon <[email protected]> wrote:

> That's "standard", even if it's a behavior change compared to 0.94.
> It means you're sending puts faster that the server can write.
> In such situation, in 0.94, the operation was paused server side. In 0.96,
> HBase sends an exception back to the client, and it's up to it to retry
> (and it does retry).
> Now this server seems quite busy, it's the attempt #12... May be something
> bad is happening on the region server.
>
>
> On Tue, Feb 25, 2014 at 5:16 PM, shapoor <[email protected]> wrote:
>
> > hello,
> > I just got this exception from hbase-0.96.1.1-hadoop2 while sending too
> > many
> > read/write requests for a longer time. Should something be configured?
> >
> > 14/02/25 16:26:37 INFO client.AsyncProcess: #3, waiting for some tasks to
> > finish. Expected max=0, tasksSent=898465, tasksDone=898464,
> > currentTasksDone=898464, retries=215 hasError=false, tableName=test-table
> > 14/02/25 16:26:37 INFO client.AsyncProcess: #3, table=test-table,
> > attempt=12/35 failed 1 ops, last exception:
> > org.apache.hadoop.hbase.RegionTooBusyException:
> > org.apache.hadoop.hbase.RegionTooBusyException: Above memstore limit,
> >
> >
> regionName=test-table,doc-id-843162,1393341942533.8477b42b33d2fe9abb2b25a4e5e94b24.,
> > server=kcs-testhadoop01,60020,1393335573827, memstoreSize=268441392,
> > blockingMemStoreSize=268435456
> >         at
> >
> >
> org.apache.hadoop.hbase.regionserver.HRegion.checkResources(HRegion.java:2546)
> >         at
> >
> org.apache.hadoop.hbase.regionserver.HRegion.batchMutate(HRegion.java:1948)
> >         at
> >
> >
> org.apache.hadoop.hbase.regionserver.HRegionServer.doBatchOp(HRegionServer.java:4043)
> >         at
> >
> >
> org.apache.hadoop.hbase.regionserver.HRegionServer.doNonAtomicRegionMutation(HRegionServer.java:3354)
> >         at
> >
> >
> org.apache.hadoop.hbase.regionserver.HRegionServer.multi(HRegionServer.java:3258)
> >         at
> >
> >
> org.apache.hadoop.hbase.protobuf.generated.ClientProtos$ClientService$2.callBlockingMethod(ClientProtos.java:26935)
> >         at
> org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2175)
> >         at
> > org.apache.hadoop.hbase.ipc.RpcServer$Handler.run(RpcServer.java:1879)
> >  on kcs-testhadoop01,60020,1393335573827, tracking started Tue Feb 25
> > 16:25:49 CET 2014, retrying after 20150 ms, replay 1 ops.
> >
> > regards,
> >
> >
> >
> > --
> > View this message in context:
> >
> http://apache-hbase.679495.n3.nabble.com/egionTooBusyException-Above-memstore-limit-tp4056339.html
> > Sent from the HBase User mailing list archive at Nabble.com.
> >
>

Reply via email to