PDA

View Full Version : 2001 Upgrade Notice: mySQL Engine


Deb
01-04-2001, 08:00 PM
The MySQL engines will be upgraded from 3.22.x to 3.23.x

The tentative upgrade schedule is as follows: MySQL03 between 1am and 5am EST Saturday January 13th 2001 Completed

MySQL02 between 1am and 5am EST Saturday January 20th 2001 Completed

MySQL01 between 1am and 5am EST Saturday January 27th 2001 Completed
MySQL notices have been sent out to all site owners known to have not yet upgraded from a single mySQL database on community servers to having 6 mySQL Databases on the mySQL dedicated servers.[nbsp][nbsp]

If you feel you should have received one of these notices but have not, please send a note to Service@FutureQuest.net explaining the situation.[nbsp][nbsp]

If you use mySQL and are still connecting to "localhost" your account is required to upgrade by January 13th 2001.[nbsp][nbsp]All mySQL engines will be removed from the Community Servers on this date so it is imperative that no one continues to use them.

Note:
The following link tells what you should watch out for when upgrading to Version 3.23:

http://www.mysql.com/documentation/mysql/commented/manual.php?section=Upgrading-from-3.22

<edit>Added MySQL Link</edit>


[This message has been edited by Deb (edited 01-27-01@2:20 pm)]

LeeH
01-04-2001, 09:51 PM
Hi FQ,

OK, what do I need to do to find out what MySQL server I am on?

What do I need to &quot;upgrade&quot; if I am still connecting to &quot;localhost&quot;.

And, do you by chance have a fast - stable server that doesn't upgrade so often? I just want a server that works without new bugs (programmers = $$$).

Lee H

Deb
01-04-2001, 10:09 PM
I have responded to your email incident concerning your upgrade requirements.[nbsp][nbsp]You are already on MySQL01 so there is no need for you to make any adjustments.[nbsp][nbsp]

As far as a machine that does not upgrade that would require a world where none of the technology is ever improved...doubtful.[nbsp][nbsp]The only other option is a dedicated server where you can control what software you want and leave it be until such a time that you yourself would rather the upgrade.[nbsp][nbsp]

On a Community Host we have to work toward satisfying the masses, and though everything is working GREAT as-is, they do prefer we upgrade so that is what we must do.

Deb
[nbsp]- If it's not broke upgrade it.[nbsp][nbsp]If it then breaks, upgrade it again.

LeeH
01-04-2001, 10:34 PM
Hi Deb,

Thanks for responding so quickly, however I did not get your email concerning my upgrade requirements. All I received was the email:

&quot;Your request for personal assistance has been received.
You should expect a response from us within 24 hours.&quot;

Deb
01-04-2001, 10:40 PM
I have resent the response as it seems it was not processed correctly the first time.

Deb
[nbsp]- Try and try again...

LeeH
01-04-2001, 10:47 PM
Got it this time, thanks again for the quick response.

Lee H

Terra
01-12-2001, 11:37 PM
MYSQL03 will be upgrading from 3.22.32 --> 3.23.30

Just a friendly reminder that these upgrades are scheduled for tonight in the AM hours...

Overall, I don't believe the cutover should last for more than 30 minutes since the new core is in place and ready to roll...

--
Terra
sysAdmin
FutureQuest

Terra
01-13-2001, 02:32 AM
MYSQL03 has now completed the upgrade to 3.23.30...

--
Terra
sysAdmin
FutureQuest

Deb
01-18-2001, 06:34 PM
~~> Bump *

Terra
01-20-2001, 01:39 AM
MYSQL02 will be upgrading from 3.22.32 --> 3.23.30

Just a friendly reminder that these upgrades are scheduled to begin at 1:00am EST and should be rather uneventful...

--
Terra
sysAdmin
FutureQuest

Terra
01-20-2001, 02:44 AM
All 'isamchk' processing has been completed...

I am now converting all ISAM tables to the new MyISAM structure...[nbsp][nbsp]This procedure could take up to an hour for completion...[nbsp][nbsp]I went ahead and chose to perform this now, as a courtesy to everyone...

--
Terra
sysAdmin
FutureQuest

Terra
01-20-2001, 03:15 AM
MYSQL02 is now back online and in full production...

All tables have been converted to the new MyISAM structure with full myisamchk integrity checks producing 100% success...

From here, I will be updating the command-line utilities on:
PHOENIX, DEXTER, and DEEDEE

--
Terra
sysAdmin
FutureQuest

