QuestionQ100

VerifiedDeploy scalable and highly available databases in Google Cloud

Your application uses Cloud SQL for MySQL. Users run reports against data that requires near-real-time updates; however, the added analytics created excessive load on the primary database. You created a read replica for the analytics workloads, but users now complain about delayed data changes and reports that remain slow. You need to enhance report performance and reduce replication lag without changing the existing reports. Which two approaches should you implement?

Choose two
Explanation

Cloud SQL for MySQL supports secondary indexes on read replicas specifically to optimize reporting-query performance without changing the reporting workload. It also supports parallel replication on read replicas, which uses multiple SQL threads to apply replicated transactions and can reduce replication lag; the documented configuration sequence is to disable replication on the replica, set the parallel-replication flags, re-enable replication, and optionally tune the primary-instance flags for parallel replication.

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!