From owner-freebsd-current@FreeBSD.ORG Tue Feb 3 13:22:22 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6EB3916A4CE for ; Tue, 3 Feb 2004 13:22:22 -0800 (PST) Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4E62343D3F for ; Tue, 3 Feb 2004 13:22:21 -0800 (PST) (envelope-from eischen@vigrid.com) Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4]) by mail.pcnet.com (8.12.10/8.12.1) with ESMTP id i13LMJiw023240; Tue, 3 Feb 2004 16:22:19 -0500 (EST) Date: Tue, 3 Feb 2004 16:22:19 -0500 (EST) From: Daniel Eischen X-Sender: eischen@pcnet5.pcnet.com To: Sven Willenberger In-Reply-To: <1075842770.23952.15.camel@lanshark.dmv.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-current@freebsd.org Subject: Re: MySQL with KSE -- Unstable? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Feb 2004 21:22:22 -0000 On Tue, 3 Feb 2004, Sven Willenberger wrote: > On Tue, 2004-02-03 at 14:34, Kris Gale wrote: > > I've given MySQL on KSE a couple of tries in production, and I've > > run into a problem where threads seem to build up after an hour > > or so, depending on load. > > > > > Any ideas? Has anyone else had success with MySQL on 5.2 > > with KSE in high-load environments? > > > > Kris Gale > > Ran into a similar situation when I used libmap.conf to use libkse for > apache and mpm worker model. Following the manpage example, I set > default threads to use libthr instead of libc_r. Running a fairly hi > load web/mysql server, I ended up with with the error "unable to create > new threads" and and had to kill the mysql server. It seems that mysql > is partial to libc_r rather than libkse or libthr(?) as changing the > libmap entry back to libc_r for default cured the mysql woes. That sounds like mysql doesn't clean up its threads properly or there is something wrong in both libpthread and libthr in that regard. Perhaps mysql knows a little too much about how libc_r works and this causes problems for the other two thread libraries... -- Dan