[OpenSIPS-Users] HA ongoing call support in 2.4 - transaction replication

[Jeff Pyle]

Alexei,

I see the article.  In summary, transactions are too complicated to
synchronize between nodes of a cluster because of their short timing
intervals and complex structures.  Instead the approach is to get the
messages of a transaction back to the individual node that owns the
transaction so it can process there.  Got it.

For a cluster with many anycast nodes, this makes a lot of sense.  For a
simple active/standby setup, it prevents one from achieving a hitless
failover from one node to another if there are active transactions.
Bummer.  I'm sure Razvan and the team understood this when deciding on this
architecture.  Big picture their approach solves a lot more problems than
it creates, and it's very cool nonetheless.


- Jeff


On Thu, Feb 20, 2020 at 1:56 AM Alexey Vasilyev <alexei.vasilyev at gmail.com>
wrote:

> Hi Jeff,
>
> Transactions are not replicated.
> Here
> https://blog.opensips.org/2018/03/21/full-anycast-support-in-opensips-2-4/
> Razvan explains why. Section "Distributed transactions handling".
>
>
>
> -----
> ---
> Alexey Vasilyev
> --
> Sent from:
> http://opensips-open-sip-server.1449251.n2.nabble.com/OpenSIPS-Users-f1449235.html
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20200220/0026eef6/attachment.html>