Storing data in distributed systems

• US 10,693,965 B2
• Filed: 12/20/2019
• Issued: 06/23/2020
• Est. Priority Date: 06/20/2016
• Status: Active Grant

• Current Assignee: Beijing Oceanbase Technology Company Limited
• Original Assignee: Alibaba Group Holding Ltd.
• Inventors: Yang, Zhenkun, Zhao, Yuzhong, Shi, Wenhui
• Primary Examiner(s): Jahnige, Caroline H
• Application Number:
  US16/722,531
• Publication Number:
  US 20200128076A1
• Time in Patent Office: 186 Days
• CPC Class Codes: G06F 11/1658 Data re-synchronization of a redundant component, or initial sync of replacement, additional or spare unit
• CPC Class Codes: G06F 11/2023 Failover techniques
• CPC Class Codes: G06F 16/182 Distributed file systems
• CPC Class Codes: G06F 16/1844 Management specifically adapted to replicated file systems
• CPC Class Codes: G06F 16/2379 Updates performed during online database operations; commit processing
• CPC Class Codes: G06F 2201/85 Active fault masking without idle spares active fault masking without idle spare hardware where processing functionality is redundant G06F11/2035
• CPC Class Codes: H04L 41/0668 by dynamic selection of recovery network elements, e.g. replacement by the most appropriate element after failure
• CPC Class Codes: H04L 65/40 Support for services or applications
• CPC Class Codes: H04L 67/1097 for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]

Abstract

One example method includes receiving, by the one or more processors, a request to update data stored on a distributed data storage system that comprises a primary server and a plurality of secondary servers, the request comprising data updates; sending, by the one or more processors, an update log instruction to the primary server and the plurality of secondary servers so that each of the primary server and the plurality of secondary servers records a log associated with the request; determining, by the one or more processors, that the log has been recorded; and in response to determining that the log has been recorded, sending, by the one or more processors, a data storage instruction to the primary server and a secondary server of the plurality of secondary servers so that each of the primary server and the secondary server stores the data updates.

Claims

1. A computer-implemented method executed by one or more processors, the method comprising:

receiving, by the one or more processors, a user input comprising a service request;

generating, by the one or more processors, a service response to the service request;

subsequent to generating the service response, receiving, by the one or more processors, a request to update data stored on a distributed data storage system that comprises a primary server and a plurality of secondary servers, the request comprising data updates, the primary server being randomly selected, wherein the data updates are associated with the service request;

sending, by the one or more processors, an update log instruction to the primary server and the plurality of secondary servers, wherein at least one of the primary server and the plurality of secondary servers records a log associated with the request;

determining, by the one or more processors, that a log operation was completed, wherein the log has been recorded by a first secondary server of the plurality of secondary servers;

in response to determining that the log operation was completed by the first secondary server of the plurality of secondary servers, sending, by the one or more processors, a data storage instruction to the primary server and the first secondary server of the plurality of secondary servers, wherein each of the primary server and the first secondary server stores the data updates; and

sending, by the one or more processors, a null-operation instruction to a second secondary server, wherein the null-operation instruction is used to instruct the second secondary server to perform no operation with respect to the data updates to reduce a number of copies of the data updates.

2. The computer-implemented method of claim 1, wherein at least one secondary server of the plurality of secondary servers is predetermined as being the second secondary server.

3. The computer-implemented method of claim 1, wherein the primary server is in communication with an external computing device to perform external read or write operations associated with the data updates.

4. The computer-implemented method of claim 1,

wherein the null-operation instruction instructs the second secondary server to cancel storage of the data updates.

5. The computer-implemented method of claim 1, further comprising:

determining that the primary server or the first secondary server has failed.

6. The computer-implemented method of claim 5, further comprising:

in response to determining that the primary server or the first secondary server has failed, sending a data synchronization instruction to a third secondary server, wherein the third secondary server synchronizes with the primary server or the first secondary server that has not failed, to store the data updates.

