[jira] [Updated] (PHOENIX-6125) Make sure SYSTEM.TASK does not split

["Viraj Jasani (Jira)" <ji...@apache.org>]

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

Viraj Jasani updated PHOENIX-6125:
----------------------------------
    Release Note: 
we have new split policy introduced for SYSTEM.TASK which for now is just extending DisabledRegionSplitPolicy. As part of an upgrade to 4.16/5.1, updating split policy will be taken care of unless it was already updated manually.

Hence, before 4.16/5.1 upgrade, if operator has already manually updated split policy of SYSTEM.TASK, an exception will be thrown during upgrade to 4.16 which would mandate an operator intervention to perform:

1. Merging SYSTEM.TASK regions into one single region (if multiple regions were already available before 4.16/5.1 upgrade)
2. Remove split policy of the table manually.

> Make sure SYSTEM.TASK does not split
> ------------------------------------
>
>                 Key: PHOENIX-6125
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-6125
>             Project: Phoenix
>          Issue Type: Improvement
>    Affects Versions: 5.0.0, 4.15.0
>            Reporter: Chinmay Kulkarni
>            Assignee: Viraj Jasani
>            Priority: Major
>             Fix For: 5.1.0, 4.16.0
>
>         Attachments: PHOENIX-6125.4.x.000.patch
>
>
> To avoid problems such as [PHOENIX-5945|https://issues.apache.org/jira/browse/PHOENIX-5945] we can just prevent SYSTEM.TASK from splitting. 
> Currently we only store relatively rare tasks inside SYSTEM.TASK and so we should probably be safe to assume that it only spans a single region. Note that we will also have to handle changing the split policy during the upgrade path for 4.15 operators.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)