CN108093094B

CN108093094B - Database instance access method, device, system, storage medium and equipment

Info

Publication number: CN108093094B
Application number: CN201711294064.7A
Authority: CN
Inventors: 黄辉; 王甲坤; 胡彬
Original assignee: Tencent Technology Shenzhen Co Ltd; Tencent Cloud Computing Beijing Co Ltd
Current assignee: Tencent Technology Shenzhen Co Ltd; Tencent Cloud Computing Beijing Co Ltd
Priority date: 2017-12-08
Filing date: 2017-12-08
Publication date: 2021-05-28
Anticipated expiration: 2037-12-08
Also published as: CN108093094A

Abstract

The invention relates to a method, a device, a system, a storage medium and equipment for accessing a database instance, wherein the method for accessing the database instance comprises the following steps: acquiring a database instance access request; extracting a virtual connection address from the database instance access request; the virtual connection address corresponds to a target database instance requested to be accessed by the database instance access request; acquiring an entity connection address which has a mapping relation with the virtual connection address; determining a database type to which the target database instance belongs; and accessing the target database instance through the database plug-in matched with the database type according to the entity connection address. The scheme provided by the application realizes access among different database instances.

Description

Database instance access method, device, system, storage medium and equipment

Technical Field

The invention relates to the technical field of computers, in particular to a database instance access method, a database instance access device, a database instance access system, a database instance access storage medium and a database instance access device.

Background

With the rapid development of computer technology, the data scale is rapidly increasing. More and more users choose to perform data processing through data services provided by database servers. Currently, a database instance on a database server provides data services for a user by connecting addresses.

However, in the conventional database access form, the virtual connection address provided by each database instance externally only allows the user to separately access each database instance externally, thereby causing a problem that different database instances cannot access each other.

Disclosure of Invention

Based on this, it is necessary to provide a database instance access method, apparatus, system, storage medium, and device for solving the problem that different database instances cannot be accessed to each other at present.

A database instance access method, comprising:

acquiring a database instance access request;

extracting a virtual connection address from the database instance access request; the virtual connection address corresponds to a target database instance requested to be accessed by the database instance access request;

acquiring an entity connection address which has a mapping relation with the virtual connection address;

determining a database type to which the target database instance belongs;

and accessing the target database instance through the database plug-in matched with the database type according to the entity connection address.

A database instance access device, comprising:

the first acquisition module is used for acquiring a database instance access request;

the extraction module is used for extracting a virtual connection address from the database instance access request; the virtual connection address corresponds to a target database instance requested to be accessed by the database instance access request;

the second acquisition module is used for acquiring the entity connection address which has a mapping relation with the virtual connection address;

the determining module is used for determining the database type of the target database instance;

and the access module is used for accessing the target database instance through the database plug-in matched with the database type according to the entity connection address.

A database instance access system comprising a node server and a management server, wherein:

the node server is used for acquiring a database instance access request; extracting a virtual connection address from the database instance access request; the virtual connection address corresponds to a target database instance requested to be accessed by the database instance access request;

the node server is also used for sending an address mapping request which is corresponding to the source host address and the virtual connection address to the management server; the source host address corresponds to a source database instance; the source database instance runs on the node server;

the management server is used for mapping the source host address and the virtual connection address together into an entity connection address; feeding back the entity connection address to the node server according to the address mapping request;

the node server is also used for determining the database type of the target database instance; and accessing the target database instance through the database plug-in matched with the database type according to the entity connection address.

A computer-readable storage medium having stored thereon a computer program which, when executed by a processor, causes the processor to perform the steps of:

acquiring a database instance access request;

determining a database type to which the target database instance belongs;

A computer device comprising a memory and a processor, the memory having stored therein a computer program that, when executed by the processor, causes the processor to perform the steps of:

acquiring a database instance access request;

determining a database type to which the target database instance belongs;

According to the database instance access method, the device, the system, the storage medium and the computer equipment, when the data database instance access request is locally obtained, the virtual connection address corresponding to the target database instance which is intended to be accessed can be directly extracted, the entity connection address which has a mapping relation with the virtual connection address and can be accessed among the database instances is further obtained, and the database type to which the target database instance belongs is determined, so that the data service provided by accessing the target database instance through the database plug-in matched with the database type according to the entity connection address can be realized, and the access among different database instances is realized.

A database instance management method, comprising:

receiving an address mapping request corresponding to the address of the source host and the virtual connection address together; the source host address corresponds to a source database instance; the virtual connection address corresponds to a target database instance;

mapping the source host address and the virtual connection address together into a physical connection address;

feeding back the entity connection address according to the address mapping request; the entity connection address is used for indicating the source database instance to access the target database instance according to the entity connection address.

A database instance management apparatus, comprising:

the receiving module is used for receiving an address mapping request jointly corresponding to a source host address and a virtual connection address; the source host address corresponds to a source database instance; the virtual connection address corresponds to a target database instance;

a mapping module, configured to map the source host address and the virtual connection address together into an entity connection address;

a feedback module, configured to feed back the entity connection address according to the address mapping request; the entity connection address is used for indicating the source database instance to access the target database instance according to the entity connection address.

According to the database instance management method, the device, the storage medium and the computer equipment, after the address mapping request is received, the source host address and the virtual connection address corresponding to the address mapping request can be obtained, the source host address and the virtual connection address are mapped into the entity connection address which can be accessed between the database instances together, the source database instance can access the data service provided by the target database instance according to the entity connection address, and access between different database instances is achieved.

Drawings

FIG. 1 is a diagram of an example application environment for a database access method in one embodiment;

FIG. 2 is a schematic flow chart diagram illustrating a database instance access method in one embodiment;

FIG. 3 is a schematic diagram illustrating the establishment of a database instance access connection in one embodiment;

FIG. 4 is a timing diagram illustrating updating of connection parameters in one embodiment;

FIG. 5 is a flowchart illustrating a method for managing database instances in one embodiment;

FIG. 6 is a schematic diagram of an example database access in one embodiment;

FIG. 7 is a schematic diagram of a database instance access connection update in one embodiment;

FIG. 8 is a timing diagram of deletion of connection parameters in one embodiment;

FIG. 9 is a block diagram of an exemplary database access device in one embodiment;

FIG. 10 is a block diagram showing an example database management apparatus according to an embodiment;

FIG. 11 is a block diagram showing a structure of a database instance management apparatus according to another embodiment;

FIG. 12 is a diagram illustrating an internal structure of a computer device according to an embodiment.

Detailed Description

In order to make the objects, technical solutions and advantages of the present invention more apparent, the present invention is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.

FIG. 1 is a diagram of an example application environment for a database access method in one embodiment. Referring to fig. 1, the database instance access method is applied to a database instance access system. The database instance access system includes a user terminal 110, a node server 120, a management server 130, and a gateway device 140. The node server 120 includes at least a first node server 121 and a second node server 122. A source database instance is running on first node server 121 and a target database instance is running on second node server 122. The source database instance on the first node server 121 accesses the target database instance on the second node server 122 by the database instance access method provided by the present invention. The user terminal 110 is connected to the first node server 121 through a network, and the first node server 121 is connected to the management server 130 through a network. The first node server 121 and the second node server 122 are connected to each other through a gateway device 140. The gateway device 140 may specifically be a router or a switch, etc.

Those skilled in the art will appreciate that the node server 120 and the management server 130 may be located in a cloud server network environment. Specifically, the node server 120 and the management server 130 are located in a public cloud network environment in the cloud server network environment, and may also be located in a private cloud network environment in the cloud server network environment. The first node server 121 and the second node server 122 may be located in the same cloud server network environment, or may be located in different cloud server network environments.

