HBASE-27951 Use ADMIN_QOS in MasterRpcServices for regionserver operational dependencies (#5309)

It seems not correct to have the MasterRpcServices methods for direct
regionserver<->master communication (regionServerStartup, regionServerReport,
and reportFatalRSError) contending with normal priority requests. They
should be made ADMIN_QOS priority to avoid potential operational deadlocks.

Signed-off-by: Duo Zhang <[email protected]>
Signed-off-by: Viraj Jasani <[email protected]>
Reviewed-by: Aman Poonia <[email protected]>

Author: apurtell

hbase-server/src/main/java/org/apache/hadoop/hbase/master/MasterRpcServices.java

@@ -535,6 +535,7 @@ public GetLastFlushedSequenceIdResponse getLastFlushedSequenceId(RpcController c
   }
 
   @Override
+  @QosPriority(priority = HConstants.ADMIN_QOS)
   public RegionServerReportResponse regionServerReport(RpcController controller,
     RegionServerReportRequest request) throws ServiceException {
     try {
@@ -566,6 +567,7 @@ public RegionServerReportResponse regionServerReport(RpcController controller,
   }
 
   @Override
+  @QosPriority(priority = HConstants.ADMIN_QOS)
   public RegionServerStartupResponse regionServerStartup(RpcController controller,
     RegionServerStartupRequest request) throws ServiceException {
     // Register with server manager
@@ -597,6 +599,7 @@ public RegionServerStartupResponse regionServerStartup(RpcController controller,
   }
 
   @Override
+  @QosPriority(priority = HConstants.ADMIN_QOS)
   public ReportRSFatalErrorResponse reportRSFatalError(RpcController controller,
     ReportRSFatalErrorRequest request) throws ServiceException {
     String errorText = request.getErrorMessage();