Post-Mortem
Hello everyone, these last 2 days we have been working frantically to fix things such as instance crashes and quest-states, we deployed many changes yesterday which did solve things such as:
This firstly overloaded our database on the first day and we made fixes to that which solved that issue and tags, and such were saving properly again. The issue is that tasks and objective containers are serialized to JSON which is then synced to a master instance before writing to database. The issue is the sheer volume of data being saved caused the master instance to fail to serialize, and when saved to Database, the corrupted JSON was not recognized causing Database to not save it.
This means:
Your objective is gone
But your quest state from dialogue prevents you getting the objective
Hello everyone, these last 2 days we have been working frantically to fix things such as instance crashes and quest-states, we deployed many changes yesterday which did solve things such as:
- Various performance issues
- Various skill rollbacks
- Built more redundancy into quests when server crashes
- Database saving issues
- Objectives saving
This firstly overloaded our database on the first day and we made fixes to that which solved that issue and tags, and such were saving properly again. The issue is that tasks and objective containers are serialized to JSON which is then synced to a master instance before writing to database. The issue is the sheer volume of data being saved caused the master instance to fail to serialize, and when saved to Database, the corrupted JSON was not recognized causing Database to not save it.
This means:
Your objective is gone
But your quest state from dialogue prevents you getting the objective