Closed
Bug 1357267
Opened 8 years ago
Closed 7 years ago
Consider persisting CEP state to s3
Categories
(Cloud Services Graveyard :: Metrics: Pipeline, enhancement, P3)
Cloud Services Graveyard
Metrics: Pipeline
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: whd, Unassigned)
Details
(Whiteboard: [SvcOps])
Currently, if the CEP dies we will lose all of its state (except the kafka offset of the consumer group, as that's tracked in kafka). Additionally we will lose all analysis plugins that were running except those defined explicitly as "system" plugins (those configured in puppet). We could mitigate a node failure somewhat by copying filter preservation data to s3 somewhere, and pulling it in as part of a new CEP instantiation. This would give us data up to whenever the last restart was for various plugins, which could be useful (but will still have gaps).
This includes the user database for the CEP admin UI, which is just a sqlite file on disk.
Comment 1•7 years ago
|
||
Closing abandoned bugs in this product per https://bugzilla.mozilla.org/show_bug.cgi?id=1337972
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → INCOMPLETE
Updated•6 years ago
|
Product: Cloud Services → Cloud Services Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•