You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@openmeetings.apache.org by so...@apache.org on 2018/06/06 09:04:24 UTC

[openmeetings] branch master updated: no jira: cluster documentation update

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

solomax pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/openmeetings.git


The following commit(s) were added to refs/heads/master by this push:
     new 529a56f  no jira: cluster documentation update
529a56f is described below

commit 529a56fd26a2fd1b1b3a29f37a06f02c829d8174
Author: Maxim Solodovnik <so...@gmail.com>
AuthorDate: Wed Jun 6 16:03:46 2018 +0700

    no jira: cluster documentation update
---
 openmeetings-server/src/site/xdoc/Clustering.xml               | 6 +++---
 openmeetings-web/src/main/webapp/WEB-INF/classes/hazelcast.xml | 8 ++++++++
 2 files changed, 11 insertions(+), 3 deletions(-)

diff --git a/openmeetings-server/src/site/xdoc/Clustering.xml b/openmeetings-server/src/site/xdoc/Clustering.xml
index 13eb9fc..8f3f976 100644
--- a/openmeetings-server/src/site/xdoc/Clustering.xml
+++ b/openmeetings-server/src/site/xdoc/Clustering.xml
@@ -63,8 +63,8 @@
 					<li>Using netstat check if the multicast IP is visible in your route table (see step 2.)</li>
 					<li>
 						Using tcpdump and ping check if your server is able to multicast.<br/>
-						Run the following command on <b>all</b> the servers. <source>sudo tcpdump -ni en0 host 228.0.0.4</source>
-						Run the following command on <b>any</b> server. <source>ping -t 1 -c 2 228.0.0.4</source>
+						Run the following command on <b>all</b> the servers. <source>sudo tcpdump -ni eth0 host 224.0.0.0</source>
+						Run the following command on <b>any</b> server. <source>ping -t 1 -c 2 224.0.0.0</source>
 						Check all servers receiving pings
 					</li>
 					<li>
@@ -130,7 +130,7 @@
 							</li>
 							<li>
 								In case there are more than one network interface with multicast support and/or additional hazelcast configuration is required
-								Based on the following documentation: <a href="http://docs.hazelcast.org/docs/3.8.3/manual/html-single/index.html">http://docs.hazelcast.org/docs/3.8.3/manual/html-single/index.html</a>
+								Based on the following documentation: <a href="http://docs.hazelcast.org/docs/3.10.1/manual/html-single/index.html">http://docs.hazelcast.org/docs/3.10.1/manual/html-single/index.html</a>
 							</li>
 						</ul>
 					</li>
diff --git a/openmeetings-web/src/main/webapp/WEB-INF/classes/hazelcast.xml b/openmeetings-web/src/main/webapp/WEB-INF/classes/hazelcast.xml
index c0a965b..ebb5119 100644
--- a/openmeetings-web/src/main/webapp/WEB-INF/classes/hazelcast.xml
+++ b/openmeetings-web/src/main/webapp/WEB-INF/classes/hazelcast.xml
@@ -67,6 +67,14 @@
 		</join>
 	</network>
 	<!--network>
+		<join>
+			<multicast enabled="true">
+				<multicast-group>224.0.0.0</multicast-group>
+				<multicast-port>54327</multicast-port>
+				<multicast-time-to-live>32</multicast-time-to-live>
+				<multicast-timeout-seconds>2</multicast-timeout-seconds>
+			</multicast>
+		</join>
 		<interfaces enabled="true">
 			<interface>192.168.1.*</interface>
 		</interfaces>

-- 
To stop receiving notification emails like this one, please contact
solomax@apache.org.