Hmm, as I feared, this problem is so major that no one wants to touch
it. Not that I blame anyone.
-Original Message-
From: Misao [mailto:[EMAIL PROTECTED]
Sent: Monday, September 22, 2003 6:09 PM
To: [EMAIL PROTECTED]
Subject: InnoDB, Replication, and Data warehouse: Oil, Water, and
On Mon, Sep 22, 2003 at 06:09:22PM -0700, Misao wrote:
What follows is a short story, all true and quite stressful. No database
servers were harmed in the making of this server, but a couple were
threatened with loose rack mount rails.
We are trying to move over to InnoDB, but we have a
Message-
From: Jeremy Zawodny [mailto:[EMAIL PROTECTED]
Sent: Wednesday, September 24, 2003 2:11 PM
To: Misao
Cc: [EMAIL PROTECTED]
Subject: Re: InnoDB, Replication, and Data warehouse: Oil, Water, and
little floating plastic men
On Mon, Sep 22, 2003 at 06:09:22PM -0700, Misao wrote:
*snip
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
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
On Wed, Sep 24, 2003 at 03:45:22PM -0700, Misaochankun wrote:
OS: RedHat Enterprise ES 2.1
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.
It's clearly an OS bug of some kind. I've used well
On Wed, 24 Sep 2003, Misaochankun wrote:
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
