[
https://issues.apache.org/jira/browse/HBASE-29323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17953093#comment-17953093
]
Hudson commented on HBASE-29323:
--------------------------------
Results for branch branch-2
[build #1273 on
builds.a.o|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2/1273/]:
(x) *{color:red}-1 overall{color}*
----
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2/1273/General_20Nightly_20Build_20Report/]
(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2/1273/JDK8_20Nightly_20Build_20Report_20_28Hadoop2_29/]
(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2/1273/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2/1273/JDK11_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 jdk17 hadoop3 checks{color}
-- For more information [see jdk17
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2/1273/JDK17_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 jdk17 hadoop 3.3.5 backward compatibility checks{color}
-- For more information [see jdk17
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2/1273/JDK17_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 jdk17 hadoop 3.3.6 backward compatibility checks{color}
-- For more information [see jdk17
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2/1273/JDK17_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 jdk17 hadoop 3.4.0 backward compatibility checks{color}
-- For more information [see jdk17
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2/1273/JDK17_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test for HBase 2 {color}
(/) {color:green}+1 client integration test for 3.3.5 {color}
(/) {color:green}+1 client integration test for 3.3.6 {color}
(/) {color:green}+1 client integration test for 3.4.0 {color}
(/) {color:green}+1 client integration test for 3.4.1 {color}
> Use Priority Handler for all RegionServerStatus rpc 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
> Labels: pull-request-available
> Fix For: 2.7.0, 3.0.0-beta-2, 2.6.3
>
>
> There are two main reasons to use the Priority Handler:
> 1. These reports like report for splitWalProcedure are critical for
> completing region movements and ensuring availability. Any delay in reporting
> can directly impact system availability.
> *2. Preventing Deadlocks on simultaneous Region Server Draining and
> serverCrash:*
> When draining a Region Server, the {{MoveWithAck}} API is used. This API
> waits for the {{TRSP}} to complete. If multiple Region Servers are drained
> simultaneously, all general handler threads can become occupied.
> If the draining server get crashed during this period, we will first do wal
> split. All the above moving rpc leaves no threads available to process
> `reportProcedureDone` for splitWALProcedure, resulting in a deadlock that
> blocks SCP 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)
