nats: a tool purges a stream's messages below a sequence
A build seat's work queue (SEAT_NODE_BUILD_GO) held about 370 asks of pipelines nobody waits for, ahead of the one pipeline wanted, and no tool could empty it short of removing the stream. nats_stream_purge removes the messages below a given sequence, keeping the rest, the stream and its consumers; it needs why, reads first, offers dry_run, refuses a purge past the stream's end and the module-kept data nats_drop owns, and says stream-purged as its audit event, like the three removal tools.
This commit is contained in:
@@ -57,6 +57,7 @@
|
||||
"consumer-removed",
|
||||
"bucket-keys-removed",
|
||||
"stream-removed",
|
||||
"stream-purged",
|
||||
"bucket-expiry-set",
|
||||
"snapshot-restored"
|
||||
],
|
||||
@@ -171,6 +172,7 @@
|
||||
"nats_consumer_remove",
|
||||
"nats_bucket_remove",
|
||||
"nats_stream_remove",
|
||||
"nats_stream_purge",
|
||||
"nats_bucket_expiry",
|
||||
"nats_history",
|
||||
"nats_create",
|
||||
|
||||
Reference in New Issue
Block a user