Ver código fonte

Fix Data Cleanup doc (#1121)

master
Facundo Aita 2 anos atrás
committed by GitHub
pai
commit
ddf5ddd6af
Nenhuma chave conhecida encontrada para esta assinatura no banco de dados ID da chave GPG: 4AEE18F83AFDEB23
1 arquivos alterados com 2 adições e 2 exclusões
  1. +2
    -2
      docs/content/user-guide/en/cap/messaging.md

+ 2
- 2
docs/content/user-guide/en/cap/messaging.md Ver arquivo

@@ -125,8 +125,8 @@ There is an `ExpiresAt` field in the database message table indicating the expir

Consuming failure will change the message status to `Failed` and `ExpiresAt` will be set to **15 days** later.

By default, the data of the message in the table is deleted **5 minutes** to avoid performance degradation caused by too much data. The cleanup strategy `ExpiresAt` is performed when field is not empty and is less than the current time.
By default, the data of the message in the table is deleted every **5 minutes** to avoid performance degradation caused by too much data. The cleanup strategy `ExpiresAt` is performed when field is not empty and is less than the current time.

That is to say, the message with the status Failed (by default they have been retried 50 times), if you do not have manual intervention for 15 days, it will **also be** cleaned up.

You can use [CollectorCleaningInterval](../configuration#collectorcleaninginterval) configuration items to custom the interval time.
You can use [CollectorCleaningInterval](../configuration#collectorcleaninginterval) configuration items to custom the interval time.

Carregando…
Cancelar
Salvar