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

["Vincent Poon (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/PHOENIX-5005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vincent Poon resolved PHOENIX-5005.
-----------------------------------
       Resolution: Resolved
    Fix Version/s: 4.15.0

Pushed to 4.x branches.  It seems the 5.x branch no longer has a preSplit hook, so not applying it there.

> 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
>            Assignee: Vincent Poon
>            Priority: Major
>             Fix For: 4.15.0
>
>         Attachments: PHOENIX-5005.4.x-HBase-1.4.v1.patch, PHOENIX-5005.4.x-HBase-1.4.v2.patch, PHOENIX-5005.4.x-HBase-1.4.v3.patch
>
>
> 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)