Well, from what you've provided, I can't really say it's an actual connection issue. You raised it to 10,000 max and still got the error. I'd either say it's mysql locking issues on the tables due to the applications (users) hitting it or something else perhaps, not totally sure.

2.3GB database though is worrisome. That's rather big for a MyISAM engine for the backend. You'll get better performance on larger databases using InnoDB. That's one suggestion but I'd say test it first on another machine if available.

Is there anything else on this machine running? Or is it just a database machine? Are the applications connecting remotely from an application or other server running the webserver?

How many users would say are using the forums at any given time?

no. only my website running on this machine.

may be 10,000 a hour. More then 70,000 unique a day.

How to move from MyISAM to InnoDB?

Here's a good tutorial: http://www.linux.com/articles/46370

I'd recommend doing the test on another server though, convert and then test applications before migrating to the live system. They do the simple way of editing the dump file from a mysqldump. This could be tedious. If you dumped the 2.3GB ipb database, editing that file for each table to convert to InnoDB is painful.

You can also use the alter statement to change the Engine time. It would be something like:

Another way you could do it is:

But like I said, I'd say experiment on another server or create another database perhaps. You could even create another database, dump the schema of the existing ipb or phpBB, edit the table creations to use INNODB, reload that into the new temporary database, then take a dump of the data for each table and insert.

Many different approaches. I think the easiest would be to setup another server, take a full dump, reload into server, use the alter table to change engine for each table, test once all have been converted. If all goes well, you can probably convert one table at a time while the server is alive. But making sure you edit your my.cnf file to support the new INNODB files, space you need to allocate for the ibdata files that will be used, etc.

Also note, if and when you convert, don't convert the mysql database to InnoDB, it needs to use MyISAM. I'd say start with the ipb database that is over 2GB in size.

it's crazy... http://www.linux.com/articles/46370
how to edit each line if i have 2gb?!...

That's why I said when you're dealing with a dump that big, the alternative is necessary.

Now you could do a sed search and replace on the file to edit, but that might take awhile itself.

That's why I'd recommend the alter table on a test system.

this seems like a good one
-ALTER TABLE table_name ENGINE = InnoDB;

http://mysqldatabaseadministration.b...to-innodb.html

Yup, just as I outlined in a previous response. But like I said, I'd test it on another system from a dump of the current system. Also remember, you need to make the proper changes to my.cnf to setup the ibdata files InnoDB will use, etc. Especially to accomodate the existing size of the database and future growth.

Depending on your disk size and available space, you might be good to start with 3 or 4 2GB ibdata files for INNODB to give you 6-8GB total to grow into. You can always add more at later times. These files once specified and configured in the my.cnf are created upon a mysql restart of the database.

SQL-запрос:

ALTER TABLE ibf_posts ENGINE = InnoDB

Ответ MySQL: Документация
#1214 - The used table type doesn't support FULLTEXT indexes

Do a:

show create table ibf_posts;

And see what the default language was used for the setup of that table, which is probably the same for all others.

What you talking about?

Innodb just doesn’t sepport fulltext!
and i can't change the `ibf_posts` to index

ALTER TABLE `ibf_posts` DROP INDEX `post` ,
ADD INDEX `post` ( `post` )

Ответ MySQL: Документация
#1170 - BLOB/TEXT column 'post' used in key specification without a key length

Nevermind previous post, got confused on the language output in your message.

As for the FULLTEXT, google search found this: http://bugs.mysql.com/bug.php?id=6713

Seems only MyISAM only supports FULLTEXT for sure and ibf uses full text indexes.

so what to do?

This is the test with the forum application. Perhaps you can hit up their own support or developers to find a way to convert the tables to use INNODB and still create Indexes.

According to their official documentation, InnoDB is supported as you can select it or MyISAM during the initial install.

Perhaps you could test by dropping the index, convert the engine to InnoDB, then attempt to add an index but not as fulltext indexing.