clusterer.so settings in 2.4.x

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

clusterer.so settings in 2.4.x

OpenSIPS - Users mailing list
Hi list!

I have a working active-backup cluster of two OpenSIPS 2.4.5 nodes.
(listening on virtual IP being moved by Keepalived,
and Redis instances for RTPEngines).

I configured clusterer module without DB support.
I'm a little bit confused if I have to use 'flags=seed' only in one
config or in both nodes's configs?

As for now, it is so:

# OpenSIPS1
modparam("clusterer", "current_info","cluster_id=1,url=bin:10.145.213.63:5555,flags=seed")
modparam("clusterer", "neighbor_info","cluster_id=1,node_id=2,url=bin:10.145.213.155:5555")

# OpenSIPS2
modparam("clusterer", "current_info", "cluster_id=1,url=bin:10.145.213.155:5555,flags=seed")
modparam("clusterer", "neighbor_info", "cluster_id=1,node_id=1,url=bin:10.145.213.63:5555")


https://blog.opensips.org/2018/03/23/clustering-ongoing-calls-with-opensips-2-4/
https://opensips.org/html/docs/modules/2.4.x/clusterer.html

-----------------------------------------------
BR, Alexey
http://alexeyka.zantsev.com/
_______________________________________________
Users mailing list
[hidden email]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Reply | Threaded
Open this post in threaded view
|

Re: clusterer.so settings in 2.4.x

Vlad Patrascu
Hi Alexey,

For your clustering scenario you should use the seed flag only in one of
the nodes' configs.

Regards,

Vlad Patrascu
OpenSIPS Developer
http://www.opensips-solutions.com

On 03/15/2019 11:13 AM, Alexey Kazantsev via Users wrote:

> Hi list!
>
> I have a working active-backup cluster of two OpenSIPS 2.4.5 nodes.
> (listening on virtual IP being moved by Keepalived,
> and Redis instances for RTPEngines).
>
> I configured clusterer module without DB support.
> I'm a little bit confused if I have to use 'flags=seed' only in one
> config or in both nodes's configs?
>
> As for now, it is so:
>
> # OpenSIPS1
> modparam("clusterer", "current_info","cluster_id=1,url=bin:10.145.213.63:5555,flags=seed")
> modparam("clusterer", "neighbor_info","cluster_id=1,node_id=2,url=bin:10.145.213.155:5555")
>
> # OpenSIPS2
> modparam("clusterer", "current_info", "cluster_id=1,url=bin:10.145.213.155:5555,flags=seed")
> modparam("clusterer", "neighbor_info", "cluster_id=1,node_id=1,url=bin:10.145.213.63:5555")
>
>
> https://blog.opensips.org/2018/03/23/clustering-ongoing-calls-with-opensips-2-4/
> https://opensips.org/html/docs/modules/2.4.x/clusterer.html
>
> -----------------------------------------------
> BR, Alexey
> http://alexeyka.zantsev.com/
> _______________________________________________
> Users mailing list
> [hidden email]
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users


_______________________________________________
Users mailing list
[hidden email]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Reply | Threaded
Open this post in threaded view
|

Re: clusterer.so settings in 2.4.x

OpenSIPS - Users mailing list
Hi Vlad, thank you for the reply.

So I have to configure it in this way:

   # main node, which is active if everything's OK
   modparam("clusterer", "current_info","cluster_id=1,url=bin:10.45.144.77:5555,flags=seed")
   modparam("clusterer", "neighbor_info","cluster_id=1,node_id=2,url=bin:10.45.144.79:5555")

   # backup node, which is standby and will work in case of node1 failure
   modparam("clusterer", "current_info","cluster_id=1,url=bin:10.45.144.79:5555")
   modparam("clusterer", "neighbor_info","cluster_id=1,node_id=1,url=bin:10.45.144.77:5555")


Is it correct?
So, node with BIN IP 10.45.144.77 will be a seed, a source of ready cluster info/data.

-----------------------------------------------
BR, Alexey
http://alexeyka.zantsev.com/
_______________________________________________
Users mailing list
[hidden email]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Reply | Threaded
Open this post in threaded view
|

Re: clusterer.so settings in 2.4.x

Vlad Patrascu
Yes, that is correct.

Vlad Patrascu
OpenSIPS Developer
http://www.opensips-solutions.com

On 03/15/2019 12:32 PM, Alexey Kazantsev via Users wrote:

> Hi Vlad, thank you for the reply.
>
> So I have to configure it in this way:
>
>     # main node, which is active if everything's OK
>     modparam("clusterer", "current_info","cluster_id=1,url=bin:10.45.144.77:5555,flags=seed")
>     modparam("clusterer", "neighbor_info","cluster_id=1,node_id=2,url=bin:10.45.144.79:5555")
>
>     # backup node, which is standby and will work in case of node1 failure
>     modparam("clusterer", "current_info","cluster_id=1,url=bin:10.45.144.79:5555")
>     modparam("clusterer", "neighbor_info","cluster_id=1,node_id=1,url=bin:10.45.144.77:5555")
>
>
> Is it correct?
> So, node with BIN IP 10.45.144.77 will be a seed, a source of ready cluster info/data.
>
> -----------------------------------------------
> BR, Alexey
> http://alexeyka.zantsev.com/
> _______________________________________________
> Users mailing list
> [hidden email]
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users


_______________________________________________
Users mailing list
[hidden email]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users