26 Dec
2018
26 Dec
'18
4:50 p.m.
There are many situations that can block a proxy, including writing to
syslog, dns and DB queries,... At the end you cannot rely on a single app
to have a smooth runtime, the ecosystem has to be also in good parameters.
The current implementation is like this now, the choice of developer. You
can improve it if you want, or use the old no-db mode. My patch ensured
that the old mode work as it was before adding db support. That was a
regression. But what is offered with db support, is what the developer
added, and apparently he did it for all instances to be available at that
moment. Maybe a note about that can be added in the docs.
Otherwise similar case can be that sqlops (or db_cluster, not sure by
heart) didn't start without all db servers available. Recently someone
proposed a patch to allow sqlops even when connection fails. We had
blocking tcp for years, it was not disabled because of that. So things can
be improved as one needs something different, it is open source...
Cheers,
Daniel
On Wed, 26 Dec 2018, 14:04 Juha Heinanen <jh(a)tutpro.com wrote:
Daniel-Constantin Mierla writes:
You can make a fix yourself if you want and have
the time. It is not a
module I coded, nor the one that added db support for it, so I am also
coding by learning what was done there.
Understand. Perhaps the solution for now is to disable db mode in the
code, since it is not a good idea to allow modules in K that freeze the
whole sip proxy.
-- Juha