Darrell,
Friday, July 26, 2002, 10:43:32 PM, you wrote:
DAS> I am just getting started with MySQL and one of the first things I was
DAS> trying is converting one of my larger tables to MySQL to see what kind of
DAS> performance I would get from some standard queries that I run against it.
DAS> I
I am just getting started with MySQL and one of the first things I was
trying is converting one of my larger tables to MySQL to see what kind of
performance I would get from some standard queries that I run against it.
I built the table and created some indices that I thought would boost the
perf
I have been having consistent problems with index corruption using BDB
tables in the 3.23.38 source version. Looking at the Change Log entries for
3.23.40, i think upgrading may help me out. Does anyone have a more detailed
explanation of the bugs addressed by these two fixes:
Changes in release
Hi,
I'm running MySQL 3.22.32 on Slackware Linux (not sure about the exact
configuration or kernel - don't have telnet access to the machine at the
moment; apologies). I have three tables:
* domains - a large monolithic table with 1 primary key and 3 other
keys, 43
fields in total, 1344 bytes
Hi Joseph,
>Hardware platform :
> Dell PowerEdge 2450 bipro PIII/733,
> 2Gb RAM,
> integrated hardware RAID crontroller (PERC3)
> with 2x18Gb disks configured
> in RAID1 (mirroring) mode.
>
>Operating system:
> Linux RedHat 6.2 (kernel 2.2.14 SMP)
>[...]
> I tried to use --safe-mode but I had to
h> upgrading from 3.22.32 to 3.23.30 server crashes have
Joseph> disappeared but with still had index corruptions (between one
Joseph> and two tables corrupted every two hours).
Joseph> Workaround:
Joseph> I have rebooted the server in single-processor mode and there
Joseph> was
disappeared but with still had index corruptions (between one
> and two tables corrupted every two hours).
>
> Workaround:
> I have rebooted the server in single-processor mode and there
> was NO index corruption in the last 24 hours (although the server
> was even more loaded than
had index corruptions (between one
> and two tables corrupted every two hours).
>
> Workaround:
> I have rebooted the server in single-processor mode and there
> was NO index corruption in the last 24 hours (although the server
> was even more loaded than during previous
two hours).
Workaround:
I have rebooted the server in single-processor mode and there
was NO index corruption in the last 24 hours (although the server
was even more loaded than during previous days: between 300
and 350 queries/s).
Hardware platform :
Dell PowerEdge 2450 bipro PIII/733
Hello,
I have posted several emails to this list during the last few
days because of mysqld crashes and index corruptions. Since
then I have made several modifications to the server but I
still have occasional index corruptions (about one corruption
every two hours, the figure seems to vary with
Joseph Bueno writes:
> Sinisa Milivojevic a écrit :
>
> Yes, from MySQL-3.23.30-1.i386.rpm
>
> BTW, are there any known issues with:
>
> - glibc from RedHat 6.2 (I have checked Red Hat site there is
> no update for it)
>
> - MySQL with SMP (I have been told to try with one CPU onl
Marco Bizzarri wrote:
>
> Hi all.
>
> We're using mysql 3.22, on a Red Hat Linux 6.2 system. We're also
> accessing the data through MyODBC, from Windows. The mysqld is started
> with the skip-locking feature activated
>
> The problem is that we are experienci
Sinisa Milivojevic a écrit :
>
> Joseph Bueno writes:
> > Hello,
> >
> > I posted message below a few hours ago.
> > Since then, I have tried to find how fast indexes become corrupt.
> > I have run a CHECK TABLE QUICK
> > on different tables in my database and run a
> > REPAIR TABLE whe
Joseph Bueno writes:
> Hello,
>
> I posted message below a few hours ago.
> Since then, I have tried to find how fast indexes become corrupt.
> I have run a CHECK TABLE QUICK
> on different tables in my database and run a
> REPAIR TABLE when an error is reported followed
> by a CHECK T
Hi all.
We're using mysql 3.22, on a Red Hat Linux 6.2 system. We're also
accessing the data through MyODBC, from Windows. The mysqld is started
with the skip-locking feature activated
The problem is that we are experiencing index corruption when we access
both with the clients and w
tests
so it may be possible that they are related to the high load
on the production server (between 250 and 300 queries/s).
Thanks for your help
--
Joseph Bueno
Original Message
Subject: Re: index corruption and mysqld crash
Date: Fri, 12 Jan 2001 17:23:48 +0100
From: Joseph Bu
EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Friday, January 12, 2001 1:31
> Subject: index corruption and mysqld crash
>
> > Hello,
> >
> > I have switched this morning our Web server from mSQL to MySQL.
> > I am using MySQL 3.22.32 installed f
I can think of only one suggestion. See if there is a cron job or something
killing a process. I doubt it though. Hope it helps.
- Original Message -
From: "Joseph Bueno" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, January 12, 2001 1:31
Subject
Hello,
I have switched this morning our Web server from mSQL to MySQL.
I am using MySQL 3.22.32 installed from MySQL-3.22.32-1.i386.rpm
on a Linux server (RedHat 6.2).
mysqld dies very ofen (uptime is between 2mn and 20mn) and
the only messages I have in error file look like :
Number of process
19 matches
Mail list logo
