Nissan 370Z Forum

Nissan 370Z Forum (http://www.the370z.com/)
-   Announcements (http://www.the370z.com/announcements/)
-   -   THE370Z is Moving to a New Server (starting) on July 18th!!! (http://www.the370z.com/announcements/39626-the370z-moving-new-server-starting-july-18th.html)

xohmx 07-20-2011 03:11 PM

Very fast so far! Great job on the move as well, I know they can turn out very bad.

b1adesofcha0s 07-21-2011 09:51 AM

Just got some more database errors :|

Red__Zed 07-21-2011 09:54 AM

Quote:

Originally Posted by b1adesofcha0s (Post 1223195)
Just got some more database errors :|

That is because you touch yourself at night.

b1adesofcha0s 07-21-2011 09:57 AM

Quote:

Originally Posted by Red__Zed (Post 1223203)
That is because I touch Shado and Steve at night.

:werd:

I guess not even the new server can handle that massive amount of ghey.

CBRich 07-21-2011 07:08 PM

iPad support. Thank you.

Red__Zed 07-21-2011 07:09 PM

Quote:

Originally Posted by b1adesofcha0s (Post 1223211)
:werd:

I guess not even the new server can handle that massive amount of ghey.

:eek:

b1adesofcha0s 07-22-2011 08:25 AM

Quote:

Originally Posted by Red__Zed (Post 1224380)
:eek:

:rofl2:

houkouonchi 07-23-2011 04:29 AM

Nicer latency now that the servers in california =)

PING the370z.com (50.23.110.197) 56(84) bytes of data.
64 bytes from 50.23.110.197-static.reverse.softlayer.com (50.23.110.197): icmp_seq=1 ttl=54 time=9.20 ms
64 bytes from 50.23.110.197-static.reverse.softlayer.com (50.23.110.197): icmp_seq=2 ttl=54 time=8.99 ms
64 bytes from 50.23.110.197-static.reverse.softlayer.com (50.23.110.197): icmp_seq=3 ttl=54 time=8.97 ms

Isamu 08-01-2011 01:54 AM

2 Attachment(s)
AK,

as I promised!
http://www.the370z.com/attachment.ph...1&d=1312181655

AK370Z 08-01-2011 08:02 AM

Isamu thanks for posting. But I have noticed that the downtime starts at 2 am and takes about 3 hours to complete. During this 3 hour time, forum is on and off (some section works while some sections get DB errors. Also some features work and some features doesn't). But after 3 hours when it's fully backed up, the site works perfectly. So judging by your time stamp, it looks like you got the DB error during those time (1:00 am to 4:00ish for you. CST.). Hope it makes sense. I am gonna update the downtime thread soon with new info.

thanks

Isamu 08-01-2011 08:31 AM

Quote:

Originally Posted by AK370Z (Post 1239265)
Isamu thanks for posting. But I have noticed that the downtime starts at 2 am and takes about 3 hours to complete. During this 3 hour time, forum is on and off (some section works while some sections get DB errors. Also some features work and some features doesn't). But after 3 hours when it's fully backed up, the site works perfectly. So judging by your time stamp, it looks like you got the DB error during those time (1:00 am to 4:00ish for you. CST.). Hope it makes sense. I am gonna update the downtime thread soon with new info.

thanks

cool beans! :tup: I hope you know I wasn't bashing the new server, just wanted you to be aware! but that's cool if it's just server down time

houkouonchi 08-02-2011 08:24 AM

Quote:

Originally Posted by AK370Z (Post 1239265)
Isamu thanks for posting. But I have noticed that the downtime starts at 2 am and takes about 3 hours to complete. During this 3 hour time, forum is on and off (some section works while some sections get DB errors. Also some features work and some features doesn't). But after 3 hours when it's fully backed up, the site works perfectly. So judging by your time stamp, it looks like you got the DB error during those time (1:00 am to 4:00ish for you. CST.). Hope it makes sense. I am gonna update the downtime thread soon with new info.

thanks

AK, is there a reason why you don't convert the mysql tables to innodb (assuming they are myisam) and do mysqldump with --single-transaction to prevent the tables from being locked so you don't have the site go down during the mysqldump?

I work for a web-hosting company and our central database is over 100GB. Its not really feasible to have downtime during backup so most of our stuff is innodb. Another option is to have two mysqld's (would use more disk I/O if you don't have another server to run it on) and do mysql replication and then just run the dump on the slave.

Isamu 08-02-2011 08:57 AM

Quote:

Originally Posted by houkouonchi (Post 1241213)
AK, is there a reason why you don't convert the mysql tables to innodb (assuming they are myisam) and do mysqldump with --single-transaction to prevent the tables from being locked so you don't have the site go down during the mysqldump?

I work for a web-hosting company and our central database is over 100GB. Its not really feasible to have downtime during backup so most of our stuff is innodb. Another option is to have two mysqld's (would use more disk I/O if you don't have another server to run it on) and do mysql replication and then just run the dump on the slave.

:tup:

houkouonchi 08-03-2011 07:50 AM

Quote:

Originally Posted by Isamu (Post 1241257)
:tup:

I realized one of the things you lose (I believe still to be true) is full text searching which is probably needed for a few of the tables for a forum (but probably not all). If some tables can't be converted than the mysql replication should be a good option

EazyD 08-09-2011 11:21 PM

Feature that makes Tapatalk app worth it: the option to see only "Participated In" threads.


All times are GMT -5. The time now is 11:23 PM.

Powered by vBulletin® Version 3.8.4
Copyright ©2000 - 2025, Jelsoft Enterprises Ltd.
Search Engine Optimization by vBSEO 3.6.0 PL2