FIG. 2 is a flowchart illustrating a database instance access method according to an embodiment. This embodiment is mainly illustrated by applying the method to the first node server 121 in fig. 1. Referring to fig. 2, the database instance access method specifically includes the following steps:

s202, a database instance access request is obtained.

The database instance access request is a request for applying for accessing a database instance. The database instance access request can be a request for the user terminal to apply for accessing one database instance, or can be a request for the one database instance to apply for accessing another database instance. A database instance is an instance in which a database server provides data services to a user. The user terminal can operate the internal data of the database instance through the data service provided by the database instance. In one embodiment, the database instance may be a PostgreSOL instance, a MySQL instance, a Mongo instance, or a Redis instance.

In one embodiment, the user terminal may initiate a database instance application request to a management server in the cloud server network environment, and the management server, upon receiving the database instance application request, notifies a node server in the cloud server network environment to perform a database instance creation operation, thereby creating a database instance belonging to a user on the node server. The management server can allocate a virtual connection address for the database instance and return the virtual connection address to the user terminal, so that the user terminal can access the database instance belonging to the user terminal according to the virtual connection address. It can be understood that the user terminal may create different database instances on different node servers through the management server, or may create different database instances on the same node server.

Specifically, the user terminal may access a first database instance (source database instance) located on a first node server in the cloud server network environment through a virtual connection address of the first database instance. The user terminal can initiate a database instance access request through a database management control command provided by the first database instance, and request to access a second database instance (target database instance) located on the second node server, so that the first node server obtains the database instance access request.

The first node server in the cloud server network environment may be an actually existing physical server, or may be a virtual node server obtained by virtualizing the physical server.

For example, the user terminal may create a PostgreSOL instance on the node server a through the management server, create a MySQL instance on the node server B, and obtain a virtual connection address a for the user to access the PostgreSOL instance and a virtual connection address B for the user to access the MySQL instance. In general, a user terminal needs to connect to a node server a and a node server B through a virtual connection address a and a virtual connection address B, respectively, to access a PostgreSOL instance and a MySQL instance, respectively. In this embodiment, the user terminal accesses the PostgreSOL instance through the virtual connection address a first, and when accessing the PostgreSOL instance, accesses the MySQL instance through the PostgreSOL instance.

S204, extracting a virtual connection address from the database instance access request; the virtual connection address corresponds to a target database instance requested to be accessed by the database instance access request.

Wherein the connection address is a network address for connecting to the database instance. The connection Address may include an Internet Protocol Address (IP Address) and a network port. The virtual connection address is a connection address that is not allocated to a real node server. The physical connection address is a real connection address that has been assigned to the real node server.

In a cloud server network environment, hosts (node servers) corresponding to database servers providing data services may respectively correspond to a physical connection address and a virtual connection address. In theory, the user terminal can connect to the node server through any one of the two connection addresses, and then access the database instance on the node server. And the node servers in the cloud server network environment can only access each other through the entity connection address.

It is understood that, in order to guarantee data security in a cloud server network environment, a cloud service provider generally provides only a virtual connection address to a user terminal. That is to say, currently, when a user terminal accesses a database instance in a cloud server network environment, different database instances can be accessed separately only through virtual connection addresses.

In particular, database instance access requests may carry connection parameters. Connection parameters are data that characterize the source and target database instances that are intended to make the connection. When the user terminal initiates a database instance access request, the related data of the target database instance which is intended to be accessed can be taken as the connection parameters to be carried in the database instance access request. Since the cloud service provider typically provides only the virtual connection address to the user terminal, the connection parameter may be a virtual connection address or the like corresponding to the target database instance. The connection parameter may specifically be an IP address and a network port number of the target database instance.

S206, acquiring the entity connection address which has a mapping relation with the virtual connection address.

Specifically, the first node server may query a mapping relationship between a virtual connection address and an entity connection address established in advance, compare the extracted virtual connection address with each virtual connection address in the mapping relationship, and obtain an entity connection address to which the queried virtual connection address is mapped when a virtual connection address consistent with the extracted virtual connection address is queried, thereby obtaining an entity connection address having a mapping relationship with the extracted virtual connection address.

The mapping relationship between the virtual connection address and the physical connection address, which is established in advance, may be a mapping relationship established when different database instances access each other before the current time. The mapping relation is established through the management server, and the mapping relation can be stored on the management server after being established, and can also be stored on other computer equipment independent of the management server, so that the node server can inquire when the mapping relation needs to be inquired. In one embodiment, the mapping relationship may be stored as a network connection relationship mapping table by way of a table.

S208, determining the database type of the target database instance.

The database type is a basis for classifying the database. In this embodiment, the databases belong to different database types when the databases are different. For example, a PostgreSOL instance, a MySQL instance, a Mongo instance, or a Redis instance may belong to different database types.

In particular, a database instance access request may specify a request type. The first node server may analyze a request type specified by the database instance access request to obtain a database type to which the database instance that the user terminal intends to access belongs.

And S210, accessing the target database instance through the database plug-in matched with the database type according to the entity connection address.

Wherein the database plug-in is a computer program that provides extended functionality for the database. Different databases are logically independent from each other, and when a certain database instance intends to access other databases for cross-database operation, the expansion function of the cross-database operation needs to be realized through a database plug-in.

For example, for a PostgreSOL instance, for which the PostgreSOL authority developed a postgres _ fdw module, the postgres _ fdw module provided an external data wrapper fdw that can be used to access external data within the PostgreSOL instance. External data pertaining to different database instances can be implemented through different types of external data wrappers, such as Mongo _ fdw for accessing Mongo instances, MySQL _ fdw for accessing MySQL instances, and Redis _ fdw for accessing Redis instances, among others.

Specifically, after determining the database type to which the target database instance belongs and acquiring the entity connection address corresponding to the target database instance, the first node server may invoke a database plug-in matched with the database type to initiate connection to the target database instance according to the entity connection address, so as to access the target database instance.

According to the database instance access method, when the data database instance access request is locally obtained, the virtual connection address corresponding to the target database instance which is supposed to be accessed can be directly extracted, the entity connection address which has a mapping relation with the virtual connection address and can be accessed among the database instances is further obtained, the database type to which the target database instance belongs is determined, and therefore the data service provided by accessing the target database instance through the database plug-in matched with the database type according to the entity connection address can be achieved, and access among different database instances is achieved.

In one embodiment, the physical connection address is obtained by mapping the local host address and the virtual connection address together according to a mapping mode corresponding to a network environment where the target database instance is located.

It can be understood that the database access method provided in the embodiment of the present invention is applied to a cloud server network environment. The cloud server network environment is a basic network environment for constructing other networks. Other networks such as a public cloud network or a private cloud network, etc. The public cloud network is an external cloud network provided by a cloud service provider, is constructed on a cloud service network environment, and is logically isolated. The private cloud network provides a self-defined cloud network for a cloud service provider, provides a cloud service user with the capability of self-defining a network environment, and the cloud service user can deploy cloud service resources such as a cloud host, load balancing, a database, Nosql fast storage and the like in the private cloud network. Network logic isolation between private cloud networks.

For example, the Cloud server network environment may be a network environment in which a CDB (Cloud Database) provided by the Tencent Cloud is located, wherein the CDB is ready-to-use, stable, reliable, and flexible. Tencent Cloud servers (CVM) are high-performance and high-stability Cloud Virtual machines, and users can create database instances of the users on the CVM. A Virtual Private Cloud network (VPC) is a network space that can be customized.

In particular, the step of mapping to the physical connection address is performed by the management server. The management server is used for uniformly managing the network connection mapping relation in the cloud server network environment.

