[
https://issues.apache.org/jira/browse/EAGLE-750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Su Ralph reassigned EAGLE-750:
------------------------------
Assignee: Garrett Li (was: Su Ralph)
> Improve coordinator schedule strategy to reuse alert work slot
> --------------------------------------------------------------
>
> Key: EAGLE-750
> URL: https://issues.apache.org/jira/browse/EAGLE-750
> Project: Eagle
> Issue Type: Bug
> Affects Versions: v0.5.0
> Reporter: Hao Chen
> Assignee: Garrett Li
> Fix For: v0.5.0
>
>
> We catch with some critical problem about alert engine policy schedule
> strategy:
> For example for an alert topology with 20 alert bolts , and after boarding 4
> policies and each assigning 5 slots, then the current alert coordinator will
> treat the work slots as used up and be unable to schedule any more new
> policies.
> But in fact some typical eagle deployment will have at least 20+ streams with
> lots of different partition requirements, which means we could just define
> very few policies under such scheduling strategy and may waste slot resources
> of eagle’s deployment infrastructure.
> In original design, we should have designed to reused slot queue among
> in-conflict monitored stream (stream-partition-sort), then eagle could try to
> reuse alert slots if possible to improve resource utilization, and it should
> be time to implement it now.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
