Hi all,
Jock: just like Alexei said, I assume you don't have a "seed" node.
Make sure one node of your opensips.clusterer table has "seed" in the
"flags" column. Regarding offline restart persistence: you may skip the
"working_mode_preset" parameter and individually set "cluster_mode" [1]
and "restart_persistency" [2] in order to achieve a restart-persistent
cluster using an SQL DB, rather than point-to-point sync.
Alexei: that is exactly how we meant it to be used. With 0 nodes
online, you have to bootstrap the cluster somehow -- this is the purpose
of the "seed" node.
Cheers,
[1]:
https://opensips.org/html/docs/modules/3.0.x/usrloc.html#param_cluster_mode
[2]:
https://opensips.org/html/docs/modules/3.0.x/usrloc.html#restart_persistency
Liviu Chircu
OpenSIPS Developer
http://www.opensips-solutions.com
On 18.10.2018 09:28, vasilevalex wrote:
Hi Jock.
I also use full-sharing cluster with just two nodes. Everything in memory,
no DB.
Do you have "seed" node? Because without it, as far as I tested, it is
impossible to get out from "not synced state". All nodes unsynced so no one
can be taken as trusted point.
I made seed flag for one server. So the second server starts and trusts seed
node. If I restart seeding node, it starts clean (and this state is
considered trusted and synced for itself) then I have to run "opensipsctl
fifo ul_cluster_sync" on it to add all the data from cluster to it's clean
state. So it became synced and containing all data.
May be this is not the best way, but I don't know, how also can be solved
this state.
--
Sent from:
http://opensips-open-sip-server.1449251.n2.nabble.com/OpenSIPS-Users-f1449235.html
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
