[OpenSIPS-Users] RabbitMQ high availability

[Gerwin van de Steeg]

Ahmed,

In theory:

You can configure RabbitMQ as a 2+ node (although i'd start with 3 nodes)
highly available cluster, and depending on how you configure it you can get
it to the point where it doesn't matter about which node you publish to to
get the message into the right exchange, all you need to do then is consume
from it.
If you then stick an HA Proxy based (or other type of network load
balancer) load balancer in front then you have a single point you can
connect to and the HA Proxy will load balance the connection from OpenSIPS
through to a running RabbitMQ broker.

That should work, but you may have to try it and find out how that all
works.




On Thu, 14 Mar 2019 at 00:37, Răzvan Crainea <razvan at opensips.org> wrote:

> Hi, Ahmed!
>
> None of the module supports this by themselves, but you can achieve this
> for each of them using existing tools:
> * for event_rabbitmq, you can put multiple rabbitmq subscribers in an
> event_virtual handler
> * for rabbitmq you can test in the script if the command was
> successfully sent
> Note that for both modules you need to run in synchronous mode to
> support this feature.
>
> Best regards,
> Răzvan
>
> On 3/12/19 12:54 PM, Ahmed Shabana wrote:
> > Dears ,Does any of the rabbitmq 2 modules supported at opensip 2.4.x
> support high availability mode i.e. fallback to second rabbitmq if the
> first one not working properly ?
> >
> > Also if it fail to send to the rabbmitmq does the script fail ?
> >
> >
> > _______________________________________________
> > Users mailing list
> > Users at lists.opensips.org
> > http://lists.opensips.org/cgi-bin/mailman/listinfo/users
> >
>
> --
> Răzvan Crainea
> OpenSIPS Core Developer
>    http://www.opensips-solutions.com
> Meet the OpenSIPS team at the next OpenSIPS Summit:
>    https://www.opensips.org/events
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20190314/f2e92e10/attachment.html>