OS: RedHat Enterprise ES 2.1 Current working InnoDB settings:
innodb_data_home_dir = /home/mysql innodb_data_file_path = ibdata1:20000M:autoextend innodb_log_group_home_dir = /home/mysql innodb_log_arch_dir = /home/mysql innodb_log_files_in_group=2 # You can set .._buffer_pool_size up to 50 - 80 % # of RAM but beware of setting memory usage too high innodb_buffer_pool_size = 512M innodb_additional_mem_pool_size = 20M # Set .._log_file_size to 25 % of buffer pool size innodb_log_file_size = 512M innodb_log_buffer_size = 8M innodb_flush_log_at_trx_commit = 0 innodb_lock_wait_timeout = 50 Error(using 2.5G RAM out of 4G total): 030924 15:39:55 mysqld started Warning: Ignoring user change to 'mysql' because the user was set to 'mysql' earlier on the command line InnoDB: Fatal error: cannot allocate 2684370944 bytes of InnoDB: memory with malloc! Total allocated memory InnoDB: by InnoDB 24482732 bytes. Operating system errno: 12 InnoDB: Cannot continue operation! InnoDB: Check if you should increase the swap file or InnoDB: ulimits of your operating system. InnoDB: On FreeBSD check you have compiled the OS with InnoDB: a big enough maximum process size. InnoDB: We now intentionally generate a seg fault so that InnoDB: on Linux we get a stack trace. 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 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=134217728 read_buffer_size=2093056 max_used_connections=0 max_connections=800 threads_connected=0 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 3404665 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. I talked with RedHat about any OS limitations, and they had me change the max shared to a suitable number, and still I am stuck at 512MB of RAM. Top output: 3:43pm up 23:24, 2 users, load average: 0.00, 0.00, 0.00 36 processes: 35 sleeping, 1 running, 0 zombie, 0 stopped CPU0 states: 0.0% user, 0.0% system, 0.0% nice, 100.0% idle CPU1 states: 0.0% user, 0.0% system, 0.0% nice, 100.0% idle CPU2 states: 0.0% user, 0.0% system, 0.0% nice, 100.0% idle CPU3 states: 0.0% user, 0.0% system, 0.0% nice, 100.0% idle Mem: 3943852K av, 165796K used, 3778056K free, 0K shrd, 40760K buff Swap: 2044072K av, 0K used, 2044072K free 48972K cached -----Original Message----- From: Jeremy Zawodny [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 24, 2003 3:28 PM To: Misaochankun Cc: [EMAIL PROTECTED] Subject: Re: InnoDB, Replication, and Data warehouse: Oil, Water, and little floating plastic men On Wed, Sep 24, 2003 at 03:03:20PM -0700, Misaochankun wrote: > MySQL tells me at startup that it can not allocate more than 512MB of > RAM. > It will fail to start the server if I specify any further. On what OS? Can we see the exact error? Have you checked things like ulimit? Jeremy -- Jeremy D. Zawodny | Perl, Web, MySQL, Linux Magazine, Yahoo! <[EMAIL PROTECTED]> | http://jeremy.zawodny.com/ MySQL 4.0.15-Yahoo-SMP: up 10 days, processed 393,361,824 queries (416/sec. avg) -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
