You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Andrew Kyle Purtell (Jira)" <ji...@apache.org> on 2021/05/02 21:22:00 UTC

[jira] [Updated] (HBASE-25835) Ignore duplicate split requests from regionserver reports

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

Andrew Kyle Purtell updated HBASE-25835:
----------------------------------------
    Status: Patch Available  (was: Open)

> Ignore duplicate split requests from regionserver reports
> ---------------------------------------------------------
>
>                 Key: HBASE-25835
>                 URL: https://issues.apache.org/jira/browse/HBASE-25835
>             Project: HBase
>          Issue Type: Sub-task
>    Affects Versions: 2.4.3
>            Reporter: Andrew Kyle Purtell
>            Assignee: Andrew Kyle Purtell
>            Priority: Major
>             Fix For: 3.0.0-alpha-1, 2.5.0, 2.4.3
>
>
> A SplitTableRegionProcedure may already be running when a regionserver report is received that includes a split request. The outcome is multiple SplitTableRegionProcedure procedures scheduled for the split request, only one of which can succeed. The others error out. Perhaps it is only WARN level noise in the logs that will cause operator concern, but is clearly not correct. 
> Do not create a split procedure in response to a region state change report if the region is not open or already splitting.



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