[
https://issues.apache.org/jira/browse/HBASE-29323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17952170#comment-17952170
]
Umesh Kumar Kumawat commented on HBASE-29323:
---------------------------------------------
Looks like a duplicate of https://issues.apache.org/jira/browse/HBASE-21754.
Looking at that change.
> Use Priority Handler for reportRegionStateTransition and reportProcedureDone
> at Master
> --------------------------------------------------------------------------------------
>
> Key: HBASE-29323
> URL: https://issues.apache.org/jira/browse/HBASE-29323
> Project: HBase
> Issue Type: Improvement
> Components: master
> Affects Versions: 2.6.2
> Reporter: Umesh Kumar Kumawat
> Assignee: Umesh Kumar Kumawat
> Priority: Major
>
> There are two main reasons to use the Priority Handler:
> # These reports are critical for completing region movements and ensuring
> availability. Any delay in reporting can directly impact system availability.
> # *Preventing Deadlocks During Region Server Draining:*
> When draining a Region Server (RS), the {{MoveWithAck}} API is used. This API
> waits for the {{TRSP}} (Transit Region State Procedure) to complete. During
> this process, the Region Server calls {{reportRegionStateTransition}} after
> opening or closing a region.
> If multiple Region Servers are drained simultaneously, all general handler
> threads can become occupied. This leaves no threads available to process
> {{{}reportRegionStateTransition{}}}, resulting in a deadlock that blocks
> region movements from completing.
> Using a Priority Handler ensures that critical operations like state
> transitions are not blocked by general handler saturation.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
