What's the current region size you use ? bq. During the processing size of the data gets increased
Can you give us some quantitative measure as to how much increase you observed (w.r.t. region size) ? bq. I was looking for some "global lock" in source code Probably not a good idea using global lock. I am curious, looks like your coprocesser may rewrite a lot of data written into the table. Can client side accommodate such logic so that the rewrite is reduced ? Thanks On Fri, Mar 25, 2016 at 8:55 AM, Daniel Połaczański <[email protected]> wrote: > Hi, > I have some processing in my coprocesserService which modifies the existing > data in place. It iterates over every row, modifies and puts it back to > region. The table can be modified by only one client. > > During the processing size of the data gets increased -> region's size get > increased -> region's split happens. It makes that the processing is > stopped by exception NotServingRegionException (because region is closed > and splited to two new regions so it is closed and doesn't exist anymore). > > Is there any clean way to block Region's splitting? > > I was looking for some "global lock" in source code but I haven't found > anything helpfull. > Another idea is to create custom RegionSplitPolicy and explicilty set some > Flag which will return false in shouldSplit(), but I'm not sure yet if it > is safe. > Could you advise? > Regards >