In an embodiment, when the network environment in which the target database instance is located and the network environment in which the source database instance is located are the same network environment, that is, the node server in which the target database instance is located and the node server in which the source database instance is located belong to the same Internet Data Center (IDC), the source database instance and the target database instance may be directly connected and accessed through a host physical address. The management server can directly acquire the host physical address of the node server corresponding to the virtual connection address, and feed back the host physical address to the first node server, so that the first node server acquires the entity connection address which has a mapping relation with the virtual connection address.

In an embodiment, when the target database instance runs on a cloud virtual server CVM obtained by virtualization of a physical server, that is, when a node server where the target database instance is located and a node server where the source database instance is located belong to the same cloud server network environment, the management server may determine a host parameter (host parameter) of the node server corresponding to the virtual connection address and a host parameter of the source database instance, and form an access path for accessing the target database instance by the source database instance according to a routing policy of a gateway device in the current cloud server network environment to obtain an entity connection address accessible to the target database instance, so as to map the virtual connection address to the entity connection address. The gateway device may include a router, a switch, and the like. The routing policy of the gateway device is the basis for adding routing paths between the gateway devices.

In an embodiment, when the node server where the target database instance is located and the node server where the source database instance is located belong to different internet data centers, that is, when the node server where the target database instance is located and the node server where the source database instance is located belong to different cloud server network environments, the management server may obtain an entity connection address where the target database instance is accessible by determining a host address of the database server corresponding to the virtual connection address and/or a host parameter of a local host of the source database instance, and forming a routing path where the source database instance accesses the target database instance according to a current cloud server network environment and a routing policy of a gateway device in the load balancing system, so that the virtual connection address is mapped to the entity connection address. The load balancing system may be specifically tgw (tencent gateway way), which is a set of systems for implementing unified access of multiple networks, forwarding of external network requests, and supporting automatic load balancing.

In the embodiment, a way for mapping the target database instances in different network environments to obtain the real accessible connection address is provided, and mutual access between the database instances in different network environments is realized.

In one embodiment, the database access method further comprises: when the mapping relation corresponding to the virtual connection address does not exist, the local host address is obtained; sending the local host address and the virtual connection address to a management server; receiving an entity connection address fed back by a management server; the fed back entity connection address is determined by the management server according to the local host address and the virtual connection address; and establishing a mapping relation of the virtual connection address to the fed-back entity connection address.

Specifically, the first node server may obtain the local host address when the mapping relationship corresponding to the virtual connection address is not queried, and then send the local host address and the virtual connection address to the management server. When receiving the virtual connection address, the management server may determine, according to the local host address and the virtual connection address, an entity connection address at which the source database instance can access the target database instance. The physical connection address may also be obtained by mapping the local host address and the virtual connection address together by the management server according to a mapping manner corresponding to the network environment where the target database instance is located.

The local host address may be only a host physical address of the node server where the source database instance is located; or a host parameter of the node server where the source database instance is located, where the host parameter is data reflecting the address of the host, including the physical address of the host.

In this embodiment, in the solution way when the connection address capable of directly accessing the target database instance is not found currently, the server generates the connection address capable of directly accessing the target database instance according to the local host address and the virtual connection address, thereby implementing access between different database instances.

In one embodiment, the database instance access request is intercepted by a proxy plugin. The agent plug-in is installed in the database instance and used for intercepting a request of a user terminal for initiating the creation of an external server through a database management control command provided by the first database instance and generating a database instance access request.

For example, a user, upon accessing a PostgreSol instance, may call CREATE SERVER to command the creation of server. Here "CREATE SERVER" is a database management control command provided by the PostgreSOL instance to define a new external server, the user defining which will become the owner. The Server is the created external Server, which typically includes the connection parameters needed by the external data wrapper fdw to access an external data source (target database instance).

The specific codes are as follows:

CREATE SERVER foreign_server

FOREIGN DATA WRAPPER postgres_fdw

OPTIONS(host'192.83.123.89',port'5432',dbname'foreign_db')；

in this example, the user terminal is intended to connect to a PostgreSQL instance that is located on host 192.83.123.89 and listens to the 5432 port. The database instance is named foreign _ db.

Specifically, the agent plug-in can intercept a request for establishing an external server initiated by a user terminal through an interception function provided by the database instance, and generate a database instance access request. Such as: the Agent plug-in Agent can intercept the request of a user for creating the Server through a Hook function ProcessUtility _ Hook of PostgreSQL and generate a database instance access request.

Further, after the first node server intercepts and generates a database instance access request through the proxy plug-in, the first node server may extract connection parameters defined by the database instance access request, so as to obtain a virtual connection address corresponding to the target database instance. The first node server can query the network connection mapping table through the proxy plug-in to obtain the entity connection address which has a mapping relation with the virtual connection address.

In one embodiment, when the mapping relation corresponding to the virtual connection address is not inquired in the network connection mapping table through the proxy plugin, the local host address and the virtual connection address are sent to the management server; receiving an entity connection address fed back by a management server through an agent plug-in; the fed back entity connection address is determined by the management server according to the local host address and the virtual connection address; and newly establishing the mapping relation of the virtual connection address to the fed-back entity connection address in the network connection mapping table through the proxy plug-in.

Specifically, when the agent plug-in does not inquire that the mapping relation corresponding to the virtual connection address is not inquired in the network connection mapping table, the first node server may send the generated database instance access request to the management server, and the management server obtains the virtual connection address corresponding to the target database instance from the database instance access request. The management server can also obtain a host address corresponding to the first node server, and maps the host address and the virtual connection address together to obtain an entity connection address according to a mapping mode corresponding to the network environment where the target database instance is located.

Fig. 3 shows a schematic diagram of the establishment of a database instance access connection in one embodiment. Referring to fig. 3, in the present embodiment, the source database instance is a PostgreSQL instance. The user terminal can call CREATE SERVER in the PostgreSQL to command the creation of the Server, the Agent installed on the PostgreSQL intercepts the request of the user terminal to create the Server through the Hook function ProcessUtility _ Hook of the PostgreSQL, analyzes the request type and the connection parameters, and then sends the connection parameters to the management Server Center. The management server can determine the network environment of the target database instance according to the virtual connection address in the connection parameter, and further create network mapping according to the network environment classification of the target database instance to obtain an entity connection address for the source database instance to directly access the target database instance.

When the virtual connection address in the connection parameter is the virtual IP address of the private cloud network VPC, it may be determined that the network environment where the target database instance is located is an internal IDC (the server where the source database instance is located is in the same network) or a cloud server CVM virtualized by a private cloud network VPC host. When the virtual connection address in the connection parameter is the virtual IP address of the external network, it may be determined that the network environment where the target database instance is located is the external IDC (a cloud service network environment different from the server where the source database instance is located). The database instances belonging to the same IDC environment can be accessed directly through connection by host addresses. For the cloud server CVM virtualized by the parent machine, a Virtual Private Network (VPN) may be established through a routing policy of the gateway device, thereby establishing a Network connection between the source database instance and the target database instance. For database instances belonging to different IDC environments (virtual connection addresses are external network IP addresses), network connection between a source database instance and a target database instance can be established through the TGW.

And after the management server Center successfully creates the network mapping, returning the obtained entity connection address to the Agent plug-in Agent. After the Agent receives the entity connection address returned by the Center, inserting the newly-established mapping relation into the network connection mapping table, ending the Hook function flow, entering the program flow of creating the Server by the postgreSQL, and then initiating TCP connection according to the entity connection address through fdw to access the target database instance.

In one embodiment, the source database instance on the first node server may also continue to access the second target database instance after accessing the first target database instance. At this time, the proxy plugin can intercept a request of initiating an update of an external server by a database management control command provided by the user terminal through the first database instance, and then check whether a mapping relation corresponding to the virtual connection address exists in the network connection mapping table. For example, a user may invoke ALTER SERVER command to update the server when accessing a PostgreSOL instance.

