distributed database

[Ryan Williams]

I'm looking at implementing freeradius w/MySQL for auth & accounting with a
single master database and multiple (initially two) radius servers (slaves).

 

The idea is that the slaves will run freeradius and the master will be
integrated with the billing system.
The slaves can download an exact copy of the masters radcheck & radreply
tables at frequent intervals. - That bit is easy.

 

The difficulty arises when trying to run a distributed session table and
also trying to implement some sort of replication so the slaves can push
their radacct table back up to the master while avoiding PK conflicts.

 

I'm considering one of the two solutions

1) Make the ID column in both the session table and radacct a NEWID / GUID /
statistical key

or 

2) Add a SlaveID int column to both tables and use a joint ID,SlaveID
Primary Key.

 

Does anyone have any experience with either or does anyone have any thoughts
on the matter?

 


Regards,


Ryan Williams

 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freeradius.org/pipermail/freeradius-users/attachments/20110914/fe4dc3f6/attachment.html>