Hi again,
as there was not a single answer to my question I can imagine that no one
encountered the same issue, but anyways, can there be any hints? First of
all, are there any means of looking at mysql memory allocation list
grouped by some major parts - for example,
innodb main pool - can be retrieved from innodb monitor
innodb additional pool - can be retrieved from innodb monitor
myisam main cache - ...?
myisam sort buffer - ...?
memory allocated from OS - ...?
The questiion is why mysql is trying to allocate memory via malloc from OS
while the innodb additional pool is occupied only by 50%? Or is it myisam
buffer that mysql is trying to extend?
Regards
---
Alex
On Tue, 14 Oct 2003, alex wrote:
> Hi people,
>
> I have mysql 4.0.7-gamma/linuxthreads running under FreeBSD 4.6.2 (server
> has 4G phisical memory), and occasionally mysql traps with the message:
>
> InnoDB: Fatal error: cannot allocate 1064960 bytes of
> InnoDB: memory with malloc! Total allocated memory
> InnoDB: by InnoDB 513951016 bytes. Operating system errno: 12
> InnoDB: Cannot continue operation!
>
> The first strange thing is that MAXDSIZ and DFLDSIZ in kernel config are
> setted to 1536M, and the second one is that each time it happens, while
> the number of bytes reported to cannot be allocated is different, total
> memory allocated by InnoDB is exactly the same - 513951016 bytes. Which
> restrictions are the cause of this - InnoDB's or FreeBSD's?
>
> Thanks in advance
>
> ----
> Alex
>
> --
> MySQL General Mailing List
> For list archives: http://lists.mysql.com/mysql
> To unsubscribe: http://lists.mysql.com/mysql?unsub=1
>
