From 7152a8b0f3d058479f53738e7d637957ac66fe2c Mon Sep 17 00:00:00 2001 From: Ryan Emerson Date: Wed, 30 Oct 2024 11:47:32 +0000 Subject: [PATCH] Update caching docs to reflect that IP multicast is no longer used by default Closes #34495 Signed-off-by: Ryan Emerson Signed-off-by: Alexander Schwartz Co-authored-by: Alexander Schwartz --- docs/guides/server/caching.adoc | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/guides/server/caching.adoc b/docs/guides/server/caching.adoc index aed0f1b5d8..48a6e39f72 100644 --- a/docs/guides/server/caching.adoc +++ b/docs/guides/server/caching.adoc @@ -14,7 +14,8 @@ The current distributed cache implementation is built on top of https://infinisp == Enable distributed caching When you start {project_name} in production mode, by using the `start` command, caching is enabled and all {project_name} nodes in your network are discovered. -By default, caches are using a UDP transport stack so that nodes are discovered using IP multicast transport based on UDP. For most production environments, there are better discovery alternatives to UDP available. {project_name} allows you to either choose from a set of pre-defined default transport stacks, or to define your own custom stack, as you will see later in this {section}. +By default, caches use the `jdbc-ping-udp` stack which is based upon a UDP transport and uses the configured database to track nodes joining the cluster. +{project_name} allows you to either choose from a set of pre-defined default transport stacks, or to define your own custom stack, as you will see later in this {section}. To explicitly enable distributed infinispan caching, enter this command: