[ https://issues.apache.org/jira/browse/HBASE-23595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16999798#comment-16999798 ]
Duo Zhang commented on HBASE-23595: ----------------------------------- This is by design I think? There is no simple way to recover this... > HMaster abort when write to meta failed > --------------------------------------- > > Key: HBASE-23595 > URL: https://issues.apache.org/jira/browse/HBASE-23595 > Project: HBase > Issue Type: Bug > Reporter: Lijin Bin > Priority: Major > > RegionStateStore > {code} > private void updateRegionLocation(RegionInfo regionInfo, State state, Put > put) > throws IOException { > try (Table table = > master.getConnection().getTable(TableName.META_TABLE_NAME)) { > table.put(put); > } catch (IOException e) { > // TODO: Revist!!!! Means that if a server is loaded, then we will > abort our host! > // In tests we abort the Master! > String msg = String.format("FAILED persisting region=%s state=%s", > regionInfo.getShortNameToLog(), state); > LOG.error(msg, e); > master.abort(msg, e); > throw e; > } > } > {code} > When regionserver (carry meta) stop or crash, if the ServerCrashProcedure > have not start process, write to meta will fail and abort master. -- This message was sent by Atlassian Jira (v8.3.4#803005)