Your organization operates a production Cloud SQL for MySQL instance that supports a mission-critical transactional application. During peak hours, complex analytical reporting queries involving multi-table SQL joins cause severe CPU throttling on the primary instance, impacting transaction processing. You must resolve the performance bottleneck for reporting workloads while maintaining real-time transactional data access, ensuring no schema changes are required, and minimizing operational overhead. What should you do?
- Create a Cloud SQL read replica, configure the reporting application to query the read replica's IP address, and maintain write operations on the primary instance.Cevap
- BExport the transactional tables daily to a Cloud Storage Archive bucket and configure BigQuery external tables to execute the reporting queries.
- CMigrate the database tables to Cloud Bigtable to handle high-throughput analytical reporting and transactional queries within a single NoSQL cluster.
- DEnable High Availability (HA) failover on the primary Cloud SQL instance so that read traffic is automatically load balanced to the standby instance.
Cevap
Create a Cloud SQL read replica, configure the reporting application to query the read replica's IP address, and maintain write operations on the primary instance.
Creating a Cloud SQL read replica allows read-heavy reporting queries to be processed independently from the primary instance. This eliminates CPU contention on the primary database, maintains relational SQL join functionality, provides near real-time data access via asynchronous replication, and requires zero schema migration overhead.
Adım Adım Çözüm
Anahtar Kavram
Managing Cloud SQL Read Replicas for Operational Performance Optimization