For sure the regions was not doubly-assigned? Split happened of the region on one server but on another server, the same region was being compacted? You'd need the master logs to figure it a dbl-assign
Unfortunately, didn't save the master logs when the failure happened..
Can you figure a place where we'd be running compactions on a region concurrent w/ our splitting it? Compacting we take out write lock. Doesnt look like any locks while SplitTransaction is running (closing parent, it'll need write lock... thats after daughters open though).
I can't figure out a place where this could happen in the natural execution of the regionserver.
Storefiles are an ImmutableList.
Yes.. but that still could be exposed to the problems of memory inconsistencies when multiple threads are accessing the object in unsynchronized/non-volatile ways, no?
After a long time, someone addressed me by that name
So before this itself the region got closed. I feel the store file list should have been updated by the time. No ?
Can't say Ram for sure. There is no guarantee unless the access (read/write) are synchronized or the field is declared volatile..