19 Feb
2012
19 Feb
'12
11:41 p.m.
Hello,
what you can do is to save only in memory (see flag parameter for save
function) and replicate the register requests to a node that writes to
the master database. There will be probably errors after startup, when
loaded records will expire (if they are not updated), but after that it
should stay clean.
I have discussed with some people that were looking at something
similar, so a new db mode may be contributed soon to do read from db at
startup and then no updates back to db -- there should be another node
taking care of storing in db.
Cheers,
Daniel
On 2/18/12 5:11 AM, Spencer Thomason wrote:
Hello,
I'm currently working on a HA setup with geographically separated
proxies. Each proxy is in a different data center with an MPLS link
between them. The proxies access a locally connected PostgreSQL
database that is replicated from a master in the primary data center.
Note that the replicated dbs are read only. Everything works great for
read only queries but registrations seem to pose a problem as they
must use the primary db directly to deal with the writes. If I set
userloc to db mode 2 the secondary proxies wipe out the entries in the
database. If I use db mode 3 everything works great but all of the
secondary proxies must use the primary database directly and a network
link failure will cause a service disruption. Is there any way I can
use separate read and write databases without p_userloc? Is there a
better way to replicate registrations maintaining availability and
scalability? And advice is appreciated.
Thanks,
Spencer
/Connected by DROID on Verizon Wireless/
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
--
Daniel-Constantin Mierla -- http://www.asipto.com
http://linkedin.com/in/miconda -- http://twitter.com/miconda