[
https://issues.apache.org/jira/browse/EAGLE-569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15526832#comment-15526832
]
ASF GitHub Bot commented on EAGLE-569:
--------------------------------------
Github user RalphSu commented on the issue:
https://github.com/apache/incubator-eagle/pull/457
Fix to use copy&swap way to refresh metadata changes.
> AlertPublishImpl: Concurrency : Inplace change metadata cause concurrent
> modification issue
> -------------------------------------------------------------------------------------------
>
> Key: EAGLE-569
> URL: https://issues.apache.org/jira/browse/EAGLE-569
> Project: Eagle
> Issue Type: Bug
> Affects Versions: v0.5.0
> Reporter: Su Ralph
> Assignee: Su Ralph
> Priority: Critical
> Fix For: v0.5.0
>
>
> We are try to re-use eagle alert module as part our streaming processing
> core, during test, we found below error.
> 6700 java.util.ConcurrentModificationException at
> java.util.ArrayList$Itr.checkForComodification(ArrayList.java:901) at
> java.util.ArrayList$Itr.next(ArrayList.java:851) at
> org.apache.eagle.alert.engine.publisher.impl.AlertPublisherImpl.notifyAlert(AlertPublisherImpl.java:74)
> It happens to be in AlertPublisherImpl, the metadata change is doing inplace
> update, which cause the concurrency issue when the bolt is continuing ingest
> data.
> This exception should cause following data stream not able to be published.
> Hence be blocker
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
