Comments on: Better Scalability with Multiple Rollback Segments

By: MySQL 5.5 Feature List | CastlerockResearch India Developer Blog

MySQL 5.5 Feature List | CastlerockResearch India Developer Blog — Thu, 13 Oct 2011 06:09:10 +0000

[...] http://planet.mysql.com/entry/?id=22648 http://blogs.innodb.com/wp/2010/04/innodb-multiple-rollback-segments/ http://blogs.innodb.com/wp/2010/09/mysql-5-5-innodb-as-default-storage-engine/ [...]

By: Marko Mäkelä

Marko Mäkelä — Mon, 06 Sep 2010 09:10:20 +0000

@Cvecara Beograd, the maximum table size does not have anything to do with the undo logging of transactions. InnoDB supports up to 4,294,967,296 (2^32) pages per tablespace. Older versions of InnoDB limit it to 2,415,919,104 (0×90000000) pages when applying the redo log in crash recovery. 2^32 pages of 16 kilobytes (2^14 bytes) would be 2^46 bytes, or 64 TiB per tablespace, but that figure will include some administrative overhead (allocation and insert buffer bitmap pages, node pointer pages, B-tree leaf page headers and footers).

In the past, InnoDB did return the misleading error code HA_ERR_RECORD_FILE_FULL when it failed to allocate an undo log segment. Currently, it returns the code HA_ERR_TOO_MANY_CONCURRENT_TRXS, which is mapped to ER_TOO_MANY_CONCURRENT_TRXS.

By: Piyush

Piyush — Mon, 23 Aug 2010 10:13:12 +0000

@Harpej Singh, check the Disk Space Available dude.

By: Cvecara Beograd

Cvecara Beograd — Mon, 19 Jul 2010 12:01:48 +0000

I’m also interested in resolving large table issue.
What is the limit there. We are speaking about 100 billions in one table here.

By: Harpej Singh

Harpej Singh — Sat, 24 Apr 2010 11:13:27 +0000

Dear Sir/Mam
I am facing a problem with MYSQL that we can’t store more then 123999475 rows. here 43 fields are in each row. ok. now error displayed
ERROR-CODE-1114(HY000). Table is full. now how we rectify thease problem please send me solution about this problem
thanks

Harpej Singh
Ajmer- Rajasthan (INDIA)
(91)9214311070

By: MySQL 5.5.4 looks awesome. « SmugMug's Don MacAskill

MySQL 5.5.4 looks awesome. « SmugMug's Don MacAskill — Thu, 15 Apr 2010 21:43:26 +0000

[...] and behold, it’s fixed! You can now have a whopping 128K transactions in flight. Best of all, it’s far more [...]

By: MySQL 5.5.4 is Very Exicting « Jeremy Zawodny's blog

MySQL 5.5.4 is Very Exicting « Jeremy Zawodny's blog — Wed, 14 Apr 2010 15:32:30 +0000

[...] Multiple Rollback Segments mean the 1,024 concurrent transaction limit goes away and concurrent transactions will have less mutex (lock) contention. [...]

By: James Day

James Day — Wed, 14 Apr 2010 03:22:23 +0000

Sunny, has this actually been tested with say MySQL 4.0 or 4.1 or 5.0 being able to use the extra rollback segments once they have been created with a later version?