[
https://issues.apache.org/jira/browse/HBASE-14977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15060554#comment-15060554
]
Vladimir Rodionov commented on HBASE-14977:
-------------------------------------------
That is because of a deadlock. ScheduledChore is heavily synchronized, even
getName() is synchronized and toString(). I attached small addendum which fixes
this issue.
> ChoreService.shutdown may result in ConcurrentModificationException
> -------------------------------------------------------------------
>
> Key: HBASE-14977
> URL: https://issues.apache.org/jira/browse/HBASE-14977
> Project: HBase
> Issue Type: Bug
> Reporter: Vladimir Rodionov
> Assignee: Vladimir Rodionov
> Priority: Minor
> Fix For: 2.0.0, 1.2.0, 1.3.0, 1.1.4
>
> Attachments: HBASE-14977-add.patch, HBASE-14977-v1.patch
>
>
> As seen in this test:
> https://builds.apache.org/job/HBase-1.3/jdk=latest1.8,label=Hadoop/425/artifact/hbase-server/target/surefire-reports/org.apache.hadoop.hbase.regionserver.compactions.TestFIFOCompactionPolicy-output.txt
> We need to make shutdown method synchronized to avoid this issue.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
