Does the dialog module do anything similar to the htable dmq_init_sync behavior?
The scenario is restarting the offline member of an HA pair after modifying the script. We're unsure of the state of the replicated dialogs post-restart. Will the standby become aware of the dialogs prior to the restart? In other words, do we need to wait until the pre-restart calls end before we can safely failover?
-Calvin E.
Hello,
are you aware of the DMQ synchronisation for dialog data? It’s not replicated everything, but certainly a way to seed the dialog information after a restart. Another way is of course the usual shared database, just keep in mind that you need to configure the dialog module (hash table “step” variables”) to properly work.
Cheers,
Henning
-- Henning Westerholt – https://skalatan.de/blog/ Kamailio services – https://gilawa.comhttps://gilawa.com/
From: Calvin E. calvine@gmail.com Sent: Donnerstag, 8. Juni 2023 19:36 To: Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org Subject: [SR-Users] Dialog DMQ state after restart
Does the dialog module do anything similar to the htable dmq_init_sync behavior?
The scenario is restarting the offline member of an HA pair after modifying the script. We're unsure of the state of the replicated dialogs post-restart. Will the standby become aware of the dialogs prior to the restart? In other words, do we need to wait until the pre-restart calls end before we can safely failover?
-Calvin E.
Henning,
Does the dialogs' profile membership get DMQ-synced nowadays, too?
-- Alex
On Jun 8, 2023, at 3:53 PM, Henning Westerholt hw@gilawa.com wrote:
Hello, are you aware of the DMQ synchronisation for dialog data? It’s not replicated everything, but certainly a way to seed the dialog information after a restart. Another way is of course the usual shared database, just keep in mind that you need to configure the dialog module (hash table “step” variables”) to properly work. Cheers, Henning -- Henning Westerholt – https://skalatan.de/blog/ Kamailio services – https://gilawa.com From: Calvin E. calvine@gmail.com Sent: Donnerstag, 8. Juni 2023 19:36 To: Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org Subject: [SR-Users] Dialog DMQ state after restart Does the dialog module do anything similar to the htable dmq_init_sync behavior? The scenario is restarting the offline member of an HA pair after modifying the script. We're unsure of the state of the replicated dialogs post-restart. Will the standby become aware of the dialogs prior to the restart? In other words, do we need to wait until the pre-restart calls end before we can safely failover? -Calvin E. __________________________________________________________ Kamailio - Users Mailing List - Non Commercial Discussions To unsubscribe send an email to sr-users-leave@lists.kamailio.org Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe:
Hi Alex,
according to docs only basic dialog (profile) information is synchronized. I quickly checked the code, and its synchronizing profiles as well. But some functionality will work only on the original node, like sending in-dialog requests.
Cheers,
Henning
Henning,
If profile membership is synchronised, does that mean it is possible to get a count of dialogs in a given profile on any node?
-- Alex
On Jun 9, 2023, at 4:31 AM, Henning Westerholt hw@gilawa.com wrote:
Hi Alex,
according to docs only basic dialog (profile) information is synchronized. I quickly checked the code, and its synchronizing profiles as well. But some functionality will work only on the original node, like sending in-dialog requests.
Cheers,
Henning
-- Henning Westerholt – https://skalatan.de/blog/ Kamailio services – https://gilawa.com
-----Original Message----- From: Alex Balashov abalashov@evaristesys.com Sent: Donnerstag, 8. Juni 2023 22:28 To: Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org Subject: [SR-Users] Re: Dialog DMQ state after restart
Henning,
Does the dialogs' profile membership get DMQ-synced nowadays, too?
-- Alex
On Jun 8, 2023, at 3:53 PM, Henning Westerholt hw@gilawa.com wrote:
Hello, are you aware of the DMQ synchronisation for dialog data? It’s not replicated
everything, but certainly a way to seed the dialog information after a restart.
Another way is of course the usual shared database, just keep in mind that you
need to configure the dialog module (hash table “step” variables”) to properly work.
Cheers, Henning -- Henning Westerholt – https://skalatan.de/blog/ Kamailio services – https://gilawa.com From: Calvin E. calvine@gmail.com Sent: Donnerstag, 8. Juni 2023 19:36 To: Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org Subject: [SR-Users] Dialog DMQ state after restart Does the dialog module do anything similar to the htable dmq_init_sync behavior? The scenario is restarting the offline member of an HA pair after modifying the
script. We're unsure of the state of the replicated dialogs post-restart. Will the standby become aware of the dialogs prior to the restart? In other words, do we need to wait until the pre-restart calls end before we can safely failover?
-Calvin E. __________________________________________________________ Kamailio - Users Mailing List - Non Commercial Discussions To unsubscribe send an email to sr-users-leave@lists.kamailio.org Important: keep the mailing list in the recipients, do not reply only to the
sender!
Edit mailing list options or unsubscribe:
-- Alex Balashov Principal Consultant Evariste Systems LLC Web: https://evaristesys.com Tel: +1-706-510-6800
Kamailio - Users Mailing List - Non Commercial Discussions To unsubscribe send an email to sr-users-leave@lists.kamailio.org Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe:
Hi Alex
If profile membership is synchronised, does that mean it is possible to get a count of dialogs in a given profile on any node?
Correct. I'm using this to implement a channel limit per trunk or per customer on two dialog DMQ synced nodes.
The question is whether that DMQ synchronization for dialog data is sending all dialogs or only delta/incremental data. Some SBCs I've worked with only synchronize new dialog data, leaving standby nodes only aware of dialogs established since restarting or joining the cluster, not existing dialogs. In that circumstance, a failover to the restarted or new standby would break any dialogs created prior to the restart.
If Kamailio dialog DMQ synchronization is "complete" then we just need to know how to confirm the new standby is synchronized before performing a failover.
On Thu, Jun 8, 2023 at 12:53 PM Henning Westerholt hw@gilawa.com wrote:
Hello,
are you aware of the DMQ synchronisation for dialog data? It’s not replicated everything, but certainly a way to seed the dialog information after a restart.
Another way is of course the usual shared database, just keep in mind that you need to configure the dialog module (hash table “step” variables”) to properly work.
Cheers,
Henning
--
Henning Westerholt – https://skalatan.de/blog/
Kamailio services – https://gilawa.com
*From:* Calvin E. calvine@gmail.com *Sent:* Donnerstag, 8. Juni 2023 19:36 *To:* Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org *Subject:* [SR-Users] Dialog DMQ state after restart
Does the dialog module do anything similar to the htable dmq_init_sync behavior?
The scenario is restarting the offline member of an HA pair after modifying the script. We're unsure of the state of the replicated dialogs post-restart. Will the standby become aware of the dialogs prior to the restart? In other words, do we need to wait until the pre-restart calls end before we can safely failover?
-Calvin E.
Hi Calvin,
Iam not using dmq but there are different aspects.
First what you assume it should do. Second what the module documentation described and last what in reality happens.
Did you try it in a test setup with your config and if it is "broken" in your opinion, you can then fill an issue for the devs with an minimal setup description and how to recreate the issue.
That would I do.
Kind regards Karsten Horsmann
Calvin E. calvine@gmail.com schrieb am Fr., 9. Juni 2023, 21:33:
The question is whether that DMQ synchronization for dialog data is sending all dialogs or only delta/incremental data. Some SBCs I've worked with only synchronize new dialog data, leaving standby nodes only aware of dialogs established since restarting or joining the cluster, not existing dialogs. In that circumstance, a failover to the restarted or new standby would break any dialogs created prior to the restart.
If Kamailio dialog DMQ synchronization is "complete" then we just need to know how to confirm the new standby is synchronized before performing a failover.
On Thu, Jun 8, 2023 at 12:53 PM Henning Westerholt hw@gilawa.com wrote:
Hello,
are you aware of the DMQ synchronisation for dialog data? It’s not replicated everything, but certainly a way to seed the dialog information after a restart.
Another way is of course the usual shared database, just keep in mind that you need to configure the dialog module (hash table “step” variables”) to properly work.
Cheers,
Henning
--
Henning Westerholt – https://skalatan.de/blog/
Kamailio services – https://gilawa.com
*From:* Calvin E. calvine@gmail.com *Sent:* Donnerstag, 8. Juni 2023 19:36 *To:* Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org *Subject:* [SR-Users] Dialog DMQ state after restart
Does the dialog module do anything similar to the htable dmq_init_sync behavior?
The scenario is restarting the offline member of an HA pair after modifying the script. We're unsure of the state of the replicated dialogs post-restart. Will the standby become aware of the dialogs prior to the restart? In other words, do we need to wait until the pre-restart calls end before we can safely failover?
-Calvin E.
Kamailio - Users Mailing List - Non Commercial Discussions To unsubscribe send an email to sr-users-leave@lists.kamailio.org Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe:
-
Alex Balashov -
Benoît Panizzon -
Calvin E. -
Henning Westerholt -
Karsten Horsmann