[
https://issues.apache.org/jira/browse/OPENMEETINGS-2186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17064184#comment-17064184
]
Aleix Dorca commented on OPENMEETINGS-2186:
-------------------------------------------
Maxim,
Thanks for taking the time to investigate this. Do you have any news?
So far I have managed to setup 2 servers that share MySQL and NFS folders.
I have disabled the _Dashboard_ right for all users and have setup a landing
page with the "distributed" rooms that sends users to one or the other server.
This is far from optimal but it does the job of not saturating a server while
having all data centralized. This can be "scaled" to n servers, of course, as
long as I manually choose the servers rooms will be held.
It would be great to have this done automatically.
Thanks,
Aleix.
> Clustering does nothing in version 5.0-M3
> -----------------------------------------
>
> Key: OPENMEETINGS-2186
> URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2186
> Project: Openmeetings
> Issue Type: Bug
> Components: Cluster
> Affects Versions: 5.0.0-M3
> Environment: Ubuntu 18.04 LTS
> Reporter: Aleix Dorca
> Assignee: Maxim Solodovnik
> Priority: Major
>
> I can not, for the life of me, to get Clustering to work. I have followed the
> latest guide: [https://openmeetings.apache.org/Clustering.html]. My setup is
> 100% local, no NAT or any kind of routing between networks.
> Here is a summary of the steps I have followed:
> * Two OM servers, both installed using the Ubuntu Bionic 18.04 LTS guide.
> Local IPs: 192.168.0.100/24 and 192.168.0.101/24.
> * One (the primary if you will) has the MySQL server and shares the
> stream/upload folders using NFS. No problems with this.
> * When I log into any OM server and access rooms, all (video, audio,
> recording/sharing screen, files...) works as expected.
> I have, then, followed the Clustering guide to:
> * Enable Multicast. Works without any problems.
> * Share database and folders
> * Enable multicast on OM, on both nodes.
> * Restart OM.
> * I see pings and cluster goes online.
> I can see that all starts fine. The cluster is up with both instances
> detected:
> {noformat}
> Members {size:2, ver:2} [
> Member [192.168.0.100]:5701 - d8a5272a-cc80-42cf-98bd-80b04a2b5c7f this
> Member [192.168.0.101]:5701 - a7746996-cc40-46e6-9a4a-75be0b28e7f7
> ]
> {noformat}
> From this moment I try to ensure everything works as expected:
> * Login with two users and go to the same room: Both users have logged in on
> the server 192.168.0.100. On the Connections tab I see both are in
> "server-1". So far so good.
> * Enter a room, both users end up in the same room, in the same server,
> still "server-1". Ok... I guess.
> * Login with two users from different servers and then go to the same room:
> Yes, they see each other, but chat does not work, video and audio do not work
> as well. It looks like the clustering configuration does no re-route the
> second user to the first server.
> * Login with four users and access two different rooms: The problems above
> are seen again, there is never any re-routing of users so they end up always
> in rooms in the server they have initially logged in.
> Thanks for any tips that can enlighten me.
> Aleix.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
