UBB.threads PHP Forum Software Community Forums General Off Topic server load is getting me down right down :(

Ok, if it's the .myi that keeps getting corrupt then that's definitely the indexes. I'd move it to 4. With 7.2 I'll be putting back the option to use the old search method if you need to search for less than 4 characters.

I'm sure you can specify a different tmp folder, but I'm not exactly sure how. Let me know when you plan on doing this, I'd like to do/check a few things before hand.

Ok, you should be able to specify a different temp directory with the following in your my.cnf file:

tmpdir = /path/to/mysqltempdirectory

Thanks.

LOL - do I need to restart MySQL to enable that?

If I do the table will corrupt. Can't win;)

Yes, you'd need to restart mysql, if you're going to change the min word length to 4, then do it at the same time

Thanks - I am going to start this in the next hour.

Just to make matters worse, I have a large number of emails being sent from the server, which is bouncing - I am told they are being generated from /forums They are certainly coming from the domain.

Never rains, but it pours LOL

I think the fact that you're running out of space in /tmp is, if not all of your load problem, then a large part of it.

When you run a query against mysql and the result set is too large to sort in memory it does it on disc. And where do you suppose it does that? If you guessed /tmp you win.

If you're running out of space in /tmp what do you think happens if two people try to search at the same time?

See where I'm going?

You need to find out why you're running out of space in /tmp. /tmp by the way, is not some place for you to put things temporarily. That's where the computer puts things temporarily.

sure - agree 100%

I have asked my server guys about increasing it - but never got an answer (surprise surprise)

247919 9097 226022 4% /tmp

are the figures.

I think that error 127 is due to using and repairing the tables at the same time.

Also, you'll find that running the command through the CLI will run much faster than utilizing it through a web script.

And I think it runs through the area defind in the config; I have no clue other than that though; never ran into issues like that yet

Error 127 is corruption for sure, but how it can be due to using and repairing at the same time I'm not sure. I was under the impression that the table locks while it is being repaired. Am I wrong?

Ian, might also be a good idea at some point to have the hard drives checked. If you had one bad drive, with the way your drives are setup. you would see exactly this. I think this is lower on the list of "could be the problem" than the previously mentioned things to check, but surely it needs to be on the list.

As I said to you before, I think it's more a combination of problems than it is one single cause.

I do believe that they are locked when repaired but the MySQL forums reported the error information i reported above; so it's conflicting information to say the least lol