[
https://issues.apache.org/jira/browse/HBASE-13986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Abhishek Kumar updated HBASE-13986:
-----------------------------------
Description:
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.
was: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.
> 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)
