From 64fb60720842a9ce10c37f2b300e14652dc781fb Mon Sep 17 00:00:00 2001 From: David Venable Date: Wed, 12 Oct 2022 14:13:12 -0500 Subject: [PATCH] Removed "all" per recommendation. Signed-off-by: David Venable --- _posts/2022-10-10-Announcing-Data-Prepper-2.0.0.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_posts/2022-10-10-Announcing-Data-Prepper-2.0.0.md b/_posts/2022-10-10-Announcing-Data-Prepper-2.0.0.md index f8c3d42670..0be046984d 100644 --- a/_posts/2022-10-10-Announcing-Data-Prepper-2.0.0.md +++ b/_posts/2022-10-10-Announcing-Data-Prepper-2.0.0.md @@ -89,7 +89,7 @@ single node. With peer forwarding as a core feature, pipeline authors can perform stateful aggregations on multiple Data Prepper nodes. When performing stateful aggregations, Data Prepper uses a hash ring to determine which nodes are responsible for processing different events based on the values of certain fields. Peer forwarder -routes events to the node responsible for processing them. That node then holds all the state necessary for performing the aggregation. +routes events to the node responsible for processing them. That node then holds the state necessary for performing the aggregation. To use peer forwarding, configure how Data Prepper discovers other nodes and the security for connections in your `data-prepper-config.yaml` file.