KR102351220B1 - Database duplexing method for efficient server load distribution when processing large amounts of data and apparatus thereof - Google Patents

Abstract

Provided is a method that is performed by a device including a plurality of databases (DBs), in which the method includes: distributing acquired data to generate first data and second data; storing the first data in a first master DB of a first replica set; duplicating the first data by the first master DB to transmit the first data to a first slave DB of the first replica set; storing the first data by the first slave DB; loading the first data from the first slave DB; storing the second data in a second master DB of a second replica set; duplicating the second data by the second master DB to transmit the second data to a second slave DB of the second replica set; storing the second data by the second slave DB; and loading the duplicated second data from the second slave DB, wherein the first replica set includes the first master DB, the first slave DB, and a first manager, the second replica set includes the second master DB, the second slave DB, and a second manager, the first manager is formed in the same server as the second master DB or the second slave DB, so that the first replica set and the second replica set are configured in a complementary manner, or the second manager is formed in the same server as the first master DB or the first slave DB, so that the first replica set and the second replica set are configured in a complementary manner. The present invention can minimize the delay caused by the disk input/output (I/O) of the DB.

Description

A DB duplication method for efficient server load balancing when processing large amounts of data and a device supporting it

The present invention relates to a method of duplicating a database for efficient server load balancing when processing large amounts of data.

In-memory databases (DB: database) are generally developed for the purpose of storing small-capacity data in a cache, and the reality is that they are not suitable for processing large amounts of data.

For this reason, DBMS developers are supporting the configuration of replica sets for HA (high availability) in order to process big data or large amounts of data.

US Patent Application Publication No. 14/145,444, 2013.12.31 Patent Publication No. 10-2020-0100173, 2018.07.06

A DBMS (database management system) supports to automatically distribute and store data in a replica set. However, when the amount of input data is very large, it takes more time for the DBMS to determine, divide, and store the data, so performance is lower than when using the standalone method or only one replica set. .

An object of the present invention is to provide a configuration of a DB replica set to solve such a problem. Specifically, the present invention allows the master DB and the slave DB included in the DB replica set to be included in one server, respectively, for efficient load balancing.

The problems to be solved by the present invention are not limited to the problems mentioned above, and other problems not mentioned will be clearly understood by those skilled in the art from the following description.

According to an embodiment of the present invention for solving the above problems, in a method performed by an apparatus including a plurality of databases (DB), the obtained data is distributed to generate first data and second data, ; storing the first data in a first master DB of the first replica set; the first master DB duplicates the first data and transmits it to a first slave DB of the first replica set; the first slave DB stores the first data; loading the first data from the first slave DB; store the second data in a second master DB of the second replica set; the second master DB duplicates the second data and transmits it to a second slave DB of the second replica set; the second slave DB stores the second data; and loading the duplicated second data from the second slave DB.

The first replica set includes the first master DB, the first slave DB, and a first manager, and the second replica set includes the second master DB, the second slave DB, and a second manager can do.

The first manager may be formed in the same server as the second master DB or the second slave DB, so that the first replica set and the second replica set are complementary.

The second manager may be formed in the same server as the first master DB or the first slave DB, so that the first replica set and the second replica set are complementary.

When the first manager is unavailable, the first master DB and the first slave DB may be connected to the second manager.

When the second manager is unavailable, the second master DB and the second slave DB may be connected to the first manager.

Storing the first data in the first master DB may further include storing in a binary log file of the first master DB.

Storing the first data in the first slave DB may further include storing in a relay log file of the first slave DB.

If the first replica set is unavailable, the first data may be processed in the second replica set.

If the second replica set is unavailable, the second data may be processed in the first replica set.

The first master DB, the first slave DB, the second master DB, and the second slave DB may be configured not to be configured in the same server.

The method may include complementarily configuring an N-1 th replica set and an N th replica set.

Complementarily configuring the N-1 th replica set and the N th replica set includes: configuring the master DB or slave DB of the N th replica set and the manager of the N-1 th replica set to be included in the same server, or , or configuring the master DB or slave DB of the N-1 th replica set and the manager of the N th replica set to be included in the same server.

The method may further include expanding the replica set.

