Dropbox, Inc.

Mehant Baid

Bogdan Munteanu

Daniel K Tahara

Mihnea Cezar Giurgea

Robert Escriva

Computer-implemented techniques for replication-lag constrained deletion of data in a distributed data storage system. In some aspects, the techniques improve the operation of a computing system by preventing too high of a delete rate that causes severe replication lag while at the same time increasing and decreasing the delete rate over time to a maximum allowable delete rate constrained by measured replication lag in terms of both local replication lag and geographic replication lag. In one implementation, the delete rate is adjusted by increasing or decreasing a pause interval that determines how long a database data deletion process pauses between submitting database deletion commands to a database server.

Replication lag-constrained deletion of data in a large-scale distributed data storage system

Computer-implemented techniques for automatically coordinating application schema changes in a distributed data storage system. The techniques improve the operation of a computing system by automating the deployment of application schemas changes to a distributed data storage system in a manner that does not introduce orphaned data inconsistencies or integrity inconsistencies to the application data stored in the distributed data storage system. The techniques include a schema change deployment protocol that ensures that all of the database servers of the distributed data storage system are using no more than two consecutive versions of the application schema at any given time.

Automatically coordinating application schema changes in a distributed data storage system

Techniques are provided for a linearizable primary-secondary database system that replicates database data with eventual consistency. The techniques include obtaining a logical clock value of a logical clock that orders transactions committed at a primary database system that includes a primary database. The logical clock value is obtained after a write transaction is committed at the primary database system and while processing a read request. The logical clock value is used to determine whether a secondary database is in a consistent replication state corresponding to the logical clock value with respect to the primary database. The read request is maintained in a linger state while the secondary database is not yet in the consistent replication state. The read request exits the linger state and is allowed to be processed against the secondary database after the secondary database has reached the consistent replication state.

Growing community of inventors

San Mateo, CA, United States of America

Mehant Baid