[jira] [Resolved] (EAGLE-683) AlertEngine : Improve metadata store performance

["Su Ralph (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/EAGLE-683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Su Ralph resolved EAGLE-683.
----------------------------
    Resolution: Fixed

close as merged

> AlertEngine : Improve metadata store performance
> ------------------------------------------------
>
>                 Key: EAGLE-683
>                 URL: https://issues.apache.org/jira/browse/EAGLE-683
>             Project: Eagle
>          Issue Type: Improvement
>    Affects Versions: v0.5.0
>            Reporter: Su Ralph
>            Assignee: Zeng, Bryant
>             Fix For: v0.5.0
>
>
> Currently, we enable periodically schedule in coordinator service itself. If this is enabled, the schedule spec will finally used up metadata storage.
> We should
> 1. Disable periodically schedule by default (storage like mysql doesn't have capped feature)
> 2. For mongodb storage, use capped collection for schedule_specs, policy_snapshots, streamSnapshots, groupSpecs, alertSpecs, monitoredStreams, spoutSpecs (all schedule spec related collection).
> Let use default config of 20,000 as capped collection size.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)