Expanding the replica set may include expanding the replica set in a number of multiples of 2 so that four servers are allocated per two replica sets.

storing the first data in the first master DB; loading the first data from the first slave DB; storing the second data in the second master DB; and loading the second data from the second slave DB may be performed through the DB connector.

According to an embodiment of the present invention, it is possible to provide an apparatus including a plurality of databases (databases, DBs).

The apparatus includes a memory configured to store data; and one or more processors connected to the memory.

The one or more processors are configured to: distribute the acquired data to generate first data and second data; storing the first data in a first master DB of the first replica set; the first master DB duplicates the first data and transmits it to a first slave DB of the first replica set; the first slave DB stores the first data; loading the first data from the first slave DB; store the second data in a second master DB of the second replica set; the second master DB duplicates the second data and transmits it to a second slave DB of the second replica set; the second slave DB stores the second data; and loading the duplicated second data from the second slave DB.

The first replica set may include the first master DB, the first slave DB, and a first manager.

The second replica set may include the second master DB, the second slave DB, and a second manager.

The one or more processors are configured to: configure a first replica set including a first master DB, a first slave DB, and a first manager; and a second replica set including a second master DB, a second slave DB, and a second manager.

The first manager is formed in the same server as the second master DB or the second slave DB so that the first replica set and the second replica set are complementary, or the second manager is the first master DB It may be formed in the same server as the DB or the first slave DB, so that the first replica set and the second replica set are complementary.

Other specific details of the invention are included in the detailed description and drawings.

According to the present invention, a large amount of data is divided and stored in at least two or more replica sets of the DBMS, thereby effectively balancing the server load and minimizing the delay due to the DB's disk I/O (input/output, input/output). .

Effects of the present invention are not limited to the effects mentioned above, and other effects not mentioned will be clearly understood by those skilled in the art from the following description.

BRIEF DESCRIPTION OF THE DRAWINGS The accompanying drawings, which are included as part of the detailed description to aid understanding of the present invention, provide various embodiments and, together with the detailed description, explain technical features of the various embodiments.
1 is a diagram illustrating a database system.
2 is a diagram illustrating an example of a master-slave structure of a database.
3 is a diagram illustrating two replica sets including a master DB and a slave DB according to the present invention.
4 is a diagram illustrating an embodiment of the DBMS supporting to automatically divide and store data in a replica set.
5 is a diagram illustrating an embodiment of a case in which load balancing processing is performed using a replica set according to the present invention.
6 is a diagram illustrating another embodiment of a case in which load balancing processing is performed using a replica set rather than a DBMS own function according to the present invention.
7 is a diagram illustrating a process of load balancing processing using a replica set according to the present invention.
8 is a diagram illustrating an example of an apparatus in which the present invention may be implemented.

Advantages and features of the present invention and methods of achieving them will become apparent with reference to the embodiments described below in detail in conjunction with the accompanying drawings. However, the present invention is not limited to the embodiments disclosed below, but may be implemented in various different forms, and only the present embodiments allow the disclosure of the present invention to be complete, and those of ordinary skill in the art to which the present invention pertains. It is provided to fully understand the scope of the present invention to those skilled in the art, and the present invention is only defined by the scope of the claims.

The terminology used herein is for the purpose of describing the embodiments and is not intended to limit the present invention. In this specification, the singular also includes the plural unless specifically stated otherwise in the phrase. As used herein, “comprises” and/or “comprising” does not exclude the presence or addition of one or more other components in addition to the stated components. Like reference numerals refer to like elements throughout, and "and/or" includes each and every combination of one or more of the recited elements. Although "first", "second", etc. are used to describe various elements, these elements are not limited by these terms, of course. These terms are only used to distinguish one component from another. Accordingly, it goes without saying that the first component mentioned below may be the second component within the spirit of the present invention.

Unless otherwise defined, all terms (including technical and scientific terms) used herein will have the meaning commonly understood by those of ordinary skill in the art to which this invention belongs. In addition, terms defined in a commonly used dictionary are not to be interpreted ideally or excessively unless specifically defined explicitly.

