Can you check region server log to see if region m_test, 64d7e88463b88e7325b623fbd6629cda,1408803862959. cb513be341b94588469efa9d26d29857. moved / splitted between MR job launch and the time when this error showed up ?
Thanks On Fri, Oct 3, 2014 at 4:08 PM, Thomas Kwan <thomas.k...@manage.com> wrote: > Hi there, > > Wonder if anyone has seen error like this > > 2014-10-03 16:03:45,203 WARN [RpcServer.handler=7,port=60020] > regionserver.HRegion: Failed getting lock in batch put, > row=65317d52abfedc8b94a19f6fbffe187c > org.apache.hadoop.hbase.regionserver.WrongRegionException: Requested row > out of range for row lock on HRegion > > m_test,64d7e88463b88e7325b623fbd6629cda,1408803862959.cb513be341b94588469efa9d26d29857., > startKey='64d7e88463b88e7325b623fbd6629cda', > getEndKey()='6516687f5dae26f529c53f309cb36fca', > row='65317d52abfedc8b94a19f6fbffe187c' > > > Recently, we have added 10 more region servers to our cluster and then I > started seeing errors like above when doing puts via TableOutputFormat in a > MR job. > > Maybe where hbase stores the region info is corrupted? > > thanks for your help in advance > thomas >
