Degraded Performance Observed in London and Dublin environments

Impact:

During the incident, customers experienced slowness across both the iSell London and Dublin platforms due to database storage reaching critical capacity levels. The issue affected all users of cruise products on both platforms.

Cause & Resolution:

The incident was caused by the accumulation of MySQL binary logs and issues with the replication configuration, which prevented automatic log cleanup. As a result, storage filled up over time, leading to performance degradation.
To quickly restore service stability, manual storage expansion was performed, followed by corrective actions to address binary log retention and replication health.

Prevention Measures:

To prevent recurrence, the following measures are being implemented:

• Configure automated binary log management with appropriate retention settings and monitoring alerts to avoid excessive accumulation.
• Implement enhanced storage monitoring covering binary logs, table fragmentation, and replication health, with alerts at critical thresholds.