In one embodiment, the database access method further comprises: and acquiring a requester identifier corresponding to the database instance access request. Sending the local host address and the virtual connection address to a management server, comprising: correspondingly sending the requester identifier, the local host address and the virtual connection address to a management server; the step of receiving the entity connection address fed back by the management server is performed when the requestor identifies that access rights exist for the virtual connection address.

The requester identifier may be a character string including at least one of a number, a letter, and a symbol, and uniquely identifies a requester. The requestor is the user that initiated the database instance access request. The database instance access request initiated by the user terminal can carry a requester identifier. The user terminal may also initiate a database instance access request corresponding to the requestor identification.

Specifically, when receiving a database instance access request sent by the first node server or the proxy plug-in on the first node server, the management server first performs parameter verification. The parameter check comprises parameter format check and user authority check. User permission verification requires detecting whether the requestor identification has access permission to the virtual connection address. The management server only continues to perform subsequent operations when the requestor identifies that access rights exist for the virtual connection address.

In this embodiment, before mapping the virtual connection address to the physical connection address to access the target database instance, authentication is performed first, and only after the authentication is passed, address mapping is performed, thereby ensuring the security of data access.

In one embodiment, the database access method further comprises: recording the entity connection address as a connection parameter corresponding to the database instance access request; the recorded connection parameters are used for reserving mapping relations corresponding to the connection parameters in the network connection mapping table; when the target database instance running on the standby node server is finished being accessed, the connection parameters are deleted.

Specifically, when an external server (server) is created through a local database instance and accesses other database instances, a node server in the cloud service network environment may record a connection parameter in the local database instance to indicate that both connection parties corresponding to the connection parameter are performing data access operations, and when a management server manages a network connection mapping table, the management server needs to keep a mapping relationship corresponding to the connection parameter in the network connection mapping table.

The connection parameter is a general name of data corresponding to both connection parties. The connection parameter may be a plurality of data. The local host address may be a connection parameter, the virtual connection address of the target database instance may be a connection parameter, and the physical connection address of the target database instance may be a connection parameter.

In the embodiment, for the connection parameters in accessing which are recorded in time when the target database instance is accessed, the relevant connection parameters are deleted after the accessing is finished, so that the waste of storage resources due to the residue of invalid data is avoided.

Fig. 4 shows a timing diagram for updating connection parameters in one embodiment. Referring to fig. 4, after the user terminal triggers a connection parameter update request (ALTER SERVER command), the first node server may intercept the request, and further search a network connection mapping table for a mapping relationship corresponding to a virtual connection address of the target database instance (specifically, the request may be a Hook function of Agent, and query the network connection mapping table). When the mapping relation does not exist, a first node server (Agent) requests a management server to establish a new mapping relation. When monitoring the request, the management server checks the access authority of the requester identifier, and creates a routing path after the check is passed, obtains an entity connection address corresponding to the virtual connection address, and returns the entity connection address to the first node server (Agent). The first node server (Agent) may write a mapping relationship of the virtual connection address and the physical connection address into a network connection mapping table. The first node server (Agent) may also record the physical connection address as a connection parameter to update the connection parameter, and return the updated connection parameter to the user terminal.

In the embodiment, the access process of the cross-database instance is uniformly processed through the proxy plug-in, so that the feasibility of access among different database instances is ensured, and the access efficiency among different database instances is improved.

In one embodiment, accessing the target database instance through a database plug-in matching the database type based on the physical connection address comprises: and accessing a target database instance running on the main node server through the database plug-in matched with the database type according to the entity connection address. The database instance access method further comprises the following steps: when the access to a target database instance running on a main node server fails, a standby connection address corresponding to the entity connection address is obtained; and accessing the target database instance running on the standby node server through the database plug-in matched with the database type according to the standby connection address.

It is understood that a database instance in a cloud services network environment may typically correspond to two node servers to ensure high reliability. When the main node server is down, the standby node server can be switched to, so that the reliability of the database instance for providing data service is ensured.

Specifically, the entity connection address acquired by the first node server is a connection address for accessing the target database instance running on the master node server. The backup connection address is a connection address for accessing a target database instance of the running and backup node servers. When the first node server fails to access the target database instance running on the main node server, it is determined that the master-backup switching may occur on the node server corresponding to the target database instance, and at this time, the first node server may obtain a backup connection address corresponding to the entity connection address, so as to access the target database instance running on the backup node server through the database plug-in matched with the database type according to the backup connection address.

In this embodiment, when the node server corresponding to the target database instance is switched between the active node and the standby node, a connection is established with the standby node server in time to access the target database instance on the standby server, so that smooth access of the database instance is ensured.

In one embodiment, when the first node server acquires the backup connection address, the first node server may update the connection parameters according to the backup connection address.

FIG. 5 is a flowchart illustrating a method for managing database instances in one embodiment. The embodiment mainly illustrates that the method is applied to the management server 130 in fig. 1. Referring to fig. 5, the database instance management method specifically includes the following steps:

s502, receiving an address mapping request corresponding to both a source host address and a virtual connection address; the source host address corresponds to the source database instance; the virtual connection address corresponds to a target database instance.

Specifically, the address mapping request is a request for mapping a virtual connection address to an entity connection address through a routing policy. The first node server where the source database instance is located can acquire a local source host address and a virtual connection address of a target database instance which is intended to be accessed, correspondingly send the source host address and the virtual connection address to the management server, and initiate an address mapping request, so that the management server receives the address mapping request jointly corresponding to the source host address and the virtual connection address.

S504, the source host address and the virtual connection address are mapped into the entity connection address together.

Specifically, the management server may map the source host address and the virtual connection address together into an entity connection address according to a preset routing policy. For example, the management server may call an interface provided by a public cloud network management module to obtain the entity connection address, and the public cloud network management module is configured to manage a relevant routing policy and map the virtual connection address to a connection address that can be directly accessed in an internal network.

S506, feeding back an entity connection address according to the address mapping request; the entity connection address is used to instruct the source database instance to access the target database instance according to the entity connection address.

FIG. 6 is a schematic diagram illustrating access to a database instance in one embodiment. Referring to fig. 6, a user terminal may initiate a database instance access request, and after intercepting the request, an Agent installed on a source database instance (PostgreSQL instance) correspondingly sends a source host address and a virtual connection address to a management server center, and initiates an address mapping request. The center maps the source host address and the virtual connection address together into a physical connection address and feeds back the physical connection address to the Agent, and the Agent writes the newly-built mapping relation into a network connection mapping table and accesses a target database instance (MySQL instance, Mongo instance or Redis instance) according to the physical connection address.

According to the database instance management method, after the address mapping request is received, the source host address and the virtual connection address corresponding to the address mapping request can be obtained, the source host address and the virtual connection address are mapped into the entity connection address which can be accessed among database instances, and therefore the source database instance can access data services provided by the target database instance according to the entity connection address, and access among different database instances is achieved.

In one embodiment, co-mapping the source host address and the virtual connection address to a physical connection address comprises: determining the network environment of the target database instance according to the virtual connection address; and mapping the source host address and the virtual connection address together into an entity connection address according to a mapping mode corresponding to the network environment.

In one embodiment, the database instance management method further includes obtaining a requestor identifier corresponding to the address mapping request; verifying the access authority of the requester identifier to the virtual connection address; and after the access authority passes the verification, executing the step of mapping the source host address and the virtual connection address together into the entity connection address.

In one embodiment, the source database instance runs on a first master node server. The database instance management method further comprises the following steps: when the source database instance changes to run on the first standby node server, the first standby node server is notified to revisit the target database instance.

