Updated guidance around time-to-be-received (TTBR) and auditing #6717
Conversation
There was a problem hiding this comment.
I am wondering if it would not be better to invert the documentation and just state "TTBR is processed at the receiver" and (maybe) add small note for RabbitMQ that in addition to that, the broker is able to remove expired messages but it looks only at the head of the queue.
| | Scripted Deployment | SQL Scripts | | ||
| | Installers | Optional | | ||
| | Native integration | Supported, see [SQL statements used by the transport](https://github.com/Particular/NServiceBus.SqlServer/blob/master/src/NServiceBus.Transport.PostgreSql/PostgreSqlConstants.cs) | | ||
| | [time-to-be-received](#time-to-be-received) (TTBR) | Storage reclaimed at most 5 minutes after expiration when receiving endpoint is running | |
There was a problem hiding this comment.
Why 5 minutes? The PostgreSQL transport does not have periodic task that deletes these messages. The only way to remove expired messages is by receiving them.
| | Scripted Deployment | Sql Scripts | | ||
| | Installers | Optional | | ||
| | Native integration | [Supported](native-integration.md) | | ||
| | [time-to-be-received](#time-to-be-received) (TTBR) | Storage reclaimed at most 5 minutes after expiration when receiving endpoint is running | |
There was a problem hiding this comment.
Why 5 minutes? SQLT has a (disabled by default) feature to remove the expired messages on startup but it runs once (when the endpoint starts), not periodically.
There was a problem hiding this comment.
@SzymonPobiega because the docs state so: https://docs.particular.net/nservicebus/messaging/discard-old-messages?version=core_7#caveats-sql-transport
The SQL Server transport runs a periodic task that removes expired messages from the queue. The task is first executed when the endpoint starts and is subsequently scheduled to execute 5 minutes after the previous run when the task has been completed. Expired messages are not received from the queue and their disk space will be reclaimed when the periodic task executes.
And as Postgresql uses the same base design I assumed same behavior hence me stating "SQL Transport"
|
|
||
| ## Time-to-be-received | ||
|
|
||
| The SQL transport runs a periodic task that removes expired messages from the queue. The task is first executed when the endpoint starts and is subsequently scheduled to execute 5 minutes after the previous run when the task has been completed. Expired messages are not received from the queue and their disk space will be reclaimed when the periodic task executes. |
There was a problem hiding this comment.
Not any more. It has been removed because it tended to deadloack with the receive tasks.
There was a problem hiding this comment.
So, good to know since which version this behavior changed. Do you know what major that changed @SzymonPobiega ?
|
This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
github-actions
bot
removed
the
stale
No description provided.