[ https://issues.apache.org/jira/browse/HBASE-20709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16518801#comment-16518801 ]
Guanghao Zhang commented on HBASE-20709: ---------------------------------------- Change the issue type to minor improvement. > CompatRemoteProcedureResolver should call remoteCallFailed method instead of > throw UnsupportedOperationException > ---------------------------------------------------------------------------------------------------------------- > > Key: HBASE-20709 > URL: https://issues.apache.org/jira/browse/HBASE-20709 > Project: HBase > Issue Type: Improvement > Affects Versions: 3.0.0, 2.1.0, 2.0.0 > Environment: # > Reporter: Guanghao Zhang > Assignee: Guanghao Zhang > Priority: Minor > Attachments: HBASE-20709.master.001.patch, > HBASE-20709.master.002.patch > > > hbase-server/src/main/java/org/apache/hadoop/hbase/master/procedure/RSProcedureDispatcher.java > {code:java} > @Override > public void dispatchServerOperations(MasterProcedureEnv env, > List<ServerOperation> operations) { > throw new UnsupportedOperationException(); > } > {code} > As the procedure request not send to remote server, remoteOperationFailed and > remoteOperationCompleted can't be called. So the procedure will stuck and no > log to show this. The new patach will call remoteCallFailed method and make > the procedure failed. It is easy to find problem by the new exception message. -- This message was sent by Atlassian JIRA (v7.6.3#76005)