Specifically, the first master node server running the source database instance may report the running state to the monitoring server, and the monitoring server may perform corresponding recording when receiving the reported running state. The management server can thus obtain the hardware environment of the source database instance by querying the running state recorded in the monitoring server. The first master node server running the source database instance may also directly report the running status to the management server.

When the monitoring server or the management server does not receive the running state reported by the first main node server after overtime, the source database instance can be judged to be changed to run in the first standby node server, and the management server informs the first standby node server to access the target database instance again.

In one embodiment, the first master node server may be in the same public cloud network environment as the monitoring server, and the first master node server may also be in the same public cloud network environment as the management server.

In one embodiment, notifying the first standby node server to revisit the target database instance comprises: acquiring a standby host address corresponding to a first standby node server; determining a first standby connection address according to the standby host address and the virtual connection address; feeding back the first standby connection address to the first standby node server; the first alternate connection address is used to indicate that the target database instance is to be revisited.

FIG. 7 is a schematic diagram illustrating database instance access connection updates in one embodiment. Referring to fig. 7, the source database instances correspond to Master node servers Master1 and Slave1, and the target database instances correspond to Master node servers Master2 and Slave 2. Master1 interfaces with Master2 to enable access to the target database instance through the source database instance. The Master1 may report the node status to the monitoring server, and the management server center may obtain the hardware environment of the source database instance by querying the running status recorded in the monitoring server. When the Master1 is down, the center may check whether a mapping relationship corresponding to the connection of the Slave1 and the Master2 exists in a network connection mapping table, and if not, acquire a standby host address corresponding to the Slave1, and determine a first standby connection address according to the standby host address and the virtual connection address to create a mapping relationship corresponding to the connection of the Slave1 and the Master 2. The Center may write the mapping relationship into a network connection mapping table, and feed back the first backup connection address to the Slave1, and the Slave1 may connect with the Master2 through the first backup connection address to access the target database instance through the source database instance.

In the above embodiment, the node server corresponding to the source database instance adopts a master-slave mode to ensure high availability, and when the master-slave mode switching is detected, the node server establishing the connection is updated in time, so that the high availability of the database instance access is ensured.

In one embodiment, the entity connection address is used to indicate a source database instance, and the target database instance running on the second master node server is accessed based on the entity connection address. The database instance management method further comprises the following steps: when the target database instance is changed to run in a second standby node server, acquiring a second standby connection address corresponding to the entity connection address; feeding back a second standby connection address according to the address mapping request; the second backup connection address is used for indicating a source database instance and accessing a target database instance running on the second backup node server according to the backup connection address.

Specifically, the second master node server running the target database instance may report the running state to the monitoring server, and the monitoring server may perform corresponding recording when receiving the reported running state. The management server can thus obtain the hardware environment of the source database instance by querying the running state recorded in the monitoring server. The second master node server running the target database instance may also directly report the running status to the management server.

When the monitoring server or the management server does not receive the running state reported by the second main node server after overtime, the source database instance can be judged to be changed to run in the second standby node server, and the management server acquires a second standby connection address corresponding to the entity connection address and feeds the second standby connection address back to the entity connection address; the second backup connection address is used for indicating a source database instance and accessing a target database instance running on the second backup node server according to the backup connection address.

In one embodiment, the second master node server may be in the same public cloud network environment as the monitoring server, and the second master node server may also be in the same public cloud network environment as the management server.

Referring to fig. 7 again, the Master2 may report the node status to the monitoring server, and the management server center may obtain the hardware environment of the target database instance by querying the running status recorded in the monitoring server. When the Master2 is down, the center may check whether a mapping relationship corresponding to the connection of the Master1 and the Slave2 exists in the network connection mapping table, and if not, acquire a standby host address corresponding to the Slave2, and determine a second standby connection address according to the standby host address and the virtual connection address to create a mapping relationship corresponding to the connection of the Master1 and the Slave 2. The Center may write the mapping relationship into a network connection mapping table, and feed back the second backup connection address to Master1, and Master1 may connect with Slave2 through the first backup connection address to access the target database instance through the source database instance.

In this embodiment, the node server corresponding to the target database instance adopts a master-slave mode to ensure high availability, and when the master-slave mode switching is detected, the node server establishing the connection is updated in time, so that the high availability of database instance access is ensured.

In one embodiment, the database instance management method further includes: in a network connection mapping table, a mapping relation of a virtual connection address to an entity connection address is newly established; scanning connection parameters recorded by a first node server running a source database instance; adding marks for mapping relations corresponding to the connection parameters in the network connection mapping table; and deleting the mapping relation without the mark in the network connection mapping table.

Specifically, the management server may periodically scan connection parameters on the node servers in the cloud service network environment, and each time a connection parameter is scanned, a mark is added to a mapping relationship corresponding to the connection parameter in the network connection mapping table. The flag indicates that the mapping is still valid and needs to be preserved during cleaning. And after the scanning is finished, the management server detects the marks in the network connection mapping table and deletes the mapping relation without the marks. The management server may also delete the routing policy added when creating the mapping.

In one embodiment, the flag may be a clear flag bit. FIG. 8 illustrates a timing diagram for removing connection parameters in one embodiment. Referring to fig. 8, when the management server starts to perform network connection mapping table cleaning, the management server initializes a cleaning flag bit of each mapping relation in the network connection mapping table. The management server can scan the connection parameters on the node servers in the cloud service network environment again, and when the connection parameters are scanned, the cleaning flag bit of the mapping relation corresponding to the connection parameters is set in the network connection mapping table. And after the connection parameter scanning is finished, detecting a cleaning flag bit record in the network connection mapping table, if the cleaning flag bit record is not set, deleting the added routing path when the mapping relation is created according to the deletion, and deleting the mapping relation in the mapping information table.

It should be understood that, although the steps in the flowcharts of the above embodiments are shown in sequence as indicated by the arrows, the steps are not necessarily executed in sequence as indicated by the arrows. The steps are not performed in the exact order shown and described, and may be performed in other orders, unless explicitly stated otherwise. Moreover, at least a part of the steps in the above embodiments may include multiple sub-steps or multiple stages, which are not necessarily performed at the same time, but may be performed at different times, and the order of performing the sub-steps or the stages is not necessarily performed in sequence, but may be performed alternately or alternately with other steps or at least a part of the sub-steps or the stages of other steps.

As shown in FIG. 9, in one embodiment, a database instance access device 900 is provided. Referring to fig. 9, the database instance accessing apparatus 900 includes: a first obtaining module 901, an extracting module 902, a second obtaining module 903, a determining module 904 and an accessing module 905.

A first obtaining module 901, configured to obtain a database instance access request.

An extracting module 902, configured to extract a virtual connection address from a database instance access request; the virtual connection address corresponds to a target database instance requested to be accessed by the database instance access request.

A second obtaining module 903, configured to obtain an entity connection address having a mapping relationship with the virtual connection address.

A determining module 904, configured to determine a database type to which the target database instance belongs.

And the access module 905 is configured to access the target database instance through the database plugin matched with the database type according to the entity connection address.

In one embodiment, the second obtaining module 903 is further configured to obtain the local host address when there is no mapping relationship corresponding to the virtual connection address; sending the local host address and the virtual connection address to a management server; receiving an entity connection address fed back by a management server; the fed back entity connection address is determined by the management server according to the local host address and the virtual connection address; and establishing a mapping relation of the virtual connection address to the fed-back entity connection address.

In one embodiment, the second obtaining module 903 is further configured to obtain a requestor identifier corresponding to the database instance access request; correspondingly sending the requester identifier, the local host address and the virtual connection address to a management server; the step of receiving the entity connection address fed back by the management server is performed when the requestor identifies that access rights exist for the virtual connection address.