Spatially relative terms "below", "beneath", "lower", "above", "upper", etc. It can be used to easily describe the correlation between a component and other components. Spatially relative terms should be understood as terms including different directions of components during use or operation in addition to the directions shown in the drawings. For example, when a component shown in the drawing is turned over, a component described as “beneath” or “beneath” of another component may be placed “above” of the other component. can Accordingly, the exemplary term “below” may include both directions below and above. Components may also be oriented in other orientations, and thus spatially relative terms may be interpreted according to orientation.

Hereinafter, preferred embodiments according to the present specification will be described in detail with reference to the accompanying drawings. DETAILED DESCRIPTION The detailed description set forth below in conjunction with the appended drawings is intended to describe exemplary embodiments of various embodiments, and is not intended to represent the only embodiments.

Definitions of terms used in the present invention are as follows.

DBS (database system): A database system is a system that stores data in a database, manages the stored data, and creates necessary information for the organization. The database system of the present invention serves to provide information necessary for an organization using a database and a database management system.

DB (database): Generally, a database is defined as a set of operational data that is integrated and stored so that it can be shared and used by multiple users in a specific organization. The database plays a role of managing complex data instead of extracting useful information accurately.

DBMS (database management system): A database management system is software that manages a database and provides an environment where applications can share and use the database. DBMS provides a framework for building a database and provides functions for efficiently retrieving and storing data. DBMS integrates the scattered data for each program, and each program shares the integrated data so that information can be systematically utilized. A general type of DBMS is a relational database management system (RDBMS), and the standardized user and program interface of the RDBMS is called SQL (structured query language).

SQL (structured query language): SQL is a language used to build and utilize databases. SQL is largely divided into Data Definition Language (DDL) and Data Manipulation Language (DML).

NoSQL (non SQL, not only SQL): As a non-relational DBMS for big data processing, it can flexibly process large-scale data. NoSQL optimizes key values for simple search and addition operations in a distributed environment without a schema such as table-column, and has excellent latency and throughput. A NoSQL database is a highly optimized key-value storage for simple search and append operations, with the goal of yielding significant performance gains in terms of latency and throughput. NoSQL databases are widely used for commercial use of big data and real-time web applications. Also, the NoSQL system is sometimes called "Not only SQL" because it emphasizes the fact that a SQL-like query language can be used.

DB clustering: DB clustering is a method of grouping multiple DBs to build a horizontal structure and use them as one.

DB replication: DB replication is a method of replicating data by building multiple DBs in a vertical structure (Master-Slave) according to authority. In the case of the clustering method discussed above, several servers are used, but in the end, a problem occurs because there is only one physical storage. Replication also replicates storage along with the server to solve this problem. The replicated DB can be divided into master and slave roles.

1 is a diagram illustrating a database system.

The database system includes a database (DB), a database management system (DBMS), a database language, and a user, as shown in FIG. 1 . (Or, in addition to the database and the database management system, it consists of the user, the data language used by the user to access the database, and the computer that installs the database and the database management system and is responsible for data processing operations.)

A database means a set of integrated and stored operational data with minimal redundancy to be shared by multiple application systems of an organization.

A database language is a programming language used to build, manipulate, and retrieve databases.

Users are largely 1) a database administrator (DBA) who manages and operates a database system, 2) a database application programmer who develops a database application program using a development tool, and 3) a user who uses the database. classified as users (normal users or end users).

The database management system (DBMS) acts as an intermediary between the application program and the database, and thus the database is manipulated and managed through the DBMS rather than being directly manipulated by the application programs.

2 is a diagram illustrating an example of a master-slave structure of a database.

2, in order to provide a replica set for high availability of the DB, a method of storing the same data by dividing two or more DBs into a master and a slave is disclosed. High availability of DB means multiplexing the equipment related to the database in order to increase the operation rate from system failure.

Referring to FIG. 2 , the DB high availability function is implemented through a replica set configured as a manager, a master DB, and a slave DB by configuring two or more DBs on different servers.

The manager plays a role in selecting the master DB by periodically checking the status of the master DB and the slave DB.

In general, the master DB is used when data is changed such as insert/delete/update, and the slave DB is used for data inquiry (selection) processing. Therefore, a lot of disk input/output occurs in the master DB and the slave DB.

According to an exemplary embodiment, the number of master DBs or slave DBs may be one or two or more.

