From 822231f100bd6ddcfacf730e321da96e4a3fc646 Mon Sep 17 00:00:00 2001 From: Yingrong Zhao <22300958+VinozzZ@users.noreply.github.com> Date: Mon, 2 Dec 2024 11:34:59 -0500 Subject: [PATCH] Update refinery_config.md Co-authored-by: Kent Quirk --- refinery_config.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/refinery_config.md b/refinery_config.md index 81f6b5b643..cc018fdde2 100644 --- a/refinery_config.md +++ b/refinery_config.md @@ -1016,7 +1016,8 @@ When `distributed`, Refinery will instead keep spans on the node where they were This can reduce the amount of traffic between peers in most cases, and can help avoid a situation where a single large trace can cause a memory overrun on a single node. If `distributed`, the amount of traffic between peers will be reduced, but the amount of traffic between Refinery and Redis will significantly increase, because Refinery uses Redis to distribute the trace decisions to all nodes in the cluster. It is important to adjust the size of the Redis cluster in this case. -NOTE: This setting is not compatible with `DryRun` when set to true. +The total volume of network traffic in `distributed` mode should be expected to decrease unless the cluster size is very large (hundreds of nodes). +NOTE: This setting is not compatible with `DryRun` when set to `distributed`. See `DryRun` for more information. - Not eligible for live reload.