Hi Bogdan, Yes it would appear K8s implementations would be a very good topic at the Summit that is for sure!
I understand your comments on dispatcher, its unfortunate as everything else is working fine. There was a suggestion to add a loopback address for example and then update when DNS has updated and records resolve? Is there any benefit in using dr_routing instead or will this behaviour be the same in the event of a dns lookup failure? Thanks for the response! Jon Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows From: Bogdan-Andrei Iancu<mailto:bog...@opensips.org> Sent: 24 August 2022 12:29 To: OpenSIPS users mailling list<mailto:users@lists.opensips.org>; Jonathan Hunter<mailto:hunter...@hotmail.com> Subject: Re: [OpenSIPS-Users] Dispatcher within a K8s environment Hi Jonathan, I guess this will be a good topic (DS and K8S) for the OpenSIPS Summit in Athens - I think this is the 3rd time in the last week coming across it :) Unfortunately there is no way to skip at the moment that DNS failure when loading the destinations :(....even more, there some code that relies on the fact that there is an "IP" attached to any destination.....And I just checked, a local error in sending the ping (like the DNS err) does not results in marking the destination as failed or so..... so it is not so straight as ignoring the DNS error. Best regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer https://www.opensips-solutions.com<https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.opensips-solutions.com%2F&data=05%7C01%7C%7C84ee92014c7c4c0ea33e08da85c3dd19%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637969373523562738%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=vMcA8Ti1ZgupioV7%2BV%2Fn6MxoklfjuxJ8BGcqWEWDHmE%3D&reserved=0> OpenSIPS Summit 27-30 Sept 2022, Athens https://www.opensips.org/events/Summit-2022Athens/<https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.opensips.org%2Fevents%2FSummit-2022Athens%2F&data=05%7C01%7C%7C84ee92014c7c4c0ea33e08da85c3dd19%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637969373523562738%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=9VF4udkoaGT%2FBFooWi8eyPaFOzq3c7yeYoxJDXgL5C4%3D&reserved=0> On 8/24/22 12:24 AM, Jonathan Hunter wrote: Hi All, I have a query around dispatcher behaviour, I am running 3.2 in a k8s environment. I have 2 freeswitch instances defined in a destination set, both of which are pods. As people may be aware its fun implementing in k8s as pods can restart and disappear at times so I ideally want this reflected in the cache and output of opensips-cli -x mi ds_list where I was hoping the freeswitch entries would be defined but with a state of probing or inactive. With my current setup, when restarting opensips for example, I have the dispatcher table populated in postgres db , and if opensips cant resolve the URI it wont load it into cache, like wise if opensips is running and freeswitch pod drops, I see this in the logs; Aug 23 21:22:01 [55] ERROR:dispatcher:add_dest2list: could not resolve freeswitch-opensips-deployment-1.freeswitch-opensips, skipping it Aug 23 21:22:01 [55] WARNING:dispatcher:ds_load_data: failed to add destination <sip:freeswitch-opensips-deployment-1.freeswitch-opensips:5070;transport=tcp><sip:freeswitch-opensips-deployment-1.freeswitch-opensips:5070;transport=tcp> in group 10 I therefore don’t see it listed in cache when I run ds_list. Does anyone know if its possible to tweak dispatcher to always load the database entries into cache at startup, and also set their status to probing/inactive if not reachable due to a resolving issue as above? My dispatcher settings are; #### Dynamic routing loadmodule "dispatcher.so" modparam("dispatcher", "db_url", "postgres://x.x.x.x/opensips") modparam("dispatcher", "ds_probing_mode", 1) modparam("dispatcher", "ds_probing_threshhold", 1) modparam("dispatcher", "persistent_state", 0) modparam("dispatcher", "ds_ping_interval", 5) modparam("dispatcher", "table_name", "dispatcher") modparam("dispatcher", "cluster_id", 1) Hope that makes sense! Many thanks Jon _______________________________________________ Users mailing list Users@lists.opensips.org<mailto:Users@lists.opensips.org> http://lists.opensips.org/cgi-bin/mailman/listinfo/users<https://nam12.safelinks.protection.outlook.com/?url=http%3A%2F%2Flists.opensips.org%2Fcgi-bin%2Fmailman%2Flistinfo%2Fusers&data=05%7C01%7C%7C84ee92014c7c4c0ea33e08da85c3dd19%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637969373523562738%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=Vx2tfVcw2FLjKQOd5KZAwKVEfBs04rTdHqR7VD05wJs%3D&reserved=0>
_______________________________________________ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
