Your organization runs a high-traffic e-commerce application on Google Cloud. Analytical clickstream event data is written continuously to a Cloud Bigtable instance, while transactional orders are stored in a Cloud SQL for PostgreSQL instance. Monitoring alerts indicate that CPU utilization on the Cloud Bigtable cluster has exceeded 80% for the past 20 minutes, leading to increased write latency for incoming events. You need to quickly mitigate the Bigtable performance bottleneck without causing data loss or downtime. Which action should you take?
- Increase the number of nodes in the Cloud Bigtable cluster.Answer
- BMigrate the incoming clickstream event writes to a new Cloud SQL read replica.
- CConfigure an Object Lifecycle Management rule to immediately transition raw event logs to Coldline Storage.
- DRun the gsutil perfdiag command against the Bigtable cluster endpoint to re-index table partitions.
Answer
Increase the number of nodes in the Cloud Bigtable cluster.
Increasing the node count of a Cloud Bigtable cluster immediately adds processing power and storage throughput. Bigtable node scaling is dynamic and zero-downtime, allowing the cluster to rebalance table partitions (tablets) across the new nodes to lower CPU utilization below target thresholds.
Step-by-Step Solution
Key Concept
Cloud Bigtable operational scaling and performance management
Estimated Time:2m 0s