RE: deadlock - Innodb Monitor

2001-11-01 Thread Heikki Tuuri
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. sor

RE: deadlock - Innodb Monitor

2001-10-31 Thread Gisella Saavedra
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. I see two transactions issuing table locks to the same tables,

RE: deadlock - Innodb Monitor

2001-10-31 Thread Gisella Saavedra
keys 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

Re: deadlock - Innodb Monitor

2001-10-31 Thread Heikki Tuuri
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 sp

RE: deadlock - Innodb Monitor

2001-10-31 Thread Miguel Angel Solórzano
ailto:[EMAIL 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

RE: deadlock - Innodb Monitor

2001-10-31 Thread Gisella Saavedra
MAIL 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 com

Re: deadlock - Innodb Monitor

2001-10-31 Thread Gisella Saavedra
Miguel, I can look at the file /mysql/data/mysql.err by using emacs. I do not need to stop the server. If I try a Windows tool like WordPad?, yes, it does not let me see the file. Heikki, I checked the task manager. I only have one mysqld running which is the mysqld-max-nt. I had mysqlgui

Re: deadlock - Innodb Monitor

2001-10-31 Thread Miguel Angel Solórzano
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: Microsoft Windows 2000 [Versão 5.00.2195] (C) Copyright 1985-1999 Microsoft Corp. C:\>cd\mysql\bin C:\mysql

Re: deadlock - Innodb Monitor

2001-10-31 Thread Heikki Tuuri
Gisella, >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. it should come to the standard output. I am sending a copy of this email to Miguel of MySQL AB. He should check why mysqld started as --standalone

Re: deadlock - Innodb Monitor

2001-10-31 Thread Miguel Angel Solórzano
At 10:48 31/10/2001 -0800, Gisella Saavedra wrote: Hi! Take a look at /mysql/data/mysql.err for to see the output for innodb_monitor. I guess that you need to stop the server, for open this file. Regards, Miguel >Heikki, > >thanks for the reply. Regarding the trace output, My test has been >

Re: deadlock - Innodb Monitor

2001-10-31 Thread Gisella Saavedra
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 there

Re: deadlock - Innodb Monitor

2001-10-31 Thread Heikki Tuuri
Gisella, >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. this is strange. When you start the server from the command promp, does it then print something to the

Re: deadlock - Innodb Monitor

2001-10-31 Thread Gisella Saavedra
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

Re: deadlock - Innodb Monitor

2001-10-30 Thread Heikki Tuuri
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 timest