[
https://issues.apache.org/jira/browse/EAGLE-1029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16026154#comment-16026154
]
ASF GitHub Bot commented on EAGLE-1029:
---------------------------------------
GitHub user qingwen220 opened a pull request:
https://github.com/apache/eagle/pull/939
EAGLE-1029: fix bug in generateGroupbyMonitorMetadata
https://issues.apache.org/jira/browse/EAGLE-1029
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/qingwen220/eagle EAGLE-1029
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/eagle/pull/939.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #939
----
commit 1596192b901ec141a538b66b6aaa1520455ef9a4
Author: Zhao, Qingwen <[email protected]>
Date: 2017-05-26T11:12:17Z
fix bug in generateSpoutMonitorMetadata
----
> 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)
