Details
-
Improvement
-
Status: Resolved
-
Minor
-
Resolution: Won't Fix
-
1.1.2
-
None
-
None
Description
According to our observation, a running coprocessor that is automatically stopped prior to region split will not be automatically restarted for the region that was about to be split in case the split attempt is rolled back.
The expected behavior would be for the coprocessor to be automatically restarted in such situation.
According to this conversation the lack of the automatic restart looks more like an omission rather than an intended behavior.
A possible work-around seems to be handling the restart explicitly in RegionObserver#postRollBackSplit() implementation, such as in this example.