Update caching docs to reflect that IP multicast is no longer used by default
Closes #34495 Signed-off-by: Ryan Emerson <remerson@redhat.com> Signed-off-by: Alexander Schwartz <aschwart@redhat.com> Co-authored-by: Alexander Schwartz <aschwart@redhat.com>
This commit is contained in:
parent
7bbc35cba7
commit
7152a8b0f3
1 changed files with 2 additions and 1 deletions
|
@ -14,7 +14,8 @@ The current distributed cache implementation is built on top of https://infinisp
|
||||||
== Enable distributed caching
|
== 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.
|
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:
|
To explicitly enable distributed infinispan caching, enter this command:
|
||||||
|
|
||||||
|
|
Loading…
Reference in a new issue