公开(公告)号：US20190197173A1

公开(公告)日：2019-06-27

申请号：US15852271

申请日：2017-12-22

Applicant: Dropbox, Inc.

Inventor： Daniel Tahara ,  Mehant Baid ,  Robert Escriva ,  Mihnea Cezar Giurgea

IPC: G06F17/30 ,  G06F3/06 ,  H04L29/08

Abstract: 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.

公开(公告)号：US10698920B2

公开(公告)日：2020-06-30

申请号：US15852271

申请日：2017-12-22

Applicant: Dropbox, Inc.

Inventor： Daniel Tahara ,  Mehant Baid ,  Robert Escriva ,  Mihnea Cezar Giurgea

IPC: G06F16/27 ,  H04L29/08 ,  G06F3/06 ,  G06F16/21 ,  G06F16/23

Abstract: 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.