From 0720bf3a8ad8544ba06db789470ad030d74eb42a Mon Sep 17 00:00:00 2001 From: ben8t <46634684+Ben8t@users.noreply.github.com> Date: Thu, 14 Nov 2024 16:04:17 +0100 Subject: [PATCH] Add explanation to big messages protection (#1954) --- content/docs/configuration/index.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/docs/configuration/index.md b/content/docs/configuration/index.md index c377beb18f..433ee8066e 100644 --- a/content/docs/configuration/index.md +++ b/content/docs/configuration/index.md @@ -316,7 +316,7 @@ Note: this is an experimental feature available starting with Kestra 0.19. The database backend has no limit on the size of messages it can handle. However, as messages are loaded into memory, this can endanger Kestra itself and push pressure on memory usage. -To prevent that, you can configure a functionality that will refuse to store too big messages and fail the execution instead. +To prevent that, you can configure a functionality that will refuse to store too big messages in the execution context (for example data stored in `outputs` property) and fail the execution instead. The following configuration will refuse messages that exceed 1MiB by failing the execution. @@ -2010,4 +2010,4 @@ kestra: color: var(--white-always); } -``` \ No newline at end of file +```