If you use HAPort, it'll use that to determine the backend is down. When a backend is dead, all sessions connected to that backend will be immediately terminated.
Use poundctl to disable the backend. Sessions attached to the backend will continue to be sent there until the session expires. But no new sessions will be sent to that backend. Then re-enable the backend when you're done. Joe > -----Original Message----- > From: Galen Charlton [mailto:[email protected]] > Sent: Thursday, June 21, 2012 1:17 PM > To: Neil Skrypuch > Cc: [email protected] > Subject: Re: [Pound Mailing List] General question regarding handling > dead backends > > Hi, > > On Jun 21, 2012, at 1:14 PM, Neil Skrypuch wrote: > > Yes, specify a HAPort for the backend, which will be used for health > checks. > > If the HAPort stops responding, the service should be gracefully > > pulled out of the pool and then you can shut down the regular > service. > > Thanks much -- I suspected that this might be the case, but having > confirmation definitely helps. > > Regards, > > Galen > -- > Galen Charlton > Director of Support and Implementation > Equinox Software, Inc. / The Open Source Experts > email: [email protected] > direct: +1 770-709-5581 > cell: +1 404-984-4366 > skype: gmcharlt > web: http://www.esilibrary.com/ > Supporting Koha and Evergreen: http://koha-community.org & > http://evergreen-ils.org > > > -- > To unsubscribe send an email with subject unsubscribe to > [email protected]. > Please contact [email protected] for questions. -- To unsubscribe send an email with subject unsubscribe to [email protected]. Please contact [email protected] for questions.
