<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix"><tt>Hi Tito,<br>
<br>
In my case I'm using one for the modules (for the nosql part),
like mongodb, redis, couchebase, etc. The advantages of those
nosql engines are that you have an out-of-the-box
geo-distributed db cluster; there is no need to try to replicate
something like that via sql + http + other. At least that's my
opinion :).<br>
<br>
Regards,<br>
</tt>
<pre class="moz-signature" cols="72">Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
<a class="moz-txt-link-freetext" href="http://www.opensips-solutions.com">http://www.opensips-solutions.com</a></pre>
On 03.07.2014 23:00, Tito Cumpen wrote:<br>
</div>
<blockquote
cite="mid:CANZPVB4r8EK-45-EzFUrZoUUO-_y01=kc3MwfwYJYon4Jx+XCA@mail.gmail.com"
type="cite">
<div dir="ltr">Bogdan,
<div><br>
</div>
<div><br>
</div>
<div>Thanks for sharing. I was hoping to do something similar
with http_db and sql by treating new posts with php and
replicating them on a remote mysql db which will then be
queried for location type requests. In your solution are
employing DB_Cache module? Also are you using a queuing
solution for events?</div>
<div><br>
</div>
<div><br>
</div>
<div>Thanks,</div>
<div>Tito</div>
</div>
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">On Wed, Jun 25, 2014 at 5:38 AM,
Bogdan-Andrei Iancu <span dir="ltr"><<a
moz-do-not-send="true" href="mailto:bogdan@opensips.org"
target="_blank">bogdan@opensips.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
<div><tt>Hi Tito,<br>
<br>
What I do for clustering usrloc is something like
this:<br>
- each node manages the registrations
independently (there is no usrloc replication between
nodes)<br>
- I have a nosql cluster available for all nodes<br>
- I use the AOR related events+routes to
push/remove into the nosql db the AOR (only) available
on each node<br>
- basically the nosql "knows" which AORs are
registered on which node<br>
- when a node handles a call, it looks into nosql
to see which are the nodes having registrations for
the needed AOR -> call is parallel forked to local
registrations (if any) and to the other nodes (based
on nosql info)<br>
<br>
Regards,<br>
</tt>
<pre cols="72">Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
<a moz-do-not-send="true" href="http://www.opensips-solutions.com" target="_blank">http://www.opensips-solutions.com</a></pre>
<div>
<div class="h5"> On <a moz-do-not-send="true"
href="tel:24.06.2014%2015" value="+12406201415"
target="_blank">24.06.2014 15</a>:27, Tito Cumpen
wrote:<br>
</div>
</div>
</div>
<div>
<div class="h5">
<blockquote type="cite">
<div dir="ltr">Rik,
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div>My deployment is not dependant on virtual IP.
Since the failover and load balancing logic
resides on the client and I intend to use srv
records to define the weight of proxies. The
problem comes to surface if a user makes an
attempt to register and finds himself on server
A. Soon after makes an attempt to register and
finds the second client on server b. If a Ruri
request sources from server B how can I fork the
request in parallel to the first entry in server
A?</div>
<div>Thanks for your reply but I have raised the
question of using contact replication before
please see below:<br>
</div>
<div><br>
</div>
<div><br>
<br>
<div class="gmail_quote">---------- Forwarded
message ----------<br>
From: <b class="gmail_sendername">Liviu Chircu</b> <span
dir="ltr"><<a moz-do-not-send="true"
href="mailto:liviu@opensips.org"
target="_blank">liviu@opensips.org</a>></span><br>
Date: Wed, Jun 11, 2014 at 1:29 PM<br>
Subject: Re: [OpenSIPS-Users] binary
replication<br>
To: <a moz-do-not-send="true"
href="mailto:users@lists.opensips.org"
target="_blank">users@lists.opensips.org</a><br>
<br>
<br>
<div text="#000000" bgcolor="#FFFFFF">
<div><tt>Hello Tito,<br>
<br>
Both dialog and user location
replication were actually designed to
work with VIPs only! From the moment the
"receiving" instance takes over, it
should have the same pool of registered
users as instance #1, and it should be
able to process all existing dialogues.<br>
<br>
Best regards,<br>
</tt>
<pre cols="72">Liviu Chircu
OpenSIPS Developer
<a moz-do-not-send="true" href="http://www.opensips-solutions.com/" target="_blank">http://www.opensips-solutions.com</a></pre>
<div>
<div>On 06/11/2014 03:27 PM, Tito Cumpen
wrote:<br>
</div>
</div>
</div>
<blockquote type="cite">
<div>
<div>
<div dir="ltr">Group,
<div><br>
</div>
<div>Playing with the idea of using
binary replication. Just curious
if anyone can provide a use case.
Would this coupled with a virtual
ip? I am not certain how the
instance that accepts replications
would take over.</div>
<div><br>
</div>
<div><br>
</div>
<div>Thanks,</div>
<div>Tito</div>
</div>
<br>
<fieldset></fieldset>
<br>
</div>
</div>
<pre>_______________________________________________
Users mailing list
<a moz-do-not-send="true" href="mailto:Users@lists.opensips.org" target="_blank">Users@lists.opensips.org</a>
<a moz-do-not-send="true" href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a>
</pre>
</blockquote>
<br>
</div>
<br>
_______________________________________________<br>
Users mailing list<br>
<a moz-do-not-send="true"
href="mailto:Users@lists.opensips.org"
target="_blank">Users@lists.opensips.org</a><br>
<a moz-do-not-send="true"
href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users"
target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a></div>
</div>
</div>
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">On Tue, Jun 24, 2014 at
5:35 AM, Rik Broers <span dir="ltr"><<a
moz-do-not-send="true"
href="mailto:RBroers@motto.nl"
target="_blank">RBroers@motto.nl</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0
0 0 .8ex;border-left:1px #ccc
solid;padding-left:1ex">
<div link="#0563C1" vlink="#954F72" lang="NL">
<div>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif"">I’m
was also looking into this problem,
which is very similar to yours.</span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif""> </span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif"">I
found this and it is a perfect
solution to my problem.</span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif"">Think
this would help you too.</span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif""> </span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif""><a
moz-do-not-send="true"
href="http://www.opensips.org/html/docs/modules/devel/usrloc#usrloc-replication"
target="_blank">http://www.opensips.org/html/docs/modules/devel/usrloc#usrloc-replication</a></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif""> </span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif""> </span></p>
<p class="MsoNormal"
style="margin-bottom:12.0pt;line-height:12.75pt"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif"">Vriendelijke
groet,<br>
<br>
<b><span style="color:#84c41b">Rik
Broers</span></b><br>
</span><span
style="font-size:9.0pt;font-family:"Calibri","sans-serif";color:#212735">Voice
Engineer</span><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif""><br>
<br>
</span><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif""></span></p>
<p class="MsoNormal"><b><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif"">Van:</span></b><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif"">
<a moz-do-not-send="true"
href="mailto:users-bounces@lists.opensips.org"
target="_blank">users-bounces@lists.opensips.org</a>
[mailto:<a moz-do-not-send="true"
href="mailto:users-bounces@lists.opensips.org"
target="_blank">users-bounces@lists.opensips.org</a>]
<b>Namens </b>Tito Cumpen<br>
<b>Verzonden:</b> dinsdag 24 juni 2014
04:54<br>
<b>Aan:</b> OpenSIPS users mailling
list<br>
<b>Onderwerp:</b> [OpenSIPS-Users]
Distributed deployment</span></p>
<div>
<div>
<p class="MsoNormal"> </p>
<div>
<p class="MsoNormal">Hello group,</p>
<div>
<p class="MsoNormal"> </p>
</div>
<div>
<p class="MsoNormal"> </p>
</div>
<div>
<p class="MsoNormal">I am reaching
out to you because I am hitting
a roadblock in designing a
distributed deployment.
Currently I am entertaining the
idea of using DNS srv for the
sake of load balancing and
availability. The main problem
is sharing aors among the
proxies. My requirement is to
allow proxies to fork requests
to remote proxies in which a
user could be registered to in
addition to the local server.
The binary replication component
will not suffice because it is
tailored to virtual ip. I've
noticed that opensips has a
recursive timer that runs at
every second to verify which
registration expires with the
intent of removing it. Assuming
a shared mysql instance is the
only option each proxy will be
querying mysql which seems like
a ton of activity. Can anyone
advise what the best practice
for scaling would be?</p>
</div>
<div>
<p class="MsoNormal"> </p>
</div>
<div>
<p class="MsoNormal"> </p>
</div>
<div>
<p class="MsoNormal">Thanks,</p>
</div>
<div>
<p class="MsoNormal">Tito</p>
</div>
</div>
</div>
</div>
</div>
</div>
<br>
_______________________________________________<br>
Users mailing list<br>
<a moz-do-not-send="true"
href="mailto:Users@lists.opensips.org"
target="_blank">Users@lists.opensips.org</a><br>
<a moz-do-not-send="true"
href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users"
target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
<br>
</blockquote>
</div>
<br>
</div>
<br>
<fieldset></fieldset>
<br>
<pre>_______________________________________________
Users mailing list
<a moz-do-not-send="true" href="mailto:Users@lists.opensips.org" target="_blank">Users@lists.opensips.org</a>
<a moz-do-not-send="true" href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a>
</pre>
</blockquote>
<br>
</div>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</blockquote>
<br>
</body>
</html>