[Freeswitch-users] Live Upgrade Techniques

[John Dalgliesh]

I assume he's talking about hardware failures here :P

But to answer the question: crashes are easy to deal with. With a crash 
you have lost the calls that are in progress anyway; you don't have to 
manage a gradual transition.

Currently, since FS is quite quick to start up, I am just relaunching it 
immediately.

But when I have a second box up and running what I'll do is just add the 
IP of the dead machine as another IP of the second box, and then it will 
take all the old machine's traffic. That is the plan anyway. I've seen 
some commercial boxes that use a similar trick.

(I've only seen one crash that wasn't my fault. Something to do with 
terminating a bridge: when the first leg gets a hangup it hangs up the 
other leg on its own thread... which can cause problems if the other leg 
was doing something funky at the time. Leads to a heap corruption. Doesn't 
happen with MALLOC_CHECK_ set so I'm just leaving it set for now :)

{P^/

On Thu, 11 Jun 2009 at 00:41 -0400, Mathieu Rene wrote:
>
> By reporting it on Jira so it doesn't crash anymore :D
>
>
> On 11-Jun-09, at 12:04 AM, Michael Giagnocavo wrote:
>
>> How are you handling your FS box crashing?
>>
>> -----Original Message-----
>> From: freeswitch-users-bounces at lists.freeswitch.org [mailto:freeswitch-users-bounces at lists.freeswitch.org
>> ] On Behalf Of John Dalgliesh
>> Sent: Wednesday, June 10, 2009 9:04 PM
>> To: freeswitch-users at lists.freeswitch.org
>> Subject: [Freeswitch-users] Live Upgrade Techniques
>>
>>
>> Hi,
>>
>> I am slowly gaining confidence using FreeSWITCH in production, but
>> there
>> is one issue that I'm still wondering about: how are people upgrading
>> their FreeSWITCH installation binaries without dropping all current
>> calls?
>>
>> So far I have been upgrading in the dead of night, after pausing for 5
>> minutes then dropping the stragglers, but this is hardly ideal.
>>
>> What I would like to do is to run an upgraded instance of FreeSWITCH
>> on
>> the same machine, and have it handle all new call packets, whereas
>> the old
>> instance continues to handle the existing call packets, until there
>> are no
>> more old calls left.
>>
>> I can think of about seven ways to accomplish this, but before I
>> dive into
>> the code I thought I'd better ask what everyone else has been doing :)
>>
>> (The only standard way I can think of doing this is to have a SIP
>> proxy
>> sitting in front of FS the whole time, just to handle these upgrade
>> windows. It seems like a bit of a waste.)
>>
>> So how are you handling your FS software upgrades?
>>
>> {P^/
>> John
>>
>> _______________________________________________
>> Freeswitch-users mailing list
>> Freeswitch-users at lists.freeswitch.org
>> http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
>> UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
>> http://www.freeswitch.org
>>
>> _______________________________________________
>> Freeswitch-users mailing list
>> Freeswitch-users at lists.freeswitch.org
>> http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
>> UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
>> http://www.freeswitch.org
>
>
> _______________________________________________
> Freeswitch-users mailing list
> Freeswitch-users at lists.freeswitch.org
> http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
> UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
> http://www.freeswitch.org
>