Hi Pasan,
Indeed, it can help to have the DB as an alternative for restart
persistency in case it can not be achieved through cluster syncing. But
this is not _required_ and the concept of "seed" node is not linked to
the DB. Rather, this is more of a consequence of the fact that the seed
Hi Steve,
you need a db backend to have restart persistence. From what I understood seed
node require a db backend to restore data that require restart persistence.
On Wednesday, 28 August 2019, 9:25:27 am SGT, Steve Sharad Kumar
wrote:
Hi,
We have 2 openSIPS instances in HA and one
Hi,
If you are using a 2.4 build newer than 8 July, you can set the the
following modparam to configure the seed node to also try to find a sync
donor within a given interval:
...
modparam("clusterer", "seed_fallback_interval", 5)
...
Otherwise, this improvement is not included in the
Hi,
We have 2 openSIPS instances in HA and one instance is seed node with seed
flag in the DB. So each time backup node reboots and it always syncs the
dialog from seed node. But how we can make a seed node to sync the dialog
from other backup node is seed node reboots?
I tried to make both
