26 Feb
2004
26 Feb
'04
10:59 p.m.
On Thursday 26 February 2004 22:40, Arnd Vehling wrote:
Nils Ohlmeier wrote:
INVITE and subscriber table???
You can for example call for every valid REGISTER request t_replicate. If the
destination box is up and running it will then update its databases (in
memory and the DB backend, so beware of additional DB replication). But if
the secondary is down (e.g. for maintenance) it will miss the update.
Yes, comitted. But the replicated data will not
be read in by the backup
server.
Mhh, seems like i didnt really understood what t_replicate does.
I thought "t_replicate" will replicate all invites to a failover box
so the primary and secondary are synced in terms of subscribed
users?! So, if the primary box fails it the secondary should
will have an (maybe
minus ore or two records) identical database and an identical subscriber
base?!
Two choices:
- either use DB replication and restart SER on failover to re-readin the
location table on startup
- t_replicate all successfull REGISTER and omit DB replication, but beware of
the possible drawbacks.
NO
Mode=1 only means that the server writes it
immediately to the
database. But there is currently no mode available in which contact data
is read from the database for every lookup.
I thought t_replicate will do this. But if not i either restart ser as
suggested or patch it so it will re-read the subsriber table if i send
it a SIGHUP or a something via the fifo.