7. The computer-implemented method of claim 1, further comprising:

determining that the second secondary server other than the first secondary server has failed; and

sending a log synchronization instruction to a third server so that the third server synchronizes with the primary server or one secondary server of the plurality of secondary servers that is has not failed, to record the log.

8. A non-transitory computer-readable storage medium coupled to one or more computers and configured with instructions executable by the one or more computers to:

receive a user input comprising a service request;

generate a service response to the service request;

subsequent to generating the service response, receive a request to update data stored on a distributed data storage system that comprises a primary server and a plurality of secondary servers, the request comprising data updates, the primary server being randomly selected, wherein the data updates are associated with the service request;

send an update log instruction to the primary server and the plurality of secondary servers, wherein at least one of the primary server and the plurality of secondary servers records a log associated with the request;

determine that a log operation was completed, wherein the log has been recorded by a first secondary server of the plurality of secondary servers;

in response to determining that the log operation was completed by the first secondary server of the plurality of secondary servers, send a data storage instruction to the primary server and the first secondary server of the plurality of secondary servers, wherein each of the primary server and the first secondary server stores the data updates; and

send a null-operation instruction to a second secondary server, wherein the null-operation instruction is used to instruct the second secondary server to perform no operation with respect to the data updates to reduce a number of copies of the data updates.

9. The non-transitory computer-readable storage medium of claim 8, wherein at least one secondary server of the plurality of secondary servers is predetermined as being the second secondary server.

10. The non-transitory computer-readable storage medium of claim 8, wherein the primary server is in communication with an external computing device to perform external read or write operations associated with the data updates.

11. The non-transitory computer-readable storage medium of claim 8,

wherein the null-operation instruction instructs the second secondary server to cancel storage of the data updates.

12. The non-transitory computer-readable storage medium of claim 8, wherein the secondary server is a first secondary server, and the medium is further configured with instructions executable by the one or more computers to:

determine that the primary server or the first secondary server has failed.

13. The non-transitory computer-readable storage medium of claim 12, wherein the medium is further configured with instructions executable by the one or more computers to:

in response to determining that the primary server or the first secondary server has failed, sending a data synchronization instruction to a third secondary server, wherein the third secondary server synchronizes with the primary server or the first secondary server that has not failed, to store the data updates.

14. The non-transitory computer-readable storage medium of claim 8, wherein the secondary server is a first secondary server, and the medium further configured with instructions executable by the one or more computers to:

determine that the second secondary server other than the first secondary server has failed; and

send a log synchronization instruction to a third server so that the third server synchronizes with the primary server or one secondary server of the plurality of secondary servers that is has not failed, to record the log.

15. A system, comprising:

one or more computers; and

one or more computer-readable memories coupled to the one or more computers and having tangible, non-transitory, machine-readable media storing one or more instructions executable by the one or more computers to;

receive a user input comprising a service request;

generate a service response to the service request;

subsequent to generating the service response, receive a request to update data stored on a distributed data storage system that comprises a primary server and a plurality of secondary servers, the request comprising data updates, the primary server being randomly selected, wherein the data updates are associated with the service request;

send an update log instruction to the primary server and the plurality of secondary servers, wherein at least one of the primary server and the plurality of secondary servers records a log associated with the request;

determine that a log operation was completed, wherein the log has been recorded by a first secondary server of the plurality of secondary servers;

in response to determining that the log operation was completed by the first secondary server of the plurality of secondary servers, send a data storage instruction to the primary server and the first secondary server of the plurality of secondary servers, wherein each of the primary server and the first secondary server stores the data updates; and

send a null-operation instruction to a second secondary server, wherein the null-operation instruction is used to instruct the second secondary server to perform no operation with respect to the data updates to reduce a number of copies of the data updates.

16. The system of claim 15, wherein at least one secondary server of the plurality of secondary servers is predetermined as being the second secondary server.

17. The system of claim 15, wherein the primary server is in communication with an external computing device to perform external read or write operations associated with the data updates.