Enable participant pruning with 30d retention (#3090)

Signed-off-by: Julien Tinguely <[email protected]>

Author: julientinguely-da

apps/validator/src/main/scala/org/lfdecentralizedtrust/splice/validator/config/ValidatorAppConfig.scala

@@ -21,6 +21,7 @@ import com.digitalasset.canton.config.*
 import com.digitalasset.canton.config.RequireTypes.{NonNegativeLong, NonNegativeNumeric}
 
 import java.nio.file.Path
+import scala.concurrent.duration.DurationInt
 
 case class AppInstance(
     serviceUser: String,
@@ -193,7 +194,14 @@ case class ValidatorAppBackendConfig(
       NonNegativeFiniteDuration.ofSeconds(10),
     // Identifier for all Canton nodes controlled by this application
     cantonIdentifierConfig: Option[ValidatorCantonIdentifierConfig] = None,
-    participantPruningSchedule: Option[PruningConfig] = None,
+    // Participant pruning is enabled by default for all validators and SVs
+    participantPruningSchedule: Option[PruningConfig] = Some(
+      PruningConfig(
+        cron = "0 /10 * * * ?", // Runs every 10 minutes
+        maxDuration = PositiveDurationSeconds.tryFromDuration(5.minutes),
+        retention = PositiveDurationSeconds.tryFromDuration(30.days),
+      )
+    ),
     deduplicationDuration: PositiveDurationSeconds = PositiveDurationSeconds.ofHours(24),
     txLogBackfillEnabled: Boolean = true,
     txLogBackfillBatchSize: Int = 100,

docs/src/release_notes.rst

@@ -6,16 +6,23 @@
 .. _release_notes:
 
 Upcoming
-========
+--------
+
+- Canton Participant
+
+  - Participants now prune data to only retain the last 30 days matching the 30 day pruning interval of sequencers and mediators.
+    You can overwrite this default value by adding the following env variable in the `additionalEnvVars` helm values of the validator app: `ADDITIONAL_CONFIG_PARTICIPANT_PRUNING`
+
+    An example value would be: ``ADDITIONAL_CONFIG_PARTICIPANT_PRUNING=canton.validator-apps.validator_backend.participant-pruning-schedule {cron: "0 /10 * * * ?", max-duration: "5m", retention: "10h"}``
 
 - Sequencer connections
 
-    - Improve retries for sending sequencer submissions when a sequencer rejects the request with an overloaded error code by retrying immediately on another node.
-    - The network timeout for the connection was lowered to 15 seconds to detect failures faster.
+  - Improve retries for sending sequencer submissions when a sequencer rejects the request with an overloaded error code by retrying immediately on another node.
+  - The network timeout for the connection was lowered to 15 seconds to detect failures faster.
 
 
 0.5.1
-=====
+-----
 
 - Canton Participant