Sp. Raja, ----- Alkuperäinen viesti ----- Lähettäjä: "Sp.Raja" <[EMAIL PROTECTED]> Vastaanottaja: "Heikki Tuuri" <[EMAIL PROTECTED]> Kopio: "mysql" <[EMAIL PROTECTED]> Lähetetty: Friday, March 05, 2004 2:28 PM Aihe: Re: Innodb table space getting filled up without any increase in actual rows!!
>Thanks for your valuable suggestions. > >I'm committing transactions, but not all. Only the transactions which do insert/delete, commit and not all. >So I think the better solution for me is to switch to "Read Committed" isolation mode, since I don't require "Repeatable Read" Isolation for >my application. > >Do you think this will address my issue (tables don't get filled up until they have rows) ? I think not. Best to run those SELECT transactions with AUTOCOMMIT=1. In transactional databases it is a good practice always to take care that your transactions are committed quickly. Do not leave them dangling. >Thanks, >Sp.Raja Best regards, Heikki Innobase Oy http://www.innodb.com InnoDB - transactions, row level locking, and foreign keys for MySQL InnoDB Hot Backup - a hot backup tool for InnoDB which also backs up MyISAM tables Register now for the 2004 MySQL Users Conference! http://www.mysql.com/events/uc2004/index.html > ------------Original Message------------ > From: "Sp.Raja" <[EMAIL PROTECTED]> > To: "K Perinbam" <[EMAIL PROTECTED]> > Cc: "R Narayanan" <[EMAIL PROTECTED]> > Date: Fri, Mar-5-2004 9:14 AM > Subject: Re: Innodb table space getting filled up without any increase in actual rows!! - Looks like can be fixed. > > FYI. > > > Sp. Raja, > > you have 3 dangling transactions that have been active for almost 2 hours. > They prevent purge from removing those delete-marked rows. > > ---TRANSACTION 0 832338, ACTIVE 6027 sec, OS thread id 65 > MySQL thread id 41, query id 1036449 localhost root > Trx read view will not see trx with id >= 0 832339, sees < 0 832214 > ---TRANSACTION 0 832337, ACTIVE 6027 sec, OS thread id 57 > MySQL thread id 42, query id 1036436 localhost root > Trx read view will not see trx with id >= 0 832338, sees < 0 832214 > ---TRANSACTION 0 832214, ACTIVE 6055 sec, OS thread id 110 > MySQL thread id 51, query id 1036076 localhost root > Trx read view will not see trx with id >= 0 832215, sees < 0 832215 > > You should commit these transactions. > > Best regards, > > Heikki > Innobase Oy > http://www.innodb.com > InnoDB - transactions, row level locking, and foreign keys for MySQL > InnoDB Hot Backup - a hot backup tool for InnoDB which also backs up MyISAM > tables > > Register now for the 2004 MySQL Users Conference! > http://www.mysql.com/events/uc2004/index.html > > > ----- Alkuper??inen viesti ----- > L??hett??j??: "Sp.Raja" <[EMAIL PROTECTED]> > Vastaanottaja: "Heikki Tuuri" <[EMAIL PROTECTED]>; > <[EMAIL PROTECTED]> > L??hetetty: Thursday, March 04, 2004 4:38 PM > Aihe: Re: Innodb table space getting filled up without any increase in > actual rows!! > > > Heikki, > > Thanks for your reply. > As you said I have attached trace collected for SHOW INNODB STATUS. > Please point me the things which are going wrong. > > Do you mean I have to use auto-commit transactions? > What changes should I do (or) take care when using MySQL through ODBC to > avoid old transactions ? > > To be more specific my client does a lot of inserts/deletes using a ODBC > connection maintaining number of rows to be between 60 and 70. > > Thanks, > Sp.Raja > > > ------------Original Message------------ > > From: "Heikki Tuuri" <[EMAIL PROTECTED]> > > To: <[EMAIL PROTECTED]> > > Date: Thu, Mar-4-2004 1:30 AM > > Subject: Re: Innodb table space getting filled up without any increase in > actual rows!! > > > > Sp. Raja, > > > > please check with > > > > SHOW INNODB STATUS\G > > > > if purge is still running and removing delete-marked rows. Also check that > > you do not have old, dangling transactions, which can prevent purge from > > running, as those old transactions could still see the delete-marked rows. > > > > Best regards, > > > > Heikki > > Innobase Oy > > http://www.innodb.com > > InnoDB - transactions, row level locking, and foreign keys for MySQL > > InnoDB Hot Backup - a hot backup tool for InnoDB which also backs up > MyISAM > > tables > > > > Register now for the 2004 MySQL Users Conference! > > http://www.mysql.com/events/uc2004/index.html > > > Preferably, you should test the problem using the latest stable or development version of > > MySQL Server before postin1> > > > > List:MySQL General Discussion Previous MessageNext Message > > From:Sp.RajaDate:March 3 2004 8:48am > > Subject:Fw: Innodb table space getting filled up without any increase in > > actual rows!! > > > > I missed attaching the trace file! > > Sorry !! > > > > Regards, > > Sp.Raja > > > > > ------------Original Message------------ > > > From: "Sp.Raja" <[EMAIL PROTECTED]> > > > To: "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]> > > > Date: Wed, Mar-3-2004 1:13 PM > > > Subject: Innodb table space getting filled up without any increase in > > actual rows!! > > > > > > Hi List, > > > > > > My tablespace is getting filled up so quick when no. of transactions > > increase without number of rows increasing considerably. > > > I have a test client which adds and deletes row dynamically maintaining > > number of rows at any instant between 20 and 60. > > > > > > When I run this test client, after some time the client emits the > > following error: > > > > > > "[MySQL][ODBC 3.51 Driver][mysqld-4.0.15a-debug]The table > > 'axactivealarmtbl' is full." > > > > > > I was confused on seeing this. So ran the test again but this time > > monitoring table status. I noticed that Rows, Data_length and Index_length > > column increased monotonically and InnoDB free decreased. I was not able > to > > reason why ? > > > > > > But when I used select count(*) from <tablename> it consistently gave me > > numbers between 20 and 60 > > > > > > I have attached output of "show table status"(trace.txt) as I > > observed > > taken at increasing time. > > > > > > Any Pointers/Ideas on this to help me resolve this issue?? > > > > > > Thanks, > > > Sp.Raja > > > > > > > > > > > > -- > > > MySQL General Mailing List > > > For list archives: http://lists.mysql.com/mysql > > > To unsubscribe: http://lists.mysql.com/mysql?unsub=1 > > > > -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