2 shows a case of balancing the load using the DBMS's own function.

When the master DB receives an insert/delete/update query request, it creates a binarylog to record changes and can deliver change records or changed data to the slave DB. The data of the master DB is replicated and stored in the slave DB, and the slave DB is in charge of data read or select requests.

In this way, the DBMS can distribute the DB load and improve read performance by sharing the select request, which accounts for most of the query, by the slave DB.

Depending on the DBMS, the above-described operation may be performed automatically. This is to ensure that at least two data sets can be maintained by automatically replicating data to the slave DB in real time when data is inserted into the master DB.

3 is a diagram illustrating two replica sets including a master DB and a slave DB according to the present invention.

Referring to FIG. 3 , the DBMS includes two replica sets, and each replica set may include a master DB, a slave DB, and a manager.

DBMS supports to automatically divide and store data in each replica set.

Inserting or selecting data into each replica set is shown to be processed through a DB connector, but without a DB connector, the processor (or processing system) directly sends data from the slave DB of the replica set. It is also possible to select (SELECT) or insert (INSERT) data into the master DB of the replica set.

4 is a diagram illustrating an embodiment of a process in which data is automatically divided and stored in a replica set in a DBMS.

Referring to FIG. 4 , one master DB, one slave DB, and one manager are assigned to each of six servers, and the first replica set (DB Replica Set #1) and the second replica set (DB Replica Set #2) are respectively the master It can include DB, slave DB, and manager.

The DB connector/proxy of FIG. 4 is a server that relays resource requests to other servers in a computer network, and serves to reduce the complexity of services by simplifying and encapsulating the structure of a distributed system.

The processing system may process the data, store it in the DB connector/proxy, and read the data stored in the DB connector/proxy.

Specifically, the processing system primarily processes data, and stores the primary processed data (hereinafter, first data) in the master DB of the first replica set through a DB connector/proxy (S401).

The master DB stores the first data. In addition, the master DB replicates the first data and transmits it to the slave DB of the first replica set. The slave DB stores the first data received from the master DB.

The processing system reads (read, select) the first data stored in the slave DB through the DB connector/proxy (S403).

The processing system performs secondary processing of data, and stores the secondary processed data (hereinafter, second data) in the master DB of the second replica set through the DB connector/proxy (S405).

The master DB replicates the second data and delivers it to the slave DB of the second replica set, and the slave DB stores the second data.

The master DB stores the second data. In addition, the master DB replicates the second data and transmits it to the slave DB of the second replica set. The slave DB stores the second data received from the master DB.

The processing system reads the second data stored in the slave DB through the DB connector/proxy (read, select) (S407).

In the above process, the manager periodically checks the status of the master DB and the slave DB, and plays a role in continuously updating the target to be the master DB.

In the above process, there may be cases in which the manager cannot be used, such as when an error occurs in the manager or when the manager cannot be connected. In this way, when the manager cannot be used, the DB connector can perform the role of the manager instead.

Through the above process, performance can be improved by balancing the DB load by using two or more DB replica sets.

Hereinafter, when two or more DB replica sets are used, another method for improving performance through DB load balancing will be disclosed.

5 is a diagram illustrating an embodiment of a case in which load balancing processing is performed using a replica set according to the present invention.

5 illustrates an example of distributing data into first data and second data in a processing system.

The first data is input (insert, write) into the master DB (hereinafter, the first master DB) of the first replica set (DB Replica Set #1) (S501).

The first master DB stores the first data, duplicates the first data, and transfers the first data to the slave DB (hereinafter, referred to as the first slave DB) of the first replica set. The first master DB may store the first data in a binary log file.

The first slave DB stores the first data received from the first master DB, and when the processing system reads the first data, it reads from the first slave DB (read, select) (S503). The first slave DB may store the first data in a relay log file.

The second data is input to the master DB (hereinafter referred to as the second master DB) of the second replica set (DB Replica Set #2) (S505).

The second master DB stores the second data, replicates the second data, and transfers the second data to the slave DB (hereinafter, referred to as the second slave DB) of the second replica set.

The second slave DB stores the second data received from the second master DB, and the processing system reads the second data from the second slave DB (read, select) (S507).

In the above process, if an error occurs in the DBMS and the first replica set cannot be used (broken) or the first manager cannot be used, the first master DB and the first slave DB are connected to the second manager, and the second replica It may be processed (or operated) within a set. In addition, in the above process, when the second replica set cannot be used or the second manager cannot be used, the second master DB and the second slave DB are connected to the first manager and processed in the second replica set. .

Such a connection and processing process is temporary, and when the replica set or manager can be used again, the original connection form can be restored.

Although the DB connector/proxy is omitted in FIG. 5, a DB connector/proxy may also be configured between the processing system and the replica set.

When the manager cannot be used in the above process, the DB connector may play a role of connecting the master DB and the slave DB, and may play a role of connecting the processing system and the master DB and the slave DB.

Such a connection is temporary, and when the manager can be used again, it is connected to the manager again and restored to its original form.

A master DB configured to insert/delete/update data and a slave DB configured to inquire/select data require a lot of computing power in terms of data throughput. In contrast, the manager periodically checks the status of the master DB and the slave DB, and only continuously updates the target to be the master DB, so the demand for computing power is relatively small. Therefore, in order to consider the load for data processing, the load of the master DB and the slave DB has priority over the load of the manager.

5 , the master DB, the slave DB, and the manager are appropriately distributed to a plurality of servers, but concentration of the load on one server can be prevented by not arranging both the master DB and the slave DB on one server. , a distribution of computing power and load can be achieved. Therefore, there is an effect that load balancing between servers is possible without using a DBMS by using a replica set.

6 is a diagram illustrating another embodiment of a case in which load balancing processing is performed using a replica set rather than a DBMS own function according to the present invention.

6 is a conceptual diagram illustrating the configuration of a replica set.

When configuring a DB replica set, one master DB and one slave DB can be assigned to each server, but a manager can be assigned (formed) to the same server as the master DB and slave DB.

Therefore, when configuring one more replica set, two more servers are required.

Alternatively, two replica sets are required to complement each of the master DB, the slave DB, and the manager, and in this case, 4 more servers are required for each of the two replica sets.

Since the data processing process is substantially the same as that of FIG. 5, it is omitted.

7 is a diagram illustrating a process of load balancing processing using a replica set according to the present invention.

The processing system (or processor) distributes and generates the acquired data as first data and second data.

The generated first data is input (write) to the master DB of the first replica set (S701).

The master DB of the first replica set stores and replicates the first data (S703). The first data is stored in the binary log file of the master DB, and the duplicated first data is transmitted to the slave DB.

The slave DB of the first replica set stores the duplicated first data (S705). The first data is stored in the relay log file of the slave DB.

When data is read, first data is loaded from the slave DB of the first replica set (read) (S707). That is, the processing system selects and reads the first data among the data stored in the slave DB.

The second data is input to the master DB of the second replica set (S709).

The master DB of the second replica set stores and replicates the second data (S711). The replicated first data is transmitted to the slave DB.

The slave DB of the second replica set stores the duplicated second data (S713).

When data is read, second data is loaded from the slave DB of the second replica set (S715).

Master DB and slave DB cannot be formed (configured) on the same server. This is because the master DB configured to insert/delete/update data and the slave DB configured to inquire/select data require a lot of computing power in terms of data throughput. Therefore, the master DB and slave DB included in one replica set can be formed on different servers, and only the manager of the other replica set can be formed on the same server as the master DB or slave DB included in one replica set.

For example, the master DB and the slave DB of the first replica set are formed on different servers. The master DB and the slave DB of the second replica set are not formed in the server where the master DB and the slave DB of the first replica set are formed, but are formed in another server. Since the manager may be formed in the same server as the master DB or the slave DB, the manager of the second replica set may be formed in the same server as the master DB or the slave DB of the first replica set.

In order to minimize the number of servers required to form the replica set, after the first replica set including the master DB, the slave DB, and the manager is formed, the second replica set may be formed in a form complementary to the first replica set. .

For example, the server in which the master DB or the slave DB of the first replica set is formed may include a manager of the second replica set. In addition, the server in which the master DB or the slave DB of the second replica set is formed may include a manager of the third replica set. The server in which the master DB or the slave DB of the N-th replica set is formed may include the manager of the N-1th replica set. In the present invention, a configuration including a master DB, a slave DB, and a manager is described as an embodiment of the same replica set. Since this is an embodiment, a plurality of master DBs, a plurality of slave DBs, or a plurality of managers may be included in the same replica set.

In the present invention, only the process of "1) storing data after primary processing and reading the primary processed data again, 2) storing data after secondary processing and reading the secondary processed data" has been described, but When processing data or large amounts of data, a larger number of DB servers may be required.

According to the amount of data, it is possible to repeatedly process data by continuously alternately using the first replica set and the second replica set.

In the case of a system where the amount of data that needs to be stored continuously increases, the DB can be increased by continuously adding replica sets.

According to various embodiments of the present invention described above, there is an effect of improving overall system performance by appropriately distributing data to a plurality of DB replica sets.

8 is a diagram illustrating an example of an apparatus in which the present invention can be implemented.

Referring to FIG. 8 , the device may include an input/output unit 310 , a communication unit 320 , a sensing unit 330 , a database 340 , and a processor 350 .

The input/output unit 310 may be various interfaces or connection ports that receive user input or output information to the user. The input/output unit 310 may be divided into an input module and an output module, and the input module receives a user input from a user. The user input may be made in various forms including a key input, a touch input, and a voice input. Examples of input modules that can receive such user input include a traditional keypad, keyboard, and mouse, as well as a touch sensor that detects a user's touch, a microphone that receives a voice signal, a camera that recognizes gestures through image recognition, A proximity sensor composed of an illuminance sensor or infrared sensor that detects a user's approach, a motion sensor that recognizes a user's motion through an acceleration sensor or a gyro sensor, and various other input means for sensing or receiving various types of user input It is a comprehensive concept that includes all Here, the touch sensor may be implemented as a piezoelectric or capacitive touch sensor for detecting a touch through a touch panel or a touch film attached to the display panel, an optical touch sensor for detecting a touch by an optical method, and the like. In addition, the input module may be implemented in the form of an input interface (USB port, PS/2 port, etc.) that connects an external input device that receives a user input instead of a device that detects a user input by itself. In addition, the output module can output various information and provide it to the user. An output module is a comprehensive concept including a display that outputs an image, a speaker that outputs a sound (and/or an amplifier connected thereto), a haptic device that generates vibration, and other various types of output means. In addition, the output module may be implemented in the form of a port-type output interface for connecting the above-described individual output means.

For example, the display-type output module may display text, still images, and moving images. The display includes a liquid crystal display (LCD), a light emitting diode (LED) display, an organic light emitting diode (OLED) display, a flat panel display (FPD), and a transparent display. display), a curved display, a flexible display, a three-dimensional display, a holographic display, a projector, and various types of devices capable of performing other image output functions. It is a concept meaning an image display device in a broad sense that includes all. Such a display may be in the form of a touch display integrally formed with the touch sensor of the input module.

The communication unit 320 may communicate with an external device. Accordingly, the device (device) may transmit/receive information to and from an external device through the communication unit. For example, the device may communicate with an external device so that information stored and generated in the illegal parking/stop warning system is shared using the communication unit.

Here, communication, that is, transmission and reception of data may be performed by wire or wirelessly. To this end, the communication unit includes a wired communication module that accesses the Internet through a local area network (LAN), a mobile communication module that accesses a mobile communication network through a mobile communication base station and transmits and receives data, and a wireless local area network (WLAN) such as Wi-Fi. A short-distance communication module using an area network communication method or a wireless personal area network (WPAN) communication method such as Bluetooth or Zigbee, or a global navigation satellite system (GNSS) such as GPS (Global Positioning System) ) using a satellite communication module or a combination thereof. A wireless communication technology used for communication may include a Narrowband Internet of Things (NB-IoT) for low-power communication. In this case, for example, NB-IoT technology may be an example of LPWAN (Low Power Wide Area Network) technology, and may be implemented in standards such as LTE Cat (category) NB1 and/or LTE Cat NB2, It is not limited. Additionally or alternatively, a wireless communication technology implemented in a wireless device according to various embodiments may perform communication based on LTE-M technology. In this case, as an example, the LTE-M technology may be an example of an LPWAN technology, and may be called by various names such as enhanced machine type communication (eMTC). For example, LTE-M technology is 1) LTE CAT 0, 2) LTE Cat M1, 3) LTE Cat M2, 4) LTE non-BL (non-Bandwidth Limited), 5) LTE-MTC, 6) LTE Machine Type Communication, and/or 7) may be implemented in at least one of various standards such as LTE M, and is not limited to the above-described name. Additionally or alternatively, a wireless communication technology implemented in a wireless device according to various embodiments may include at least one of ZigBee, Bluetooth, and Low Power Wide Area Network (LPWAN) in consideration of low power communication. may include, and is not limited to the above-mentioned names. For example, the ZigBee technology can create PAN (personal area networks) related to small/low-power digital communication based on various standards such as IEEE 802.15.4, and can be called by various names.