In one embodiment, the accessing module 905 is further configured to access a target database instance running on the master node server through a database plug-in matched with the database type according to the entity connection address; when the access to a target database instance running on a main node server fails, a standby connection address corresponding to the entity connection address is obtained; and accessing the target database instance running on the standby node server through the database plug-in matched with the database type according to the standby connection address.

In one embodiment, the database instance access request is intercepted by an agent plug-in; the virtual connection address is extracted from the database instance access request through the proxy plug-in. The second obtaining module 903 is further configured to query the network connection mapping table through the proxy plugin, so as to obtain an entity connection address having a mapping relationship with the virtual connection address.

In an embodiment, the second obtaining module 903 is further configured to send the local host address and the virtual connection address to the management server when the mapping relationship corresponding to the virtual connection address is not queried in the network connection mapping table through the proxy plugin; receiving an entity connection address fed back by a management server through an agent plug-in; the fed back entity connection address is determined by the management server according to the local host address and the virtual connection address; and newly establishing the mapping relation of the virtual connection address to the fed-back entity connection address in the network connection mapping table through the proxy plug-in.

In one embodiment, the access module 905 is further configured to record the entity connection address as a connection parameter corresponding to the database instance access request; the recorded connection parameters are used for reserving mapping relations corresponding to the connection parameters in the network connection mapping table; when the target database instance running on the standby node server is finished being accessed, the connection parameters are deleted.

As shown in fig. 10, in one embodiment, a database instance management apparatus 1000 is provided. Referring to fig. 10, the database instance management apparatus 1000 includes: a receiving module 1001, a mapping module 1002 and a feedback module 1003.

A receiving module 1001, configured to receive an address mapping request corresponding to a source host address and a virtual connection address; the source host address corresponds to the source database instance; the virtual connection address corresponds to a target database instance.

The mapping module 1002 is configured to map the source host address and the virtual connection address together into an entity connection address.

A feedback module 1003, configured to feed back an entity connection address according to the address mapping request; the entity connection address is used to instruct the source database instance to access the target database instance according to the entity connection address.

In one embodiment, the mapping module 1002 is further configured to determine a network environment in which the target database instance is located according to the virtual connection address; and mapping the source host address and the virtual connection address together into an entity connection address according to a mapping mode corresponding to the network environment.

In one embodiment, the mapping module 1002 is further configured to obtain a requestor identifier corresponding to the address mapping request; verifying the access authority of the requester identifier to the virtual connection address; and after the access authority passes the verification, executing the step of mapping the source host address and the virtual connection address together into the entity connection address.

In one embodiment, the source database instance runs on a first master node server. The feedback module 1003 is further configured to notify the first standby node server to re-access the target database instance when the source database instance changes to be running on the first standby node server.

In one embodiment, the feedback module 1003 is further configured to obtain a backup host address corresponding to the first backup node server; determining a first standby connection address according to the standby host address and the virtual connection address; feeding back the first standby connection address to the first standby node server; the first alternate connection address is used to indicate that the target database instance is to be revisited.

In one embodiment, the entity connection address is used to indicate a source database instance, and the target database instance running on the second master node server is accessed based on the entity connection address. The feedback module 1003 is further configured to obtain a second backup connection address corresponding to the entity connection address when the target database instance changes to operate in the second backup node server; feeding back a second standby connection address according to the address mapping request; the second backup connection address is used for indicating a source database instance and accessing a target database instance running on the second backup node server according to the backup connection address.

As shown in fig. 11, in one embodiment, the database instance management apparatus 1000 further includes: a cleaning module 1004.

A cleaning module 1004, configured to create a mapping relationship between a virtual connection address and an entity connection address in a network connection mapping table; scanning connection parameters recorded by a first node server running a source database instance; adding marks for mapping relations corresponding to the connection parameters in the network connection mapping table; and deleting the mapping relation without the mark in the network connection mapping table.

FIG. 12 is a diagram illustrating an internal structure of a computer device in one embodiment. The computer devices may be specifically the node server 120 and the management server 130 in fig. 1. As shown in fig. 12, the computer device includes a processor, a memory, and a network interface connected by a system bus. Wherein the memory includes a non-volatile storage medium and an internal memory. The non-volatile storage medium of the computer device stores an operating system and may also store a computer program that, when executed by the processor, causes the processor to implement a database instance access/management method. The internal memory may also have stored therein a computer program that, when executed by the processor, causes the processor to perform a database instance access/management method. Those skilled in the art will appreciate that the architecture shown in fig. 12 is merely a block diagram of some of the structures associated with the disclosed aspects and is not intended to limit the computing devices to which the disclosed aspects apply, as particular computing devices may include more or less components than those shown, or may combine certain components, or have a different arrangement of components.

In one embodiment, the database instance accessing/managing apparatus provided in the present application may be implemented in a form of a computer program, where the computer program may run on a computer device as shown in fig. 12, and a non-volatile storage medium of the computer device may store various program modules constituting the database instance accessing/managing apparatus, such as a first obtaining module 901, an extracting module 902, a second obtaining module 903, a determining module 904, an accessing module 905, and the like shown in fig. 9. The computer program comprised of the respective program modules causes the processor to execute the steps in the database instance access/management method of the various embodiments of the present application described in the present specification.

For example, the computer device shown in fig. 12 may obtain the database instance access request through the first obtaining module 901 in the database instance accessing apparatus 900 shown in fig. 9. Extracting a virtual connection address from the database instance access request through an extraction module 902; the virtual connection address corresponds to a target database instance requested to be accessed by the database instance access request. And acquiring the entity connection address with a mapping relation with the virtual connection address through a second acquiring module 903. The database type to which the target database instance belongs is determined by the determination module 904. The target database instance is accessed by the accessing module 905 through the database plug-in matching the database type according to the entity connection address.

In one embodiment, there is provided a database instance access system comprising a node server and a management server, wherein:

the node server is used for acquiring a database instance access request; extracting a virtual connection address from the database instance access request; the virtual connection address corresponds to a target database instance requested to be accessed by the database instance access request.

The node server is also used for sending an address mapping request which is jointly corresponding to the source host address and the virtual connection address to the management server; the source host address corresponds to the source database instance; the source database instance runs on the node server.

The management server is used for mapping the source host address and the virtual connection address together into an entity connection address; and feeding back the entity connection address to the node server according to the address mapping request.

In one embodiment, the management server is further configured to determine, according to the virtual connection address, a network environment in which the target database instance is located; and mapping the source host address and the virtual connection address together into an entity connection address according to a mapping mode corresponding to the network environment.

In one embodiment, the management server is further configured to obtain a requestor identifier corresponding to the address mapping request; verifying the access authority of the requester identifier to the virtual connection address; and after the access authority passes the verification, executing the step of mapping the source host address and the virtual connection address together into the entity connection address. The node server is also used for acquiring a requester identifier corresponding to the database instance access request; correspondingly sending the requester identifier, the local host address and the virtual connection address to a management server; and establishing a mapping relation of the virtual connection address to the fed-back entity connection address.

In one embodiment, the node server is further configured to record the entity connection address as a connection parameter corresponding to the database instance access request; the recorded connection parameters are used for reserving mapping relations corresponding to the connection parameters in the network connection mapping table; when the target database instance running on the standby node server is finished being accessed, the connection parameters are deleted. The management server is also used for establishing a mapping relation of the virtual connection address to the entity connection address in the network connection mapping table; scanning connection parameters recorded by a first node server running a source database instance; adding marks for mapping relations corresponding to the connection parameters in the network connection mapping table; and deleting the mapping relation without the mark in the network connection mapping table.

In one embodiment, the node server is further configured to access a target database instance running on the master node server through a database plug-in matched with the database type according to the entity connection address; when the access to a target database instance running on a main node server fails, a standby connection address corresponding to the entity connection address is obtained; and accessing the target database instance running on the standby node server through the database plug-in matched with the database type according to the standby connection address.

