I see several values set to '18446744073709551615', which is an
insanely large number for any memory setting (16.7 million terabytes
unless my math is wrong; huge in any case).
There was another person on the list earlier this year who had a
similar problem with large numbers, IIRC. I'd adjust t
Kevin Old wrote:
On 12/8/06, Philip Mather <[EMAIL PROTECTED]> wrote:
So something like 15G, that's not that bad. I'd run mtop as someone
suggested and see if some query is hammering it, maybe some other
process on the machine is hogging or going IO bound?
Thanks. We are watching the querie
On 12/8/06, Philip Mather <[EMAIL PROTECTED]> wrote:
So something like 15G, that's not that bad. I'd run mtop as someone suggested
and see if some query is hammering it, maybe some other process on the machine
is hogging or going IO bound?
Thanks. We are watching the queries. The pattern we
We have 16GB total, but are only using 8GB (according to mysql and our dbadmin).
Kevin
On 12/8/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
Hi,
How much memory do you have on your system ? (the current setting in your
my.cnf could eat *a lot* of memory)
Thanks,
Jocelyn Fournier
www.me
[EMAIL PROTECTED] wrote:
Hi,
How much memory do you have on your system ? (the current setting in your
my.cnf could eat *a lot* of memory)
min_memory_needed = global_buffers + (thread_buffers * max_connections)
thread_buffers
---+-
sort_buffer_size
Hi,
How much memory do you have on your system ? (the current setting in your
my.cnf could eat *a lot* of memory)
Thanks,
Jocelyn Fournier
www.mesdiscussions.net
> On 12/7/06, David Sparks <[EMAIL PROTECTED]> wrote:
>> Kevin Old wrote:
>> > Hello everyone,
>> >
>> > We have a 4 CPU master se
On 12/7/06, David Sparks <[EMAIL PROTECTED]> wrote:
Kevin Old wrote:
> Hello everyone,
>
> We have a 4 CPU master server running the 5.0.27 RPM x86_64 version of
> MySQL with a mix of InnoDB and MyISAM tables.
>
> We normally run at 1500 queries/per second and lately, the server will
> all of a s
Kevin Old wrote:
> Hello everyone,
>
> We have a 4 CPU master server running the 5.0.27 RPM x86_64 version of
> MySQL with a mix of InnoDB and MyISAM tables.
>
> We normally run at 1500 queries/per second and lately, the server will
> all of a sudden lock up and we are forced to restart mysql.
T
No backups (like innodb-backup) running during these times.
We have 16GB of RAM and are currently using about 8GB of it.
We think we might have narrowed it down to a few hellish queries that
are hitting a few tables that we recently converted to InnoDB from
MyISAM. We're gonna convert them back
RAM too, how are you on RAM?
Obviously 100GB+ probably isn't going to fit in cache, but the usage pattern
during slower periods might be causing killer thrashing.
On Thu, Dec 07, 2006 at 12:43:17PM -0600, Dan Buettner wrote:
> Another thought is - do you have backups running during this time?
> S
Another thought is - do you have backups running during this time?
Something that might be attempting to backup live the InnoDB files?
We had similar problems with MySQL and backup software a while ago,
though we used all-MyISAM.
Dan
On 12/7/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
Hi,
Hi,
Do you use MySQL with a NPTL or a linuxthread glibc configuration ?
Regards,
Jocelyn Fournier
www.mesdiscussions.net
> Hello everyone,
>
> We have a 4 CPU master server running the 5.0.27 RPM x86_64 version of
> MySQL with a mix of InnoDB and MyISAM tables.
>
> We normally run at 1500 qu
Hello everyone,
We have a 4 CPU master server running the 5.0.27 RPM x86_64 version of
MySQL with a mix of InnoDB and MyISAM tables.
We normally run at 1500 queries/per second and lately, the server will
all of a sudden lock up and we are forced to restart mysql.
This is not related to higher l
Hi Mark,
The system in question has 1GB of RAM in it. As far
as I can tell, the box does not get stuck swapping
when the system has a query (or several) in this
state. If I log in via the command line client and
kill the query, the system continues on it's way like
nothing was wrong in the first
In my experience, inserting into a table with a unique key and more than
5 million records can be very slow because (AFAIK) it has to scan the
entire index to check if the new record is unique from the PRIMARY KEY's
point of view. (I think)
If you don't have much ram (your 128 meg key buffer sugge
Here's the whole the query, table structure, table
length and show variables output:
mysql> desc summary;
+-+--+--+-+-++
| Field | Type | Null |
Key | Default | Extra
Please include the full query you're running, the table structure, and
the number of rows in the table. A dump of 'show variables;' would be
helpful too.
On Wed, 2004-11-10 at 21:44, foo bar wrote:
> Hi Everyone,
>
> I've been Googling unsuccessfully for specific issues
> relating to queries run
Hi Everyone,
I've been Googling unsuccessfully for specific issues
relating to queries run on MySQL version 4.0.16
against "tmp" tables. I have witnessed several
occurrences where queries running on various platforms
hang in a "Copying to tmp table" state for hours or
days at a time. When the sa
Hi all!
When dealing with MySQL clusters using ndb... I have configured a 4
nodes under linux. I would like to access the 4nodes cluster using
jdbc... how do i specify that the application should connect to any of
the db servers in the cluster using connector/j?
Vic.
--
MySQL General Mailing
L PROTECTED]
> Sent: Thursday, November 06, 2003 4:09 PM
> To: Luis Lebron
> Cc: Mysql (E-mail); Php-General (E-mail)
> Subject: Re: Issues with Mysql 4.0 and PHP in a production environment
>
>
> On Thu, Nov 06, 2003 at 02:10:27PM -0600, Luis Lebron wrote:
> > Are
ECTED]
Sent: Thursday, November 06, 2003 4:09 PM
To: Luis Lebron
Cc: Mysql (E-mail); Php-General (E-mail)
Subject: Re: Issues with Mysql 4.0 and PHP in a production environment
On Thu, Nov 06, 2003 at 02:10:27PM -0600, Luis Lebron wrote:
Are there any issues with running PHP 4.3.X and Mysql 4.0
)
Subject: Re: Issues with Mysql 4.0 and PHP in a production environment
On Thu, Nov 06, 2003 at 02:10:27PM -0600, Luis Lebron wrote:
> Are there any issues with running PHP 4.3.X and Mysql 4.0 in a production
> environment?
What sort of "issues" are you looking for?
Jeremy
--
J
On Thu, Nov 06, 2003 at 02:10:27PM -0600, Luis Lebron wrote:
> Are there any issues with running PHP 4.3.X and Mysql 4.0 in a production
> environment?
What sort of "issues" are you looking for?
Jeremy
--
Jeremy D. Zawodny | Perl, Web, MySQL, Linux Magazine, Yahoo!
<[EMAIL PROTECTED]> | h
Are there any issues with running PHP 4.3.X and Mysql 4.0 in a production
environment?
thanks,
Luis R. Lebron
Project Manager
Sigmatech, Inc
Stéphane Pinel wrote:
I've installed 3.23.53 on a MacOS X box.
verything seems to be OK except:
when I use mysql like this :
/usr/local/bin/mysql test
..no problem.
but if I want to use any option like :
/usr/local/bin/mysql test -u
This is not valid usage.
/usr/local/bin/mysql -u roo
I've installed 3.23.53 on a MacOS X box.
verything seems to be OK except:
when I use mysql like this :
/usr/local/bin/mysql test
..no problem.
but if I want to use any option like :
/usr/local/bin/mysql test -u
I get a zillion lines that start with
"./bin/mysql Ver 11.18 Distrib 3.23.53, fo
Hello ... my name is Brent ..and im using the latest version of mysql
on a Freebsd box with apache & php3 & php4. My problem is that ive set a
password for the root mysql user by doing:
/usr/local/bin/mysqladmin -u root password 'x'
then i installed phpMyAdmin ..and set the correct username &
Hi,
This is a problem of the sort that is starting to make me a little
supersituous. I am using mySQL various versions, one of which is 4.01 max on
FreeBSD 4.5 stable, DBI 1.30 and I believe the latest DBD::mysql module.
Well the weird thing that is happening is that on this particular machine
wh
DBs(ML),
Saturday, July 20, 2002, 3:50:48 PM, you wrote:
DM> 2) Nope, I have nothing on the end of the line.
DM> eg.
DM> set-variable = back_log = 200
DM> this works under 4.0.1 but not under 4.0.2
DM> back_log = 200
DM> this works under 4.0.2
DM> Error: (from 4.0.2 when using set-variable =
29 matches
Mail list logo