The identification unit 330 includes a camera that recognizes an object through image recognition, a detection sensor that detects an object approach, and various types of identification/sensing means that detect or receive various types of external inputs. could be a concept. The identification unit may be understood to be the same as the input module in the input/output unit 310 and/or may be understood to be separate from the input module. The identification unit 330 includes a geomagnetic sensor, an acceleration sensor, a temperature/humidity sensor, an infrared sensor, a gyroscope sensor, a location sensor (eg, GPS), a barometric pressure sensor, a proximity sensor, and an RGB sensor (illuminance). sensor), a lidar sensor, an illuminance sensor, and a current sensor may further include, but is not limited thereto. Since a function of each sensor can be intuitively inferred from the name of a person skilled in the art, a detailed description thereof will be omitted.

The database 340 may store various types of information. A database can store data temporarily or semi-permanently. For example, in the database, an operating program (OS) for driving the first device and/or the second device, data for hosting a website or data about an application (eg, a web application), etc. This can be saved. In addition, the database may store the modules in the form of computer code as described above.

Examples of the database 340 include a hard disk (HDD), a solid state drive (SSD), a flash memory, a read-only memory (ROM), a random access memory (RAM), and the like. This can be. Such a database may be provided in a built-in type or a detachable type.

The processor 350 controls the overall operation of the device (device). To this end, the processor 350 may perform calculation and processing of various types of information and may control operations of components of the first device and/or the second device. For example, the processor 350 may execute a program or application for a method of performing large-scale data processing by duplicating a database to achieve efficient server load balancing. The processor 350 may be implemented as a computer or a similar device according to hardware software or a combination thereof. In terms of hardware, the processor 350 may be provided in the form of an electronic circuit that processes electrical signals to perform a control function, and in software, it may be provided in the form of a program for driving the processor 240 in hardware. Meanwhile, in the following description, unless otherwise specified, the operations of the first device and/or the second device may be interpreted as being performed under the control of the processor 350 . That is, if the modules required for the method of performing load balancing processing using the database replica set to minimize the disk I/O delay of the database 340 when performing repeated operation and storage of large data are executed, the module These may be interpreted as controlling the processor 350 to perform the following operations on the first device and/or the second device.

