How We Migrated Our Massive Crashes Database
Blog post from Luciq
Migrating a high-volume database like Instabug's crashes table requires careful planning and execution, especially when dealing with mission-critical data. The team opted for partitioning the table on the "deleted_at" column to enable MySQL to drop partitions instantly. They explored various migration tools, including pt-online-schema-change, fb-osc, Large Hadron Migrator (LHM), and gh-ost. After evaluating these options, they chose gh-ost due to its triggerless design, which eliminated lock contention issues. However, they encountered some challenges with gh-ost, such as not saving the latest migrated chunk and slow migration, which were addressed by editing the code. Ultimately, the team successfully migrated their database using gh-ost, ensuring a reliable and efficient solution for their high-volume data needs.
No tracked trend matches for this post yet.
Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.