I am having issue with a large site where the server is locking up. One thing we found was that the searchcore_text table is 4.3 GB. I am wondering if this table can be truncated and would just start rebuilding itself as needed or if deleting all the data would cause problems. It is running v4.2.0.
SearchCore_Text Too Large
Collapse
X
-
That table hold all of your searchable text in the entire software. IF you truncate it, you won't have any search results. -
Ok, thanks.
Are there any recommendations for when this tables gets this large? The host is saying that queries to this table and the posts table are taking a while to update which is causing a backlog for everything else and then the database crashes and needs to be reset.Comment
-
Set all your tables except the search*_text and *session to innodb. You shouldn't as many problems with them creating a backlog.
Search Updates should also be queued so they are handled in blocks instead of attempted immediately. Settings -> Options -> Message Searching Options.
Upgrade MySQL to 5.5.XTranslations provided by Google.
Wayne Luke
The Rabid Badger - a vBulletin Cloud demonstration site.
vBulletin 5 APIComment
-
Hi DRJ,
They post is a bit old - but I'm having the exact same issue. Our searchcore_text is 4GB and our SQL is crashing each morning.
We are having to repair the table each day - but then it just crashes again the next morning.
How did you end up overcoming this?
Would really appreciate some information about the process!!!
Thanks!Comment
-
Related Topics
Collapse
-
by jkotlowskiThe data length on my vb_searchlog table is 8.75 GB
Is this normal? It's really strange, because a couple nights ago it was half this size. My host recently moved my SQL server and immediately...-
Channel: Support Issues & Questions
-
-
by ilfllcHi,
Can someone please provide some insight as to what I can do to properly fix the cacheevent table? Since upgrading to vBulletin 5 connect, we've had nothing but issues and this table keeps...-
Channel: Support Issues & Questions
-
Comment