Systems and methods for managing a highly available and scalable distributed database in a cloud computing environment

Patent metadata

Field	Value
Publication number	US-11216441-B1
Application number	US-202017105127-A
Country	US
Kind code	B1
Filing date	Nov 25, 2020
Priority date	Nov 25, 2020
Publication date	Jan 4, 2022
Grant date	Jan 4, 2022

Abstract

Systems and methods for managing a highly available distributed database comprising: a memory storing instructions; and one or more processors configured to execute the instructions to: determine that a source node, in a distributed database comprising the source node and one or more replica nodes, is not available; select a most-updated replica node from the one or more replica nodes; switch a role of the most-updated replica node to source; update a data store to label the source node as unavailable and the selected replica node as being a promoted source node; send a notification to a user device to update a database topology based on the updated data store; determine whether the user device has updated the database topology; and upon determining the user device has not updated the database topology, continue to send the notification to the user device until the user device has updated the database topology.

First claim

What is claimed is:

1. A computer-implemented system for managing a highly available distributed database in a cloud computing environment, the system comprising:
a memory storing instructions; and
one or more processors configured to execute the instructions to:
determine that a source node, in a distributed database comprising the source node and one or more replica nodes, is not available;
in response to the determination, select a most-updated replica node from the one or more replica nodes;
switch a role of the most-updated replica node from replica to source;
update a data store to label the source node as unavailable and the selected replica node as being a promoted source node;
send a notification to a user device connected to the distributed database to update a database topology log based on the updated data store;
receive data corresponding to the database topology log of the user device;
determine whether the user device has updated the database topology log based on the received data; and
upon determining the user device has not updated the database topology log, continue to send the notification to the user device until the user device has updated the database topology log.

2. The system of claim 1 , wherein the processor is further configured to: determine that the source node is available; update a last seen time in the data store; wait for a specific time interval; and determine whether the source node is available.

3. The system of claim 1 , wherein the processor is further configured to: determine that no promoted source may be selected;
upon the determination, alert the user device.

4. The system of claim 1 , wherein the data store is a distributed data store comprising a last seen time, database topology labels, and user device data and statistics.

5. The system of claim 1 , wherein the processor is further configured to, upon determining the user device has updated the database topology log, terminate a previous connection with the user device.

6. The system of claim 1 , wherein determining whether the user device has updated the database topology log comprises checking the data store for a confirmation from the user device.

7. The system of claim 1 , wherein the processor is further configured to monitor the data store and the distributed database in a specific time interval to ensure the data store is up to date.

8. The system of claim 1 , wherein the distributed database exists in a cloud computing environment.

9. The system of claim 1 , wherein the notification comprises instructions to connect the user device to the promoted source node.

10. A computer-implemented method for managing a highly available distributed database in a cloud computing environment, the method comprising:
determining that a source node, in a distributed database comprising the source node and one or more replica nodes, is not available;
in response to the determination, selecting a most-updated replica node from the one or more replica nodes;
switching a role of the most-updated replica node from replica to source;
updating a data store to label the source node as unavailable and the selected replica node as being a promoted source node;
sending a notification to a user device connected to the distributed database to update a database topology log based on the updated data store;
receiving data corresponding to the database topology log of the user device;
determining whether the user device has updated the database topology log based on the received data; and
upon determining the user device has not updated the database topology log, continuing to send the notification to the user device until the user device has updated the database topology log.

11. The method of claim 10 , further comprising:
determining that the source node is available; updating a last seen time in the data store;
wait for a specific time interval; and determine whether the source node is available.

12. The method of claim 10 , further comprising:
determining that no promoted source may be selected; upon the determination, alerting the user device.

13. The method of claim 10 , wherein the data store is a distributed data store comprising a last seen time, database topology labels, and user device data and statistics.

14. The method of claim 10 , further comprising, upon determining the user device has updated the database topology log, terminating the previous connection with the user device.

15. The method of claim 10 , wherein determining whether the user device has updated the database topology log comprises checking the data store for a confirmation from the user device.

16. The method of claim 10 , further comprising monitoring the data store and the distributed database in a specific time interval to ensure the data store is up to date.

17. The method of claim 10 , wherein the distributed database exists in a cloud computing environment.

18. The method of claim 10 , wherein the notification comprises instructions to connect the user device to the promoted source node.

19. A computer-implemented system for managing a highly available distributed database in a cloud computing environment, the system comprising:
a memory storing instructions; and
one or more processors configured to execute the instructions to:
determine that a source node, in a distributed database existing in a cloud computing environment comprising the source node and one or more replica nodes, is not available;
in response to the determination, select a most-updated replica node from the one or more replica nodes;
switch a role of the most-updated replica node from replica to source;
update a data store to label the source node as unavailable and the selected replica node as being a promoted source node;
send a notification to a user device connected to the distributed database to update a database topology log based on the updated data store;
receive data corresponding to the database topology log of the user device;
determine whether the user device has updated the database topology log based on the received data;
upon determining the user device has not updated the database topology log, continue to send the notification to the user device until the user device has updated the database topology log; and
upon determining the user device has updated the database topology, terminate the previous connection with the user device.

20. The system of claim 19 , wherein the processor is further configured to: determine that the source node is available; update a last seen time in the data store; wait for a specific time interval; and determine whether the source node is available.

Assignees

• Coupang Corp

Inventors

• Chen Zhan
• Huang Zhiyong
• Dong Bin
• Han Chuanchuan
• Zhang Junzhao

Classifications

• G06F11/2041

  with more than one idle spare processing component · CPC title

• G06F11/2025

  using centralised failover control functionality · CPC title

• G06F11/0751

  Error or fault detection not based on redundancy (power supply failures G06F1/30; network fault management H04L41/06) · CPC title

• G06F11/3476

  Data logging (G06F11/14, G06F11/2205 take precedence) · CPC title

• G06F11/3006

  where the computing system is distributed, e.g. networked systems, clusters, multiprocessor systems (multiprogramming arrangements G06F9/46; allocation of resources G06F9/50) · CPC title