Fire - Config migrations – Incident details

Sentry API experiencing degraded performance

Config migrations

Resolved
Operational
Started over 5 years agoLasted 43 minutes
Updates
  • Resolved
    UTC
    Resolved

    This incident has been resolved.

  • Update
    UTC
    Update

    Fire has restarted and I am monitoring to ensure there's no lingering issues

  • Update
    UTC
    Update

    Fire is now restarting. This should only take around a minute!

  • Update
    UTC
    Update

    Migration has fully completed and was a success! Fire will soon reboot fully to remove migration & legacy code.

  • Update
    UTC
    Update

    Migration has completed on Cluster 1! I will now migrate configs for guilds Fire is no longer in. No impact on the bot is to be expected during this final stage

  • Update
    UTC
    Update

    Migration has completed on Cluster 0! Cluster 1 will now reboot to update and start migration...

  • Update
    UTC
    Update

    Migration has technically completed but I am going to rerun migration to make it delete default prefixes since there's no need to store default values. This migration will happen in a few minutes. Migration has still not happened on Cluster 1!

  • Update
    UTC
    Update

    Uh oh, seems like I made an oopsie and forgot to release the lock, causing the migration to get stuck after two guilds have been migrated. Working on getting a fix deployed!

  • Update
    UTC
    Update

    Cluster 0 is about to restart. Once again, some features may be unavailable until migration has completed for your guild. If migration has not completed, you may receive an error message when attempting to complete some actions.

  • Monitoring
    UTC
    Monitoring

    To allow for a new feature, all guild configs with the "config.prefix" or "main.prefix" setting must be migrated to a new format. This update brings support for multiple prefixes per guild meaning the prefixes must be an array, which is what this migration will change existing configs to. Migration will be done on cluster 0 first (you can check which cluster your guild is on at https://fire.gaminggeek.dev/stats by entering your guild id) and some features may be unavailable until migration has completed for your guild. A backup has been made if major issues arise but it should be smooth sailing. Cluster 0 will reboot in about 10 minutes to start migration. This incident will be updated to reflect this when it happens.