Github user qingwen220 commented on the issue:
https://github.com/apache/eagle/pull/939
This bug can be produced as follows
1. create policies with stream1 to use up all the working slot of alert
engine topology1
2. setup another alert engine topology topology2
3. create a policy with stream1 and trigger the scheduler to schedule
4. check schedule result by GET rest/metadata/schedulestates, and compare
groupSpecs & alertSpecs
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
