[asterisk-ha-clustering] Load sharing between two asterisk servers
Allan Cassaro
allan.cassaro at gmail.com
Wed Jan 16 12:55:53 CST 2008
On Jan 16, 2008 3:08 PM, Ricardo Carvalho <rjcarvalho at gmail.com> wrote:
> In my opinion there is some disadvantages with both solutions:
>
> - the one of replicating the AstDB with rsync may have the disadvantage of
> not having the registration information about those phones that may
> re-register in the time interval between the last rsync and the crash
> responsible for the second machine to assume production. Anyway I think I
> can live with that :)
>
> - the solution of using MySQL instead of AstDB I think may be too much
> effort driven for the servers since that for every call, asterisk has to
> access the MySQL DB. As far as I know, AstDB is much faster.
>
> I think that the best solution would be to use some kind of MASTER/MASTER
> replication with AstDB. Isn't it possible with DRDB or some other way?
>
> Regards,
> Ricardo Carvalho.
Well, sorry, but sync astdb is **really** necessary!?
IMHO it's perfecly possible to use asterisk in HA without this with
DUNDi and MySQL.
Maybe we has different approach of asterisk HA cluster.
Here, I do this:
All clients are "locked" in one server - one client per server - until
the server dies.
The "load balance" is really a "client balance".
Ex.: If I have 500 clients, 250 will go to server A and 250 to server
B, and this users will be "locked" into this servers.
With this, clients doesn't change of server on every call. Yes, this
is not a "load balance", but I can divide users into servers.
Regards.
More information about the asterisk-ha-clustering
mailing list