Ignite Database Synchronization

emergency-maintenance.jpg

12:40pm January 11, 2014

Update: The database sync finished this morning. We are in the process of performing a bulk republish of the nearly 4,000 CURRENT auctions in the database to make sure any edits/changes/adds put in since the database dump (Jan. 9/10) are accounted for and to update client websites. We are still working and will update as soon as we are confident all processes are functioning normally.

 

-- Tammy Tenison
Chief Operating Officer
AuctionServices.com

 

11:20 am EST January 10th, 2014

Approximately 6:30pm eastern time January 9th, we determined their was a database synchronization issue with Ignite. When this happens, which is rare, the failsafe kicks in and Ignite locks users out in order to preserve everyone's data on the master.

We pull a copy of the master database and sync it to slave database. While this process is happening, we can only wait for them to sync back up. This takes a while because 1) the Ignite database is over 100GB file. 2) You cannot just copy / paste the file ... it has to take the data from the Master and CREATE a new database on the slave ... table by table, row by row ... and there are millions of rows. This is done carefully to ensure no data loss.

As soon as the process completes, we will update this post. In the mean time, it would be helpful if you refrained from making updates in Ignite.

Due to unusually high call volume, we are not able to return every call. We apologize and appreciate your understanding.

 

-- Tammy Tenison
Chief Operating Officer
AuctionServices.com

Have more questions? Submit a request

0 Comments

Article is closed for comments.
Powered by Zendesk