Method to manage database failure

Patent metadata

Field	Value
Publication number	US-11269736-B2
Application number	US-201916445054-A
Country	US
Kind code	B2
Filing date	Jun 18, 2019
Priority date	Apr 24, 2019
Publication date	Mar 8, 2022
Grant date	Mar 8, 2022

Abstract

Disclosed is a non-transitory computer readable medium storing a computer program. When the computer program is executed by one or more processors of a computing device, the computer program performs procedures for database failure management, and the procedures may include: receiving backend failure information for at least one backend of one or more backends; receiving an event from a client after receiving the backend failure information; verifying whether the event is an event corresponding to a failed backend; verifying a type of the event if the event is an event corresponding to a failed backend; determining a method of processing the event corresponding to the failed backend based on the type of event, while backend failure occurs; receiving recovery information about the failed backend; and processing an event received from the client after receiving the recovery information about the backend.

First claim

What is claimed is:

1. A non-transitory computer readable medium storing a computer program, wherein when the computer program is executed by one or more processors of a server for database failure management, the computer program performs procedures for database failure management via the server, and the procedures include:
receiving a backend failure information for at least one backend of one or more backend computing devices;
receiving a request from a client computing device via a network after receiving the backend failure information;
verifying whether the request is a request corresponding to a failed backend based on a backend list received from a frontend computing device;
verifying a type of the request if the request is a request corresponding to a failed backend;
determining a method of processing the request corresponding to the failed backend based on the type of the request, while backend failure occurs;
receiving a recovery information about the failed backend; and
processing the request received from the client computing device after receiving the recovery information about the failed backend.

2. The non-transitory computer readable medium according to claim 1 , wherein types of the request include a streaming event for storing data or a read event for reading data included in a backend.

3. The non-transitory computer readable medium according to claim 1 , wherein, if the type of the request is a streaming event,
the determining a method of processing the request corresponding to the failed backend based on the type of the request, while backend failure occurs, includes:
determining to store a data based on the request in a physical storage space; and
wherein the procedures further include:
transmitting the stored data based on the request in the physical storage space to a recovered backend after recovery of the failed backend.

4. The non-transitory computer readable medium according to claim 1 , wherein, if the type of the request is a read event,
the determining a method of processing the request corresponding to the failed backend based on the type of the request, while backend failure occurs, includes:
determining to stop at least one of transmission or conversion of a data based on the read event.

5. The non-transitory computer readable medium according to claim 1 , wherein the processing a request received from the client computing device after receiving the recovery information about the failed backend includes:
establishing a connection with at least one backend of the one or more backend computing devices.

6. The non-transitory computer readable medium according to claim 1 , wherein the procedures further include:
transmitting a data load request information to at least one backend of the one or more backend computing devices based on the request received from the client computing device;
storing at least one of the data load request information or information about at least one backend that has received the data load request information in a buffer; and
if a process completion information is received based on the data load request information from at least one backend that has received the data load request information, deleting at least one of the data load request information or information about at least one backend that has received the data load request information from the buffer.

7. A non-transitory computer readable medium storing a computer program, wherein when the computer program is executed by one or more processors of a server for database failure management, the computer program performs procedures for database failure management, and the procedures include:
receiving a frontend list including information about one or more frontends from a frontend of one or more frontend computing devices, via a network;
establishing a connection with an other frontend other than a failed frontend based on the frontend list, if at least one frontend of the one or more frontends is failed;
establishing a connection with at least one backend of one or more backend computing devices based on a connection with the other frontend; and
determining a method of processing a request received from a client computing device via the network since when at least one frontend is failed until when connection with at least one of the one or more backends is established, while frontend failure occurs.

8. The non-transitory computer readable medium according to claim 7 , wherein the determining a method of processing an event received from a client computing device since when at least one frontend is failed until when connection with at least one of the one or more backends is established, while frontend failure occurs, includes:
determining to store a data based on the request in a physical storage space, if the event is a streaming event.

9. The non-transitory computer readable medium according to claim 8 , wherein procedures further include:
transmitting the data based on the request stored in the physical storage space to a backend in which the event is to be processed, after establishing the connection with at least one backend of the one or more backend computing devices.

10. The non-transitory computer readable medium according to claim 7 , wherein the procedures further include:
determining to perform a processing for a read event again after establishing a connection with at least one backend of the one or more backend computing devices, if a type of the request is the read event for reading data included in at least one backend of the one or more backend computing devices.

11. The non-transitory computer readable medium according to claim 10 , wherein the determining to perform the processing for a read event again after establishing a connection with at least one of the one or more backend computing devices includes:
determining to perform processing for a read event based on a data after a last storage time of the one or more backend computing devices.

12. A method for database failure management performed by a server for database failure management, comprising:
receiving a backend failure information for at least one of one or more backend computing devices;
receiving a request from a client computing device via a network after receiving the backend failure information;
verifying whether the request is a request corresponding to a failed backend based on a backend list received from a frontend computing device;
verifying a type of the request if the request is a request corresponding to a failed backend;
determining a method of processing the request corresponding to the failed backend based on the type of the request, while backend failure occurs;
receiving a recovery information about the failed backend; and
processing the request received from the client computing device after receiving the recovery information about the failed backend.

13. A server for database failure management, comprising:
a processor including one or more cores; and
a memory;
wherein the processor is configured to
receive a backend failure information for at least one of a one or more backend computing devices;
receive a request from a client computing device via a network after receiving the backend failure information;
verify whether the request is a request corresponding to a failed backend based on a backend list received from a frontend computing device;
verify a type of the request if the request is a request corresponding to a failed backend;
determine a method of processing the request corresponding to the failed backend based on the type of the request, while backend failure occurs;
receive a re

Assignees

• Tmaxdata Co Ltd
• Tmax Data Co Ltd

Inventors

• Kyeong Kiryong
• Kim Wanho
• Lee Dongjae
• Heo Stellar

Classifications

• G06F2201/82

  Solving problems relating to consistency · CPC title

• G06F2201/80

  Database-specific techniques · CPC title

• G06F11/203 Primary

  using migration · CPC title

• G06F16/211 Primary

  Schema design and management · CPC title

• G06F11/1466 Primary

  to make the backup process non-disruptive · CPC title