You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@eagle.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2016/10/26 06:41:58 UTC

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

    [ https://issues.apache.org/jira/browse/EAGLE-683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15607620#comment-15607620 ] 

ASF GitHub Bot commented on EAGLE-683:
--------------------------------------

GitHub user mizeng opened a pull request:

    https://github.com/apache/incubator-eagle/pull/566

    EAGLE-683: Improve metadata store performance

    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.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/mizeng/incubator-eagle master

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/incubator-eagle/pull/566.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 #566
    
----
commit 802570a19e9ca4a7b5f4f05e2b01a40cbe2d2d15
Author: mizeng <mi...@ebaysf.com>
Date:   2016-10-26T06:22:33Z

    EAGLE-683: Improve metadata store performance
    
    Currently, we enable periodically schedule in coordinator service itself.
    If this is enabled, the schedule spec will finally used up metadata storage.
    
    So we need to improve metadata store performance by:
    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).

----


> 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)