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

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: v0.5.0
• Fix Version/s: v0.5.0
• Assignee: Qingwen Zhao
• Reporter: Qingwen Zhao
• Created: 26/May/17 08:33
• Updated: 04/Aug/17 05:55
• Resolved: 04/Aug/17 05:55

Description

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

Issue Links

• links to: GitHub Pull Request #939