> > We recently started getting "Can't create thread" errors since > > switching to Debian. > > > > On Red Hat 8.0 we were able to spawn more than 400 mysql threads > > and never encountered this error. mysql 3.23.56 compiled from > > source, stock kernel. (2GB of RAM) > > > > Now we get it all the time on Debian and the MySQL AB 3.23.58 > > binary around 245 threads, linux 2.4.23 custom kernel. (3GB of RAM, > > not that it matters) > > > > Are we missing a setting? > > > > Does Red Hat have some kind of userland address space hack that > > we're not aware of? > > Do you have any special kernel config options that you did not use before?
Actually, we just found something interesting on the Debian box. # ps aux | grep mysqld [...] mysql 25303 0.4 30.4 1228720 947112 ? S 16:16 0:23 /usr/local/mysql/bin/mysqld --defaults-extra-file=/usr/local/mysql/data/my.cnf --basedir=/usr/local/mysql/ --datadir=/usr/local/mysql/data --user=mysql --pid-file=/usr/local/mysql/data/dbms3.pid --skip-locking [...] # tail /proc/25303/maps bee01000-bf000000 rwxp 00001000 00:00 0 bf000000-bf001000 ---p 00000000 00:00 0 bf001000-bf200000 rwxp 00001000 00:00 0 bf200000-bf201000 ---p 00000000 00:00 0 bf201000-bf400000 rwxp 00001000 00:00 0 bf400000-bf401000 ---p 00000000 00:00 0 bf401000-bf600000 rwxp 00001000 00:00 0 bf600000-bf601000 ---p 00000000 00:00 0 bf601000-bf800000 rwxp 00001000 00:00 0 bfffa000-c0000000 rwxp ffffb000 00:00 0 the thread stacks are 2MB apiece (bf601000-bf800000 is 2093056 bytes, or 2044kB)! Yet: # mysql -e 'show variables' | grep thread_stack thread_stack 196608 It seems like the setting does nothing for us. We top out at exactly 256 threads. -- Michael Bacarella 24/7 phone: 1-646-641-8662 Netgraft Corporation http://netgraft.com/ -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
