[
https://issues.apache.org/jira/browse/HBASE-13986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14610916#comment-14610916
]
stack commented on HBASE-13986:
-------------------------------
Lets see a patch [~a72877] Sounds fine. Master for a while was a RegionServer.
We are climbing back some from this classification. Would be good to see a
patch to see to see where we are doing this abort (abort of the Master is not
an op I recall us needing... lets see)
> HMaster instance always returns false for isAborted() check.
> ------------------------------------------------------------
>
> Key: HBASE-13986
> URL: https://issues.apache.org/jira/browse/HBASE-13986
> Project: HBase
> Issue Type: Bug
> Reporter: Abhishek Kumar
> Assignee: Abhishek Kumar
> Priority: Minor
>
> It seems that HMaster never set abortRequested flag to true as done by
> HRegionServer in its abort() method.We can see isAborted method being used in
> few places for HMaster instance (like in HMasterCommandLine.startMaster)
> where code flow being determined based on the result of isAborted() call.
> We can set this abortRequested flag in Hmaster's abort() method as well like
> in HRegionServer's abort method, let me know if it seems ok.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