Terra
01-27-2001, 05:27 AM
Due to a power issue with MYSQL02, the upgrades scheduled for tonight have been delayed until this problem has been resolved...

--
Terra
sysAdmin
FutureQuest

Terra
01-27-2001, 06:58 AM
MYSQL01 will be going down for upgrades in the next 20 minutes so that I can swap in the upgraded server...

Downtime could last up to 30 minutes as I will be updating as many tables as possible to the MyISAM format...[nbsp][nbsp]Those that I cannot are most likely using the value of '0' in an auto_increment column...[nbsp][nbsp]These particular tables will remain in ISAM format...

This work will bring forth MySQL 3.23.32 and will finalize all MySQL upgrades...

--
Terra
sysAdmin
FutureQuest

Terra
01-27-2001, 07:53 AM
This is going to take longer than planned due to the large bulk of transfers...[nbsp][nbsp]Some of these databases are over 200Mb a piece, and the conversion is taking longer than expected due to the nature of the tables...[nbsp][nbsp]PHPAds is the largest culprit, with w3t forum tables coming in a close second...

--
Terra
sysAdmin
FutureQuest

[This message has been edited by ccTech (edited 01-27-01@06:54 am)]

heath
01-27-2001, 08:16 AM
I am prolly guilty here as with this being a very busy time of the year for my site, one of the rows in my phpads database had grown to over 3 million rows.

I usually empty all the rows older than 60 days every month or so, but just forgot to with the holidays and now the SuperBowl.

My apologies.

Terra
01-27-2001, 08:44 AM
Heath, you are definitely up there in disk usage... ;)[nbsp][nbsp]

I'm currently grinding through your database (165Mb), however I've got a few other large databases that are weighing in well over that...

There were several tables >200Mb, but as a side effect of the MyISAM conversion - the deleted records were fully purged effectively trimming the fat...

These PHPAd tables are absolute monsters, and I think everyone will be quite surprised when I am finally able to securely include your MySQL Disk Usage within the CNC using the new 3.23.x methods...[nbsp][nbsp]http://www.aota.net/images/smile/cry.gif

MYSQL01 was the last domino to fall, before I could start paving the road into the CNC with more enhanced DB information...

You can also view this enhanced information via:
mysql> SHOW TABLE STATUS ...

Once I bring the new MYSQL01 engine back online...

--
Terra
sysAdmin
FutureQuest

[This message has been edited by ccTech (edited 01-27-01@07:51 am)]

Terra
01-27-2001, 09:21 AM
All upgrade and conversion work has just been finalized on MYSQL01...

myisamchk shows 100% integrity across the board... :)

The new 3.23.x engine appears to be responding quite well and took the initial surge of queries without breaking a sweat...

My sincerest apologies for grossly underestimating the time to perform this upgrade work...[nbsp][nbsp]I did not realize that the PHPAd tables would have taken so long to convert due to their heavy indexing...

I for one am pleased to see the MySQL upgrades come to a successful closure, and I hope that everyone uses the new features this 3.23.x series has to offer...

--
Terra
sysAdmin
FutureQuest

heath
01-27-2001, 09:47 AM
As always, excellent work.

The party, alas must be over:[nbsp][nbsp]The days are long gone of having 4 million row databases and not getting charged for disk space.

Also:[nbsp][nbsp]What are your intentions on upgrading NINE to php4?[nbsp][nbsp]I know its a precarious situation, and personally I'd be a lot happier if you got amnesia about it or something.

Thanks.
Heath

heath
01-27-2001, 09:57 AM
I am getting these errors: Warning: 0 is not a MySQL result index in /xthedailyspread/www/qqq/recently.html on line 13
Dunno if its something on my end or not.

Terra
01-27-2001, 11:11 AM
Go ahead and move that question down into the PHP 3/4 forums, as it would be more relevant there...[nbsp][nbsp]I'm sure that everyones combined assistance and knowledge will help to overcome any obstacles in the way...[nbsp][nbsp]We did it once before with last weeks upgrades, and everything worked out more smoothly than original expectations...

Without seeing more of what you are doing, it could be any number of things...[nbsp][nbsp]Also, check the MySQL changes page and cross reference what your query is with that...

Right now, I won't speculate on the server-to-server progress rate, as I am dealing with some legacy configurations that need to be brought up to current spec...

--
Terra
sysAdmin
FutureQuest

heath
01-28-2001, 08:27 AM
&quot;when&quot; is a reserved word in new version of mySQL