Re: Using *RT for HA purposes was: [Asterisk-Users] Realtime Multiple Asterisk boxes, iaxusers
Mike Fedyk wrote: I was thinking of taking over the table when the other server fails and releasing once it is back up. What do you think? Sure, that would work. ___ --Bandwidth and Colocation provided by Easynews.com -- Asterisk-Users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: Using *RT for HA purposes was: [Asterisk-Users] Realtime Multiple Asterisk boxes, iaxusers
Kevin P. Fleming wrote: Mike Fedyk wrote: Can the various *RT servers be configured to use different tables so there won't be any conflicts even if there is any client overlap between the servers? Yes, but I'm not sure how you'd manage failover in that situation then. I was thinking of taking over the table when the other server fails and releasing once it is back up. What do you think? ___ --Bandwidth and Colocation provided by Easynews.com -- Asterisk-Users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: Using *RT for HA purposes was: [Asterisk-Users] Realtime Multiple Asterisk boxes, iaxusers
Mike Fedyk wrote: Can the various *RT servers be configured to use different tables so there won't be any conflicts even if there is any client overlap between the servers? Yes, but I'm not sure how you'd manage failover in that situation then. What I'm thinking of in this instance is active/active failover. Example: The HA system detects a peer has failed, fences it and then instructs asterisk to take over the registrations in table X that the failed peer was using. There is not currently any way to accomplish that, unless you do it in the database itself. If your database supports updatable views, then each server could actually be connected to a view that provided only the desired rows out of the master table, and the failover process could rebuild the view for the new 'active' server. It'd be a bit ugly, but not horrible. ___ --Bandwidth and Colocation provided by Easynews.com -- Asterisk-Users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: Using *RT for HA purposes was: [Asterisk-Users] Realtime Multiple Asterisk boxes, iaxusers
Kevin P. Fleming wrote: If the two servers service distinctly separate groups of endpoints, they can share the same table since they won't care about the other server's entries. If the two servers service the same endpoints but in an active/passive arrangement, that would also work. Can the various *RT servers be configured to use different tables so there won't be any conflicts even if there is any client overlap between the servers? What I'm thinking of in this instance is active/active failover. Example: The HA system detects a peer has failed, fences it and then instructs asterisk to take over the registrations in table X that the failed peer was using. How close is this example to reality with *RT? ___ --Bandwidth and Colocation provided by Easynews.com -- Asterisk-Users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: Using *RT for HA purposes was: [Asterisk-Users] Realtime Multiple Asterisk boxes, iaxusers
> > With the current *RT release? > > Yes. The crux of the issue that you can't have two servers responsible > for updating the same records in the table, and that you can't have two > servers both expected to react to changes in those records on an > instantaneous basis (which is why you can't share the table across two > active servers and expect both of them to be aware of where the peers are). > > If the two servers service distinctly separate groups of endpoints, they > can share the same table since they won't care about the other server's > entries. If the two servers service the same endpoints but in an > active/passive arrangement, that would also work. The second paragraph is what I was basically referring to when I mentioned removing the word 'dynamic'. I kind of sensed some of the discussion was relative to simply sharing a database (without having two dynamic & active * servers), others kind of referring to multihost load-sharing, and then your comment about dynamic registration for a device (iax client). More/less a human communications issue as to what the OP might have been referring to. Rich ___ --Bandwidth and Colocation provided by Easynews.com -- Asterisk-Users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: Using *RT for HA purposes was: [Asterisk-Users] Realtime Multiple Asterisk boxes, iaxusers
Mike Fedyk wrote: With the current *RT release? Yes. The crux of the issue that you can't have two servers responsible for updating the same records in the table, and that you can't have two servers both expected to react to changes in those records on an instantaneous basis (which is why you can't share the table across two active servers and expect both of them to be aware of where the peers are). If the two servers service distinctly separate groups of endpoints, they can share the same table since they won't care about the other server's entries. If the two servers service the same endpoints but in an active/passive arrangement, that would also work. ___ --Bandwidth and Colocation provided by Easynews.com -- Asterisk-Users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: Using *RT for HA purposes was: [Asterisk-Users] Realtime Multiple Asterisk boxes, iaxusers
Kevin P. Fleming wrote: Mike Fedyk wrote: Think of this scenario: You have two * RT servers running heartbeat and one goes down. If the SIP registration information was kept in the DB tables, the backup server could take over the ethernet and IP addresses and continue without forcing the phones to re-register. Yes, that could work just as you described. With the current *RT release? ___ --Bandwidth and Colocation provided by Easynews.com -- Asterisk-Users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: Using *RT for HA purposes was: [Asterisk-Users] Realtime Multiple Asterisk boxes, iaxusers
Mike Fedyk wrote: Think of this scenario: You have two * RT servers running heartbeat and one goes down. If the SIP registration information was kept in the DB tables, the backup server could take over the ethernet and IP addresses and continue without forcing the phones to re-register. Yes, that could work just as you described. ___ --Bandwidth and Colocation provided by Easynews.com -- Asterisk-Users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
