On Tue, Jul 5, 2011 at 1:56 AM, Ramkrishna S Vasudevan <[email protected]> wrote: > I was working on the patch preparation for HBASe-4052. > Thank you for doing this.
... > Am i clear with the problem? so is it like before enabling any table do we > need to check the state of the table and if it is DISABLING make all those > regions to go to > > offline mode. > I think I follow. Yes, after all regionservers check in and after you scan the .META. table, IF a table is DISABLING or DISABLED, it might make sense to send a close to all regionservers that are members of the set of online servers so for sure you've closed all regions. Or, we need to keep state somewhere. We used to update the regioninfo in .META. adding the attribute 'offline'. But I think we only use this when splitting regions now. Perhaps if a region is disabled, we can mark it so by clearing its startcode and server from .META.; i.e. an entry in .META. without a startcode+server is an offline region (We could not do this in .20.x hbase because we had a meta scanner that would assign out anything with a bad or empty server). St.Ack
