Memory limit issue with 64 bit mysql.3.23.46
We are running an extremely large instance of mysql version 3.23.46 on Solaris 2.8. We are attempting to use a software version compiled 64 bit and have been experiencing memory related server crashes. The behavior suggests that we are still unable to use more than 4G of memory. If the server is started with the following settings: key_buffer=4608M max_allowed_packet=1M table_cache=1024 record_buffer=1M sort_buffer=1M thread_cache=12 thread_concurrency=12 myisam_sort_buffer_size=512M We observe the following symptoms / problems: (1) A mysqladmin variables call shows that the key_buffer is set to be 1 G, not 4.5G. (2) Under any sort of database load, the server crashes with the following error output: mysql got signal 10; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware. We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail. key_buffer_size=4831834112 record_buffer=1044480 sort_buffer=1048568 max_used_connections=0 max_connections=512 threads_connected=1 It is possible that mysqld could use up to key_buffer_size + (record_buffer + sort_buffer)*max_connections = 5765112 K bytes of memory Hope that's okay, if not, decrease some variables in the equation. If the server is started with more modest settings (e.g., key_buffer_size=2G), mysql operates correctly. Additionally, mysqladmin variables shows a correct key_buffer value. System memory is not a constraint ( 6 G real memory and 14.5 G swap). - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Memory limit issue with mysql.3.23.41
We are running an extremely large instance of mysql version 3.23.41 on Solaris 2.8 and have been experiencing memory related server crashes. The behavior suggests that we are running out of memory / swap, but we have over 2 gig of memory and 10 gig of swap free. Our server settings are: key_buffer=5120M max_allowed_packet=1M table_cache=1024 sort_buffer=6M record_buffer=4M thread_cache=12 thread_concurrency=12 myisam_sort_buffer_size=512M The server tends to crash upon reaching a total memory usage of around 4 GB Here is the output from the error log. Of particular interest to us is the negative key_buffer_size quoted. The same value (-4096) appears with each crash. Is there some sort of memory limit imposed on the server or do you have suggestions for debugging this problem? Thank you, Kevin Franklin 020117 18:19:58 Out of memory; Check if mysqld or some other process uses all available memory. If not you may have to use 'ulimit' to allow mysqld to use more memory or you can add more swap space 020117 18:19:58 Out of memory; Check if mysqld or some other process uses all available memory. If not you may have to use 'ulimit' to allow mysqld to use more memory or you can add more swap space mysqld got signal 11; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked agaist is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware. We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail key_buffer_size=-4096 record_buffer=4190208 sort_buffer=6291448 max_used_connections=308 max_connections=1024 threads_connected=309 It is possible that mysqld could use up to key_buffer_size + (record_buffer + sort_buffer)*max_connections = 2093044 K bytes of memory Hope that's ok, if not, decrease some variables in the equation 020117 18:19:58 Out of memory; Check if mysqld or some other process uses all available memory. If not you may have to use 'ulimit' to allow mysqld to use more memory or you can add more swap space 020117 18:19:58 Out of memory; Check if mysqld or some other process uses all available memory. If not you may have to use 'ulimit' to allow mysqld to use more memory or you can add more swap space 020117 18:20:00 mysqld restarted - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
REPLICATION BUG
From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: REPLICATION BUG Description: The bug manifests itself in the following situation. A temporary table has been created on the master server. A query is executed using an alias for that temporary table. The connection is dropped without explicitly dropping that temporary table. In the binary log, mysql records a drop of the temporary table using the table alias. When the replication server reads this command, it is unaware of a table of this name and replication is dropped. How-To-Repeat: # Perl code sample #!/usr/local/bin/perl5 -w use DBI; my $dbh = DBI-connect(DBI:mysql:DBNAME:DBHOST:DBPORT, User, Password); $dbh-do(CREATE TEMPORARY TABLE tmpTableBug(tempField int not null)); $dbh-do(SELECT TableAlias.tempField FROM tmpTableBug AS TableAlias); $dbh-do(CREATE TEMPORARY TABLE tmpTableOk(tempField int not null)); $dbh-do(SELECT tempField FROM tmpTableOk); $dbh-disconnect; # Server will log drop table APES.tmpTableOk,APES.TableAlias; Fix: Explicitly drop temporary table Submitter-Id: Originator: Organization: MySQL support: none Synopsis: TEMPORARY TABLE DROP causes disconnect of replication slave. Severity: serious Priority: medium Category: mysql Class: sw-bug Release: mysql-3.23.41 (Source distribution) Environment: System: SunOS flotsam 5.8 Generic_108528-08 sun4u sparc SUNW,Ultra-4 Architecture: sun4 Some paths: /bin/perl /usr/local/bin/make /usr/local/bin/gcc /opt/SUNWspro.5.0/SC5.0/bin/cc GCC: Reading specs from /usr/local/gcc-2.95.2-sl/lib/gcc-lib/sparc-sun-solaris2.6/2.95.2/specs gcc version 2.95.2 19991024 (release) Compilation info: CC='/usr/local/gcc-2.95.2-sl/bin/gcc -R/usr/local/gcc-2.95.2-sl/lib' CFLAGS='' CXX='/usr/local/gcc-2.95.2-sl/bin/g++ -R/usr/local/gcc-2.95.2-sl/lib' CXXFLAGS='' LDFLAGS='' LIBC: -rw-r--r-- 1 root bin 1759264 Jun 29 2001 /lib/libc.a lrwxrwxrwx 1 root root 11 Aug 22 20:13 /lib/libc.so - ./libc.so.1 -rwxr-xr-x 1 root bin 1136692 Jun 29 2001 /lib/libc.so.1 -rw-r--r-- 1 root bin 1759264 Jun 29 2001 /usr/lib/libc.a lrwxrwxrwx 1 root root 11 Aug 22 20:13 /usr/lib/libc.so - ./libc.so.1 -rwxr-xr-x 1 root bin 1136692 Jun 29 2001 /usr/lib/libc.so.1 Configure command: ./configure --prefix=/unique/apps/mysql-3.23.41 --with-innodb --without-docs Perl: This is perl, version 5.005_03 built for sun4-solaris - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