In summary, the present invention may be implemented through various means. For example, various embodiments may be implemented by hardware, firmware, software, or a combination thereof.

In the case of implementation by hardware, the method according to the present invention may include one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays), a processor, a controller, a microcontroller, a microprocessor, and the like.

In the case of implementation by firmware or software, the method according to the present invention may be implemented in the form of a module, procedure, or function that performs the functions or operations described below. For example, the software code may be stored in a memory and driven by a processor. The memory may be located inside or outside the processor, and data may be exchanged with the processor by various known means. The steps of the method or algorithm described in relation to the embodiment of the present invention may be implemented directly in hardware, as a software module executed by hardware, or by a combination thereof. A software module may include random access memory (RAM), read only memory (ROM), erasable programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), flash memory, hard disk, removable disk, CD-ROM, or It may reside in any type of computer-readable recording medium well known in the art to which the present invention pertains.

According to the present invention, the database 340 has a master-slave architecture in the present invention, and the replica set includes a master DB and a slave DB. In this case, DBs for each server should be configured so that they do not overlap. The processor 350 distributes data, inputs it to the master DB of each replica set, and reads data from the slave DB of each replica set.

As mentioned above, although embodiments of the present invention have been described with reference to the accompanying drawings, those skilled in the art to which the present invention pertains know that the present invention may be embodied in other specific forms without changing the technical spirit or essential features thereof. you will be able to understand Therefore, it should be understood that the embodiments described above are illustrative in all respects and not restrictive.

