Details
-
Improvement
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
v0.5.0
-
None
-
None
Description
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.
Attachments
Issue Links
- links to
