[ https://issues.apache.org/jira/browse/EAGLE-1029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16027347#comment-16027347 ]
ASF GitHub Bot commented on EAGLE-1029: --------------------------------------- Github user asfgit closed the pull request at: https://github.com/apache/eagle/pull/939 > Wrong groupSpec is generated when more than one alert engine topology > ---------------------------------------------------------------------- > > Key: EAGLE-1029 > URL: https://issues.apache.org/jira/browse/EAGLE-1029 > Project: Eagle > Issue Type: Bug > Affects Versions: v0.5.0 > Reporter: Zhao, Qingwen > Assignee: Zhao, Qingwen > Priority: Critical > > According to the schedule info returned by /rest/metadata/schedulestates > In alertSpecs, new policies are assigned to alertBolt 9, 18, 19, 1, 12 of the > second alert engine topology. While in groupSpecs, the worker queue(alert > bolts) allocated for each policy is not [ 9, 18, 19, 1, 12]. Actually, it > adds all working queues, including those of other alert engine topology -- This message was sent by Atlassian JIRA (v6.3.15#6346)