You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@phoenix.apache.org by "Vincent Poon (JIRA)" <ji...@apache.org> on 2018/11/07 18:58:00 UTC

[jira] [Created] (PHOENIX-5005) Server-side delete / upsert-select potentially blocked after a split

Vincent Poon created PHOENIX-5005:
-------------------------------------

             Summary: Server-side delete / upsert-select potentially blocked after a split
                 Key: PHOENIX-5005
                 URL: https://issues.apache.org/jira/browse/PHOENIX-5005
             Project: Phoenix
          Issue Type: Bug
    Affects Versions: 4.14.1
            Reporter: Vincent Poon


After PHOENIX-4214, we stop inbound writes after a split is requested, to avoid split starvation.

However, it seems there can be edge cases, depending on the split policy, where a split is not retried.  For example, IncreasingToUpperBoundSplitPolicy relies on the count of regions, and balancer movement of regions at t1 could make it such that the SplitPolicy triggers at t0 but not t2.

However, after the first split request, in UngroupedAggregateRegionObserver the flag to block inbound writes is flipped indefinitely.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)