Hi
Do you see any problems?
=
050303 12:51:11 INNODB MONITOR OUTPUT
=
Per second averages calculated from the last 20 seconds
--
SEMAPHORES
--
OS WAIT ARRAY INFO: reservation count 14266, signal count 14261
PROTECTED] [EMAIL PROTECTED]
Newsgroups: mailing.database.mysql
Date: Sunday, March 24, 2002 10:50 PM
Subject: InnoDB monitor
Hi,
Can anyone tell me how to use the InnoDB monitor please. After creating
the
table with the following command: CREATE TABLE innodb_monitor(a int) type
=
innodb; I don't
Hi,
Can anyone tell me how to use the InnoDB monitor please. After creating the
table with the following command: CREATE TABLE innodb_monitor(a int) type =
innodb; I don't know where to watch the output from the InnoDB monitor.
Can anyone help?
Balteo. (sql,query
Hi,
you can see the monitor's output in the logfile. In my case (mandrake linux), it is in
/var/lib/mysql and I do:
tail -f /var/lib/mysql/SERVERNAME.err
Also, where do I designate autocommit = 0;
Use SET AUTOCOMMIT = 0 as a SQL query. Just issue it where you do your SELECT,
UPDATE etc.
Warning
Unable to process data:
multipart/mixed; boundary=--==_846811060==_
Gisella,
At 04:24 PM 10/31/01 -0800, you wrote:
Heikki,
The output I get from the Monitor does not have the section
--
LOCKS HELD BY TRANSACTIONS
--
that I see in the manual (www.mysql.com/doc), section 7.5.9.1, The InnoDB
Monitor.
sorry
Heikki,
thanks for the reply. Regarding the trace output, My test has been
bombarding the db server with 15 simultaneous clients, each
generating up to 1000 transaction sets.
I still do not get any output from Innodb Monitor.
I created table innodb_monitor in the database that I'm accessing
Innodb Monitor.
I created table innodb_monitor in the database that I'm accessing.
Should it be created instead in the database mysql??
No, it does not matter in which database you create it.
Here is a sample session I ran in NT:
mysql client:
C:\mysql4\binmysql test
Welcome to the MySQL
Heikki,
I looked at the mysql error log and all the stuff was there.
I was expecting it on the standard output as the documentation said.
Thanks again. I'll have to restart the server again since the
innodb monitor output on the error log says that I'm not running a debugable
version, so
bombarding the db server with 15 simultaneous clients, each
generating up to 1000 transaction sets.
I still do not get any output from Innodb Monitor.
I created table innodb_monitor in the database that I'm accessing.
Should it be created instead in the database mysql??
Is there any sample that I can
again since the
innodb monitor output on the error log says that I'm not running a debugable
version, so there is no information about locking. So, I should issue
It actually means 'no information about semaphore locking'.
You will get the user lock info with
innodb_lock_monitor
not with plain
\binmysqld-max-nt --standalone --console
011031 19:08:59 InnoDB: Started
mysqld-max-nt: ready for connections
=
011031 19:11:05 INNODB MONITOR OUTPUT
=
--
SEMAPHORES
--
OS WAIT ARRAY INFO: reservation count 4
=
011031 12:35:41 INNODB MONITOR OUTPUT
=
TRANSACTIONS
Purge done for all trx's with n:o 0 2955904, undo n:o 0 0
Total number of lock structs in row lock hash table 0
PROTECTED]]
Sent: Wednesday, October 31, 2001 1:15 PM
To: Heikki Tuuri; [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]; Gisella Saavedra
Subject: Re: deadlock - Innodb Monitor
At 22:52 31/10/2001 +0200, Heikki Tuuri wrote:
Heikki,
For you to have at the shell prompt the output is necessary
the command
To: Heikki Tuuri; [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]; Gisella Saavedra
Subject: Re: deadlock - Innodb Monitor
At 22:52 31/10/2001 +0200, Heikki Tuuri wrote:
Heikki,
For you to have at the shell prompt the output is necessary
the command: mysqld-max-net --standalone --console
Like I show below
Gisella,
sorry, the printout in InnoDB Monitor is
ambiguous in its words: non-debug version
there means a version not compiled with
#define UNIV_SYNC_DEBUG
in univ.i
The monitor in .44 does not use the ambiguous
term any more.
But you do not need semaphore info, only user
lock info. When I
generate secondary indexes?
Regards,
Gisella
-Original Message-
From: Miguel Angel Solórzano [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, October 31, 2001 2:38 PM
To: Gisella Saavedra; [EMAIL PROTECTED]
Cc: Miguel Angel Solórzano
Subject: RE: deadlock - Innodb Monitor
At 13:50 31/10/2001
Hello,
I'm running into the 100 deadlock error, so I would like to trace the
problem.
Server: mysqld-max-nt 3.23.43
myodbc 2.50.39
Server application that connects to mysqld is multithreaded.
Mysqld has been installed as a service.
I stopped it. Then I issued the following command:
Gisella,
.43 only prints info when there is MySQL server
activity. I have changed it to .44 so that it
always prints info every 15 seconds, regardless of
server activity.
If you want to study locks, then
innodb_lock_monitor
is the right tool.
About your other question, I am afraid that
19 matches
Mail list logo