In one embodiment, the database instance access request is intercepted by an agent plug-in; the virtual connection address is extracted from the database instance access request through the proxy plug-in. The node server is also used for inquiring the network connection mapping table through the proxy plug-in to obtain the entity connection address which has the mapping relation with the virtual connection address.

In one embodiment, the node server is further configured to send the local host address and the virtual connection address to the management server when the mapping relationship corresponding to the virtual connection address is not queried in the network connection mapping table by the proxy plugin; receiving an entity connection address fed back by a management server through an agent plug-in; the fed back entity connection address is determined by the management server according to the local host address and the virtual connection address; and newly establishing the mapping relation of the virtual connection address to the fed-back entity connection address in the network connection mapping table through the proxy plug-in.

In one embodiment, the node servers include a first primary node server, a first backup node server, a second primary node server, and a second backup node server. The first master node server is configured to perform the steps performed by the node server. The management server is further configured to notify the first standby node server to revisit the target database instance when the source database instance changes to be running on the first standby node server.

In one embodiment, the management server is further configured to obtain a backup host address corresponding to the first backup node server; determining a first standby connection address according to the standby host address and the virtual connection address; feeding back the first standby connection address to the first standby node server; the first alternate connection address is used to indicate that the target database instance is to be revisited.

In one embodiment, the management server is further configured to obtain a second backup connection address corresponding to the physical connection address when the target database instance changes to run on a second backup node server; feeding back a second standby connection address according to the address mapping request; the second backup connection address is used for indicating a source database instance and accessing a target database instance running on the second backup node server according to the backup connection address.

In one embodiment, a computer readable storage medium is provided, having a computer program stored thereon, which, when executed by a processor, causes the processor to perform the steps of: acquiring a database instance access request; extracting a virtual connection address from the database instance access request; the virtual connection address corresponds to a target database instance requested to be accessed by the database instance access request; acquiring an entity connection address which has a mapping relation with the virtual connection address; determining a database type to which a target database instance belongs; and accessing the target database instance through the database plug-in matched with the database type according to the entity connection address.

In one embodiment, the computer program, when executed by the processor, further causes the processor to perform the steps of: when the mapping relation corresponding to the virtual connection address does not exist, the local host address is obtained; sending the local host address and the virtual connection address to a management server; receiving an entity connection address fed back by a management server; the fed back entity connection address is determined by the management server according to the local host address and the virtual connection address; and establishing a mapping relation of the virtual connection address to the fed-back entity connection address.

In one embodiment, the computer program, when executed by the processor, further causes the processor to perform the steps of: and acquiring a requester identifier corresponding to the database instance access request. Sending the local host address and the virtual connection address to a management server, comprising: correspondingly sending the requester identifier, the local host address and the virtual connection address to a management server; the step of receiving the entity connection address fed back by the management server is performed when the requestor identifies that access rights exist for the virtual connection address.

In one embodiment, accessing the target database instance through a database plug-in matching the database type based on the physical connection address comprises: and accessing a target database instance running on the main node server through the database plug-in matched with the database type according to the entity connection address. The computer program, when executed by the processor, further causes the processor to perform the steps of: when the access to a target database instance running on a main node server fails, a standby connection address corresponding to the entity connection address is obtained; and accessing the target database instance running on the standby node server through the database plug-in matched with the database type according to the standby connection address.

In one embodiment, the database instance access request is intercepted by an agent plug-in; the virtual connection address is extracted from the database instance access request through the proxy plug-in. Acquiring an entity connection address having a mapping relation with a virtual connection address, comprising: and inquiring the network connection mapping table through the proxy plug-in to obtain the entity connection address which has a mapping relation with the virtual connection address.

In one embodiment, the computer program, when executed by the processor, further causes the processor to perform the steps of: when the mapping relation corresponding to the virtual connection address is not inquired in the network connection mapping table through the proxy plugin, the local host address and the virtual connection address are sent to the management server; receiving an entity connection address fed back by a management server through an agent plug-in; the fed back entity connection address is determined by the management server according to the local host address and the virtual connection address; and newly establishing the mapping relation of the virtual connection address to the fed-back entity connection address in the network connection mapping table through the proxy plug-in.

In one embodiment, the computer program, when executed by the processor, further causes the processor to perform the steps of: recording the entity connection address as a connection parameter corresponding to the database instance access request; the recorded connection parameters are used for reserving mapping relations corresponding to the connection parameters in the network connection mapping table; when the target database instance running on the standby node server is finished being accessed, the connection parameters are deleted.

In one embodiment, there is provided a computer device comprising a memory and a processor, the memory having stored therein a computer program that, when executed by the processor, causes the processor to perform the steps of: acquiring a database instance access request; extracting a virtual connection address from the database instance access request; the virtual connection address corresponds to a target database instance requested to be accessed by the database instance access request; acquiring an entity connection address which has a mapping relation with the virtual connection address; determining a database type to which a target database instance belongs; and accessing the target database instance through the database plug-in matched with the database type according to the entity connection address.

In one embodiment, a computer readable storage medium is provided, having a computer program stored thereon, which, when executed by a processor, causes the processor to perform the steps of: receiving an address mapping request corresponding to the address of the source host and the virtual connection address together; the source host address corresponds to the source database instance; the virtual connection address corresponds to a target database instance; mapping the source host address and the virtual connection address together into an entity connection address; feeding back an entity connection address according to the address mapping request; the entity connection address is used to instruct the source database instance to access the target database instance according to the entity connection address.

In one embodiment, the computer program, when executed by the processor, further causes the processor to perform the steps of: acquiring a requester identifier corresponding to the address mapping request; verifying the access authority of the requester identifier to the virtual connection address; and after the access authority passes the verification, executing the step of mapping the source host address and the virtual connection address together into the entity connection address.

In one embodiment, the source database instance runs on a first master node server. The computer program, when executed by the processor, further causes the processor to perform the steps of: when the source database instance changes to run on the first standby node server, the first standby node server is notified to revisit the target database instance.

In one embodiment, the entity connection address is used to indicate a source database instance, and the target database instance running on the second master node server is accessed based on the entity connection address. The computer program, when executed by the processor, further causes the processor to perform the steps of: when the target database instance is changed to run in a second standby node server, acquiring a second standby connection address corresponding to the entity connection address; feeding back a second standby connection address according to the address mapping request; the second backup connection address is used for indicating a source database instance and accessing a target database instance running on the second backup node server according to the backup connection address.

In one embodiment, the computer program, when executed by the processor, further causes the processor to perform the steps of: in a network connection mapping table, a mapping relation of a virtual connection address to an entity connection address is newly established; scanning connection parameters recorded by a first node server running a source database instance; adding marks for mapping relations corresponding to the connection parameters in the network connection mapping table; and deleting the mapping relation without the mark in the network connection mapping table.

In one embodiment, there is provided a computer device comprising a memory and a processor, the memory having stored therein a computer program that, when executed by the processor, causes the processor to perform the steps of: receiving an address mapping request corresponding to the address of the source host and the virtual connection address together; the source host address corresponds to the source database instance; the virtual connection address corresponds to a target database instance; mapping the source host address and the virtual connection address together into an entity connection address; feeding back an entity connection address according to the address mapping request; the entity connection address is used to instruct the source database instance to access the target database instance according to the entity connection address.

