[jira] [Commented] (HBASE-27781) AssertionError in AsyncRequestFutureImpl when timing out during location resolution

[ https://issues.apache.org/jira/browse/HBASE-27781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17888015#comment-17888015 ] Daniel Roudnitsky commented on HBASE-27781: --- Hi [~bbeaudreault] is this someth

[jira] [Commented] (HBASE-28771) Add support for non replica actions to AsyncRequestFutureImpl.isActionComplete

[ https://issues.apache.org/jira/browse/HBASE-28771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17887674#comment-17887674 ] Daniel Roudnitsky commented on HBASE-28771: --- [~ndimiduk] yes I don't think its

[jira] [Updated] (HBASE-28608) More sensible client meta operation timeout default

[ https://issues.apache.org/jira/browse/HBASE-28608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Roudnitsky updated HBASE-28608: -- Description: Documented behavior in the HBase reference for client meta operation time

[jira] [Updated] (HBASE-28608) More sensible client meta operation timeout default

[ https://issues.apache.org/jira/browse/HBASE-28608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Roudnitsky updated HBASE-28608: -- Description: Documented behavior in the HBase reference for client meta operation time

[jira] [Commented] (HBASE-27781) AssertionError in AsyncRequestFutureImpl when timing out during location resolution

[ https://issues.apache.org/jira/browse/HBASE-27781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17885930#comment-17885930 ] Daniel Roudnitsky commented on HBASE-27781: --- My first proposed solution did no

[jira] [Updated] (HBASE-28771) Add support for non replica actions to AsyncRequestFutureImpl.isActionComplete

[ https://issues.apache.org/jira/browse/HBASE-28771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Roudnitsky updated HBASE-28771: -- Resolution: Not A Problem Status: Resolved (was: Patch Available) Not needed

[jira] [Created] (HBASE-28785) Canary should not create RefreshCredentials chore if not in daemon mode

Daniel Roudnitsky created HBASE-28785: - Summary: Canary should not create RefreshCredentials chore if not in daemon mode Key: HBASE-28785 URL: https://issues.apache.org/jira/browse/HBASE-28785 Pro

[jira] [Commented] (HBASE-28730) Locating region can exceed client operation timeout

[ https://issues.apache.org/jira/browse/HBASE-28730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17872642#comment-17872642 ] Daniel Roudnitsky commented on HBASE-28730: --- In my batch operations testing I

[jira] [Updated] (HBASE-28771) Add support for non replica actions to AsyncRequestFutureImpl.isActionComplete

[ https://issues.apache.org/jira/browse/HBASE-28771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Roudnitsky updated HBASE-28771: -- Description: The current isActionComplete method we have in AsyncRequestFutureImpl is

[jira] [Updated] (HBASE-28771) Add support for non replica actions to AsyncRequestFutureImpl.isActionComplete

[ https://issues.apache.org/jira/browse/HBASE-28771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Roudnitsky updated HBASE-28771: -- Description: The current isActionComplete method we have in AsyncRequestFutureImpl is

[jira] [Updated] (HBASE-27781) AssertionError in AsyncRequestFutureImpl when timing out during location resolution

[ https://issues.apache.org/jira/browse/HBASE-27781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Roudnitsky updated HBASE-27781: -- Status: Patch Available (was: In Progress) > AssertionError in AsyncRequestFutureImpl

[jira] [Commented] (HBASE-27781) AssertionError in AsyncRequestFutureImpl when timing out during location resolution

[ https://issues.apache.org/jira/browse/HBASE-27781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17871850#comment-17871850 ] Daniel Roudnitsky commented on HBASE-27781: --- Created a subtask HBASE-28771 and

[jira] [Updated] (HBASE-28771) Add support for non replica actions to AsyncRequestFutureImpl.isActionComplete

[ https://issues.apache.org/jira/browse/HBASE-28771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Roudnitsky updated HBASE-28771: -- Affects Version/s: 2.5.10 2.6.0 Status: Patch Ava

[jira] [Work started] (HBASE-28771) Add support for non replica actions to AsyncRequestFutureImpl.isActionComplete

[ https://issues.apache.org/jira/browse/HBASE-28771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on HBASE-28771 started by Daniel Roudnitsky. - > Add support for non replica actions to AsyncRequestFutureImpl.isAct

[jira] [Created] (HBASE-28771) Add support for non replica actions to AsyncRequestFutureImpl.isActionComplete

Daniel Roudnitsky created HBASE-28771: - Summary: Add support for non replica actions to AsyncRequestFutureImpl.isActionComplete Key: HBASE-28771 URL: https://issues.apache.org/jira/browse/HBASE-28771

[jira] [Commented] (HBASE-27781) AssertionError in AsyncRequestFutureImpl when timing out during location resolution

[ https://issues.apache.org/jira/browse/HBASE-27781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17871724#comment-17871724 ] Daniel Roudnitsky commented on HBASE-27781: --- My proposed solution that I've dr

[jira] [Work started] (HBASE-27781) AssertionError in AsyncRequestFutureImpl when timing out during location resolution

[ https://issues.apache.org/jira/browse/HBASE-27781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on HBASE-27781 started by Daniel Roudnitsky. - > AssertionError in AsyncRequestFutureImpl when timing out during loc

[jira] [Assigned] (HBASE-27781) AssertionError in AsyncRequestFutureImpl when timing out during location resolution

[ https://issues.apache.org/jira/browse/HBASE-27781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Roudnitsky reassigned HBASE-27781: - Assignee: Daniel Roudnitsky > AssertionError in AsyncRequestFutureImpl when tim

[jira] [Commented] (HBASE-28730) Locating region can exceed client operation timeout

[ https://issues.apache.org/jira/browse/HBASE-28730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17868137#comment-17868137 ] Daniel Roudnitsky commented on HBASE-28730: --- Thank you for the feedback [~bbea

[jira] [Commented] (HBASE-28358) AsyncProcess inconsistent exception thrown for operation timeout

[ https://issues.apache.org/jira/browse/HBASE-28358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17866106#comment-17866106 ] Daniel Roudnitsky commented on HBASE-28358: --- {quote}The main remaining case is

[jira] [Updated] (HBASE-28730) Locating region can exceed client operation timeout

[ https://issues.apache.org/jira/browse/HBASE-28730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Roudnitsky updated HBASE-28730: -- Description: I'll be referring to hbase.client.operation.timeout as 'operation timeout

[jira] [Updated] (HBASE-28730) Locating region can exceed client operation timeout

[ https://issues.apache.org/jira/browse/HBASE-28730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Roudnitsky updated HBASE-28730: -- Description: I'll be referring to hbase.client.operation.timeout as 'operation timeout

[jira] [Updated] (HBASE-28730) Locating region can exceed client operation timeout

[ https://issues.apache.org/jira/browse/HBASE-28730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Roudnitsky updated HBASE-28730: -- Description: I'll be referring to hbase.client.operation.timeout as 'operation timeout

[jira] [Updated] (HBASE-28730) Locating region can exceed client operation timeout

[ https://issues.apache.org/jira/browse/HBASE-28730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Roudnitsky updated HBASE-28730: -- Description: I'll be referring to hbase.client.operation.timeout as 'operation timeout

[jira] [Created] (HBASE-28730) Locating region can exceed client operation timeout

Daniel Roudnitsky created HBASE-28730: - Summary: Locating region can exceed client operation timeout Key: HBASE-28730 URL: https://issues.apache.org/jira/browse/HBASE-28730 Project: HBase

[jira] [Updated] (HBASE-28608) More sensible client meta operation timeout default

[ https://issues.apache.org/jira/browse/HBASE-28608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Roudnitsky updated HBASE-28608: -- Description: Documented behavior in the HBase reference for client meta operation time

[jira] [Updated] (HBASE-28608) More sensible client meta operation timeout default

[ https://issues.apache.org/jira/browse/HBASE-28608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Roudnitsky updated HBASE-28608: -- Description: Documented behavior in the HBase reference for client meta operation time

[jira] [Updated] (HBASE-28608) More sensible client meta operation timeout default

[ https://issues.apache.org/jira/browse/HBASE-28608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Roudnitsky updated HBASE-28608: -- Description: Documented behavior in the HBase reference for client meta operation time

[jira] [Updated] (HBASE-28608) More sensible client meta operation timeout default

[ https://issues.apache.org/jira/browse/HBASE-28608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Roudnitsky updated HBASE-28608: -- Description: Documented behavior in the HBase reference for client meta operation time

[jira] [Updated] (HBASE-28608) More sensible client meta operation timeout default

[ https://issues.apache.org/jira/browse/HBASE-28608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Roudnitsky updated HBASE-28608: -- Issue Type: Improvement (was: Bug) > More sensible client meta operation timeout defa

[jira] [Updated] (HBASE-28608) More sensible client meta operation timeout default

[ https://issues.apache.org/jira/browse/HBASE-28608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Roudnitsky updated HBASE-28608: -- Description: Documented behavior in the HBase reference for client meta operation time

[jira] [Updated] (HBASE-28608) More sensible client meta operation timeout default

[ https://issues.apache.org/jira/browse/HBASE-28608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Roudnitsky updated HBASE-28608: -- Description: Documented behavior in the HBase reference for client meta operation time

[jira] [Updated] (HBASE-28608) More sensible client meta operation timeout default

[ https://issues.apache.org/jira/browse/HBASE-28608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Roudnitsky updated HBASE-28608: -- Summary: More sensible client meta operation timeout default (was: Client meta operat

[jira] [Commented] (HBASE-28608) Client meta operation timeout does not default to the correct value

[ https://issues.apache.org/jira/browse/HBASE-28608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17856105#comment-17856105 ] Daniel Roudnitsky commented on HBASE-28608: --- PR was not automatically linked t

[jira] [Updated] (HBASE-28608) Client meta operation timeout does not default to the correct value

[ https://issues.apache.org/jira/browse/HBASE-28608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Roudnitsky updated HBASE-28608: -- External issue URL: (was: https://github.com/apache/hbase/pull/6000) > Client meta o

[jira] [Updated] (HBASE-28608) Client meta operation timeout does not default to the correct value

[ https://issues.apache.org/jira/browse/HBASE-28608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Roudnitsky updated HBASE-28608: -- External issue URL: https://github.com/apache/hbase/pull/6000 > Client meta operation

[jira] [Updated] (HBASE-28608) Client meta operation timeout does not default to the correct value

[ https://issues.apache.org/jira/browse/HBASE-28608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Roudnitsky updated HBASE-28608: -- Status: Patch Available (was: Open) > Client meta operation timeout does not default

[jira] [Updated] (HBASE-28608) Client meta operation timeout does not default to the correct value

[ https://issues.apache.org/jira/browse/HBASE-28608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Roudnitsky updated HBASE-28608: -- Description: Client meta operation timeout {{hbase.client.meta.operation.timeout}} def

[jira] [Updated] (HBASE-28608) Client meta operation timeout does not default to the correct value

[ https://issues.apache.org/jira/browse/HBASE-28608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Roudnitsky updated HBASE-28608: -- Description: Client meta operation timeout {{hbase.client.meta.operation.timeout}} def

[jira] [Commented] (HBASE-28608) Client meta operation timeout does not default to the correct value

[ https://issues.apache.org/jira/browse/HBASE-28608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17856080#comment-17856080 ] Daniel Roudnitsky commented on HBASE-28608: --- Seeing TestRecoveryPersistentBuck

[jira] [Updated] (HBASE-28608) Client meta operation timeout does not default to the correct value

[ https://issues.apache.org/jira/browse/HBASE-28608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Roudnitsky updated HBASE-28608: -- Affects Version/s: 3.0.0-beta-1 > Client meta operation timeout does not default to th

[jira] [Updated] (HBASE-28608) Client meta operation timeout does not default to the correct value

[ https://issues.apache.org/jira/browse/HBASE-28608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Roudnitsky updated HBASE-28608: -- Affects Version/s: 2.5.8 2.4.17 2.6.0 >

[jira] [Updated] (HBASE-28608) Client meta operation timeout does not default to the correct value

[ https://issues.apache.org/jira/browse/HBASE-28608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Roudnitsky updated HBASE-28608: -- Labels: timeout (was: ) > Client meta operation timeout does not default to the corre

[jira] [Commented] (HBASE-28608) Client meta operation timeout does not default to the correct value

[ https://issues.apache.org/jira/browse/HBASE-28608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17848215#comment-17848215 ] Daniel Roudnitsky commented on HBASE-28608: --- In 2.x "meta operation timeout" r

[jira] [Created] (HBASE-28608) Client meta operation timeout does not default to the correct value

Daniel Roudnitsky created HBASE-28608: - Summary: Client meta operation timeout does not default to the correct value Key: HBASE-28608 URL: https://issues.apache.org/jira/browse/HBASE-28608 Project

[jira] [Updated] (HBASE-28560) Region quotas: Split/merge procedure rollback can lead to inaccurate account of region counts

[ https://issues.apache.org/jira/browse/HBASE-28560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Roudnitsky updated HBASE-28560: -- Labels: Quota (was: quotas) > Region quotas: Split/merge procedure rollback can lead

[jira] [Created] (HBASE-28560) Region quotas: Split/merge procedure rollback can lead to inaccurate account of region counts

Daniel Roudnitsky created HBASE-28560: - Summary: Region quotas: Split/merge procedure rollback can lead to inaccurate account of region counts Key: HBASE-28560 URL: https://issues.apache.org/jira/browse/HBASE-

[jira] [Created] (HBASE-28559) Region quotas: Multi-region merge causes inaccurate accounting of region counts

Daniel Roudnitsky created HBASE-28559: - Summary: Region quotas: Multi-region merge causes inaccurate accounting of region counts Key: HBASE-28559 URL: https://issues.apache.org/jira/browse/HBASE-28559

[jira] [Updated] (HBASE-28533) Split procedure rollback can leave parent region state in SPLITTING after completion

[ https://issues.apache.org/jira/browse/HBASE-28533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Roudnitsky updated HBASE-28533: -- Status: Patch Available (was: In Progress) > Split procedure rollback can leave paren

[jira] [Updated] (HBASE-28533) Split procedure rollback can leave parent region state in SPLITTING after completion

[ https://issues.apache.org/jira/browse/HBASE-28533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Roudnitsky updated HBASE-28533: -- Description: Depending on where the split procedure fails, SplitTableRegionProcedure

[jira] [Commented] (HBASE-28405) Region open procedure silently returns without notifying the parent proc

[ https://issues.apache.org/jira/browse/HBASE-28405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17842144#comment-17842144 ] Daniel Roudnitsky commented on HBASE-28405: --- HBASE-28533 provides a partially

[jira] [Updated] (HBASE-28533) Split procedure rollback can leave parent region state in SPLITTING after completion

[ https://issues.apache.org/jira/browse/HBASE-28533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Roudnitsky updated HBASE-28533: -- Description: Depending on where the split procedure fails, SplitTableRegionProcedure

[jira] [Updated] (HBASE-28533) Split procedure rollback can leave parent region state in SPLITTING after completion

[ https://issues.apache.org/jira/browse/HBASE-28533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Roudnitsky updated HBASE-28533: -- Description: Depending on where the split procedure fails, SplitTableRegionProcedure

[jira] [Updated] (HBASE-28533) Split procedure rollback can leave parent region state in SPLITTING after completion

[ https://issues.apache.org/jira/browse/HBASE-28533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Roudnitsky updated HBASE-28533: -- Description: Depending on where the split procedure fails, SplitTableRegionProcedure

[jira] [Updated] (HBASE-28533) Split procedure rollback can leave parent region state in SPLITTING after completion

[ https://issues.apache.org/jira/browse/HBASE-28533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Roudnitsky updated HBASE-28533: -- Description: Depending on where the split procedure fails, SplitTableRegionProcedure

[jira] [Updated] (HBASE-28533) Split procedure rollback can leave parent region state in SPLITTING after completion

[ https://issues.apache.org/jira/browse/HBASE-28533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Roudnitsky updated HBASE-28533: -- Environment: (was: Tested on HBase Version 2.5.8 and latest master branch ) > Spl

[jira] [Updated] (HBASE-28533) Split procedure rollback can leave parent region state in SPLITTING after completion

[ https://issues.apache.org/jira/browse/HBASE-28533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Roudnitsky updated HBASE-28533: -- Affects Version/s: 2.5.8 3.0.0-beta-2 > Split procedure rollbac

[jira] [Updated] (HBASE-28533) Split procedure rollback can leave parent region state in SPLITTING after completion

[ https://issues.apache.org/jira/browse/HBASE-28533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Roudnitsky updated HBASE-28533: -- Description: Depending on where the split procedure fails, SplitTableRegionProcedure

[jira] [Updated] (HBASE-28533) Split procedure rollback can leave parent region state in SPLITTING after completion

[ https://issues.apache.org/jira/browse/HBASE-28533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Roudnitsky updated HBASE-28533: -- Description: Depending on where the split procedure fails, SplitTableRegionProcedure

[jira] [Updated] (HBASE-28533) Split procedure rollback can leave parent region state in SPLITTING after completion

[ https://issues.apache.org/jira/browse/HBASE-28533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Roudnitsky updated HBASE-28533: -- Description: SplitTableRegionProcedure  When a SplitTableRegionProcedure is run for a

[jira] [Updated] (HBASE-28533) Split procedure rollback can leave parent region state in SPLITTING after completion

[ https://issues.apache.org/jira/browse/HBASE-28533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Roudnitsky updated HBASE-28533: -- Summary: Split procedure rollback can leave parent region state in SPLITTING after com

[jira] [Commented] (HBASE-28533) Region split failure due to region quota limit leaves Hmaster's in memory state for the region in SPLITTING after procedure rollback

[ https://issues.apache.org/jira/browse/HBASE-28533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17841993#comment-17841993 ] Daniel Roudnitsky commented on HBASE-28533: --- Another case where the parent reg

[jira] [Work started] (HBASE-28533) Region split failure due to region quota limit leaves Hmaster's in memory state for the region in SPLITTING after procedure rollback

[ https://issues.apache.org/jira/browse/HBASE-28533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on HBASE-28533 started by Daniel Roudnitsky. - > Region split failure due to region quota limit leaves Hmaster's in

[jira] [Updated] (HBASE-28533) Region split failure due to region quota limit leaves Hmaster's in memory state for the region in SPLITTING after procedure rollback

[ https://issues.apache.org/jira/browse/HBASE-28533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Roudnitsky updated HBASE-28533: -- Environment: Tested on HBase Version 2.5.8 and latest master branch  (was: HBase Vers

[jira] [Commented] (HBASE-28533) Region split failure due to region quota limit leaves Hmaster's in memory state for the region in SPLITTING after procedure rollback

[ https://issues.apache.org/jira/browse/HBASE-28533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17840577#comment-17840577 ] Daniel Roudnitsky commented on HBASE-28533: --- I have tested and confirmed that

[jira] [Updated] (HBASE-28533) Region split failure due to region quota limit leaves Hmaster's in memory state for the region in SPLITTING after procedure rollback

[ https://issues.apache.org/jira/browse/HBASE-28533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Roudnitsky updated HBASE-28533: -- Affects Version/s: (was: 2.5.8) > Region split failure due to region quota limit l

[jira] [Commented] (HBASE-28533) Region split failure due to region quota limit leaves Hmaster's in memory state for the region in SPLITTING after procedure rollback

[ https://issues.apache.org/jira/browse/HBASE-28533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17838738#comment-17838738 ] Daniel Roudnitsky commented on HBASE-28533: --- [~wchevreuil] I believe that this

[jira] [Created] (HBASE-28533) Region split failure due to region quota limit leaves Hmaster's in memory state for the region in SPLITTING after procedure rollback

Daniel Roudnitsky created HBASE-28533: - Summary: Region split failure due to region quota limit leaves Hmaster's in memory state for the region in SPLITTING after procedure rollback Key: HBASE-28533 URL: https