Adding this tracing information to know who initiated split is in general useful thing. Right now though I'm not sure I see how that would help to make better normalization decisions? Region split failure implies underlying FS issue? Any examples/ideas?
Kind of..collect statistics to blacklist some RSs with high failure rate and don't attempt to split regions hosted there in future? On Tue, Jan 5, 2016 at 2:55 PM, Ted Yu <yuzhih...@gmail.com> wrote: > Hi, > I recently worked on improving region normalization feature. > > If region split request triggered by the execution of > SplitNormalizationPlan fails, there is no way of knowing whether the failed > split originated from region normalization. > Such association would give RegionNormalizer information so that it can > make better normalization decisions in the subsequent invocations. > > One enhancement I can think of is to embed metadata in SplitRequest which > gets passed through RegionStateTransitionContext when > RegionServerServices#reportRegionStateTransition() is called. > This way, RegionStateListener can be notified with the metadata (id of the > requester). > > Comment is welcome. > -- Thanks, Michael Antonov
