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 <miz...@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).
----
---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
