You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@eagle.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2016/12/08 07:22:59 UTC
[jira] [Commented] (EAGLE-821) coordinator bug in alert engine
[ https://issues.apache.org/jira/browse/EAGLE-821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15731395#comment-15731395 ]
ASF GitHub Bot commented on EAGLE-821:
--------------------------------------
GitHub user qingwen220 opened a pull request:
https://github.com/apache/incubator-eagle/pull/722
EAGLE-821 clear useless queue when build schedule context
https://issues.apache.org/jira/browse/EAGLE-821
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/qingwen220/incubator-eagle EAGLE-821
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-eagle/pull/722.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 #722
----
commit e75f0fb0e22fa7a9af98f24c5122f3cb5b2ad538
Author: Zhao, Qingwen <qi...@apache.org>
Date: 2016-12-07T06:44:39Z
fix bugs
commit 86d9207b207f8ef18de839d19716f97d5a811112
Author: Zhao, Qingwen <qi...@apache.org>
Date: 2016-12-08T06:54:32Z
clear useless workSlots
----
> coordinator bug in alert engine
> -------------------------------
>
> Key: EAGLE-821
> URL: https://issues.apache.org/jira/browse/EAGLE-821
> Project: Eagle
> Issue Type: Bug
> Affects Versions: v0.5.0
> Reporter: wujinhu
> Assignee: Zhao, Qingwen
> Fix For: v0.5.0
>
>
> Coordinator has bugs below:
> 1. When I disable a policy, coordinator does not clear allocated queue
> 2. Coordinator can not schedule policies while there are alert bolts with no resources
> 3. When I create some policies with stream A and B, coordinator can not schedule policy with stream C although there are free resources
> How to reproduce:
> Create 8 or more policies with stream A and some policies with Stream B, then create policy with steam C, will reproduce 2 and 3(the number may depends). When you see all the alert bolts contains stream A, then disable policy with stream A, it will reproduce 1
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)