From 903f812726ca865cbd92157d4a091fab0c038a67 Mon Sep 17 00:00:00 2001 From: Ginger Collison Date: Thu, 24 Oct 2019 12:34:59 -0500 Subject: [PATCH] Update faq.md --- faq.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/faq.md b/faq.md index d580db1..86550d9 100644 --- a/faq.md +++ b/faq.md @@ -24,6 +24,7 @@ * [Does NATS support replay/redelivery of historical data?](faq.md#does-nats-support-replayredelivery-of-historical-data) * [How do I gracefully shut down an asynchronous subscriber?](faq.md#how-do-i-gracefully-shut-down-an-asynchronous-subscriber) * [How do I create subjects?](faq.md#how-do-i-create-subjects) +* [Does adding a “max_age” to a “channel” for NATS streaming server connected to a SQL store, retroactively delete messages?](faq.md#does-adding-a-maxage-to-a-channel-for-nats-streaming-server-connected-to-a-sql-store-retroactively-delete-messages) ## General @@ -139,3 +140,7 @@ To gracefully shutdown an asynchronous subscriber so that any outstanding MsgHan Subjects are created and pruned \(deleted\) dynamically based on interest \(subscriptions\). This means that a subject does not exist in a NATS cluster until a client subscribes to it, and the subject goes away after the last subscribing client unsubscribes from that subject. +### Does adding a “max_age” to a “channel” for NATS streaming server connected to a SQL store, retroactively delete messages? + +Yes, any channel limit will be applied on startup. For more information, see [Store Limits](nats-streaming-server/configuring/storelimits.md#limits-are-retroactive). +