[Serusers] ser mysql/cache sync

Chris St Denis chris at aebc.com
Mon Jul 11 21:38:04 CEST 2005


I wrote a patch to ser 8.14 that both writes back and reads back the
database on a timer with a mode 4 setting to userloc. This may do what you
need.

http://bugs.sip-router.org/browse/SER-46

-----Original Message-----
From: serusers-bounces at iptel.org [mailto:serusers-bounces at lists.iptel.org]On
Behalf Of Jack Wei
Sent: Sunday, July 10, 2005 2:34 PM
To: Greger V. Teigre; serusers at lists.iptel.org
Subject: Re: [Serusers] ser mysql/cache sync


Greger,

Thanks for the help.  Do you know if a patch is readily available?  I am
currently using Ultra Monkey.

Jack

--- "Greger V. Teigre" <greger at teigre.com> wrote:

> Jack Wei wrote:
> > i am running a cluster with 2 sers.  i start the 1st ser and several
> > users registers.  the users show up in both the cache and the mysql
> > db.  then i start the 2nd ser, and it loads the db into the cache.
> > when the cache entries in the 2nd server times out, the entries are
> > deleted from the db.  however, when the users registers in the 1st
> > ser, they aren't entered into the db.  how do i fix this problem?
> >
> > the db_mode is set to "2" w/ timer_interval at "10".  i've even tried
> > setting the db_mode to "1", but that didn't help.
>
> Write-through DB mode will write all usrloc changes to the DB. However,
all
> locations are cached in ser memory. This means that there is no way a
> secondary ser can reload a location from DB. If a location is not found in
> memory, it is assumed not there.  A new caching approach has been
discussed
> previously on this list (or was it serdev?).
>
> You can do the following:
> - Use write-through DB mode to the shared SQL DB
> - Use t_replicate to the secondary ser
> - On the secondary ser, call save_memory() instead of save() (as the
> location has already been saved in DB)
>
> This only works for deployment scenarios where EUCs are not NATed.  The
> reason is that the secondary ser will have another public IP address than
> the primary and restricted NATs will not accept incoming packets from
other
> IPs than the one the EUC has registered to.
>
> The way to solve this is to either route all INVITEs coming to the
secondary
> through the primary (ex. using Path) or to set up LVS (or similar) where
> both SERs have the same IP address.  However, currently LVS does not do
> Call-id based load balancing and people who report this scenario have
> patched LVS or use a commercial load balancing solution.
>
> g-)
>
>


Jack Wei

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around
http://mail.yahoo.com

_______________________________________________
Serusers mailing list
serusers at lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers




More information about the sr-users mailing list