It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above can be implemented by a computer program, which can be stored in a non-volatile computer-readable storage medium, and can include the processes of the embodiments of the methods described above when the program is executed. Any reference to memory, storage, database, or other medium used in the embodiments provided herein may include non-volatile and/or volatile memory, among others. Non-volatile memory can include read-only memory (ROM), Programmable ROM (PROM), Electrically Programmable ROM (EPROM), Electrically Erasable Programmable ROM (EEPROM), or flash memory. Volatile memory can include Random Access Memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in a variety of forms such as Static RAM (SRAM), Dynamic RAM (DRAM), Synchronous DRAM (SDRAM), Double Data Rate SDRAM (DDRSDRAM), Enhanced SDRAM (ESDRAM), Synchronous Link DRAM (SLDRAM), Rambus Direct RAM (RDRAM), direct bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM).

The technical features of the above embodiments can be arbitrarily combined, and for the sake of brevity, all possible combinations of the technical features in the above embodiments are not described, but should be considered as the scope of the present specification as long as there is no contradiction between the combinations of the technical features.

The above examples only show some embodiments of the present invention, and the description thereof is more specific and detailed, but not construed as limiting the scope of the present invention. It should be noted that, for a person skilled in the art, several variations and modifications can be made without departing from the inventive concept, which falls within the scope of the present invention. Therefore, the protection scope of the present patent shall be subject to the appended claims.

Claims

1. A database instance access method, comprising:

acquiring a database instance access request;

acquiring an entity connection address which has a mapping relation with the virtual connection address; the entity connection address is obtained by mapping a local host address and the virtual connection address together according to a mapping mode corresponding to the network environment where the target database instance is located;

determining a database type to which the target database instance belongs;

2. The method of claim 1, further comprising:

when the mapping relation corresponding to the virtual connection address does not exist, acquiring a local host address;

sending the local host address and the virtual connection address to a management server;

receiving an entity connection address fed back by the management server; the fed back entity connection address is determined by the management server according to the local host address and the virtual connection address;

and establishing a mapping relation of the virtual connection address to the fed back entity connection address.

3. The method of claim 2, further comprising:

acquiring a requester identifier corresponding to the database instance access request;

the sending the local host address and the virtual connection address to a management server includes:

correspondingly sending the requester identifier, the local host address and the virtual connection address to a management server;

when the requester identifies that the access right for the virtual connection address exists, the step of receiving the entity connection address fed back by the management server is performed.

4. The method of claim 1, wherein the accessing the target database instance through the database plug-in matching the database type according to the entity connection address comprises:

accessing the target database instance running on the main node server through a database plug-in matched with the database type according to the entity connection address;

the method further comprises the following steps:

when the target database instance running on the main node server fails to be accessed, a standby connection address corresponding to the entity connection address is obtained;

and accessing the target database instance running on the standby node server through the database plug-in matched with the database type according to the standby connection address.

5. The method according to any one of claims 1 to 4, wherein the database instance access request is intercepted by a proxy plugin; the virtual connection address is extracted from the database instance access request through the proxy plug-in;

the acquiring the entity connection address having the mapping relationship with the virtual connection address includes:

and inquiring a network connection mapping table through the proxy plug-in to obtain an entity connection address having a mapping relation with the virtual connection address.

6. The method of claim 5, further comprising:

when the mapping relation corresponding to the virtual connection address is not inquired in the network connection mapping table through the proxy plugin, sending a local host address and the virtual connection address to a management server;

receiving an entity connection address fed back by the management server through the proxy plug-in; the fed back entity connection address is determined by the management server according to the local host address and the virtual connection address;

and newly establishing the mapping relation of the virtual connection address to the fed back entity connection address in the network connection mapping table through the proxy plug-in.

7. The method of claim 5, further comprising:

recording the entity connection address as a connection parameter corresponding to the database instance access request; the recorded connection parameters are used for reserving mapping relations corresponding to the connection parameters in the network connection mapping table;

and when the target database instance running on the standby node server is accessed, deleting the connection parameters.

8. A database instance management method, comprising:

9. The method of claim 8, wherein the co-mapping the source host address and the virtual connection address to a physical connection address comprises:

determining the network environment of the target database instance according to the virtual connection address;

and mapping the source host address and the virtual connection address together into an entity connection address according to a mapping mode corresponding to the network environment.

10. The method of claim 8, further comprising:

acquiring a requester identifier corresponding to the address mapping request;

verifying the access authority of the requester identifier to the virtual connection address;

and after the access authority passes the verification, executing the step of mapping the source host address and the virtual connection address together into an entity connection address.

11. The method of claim 8, wherein the source database instance runs on a first master node server;

the method further comprises the following steps:

and when the source database instance is changed to run in a first standby node server, informing the first standby node server to re-access the target database instance.

12. The method of claim 11, wherein said notifying the first standby node server to revisit the target database instance comprises:

acquiring a standby host address corresponding to the first standby node server;

determining a first standby connection address according to the standby host address and the virtual connection address;

feeding back the first backup connection address to the first backup node server; the first alternate connection address is used to indicate to re-access the target database instance.

13. The method of claim 8, wherein the physical connection address is used to indicate the source database instance, and wherein the target database instance running on the second master node server is accessed according to the physical connection address;

the method further comprises the following steps:

when the target database instance is changed to run in a second standby node server, acquiring a second standby connection address corresponding to the entity connection address;

feeding back the second standby connection address according to the address mapping request; and the second standby connection address is used for indicating the source database instance and accessing a target database instance running on the second standby node server according to the standby connection address.

14. The method of claim 8, further comprising:

in a network connection mapping table, establishing a mapping relation of the virtual connection address to the entity connection address;

scanning connection parameters recorded by a first node server running the source database instance;

adding marks for mapping relations corresponding to the connection parameters in the network connection mapping table;

and deleting the mapping relation without the mark in the network connection mapping table.

15. A database instance access device, comprising:

the second acquisition module is used for acquiring the entity connection address which has a mapping relation with the virtual connection address; the entity connection address is obtained by mapping a local host address and the virtual connection address together according to a mapping mode corresponding to the network environment where the target database instance is located;

16. The apparatus of claim 15, wherein the second obtaining module is further configured to:

17. The apparatus of claim 16, wherein the second obtaining module is further configured to:

18. The apparatus of claim 15, wherein the access module is further configured to:

19. The apparatus according to any one of claims 15 to 18, wherein the database instance access request is intercepted by a proxy plugin; the virtual connection address is extracted from the database instance access request through the proxy plug-in;

the second obtaining module is further configured to:

20. The apparatus of claim 19, wherein the second obtaining module is further configured to:

21. The apparatus of claim 19, wherein the access module is further configured to:

22. A database instance management apparatus, comprising:

23. The apparatus of claim 22, wherein the mapping module is further configured to:

24. The apparatus of claim 22, wherein the mapping module is further configured to:

acquiring a requester identifier corresponding to the address mapping request;

25. The apparatus of claim 22, wherein the source database instance runs on a first master node server;

the feedback module is further configured to:

26. The apparatus of claim 25, wherein the feedback module is further configured to:

27. The apparatus of claim 22, wherein the physical connection address is used to indicate the source database instance, and wherein the target database instance running on the second master node server is accessed according to the physical connection address;

the feedback module is further configured to:

28. The apparatus of claim 22, wherein the database instance management apparatus further comprises a cleaning module configured to:

29. A database instance access system comprising a node server and a management server, wherein:

the node server is used for acquiring a database instance access request; extracting a virtual connection address from the database instance access request; the virtual connection address corresponds to a target database instance requested to be accessed by the database instance access request; the node server is also used for sending an address mapping request which is corresponding to the source host address and the virtual connection address to the management server; the source host address corresponds to a source database instance; the source database instance runs on the node server;

30. A computer-readable storage medium, having stored thereon a computer program which, when executed by a processor, causes the processor to carry out the steps of the method according to any one of claims 1 to 14.

31. A computer device comprising a memory and a processor, the memory having stored therein a computer program that, when executed by the processor, causes the processor to perform the steps of the method of any one of claims 1 to 14.