We were unsuccessful getting the MySQL AMD64 rpms to work on RHEL3 AS.
I downloaded the source rpm and rebuilt the rpms on our Opteron server
and they have mostly worked, only one crash so far which we are in the
process of reporting to the MySQL support group.
Of course, we are experiencing
I should sleep before posting, I suppose.
I suppose this is the issue with the NPTL threads library? If so, has
anyone dealt with that issue with MySQL? I remember hearing that
perhaps using a dynamically linked mysqld would work around the problem.
Owen
Owen Scott Medd wrote:
I have Red
guessing!
Greg
-Original Message-
From: Owen Scott Medd [mailto:[EMAIL PROTECTED]
Sent: 03 November 2003 15:08
To: [EMAIL PROTECTED]
Subject: Re: MySQL 4.0.16 on RHEL3 AS AMD64
I should sleep before posting, I suppose.
I suppose this is the issue with the NPTL threads library?
If so, has
I have Red Hat Enterprise Linux 3 AS installed on a dual Opteron server
with 16GB of memory (hoping to solve innodb_buffer_pool size issues
under x86). I upgraded the MySQL included with RHEL3 (3.23.58) to the
4.0.16 rpms from the MySQL website.
I had thought this would be a piece of cake, as
Well, not logically valid in the general sense (in that naive
master-master replication can be self-destructive) but can be extremely
useful when utilized knowing all the limitations and potential pitfalls.
On Sun, 2003-08-31 at 10:01, Douglas Granzow wrote:
I think the message they were trying
I know we are facing this same question right now (I have 8 way servers
with 16GB of memory running MySQL, with 5 GB sitting unused while the poor
innodb buffer pool sits starved for memory). Do we replace these servers
with 4 way Opterons (are there 8 ways promised yet?) or is there another
[ start stupid question ]
Does setting innodb_thread_concurrency to 1 imply that only one innodb
thread will be working at any given time? So using this on SMP servers
that you would like to be answering simultaneous queries is probably not
what you would really like to be doing, no?
[ end
Actually, we are looking to do just the same thing for a pretty large
database. We've come across a project at sourceforge that claims to do
this (upsize bcp) and will be investigating how well it works next week.
Sourceforge page is http://sourceforge.net/projects/upsize-bcp/.
On Fri, 13 Apr
We've been running on RedHat distribution (starting with 5.2 or so) and
Slackware before that for the last few years (currently running mysql
3.23.32... that update bug introduced in 3.23.34 really spanked us hard,
we'll be moving to "latest" again soon).
Currently, we've got dual and quad PII
