Set your first set of servers to stop accepting new sessions a while in advance. As users end their sessions, that first block will eventually become unused, since they're not picking up any new sessions to replace the old ones. Once that happens (or gets to a sufficiently low number), kill them off. Do your upgrade, then repeat the process for the other half.
If you've designed your app right, the cost of having a mid-session server switch will be minimal, since anything that's really critical should be stored in the database, not in session variables. Still not desirable to do that, but if it happens to a few users, it shouldn't be a big deal. cheers, barneyb On 6/9/05, Douglas Knudsen <[EMAIL PROTECTED]> wrote: > How do you get zero down time doing this? We have sticky sessions on, so if > we take a member of the cluster down, we loose like 50% of my users forcing > them to relogin to the other member, in this case we have two memebers in > the cluster. > > DK -- Barney Boisvert [EMAIL PROTECTED] 360.319.6145 http://www.barneyb.com/ Got Gmail? I have 50 invites. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Find out how CFTicket can increase your company's customer support efficiency by 100% http://www.houseoffusion.com/banners/view.cfm?bannerid=49 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:209162 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