310: input / output unit
320: communication unit
330: identification unit
340: database
350: processor

Claims (11)

In a method performed by an apparatus including a plurality of databases (database, DB),
distributing the acquired data to generate first data and second data;
storing the first data in a first master DB of a first replica set;
the first master DB duplicates the first data and transmits it to a first slave DB of the first replica set;
the first slave DB stores the first data;
loading the first data from the first slave DB;
store the second data in a second master DB of a second replica set;
the second master DB duplicates the second data and transmits it to a second slave DB of the second replica set;
the second slave DB stores the second data; and
Comprising loading the duplicated second data from the second slave DB,
The first replica set includes the first master DB, the first slave DB, and a first manager,
The second replica set includes the second master DB, the second slave DB, and a second manager,
The first manager is formed in the same server as the second master DB or the second slave DB, so that the first replica set and the second replica set are complementary; or
the second manager is formed in the same server as the first master DB or the first slave DB, so that the first replica set and the second replica set are complementary;
Further comprising adding a replica set,
Expanding the replica set is characterized in that the expansion of the replica set in the number of units of multiples of 2 so that 4 servers are allocated per 2 replica sets. According to claim 1,
When the first manager or the second manager cannot be used, the connection between the first master DB and the first slave DB or the connection between the second master DB and the second slave DB is performed using a DB connector. A method, characterized in that it is made. According to claim 1,
When the first manager is unavailable, the first master DB and the first slave DB are connected to the second manager, and
When the second manager is unavailable, the second master DB and the second slave DB are connected to the first manager. According to claim 1,
Storing the first data in the first master DB further comprises storing in a binary log file of the first master DB. According to claim 1,
Storing the first data in the first slave DB further comprises storing in a relay log file of the first slave DB. According to claim 1,
if the first set of replicas is not available, the first data is processed in the second set of replicas, and
and if the second set of replicas is not available, the second data is processed within the first set of replicas. According to claim 1,
The method, characterized in that the first master DB, the first slave DB, the second master DB, and the second slave DB are configured not to be configured in the same server. According to claim 1,
Complementarily configuring the N-1 th replica set and the N th replica set,
Complementarily configuring the N-1 th replica set and the N th replica set comprises:
The master DB or slave DB of the Nth replica set and the manager of the N-1th replica set are configured to be included in the same server, or
and configuring the master DB or slave DB of the N-1 th replica set and the manager of the N th replica set to be included in the same server. delete 3. The method of claim 2,
storing the first data in the first master DB;
loading the first data from the first slave DB;
storing the second data in the second master DB; and
The method further characterized in that the loading of the second data from the second slave DB is performed through the DB connector. In the device including a plurality of databases (database, DB),
a memory configured to store data; and
one or more processors coupled to the memory;
The one or more processors include:
distributing the acquired data to generate first data and second data;
storing the first data in a first master DB of a first replica set;
the first master DB duplicates the first data and transmits it to a first slave DB of the first replica set;
the first slave DB stores the first data;
loading the first data from the first slave DB;
store the second data in a second master DB of a second replica set;
the second master DB duplicates the second data and transmits it to a second slave DB of the second replica set;
the second slave DB stores the second data; and
configured to load the duplicated second data from the second slave DB,
The first replica set includes the first master DB, the first slave DB, and a first manager,
The second replica set includes the second master DB, the second slave DB, and a second manager,
The first manager is formed in the same server as the second master DB or the second slave DB, so that the first replica set and the second replica set are complementary; or
the second manager is formed in the same server as the first master DB or the first slave DB, so that the first replica set and the second replica set are complementary;
Further comprising adding a replica set,
The extension of the replica set is characterized in that the extension of the replica set in a number of multiples of 2 so that four servers are allocated per two replica sets.

Images