You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@eagle.apache.org by "Zhao, Qingwen (JIRA)" <ji...@apache.org> on 2017/08/04 05:47:00 UTC

[jira] [Updated] (EAGLE-1029) Wrong groupSpec is generated when more than one alert engine topology

     [ https://issues.apache.org/jira/browse/EAGLE-1029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Zhao, Qingwen updated EAGLE-1029:
---------------------------------
    Affects Version/s:     (was: v0.5.0)
                       v0.5.1

> 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.1
>            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.4.14#64029)