You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@eagle.apache.org by "Su Ralph (JIRA)" <ji...@apache.org> on 2016/09/27 17:26:20 UTC
[jira] [Resolved] (EAGLE-569) AlertPublishImpl: Concurrency :
Inplace change metadata cause concurrent modification issue
[ https://issues.apache.org/jira/browse/EAGLE-569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Su Ralph resolved EAGLE-569.
----------------------------
Resolution: Fixed
> 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)