Return-Path: Delivered-To: apmail-jakarta-tomcat-dev-archive@apache.org Received: (qmail 19851 invoked from network); 6 May 2002 14:31:08 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 6 May 2002 14:31:08 -0000 Received: (qmail 25235 invoked by uid 97); 6 May 2002 14:31:03 -0000 Delivered-To: qmlist-jakarta-archive-tomcat-dev@jakarta.apache.org Received: (qmail 25218 invoked by uid 97); 6 May 2002 14:31:02 -0000 Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Tomcat Developers List" Reply-To: "Tomcat Developers List" Delivered-To: mailing list tomcat-dev@jakarta.apache.org Received: (qmail 28195 invoked by uid 98); 6 May 2002 13:59:26 -0000 X-Antivirus: nagoya (v4198 created Apr 24 2002) Date: Mon, 6 May 2002 15:59:20 +0200 Message-Id: <200205061359.g46DxKD02735@glop.federalservice.fr> X-Authentication-Warning: glop.federalservice.fr: herberts set sender to Mathias.Herberts@cmb.fr using -f From: Mathias.Herberts@iroise.net To: tomcat-dev@jakarta.apache.org, Mathias.Herberts@cmb.fr Subject: Load balancing worker in JK2 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Hi, to continue the discussion on load balancing workers in JK2, I would suggest as Bernd's initial patch did, to add two properties for the load balancing worker, one which will be the name of the local worker, and another one stating what to do if this local worker is unavailable. Three fields could be added to the worker structure, one which will hold the index of the local worker in the lb_workers array, another one holding the behavior to adopt in case the local worker is unavailable, and a third one holding the local worker name. jk2_lb_refresh needs to be modified to check if a local worker was specified and if this worker is indeed in the array lb_workers, if so the index of the local worker will be updated in the worker structure. A sanity check might also be done to ensure the local workers's lbfactor is set to 0 (even though I think we can have a default worker with a non zero lb_value since we know its index). In get_most_suitable worker, if no session route was specified, check that the local_worker is available, if not check what action to perform (either reject the request or load balance it normally on other workers). Only sessionless requests will therefore be unconditionnaly dispatched to the local worker, a request part of a session but whose worker has failed will be load balanced to another worker normally. This way we should be able to have HW load balancers in front of Apache/Tomcat and having them detect the failure of a local Tomcat thus declaring inactive the associated Apache. No specific value of lbfactor needs then to be specified. Mathias. -- -- Credit Mutuel de Bretagne -- DST / Reseaux et Systemes Distribues -- 32 rue Mirabeau -- Le Relecq-Kerhuon -- 29808 Brest Cedex 9, FRANCE -- Tel +33298004653 - Fax +33298284005 - Mail: Mathias.Herberts@cmb.fr -- Key Fingerprint: 8778 D2FD 3B4A 6B33 10AB F503 63D0 ADAE 9112 03E4 -- Ce message et toutes les pieces jointes (ci-apres le "message") sont confidentiels et etablis a l'intention exclusive de ses destinataires. Toute utilisation ou diffusion non autorisee est interdite. Tout message etant susceptible d'alteration, l'emetteur decline toute responsabilite au titre de ce message s'il a ete altere, deforme ou falsifie. ----------------------------------- This message and any attachments (the "message") are confidential and intended solely for the addressees. Any unauthorised use or dissemination is prohibited. As e-mails are susceptible to alteration, the issuer shall not be liable for the message if altered, changed or falsified. -- To unsubscribe, e-mail: For additional commands, e-mail: