Question

A logistics company is deploying a Cloud Bigtable cluster to store real-time vehicle tracking events. Each record includes a vehicle ID, a timestamp, and GPS coordinates. During load testing with millions of concurrent writes, engineers observe that most traffic is hitting a single node while others remain nearly idle, causing high write latency. The current row key is a monotonically increasing timestamp prefix. What is the most appropriate change to resolve the throughput bottleneck?

Accepted Answer

Redesign the row key to lead with a hashed or field-promoted value such as vehicle ID, followed by a reverse timestamp, to distribute writes evenly across tablets.

Answer

Increase the number of nodes in the Bigtable cluster to spread the write load across more compute resources.

Answer

Enable Bigtable replication to a second cluster so that write traffic is split between the two clusters.

Answer

Switch the table to use column families with garbage collection policies to reduce the size of each row.