From: Yuval Lifshitz Date: Wed, 14 Aug 2024 11:02:09 +0000 (+0000) Subject: doc/rgw/notification: persistent notification queue full behavior X-Git-Tag: v19.2.1~291^2 X-Git-Url: http://git.apps.os.sepia.ceph.com/?a=commitdiff_plain;h=3c3d0e7a161128bb4ff2f417e26eb9ee708ce495;p=ceph.git doc/rgw/notification: persistent notification queue full behavior Fixes: https://tracker.ceph.com/issues/50610 Signed-off-by: Yuval Lifshitz (cherry picked from commit d12ba11741dc749bcce315bf467078595fa95b24) --- diff --git a/doc/radosgw/notifications.rst b/doc/radosgw/notifications.rst index aa9a55ef966e8..259d64bf0989f 100644 --- a/doc/radosgw/notifications.rst +++ b/doc/radosgw/notifications.rst @@ -61,9 +61,15 @@ Asynchronous Notifications ~~~~~~~~~~~~~~~~~~~~~~~~~~ Notifications can be sent asynchronously. They are committed into persistent -storage and then asynchronously sent to the topic's configured endpoint. In -this case, the only latency added to the original operation is the latency +storage and then asynchronously sent to the topic's configured endpoint. +The notification will be committed to persistent storage only if the triggering +operation was successful. +In this case, the only latency added to the original operation is the latency added when the notification is committed to persistent storage. +If the endpoint of the topic to which the notification is sent is not available for a long +period of time, the persistent storage allocated for this topic will eventually fill up. +When this happens the triggering operations will fail with ``503 Service Unavailable``, +which tells the client that it may retry later. .. note:: If the notification fails with an error, cannot be delivered, or times out, it is retried until it is successfully acknowledged.