[prev in list] [next in list] [prev in thread] [next in thread] 

List:       jakarta-commons-dev
Subject:    [commons-jcs] 06/07: Document service address selection algorithm
From:       tv () apache ! org
Date:       2021-03-30 19:04:13
Message-ID: 20210330190408.3D4898E950 () gitbox ! apache ! org
[Download RAW message or body]

This is an automated email from the ASF dual-hosted git repository.

tv pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/commons-jcs.git

commit 8cc35dc0064925c5343c0e9c0c666d53f828c12e
Author: Thomas Vandahl <tv@apache.org>
AuthorDate: Tue Mar 30 21:02:53 2021 +0200

    Document service address selection algorithm
---
 xdocs/LateralUDPDiscovery.xml | 18 ++++++++++++++----
 1 file changed, 14 insertions(+), 4 deletions(-)

diff --git a/xdocs/LateralUDPDiscovery.xml b/xdocs/LateralUDPDiscovery.xml
index 4c6b6c7..32eac5f 100644
--- a/xdocs/LateralUDPDiscovery.xml
+++ b/xdocs/LateralUDPDiscovery.xml
@@ -35,10 +35,20 @@
 	  <p>
 		On startup each lateral will issue a special message requesting a
 		broadcast from the other caches.  Normal broadcasts occur every
-		30 seconds. (This is to be made configurable.)  Regions that don't
+		15 seconds. (This is to be made configurable.)  Regions that don't
 		receive, are running in send only mode, don't broadcast anything but requests.
   	  </p>
       <p>
+        The normal broadcasts publish the address and port of the service.
+        This can be configured as <code>TcpListenerHost</code> and 
+        <code>TcpListenerPort</code>, respectively. If the service address
+        is not set, the service tries to detect a suitable address using the 
+        same interface as the one that is used for multicast. If the multicast
+        uses IPv6, a link-local IPv6 address is selected if one exists. 
+        Otherwise, a site-local IPv4 address is chosen. If that attempt also 
+        fails, the first address on any non-loopback interface is used.
+      </p>
+      <p>
 	    When a lateral receives a discovery message it will try to add
 	    the lateral to the nowait facade for the region.  If it already exists
 	    nothing happens.  If a region is not configured to send laterally, nothing
@@ -51,12 +61,12 @@
         <p>
           The configuration is fairly straightforward and is done in the
           auxiliary cache section of the <code>cache.ccf</code>
-          configuration file.  In the example below, I created a TCP
-          Lateral Auxiliary Cache referenced by <code>LTCP</code>.  It uses
+          configuration file.  In the example below, a TCP
+          Lateral Auxiliary Cache referenced by <code>LTCP</code> is created.  It uses
           UDP Discovery to locate other servers.  It broadcasts to
           multicast address <code>228.5.6.8</code> and port <code>6780</code>.
           It listens to port <code>1110</code>. The UDP datagram time-to-live
-          is 4. 
+          is 4 hops. 
         </p>
         <source><![CDATA[
 jcs.auxiliary.LTCP=org.apache.commons.jcs3.auxiliary.lateral.socket.tcp.LateralTCPCacheFactory
[prev in list] [next in list] [prev in thread] [next in thread]