Quote:
Originally Posted by lebrower
Yes that is by choice.
My best guess at this point is my first attempt to upgrade to 3.0.8 was foiled by a network communication issue that either blocked or disrupted my connection to the internet. Correcting the communication issue, restoring from back up and reloading 3.0.8 seems to have worked.
|
Actually, I don't think it was a network issue. The primary issue for botched migrations was data in the old database not in the expected format for the new database. This migration happened only on your phone was done without sending any data over the internet. So it was likely that the issue was resolved with the re-run migration process which addressed the data issue.
The only thing that was used by a connection was to send a backup of a user's data to our server for emergency purposes. We decided to that in case people deleted their apps, we could then provide them that backup. As time passes we will purge those backups. They will not be part of the Fuelly community data.
Some people did have connection issues on the first night of the upgrade. A flaw in the architecture of the system accidentally created a DDOS type of event where the apps were hammering the server in an unsustainable way. Within 24 hours we had added two huge web servers we had the capacity to handle all the requests while we were working on an app update. Once the app was updated the load on the server was no longer a concern.
Some people went through the update at the exact same time as the server load being extremely high. In a few rare cases that caused the backup URL to not work. In those cases they can still re-run the migration using the data on their phone. If they also deleted the app, we can try to pull their data from the old backup server.
Linear Mode
