This issue is to discuss event log growth currently being unbounded. In order prevent OOM errors, the event log must be rolled up with some regularity.
etcd's approach to this problem appears to be compacting based on a combination of max allowed entries and elapsed time - https://github.com/etcd-io/etcd/blob/master/Documentation/op-guide/maintenance.md#raft-log-retention. Each of these approaches seem desirable to cover most situations.
Initial thoughts on possible options would be:
- snapshot at
max_sequence_id and delete from there back
- snapshot at
x events back and delete from there back
- delete back from the sequence id on the last snapshot
I propose we implement each of these approaches with sane defaults. Users can adjust these configuration options and pick a strategy that best suits their needs.
This issue is to discuss event log growth currently being unbounded. In order prevent OOM errors, the event log must be rolled up with some regularity.
etcd's approach to this problem appears to be compacting based on a combination of max allowed entries and elapsed time - https://github.com/etcd-io/etcd/blob/master/Documentation/op-guide/maintenance.md#raft-log-retention. Each of these approaches seem desirable to cover most situations.
Initial thoughts on possible options would be:
max_sequence_idand delete from there backxevents back and delete from there backI propose we implement each of these approaches with sane defaults. Users can adjust these configuration options and pick a strategy that best suits their needs.