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
does not automatically perform a sync itself. Nevertheless, it can be
forced to sync by running an MI command.
Regards,
Vlad Patrascu
OpenSIPS Developer
http://www.opensips-solutions.com
On 08/29/2019 01:41 PM, Pasan Meemaduma via Users wrote:
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
<sku...@netlinkvoice.com> wrote:
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 nodes seed but primary node (seed) never syncs
the dialog. So i execute the dialog sync command using keepalived
everytime seed node reboots. Is there any other way to make seed node
sync too please.
Any help will be appreciated.
Steve Sharad Kumar
_______________________________________________
Users mailing list
Users@lists.opensips.org <mailto:Users@lists.opensips.org>
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
