[
https://issues.apache.org/jira/browse/HBASE-20808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16532971#comment-16532971
]
Nihal Jain edited comment on HBASE-20808 at 7/4/18 5:25 PM:
------------------------------------------------------------
Apparently we were calling {{cancelChore(this.clusterStatusPublisherChore)}}
twice in existing code:
{code:java}
cancelChore(this.clusterStatusPublisherChore);
if (this.mobCompactThread != null) {
this.mobCompactThread.close();
}
cancelChore(this.clusterStatusPublisherChore);
{code}
was (Author: nihaljain.cs):
Apparently were calling {{cancelChore(this.clusterStatusPublisherChore)}} twice
in existing code:
{code:java}
cancelChore(this.clusterStatusPublisherChore);
if (this.mobCompactThread != null) {
this.mobCompactThread.close();
}
cancelChore(this.clusterStatusPublisherChore);
{code}
> Wrong shutdown order between Chores and ChoreService
> ----------------------------------------------------
>
> Key: HBASE-20808
> URL: https://issues.apache.org/jira/browse/HBASE-20808
> Project: HBase
> Issue Type: Bug
> Reporter: Reid Chan
> Assignee: Nihal Jain
> Priority: Minor
> Labels: beginner
> Attachments: HBASE-20808.master.001.patch,
> HBASE-20808.master.002.patch, HBASE-20808.master.003.patch
>
>
> When stopping master, {{ChoreService}}, which serves all the chores, is
> stopped before canceling all running chores.
> It should cancel all running chores, then shutdown {{ChoreService}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
