CN112995247A

CN112995247A - Method, device and system for transmitting or processing data

Info

Publication number: CN112995247A
Application number: CN201911274842.5A
Authority: CN
Inventors: 周泰
Original assignee: Alibaba Group Holding Ltd
Current assignee: Alibaba Group Holding Ltd
Priority date: 2019-12-12
Filing date: 2019-12-12
Publication date: 2021-06-18

Abstract

The application discloses a method, a device and a system for data transmission or processing. Wherein, the method comprises the following steps: acquiring a target domain name from a domain name resolution record, wherein the target domain name is used for representing a network access between a distributed file system and different service systems; determining a virtual IP address corresponding to a target domain name, wherein the virtual IP address is an IP address corresponding to a load balancing example, and the load balancing example is used for providing access interfaces of different service systems to the outside; a data processing request is sent to a server in the distributed file system via a load balancing instance corresponding to the virtual IP address. The invention solves the technical problem that the data in the distributed file system example only supports the service system access of a single network environment, which causes the repeated service deployment.

Description

Method, device and system for transmitting or processing data

Technical Field

The present application relates to the field of computer technologies, and in particular, to a method, an apparatus, and a system for data transmission or processing.

Background

The distributed File System cloud service is a service of a fully hosted distributed File System provided by a cloud service manufacturer, provides a standard distributed File System (HDFS) interface, has a single name space, and supports the capability of rapid and flexible lifting and matching. The basic unit provided by the distributed file system cloud service for users is a distributed file system example, and the distributed file system example is a virtual distributed file system cluster providing an HDFS interface and is a container of user data. The distributed file system instance supports a computing storage separation architecture, namely, a user purchases a distributed file system cloud service instance as a storage system, purchases a virtual machine instance to deploy a computing engine of a Hadoop ecosystem as computing service, and the computing service accesses the storage service through a network instead of being directly deployed on the same set of server.

Because the private network has two-layer logic isolation capability, the security and the isolation are better, and new services of cloud product users are often deployed in the private network; however, at the same time, there are also some legacy services deployed within the classical network. Business systems within user-specific networks and business systems within classical networks often need to share data stored within distributed file system instances.

Aiming at the technical problem that data in a distributed file system instance only supports service system access of a single network environment in the related technology, so that service deployment is repeated, an effective solution is not provided at present.

Content of application

The embodiment of the application provides a method, a device and a system for sending or processing data, so as to at least solve the technical problem that the data in a distributed file system instance only supports the service system access of a single network environment, which causes the service deployment to be repeated.

According to an aspect of an embodiment of the present application, there is provided a method for transmitting data, including: acquiring a target domain name from a domain name resolution record, wherein the target domain name is used for representing a network access between a distributed file system and different service systems; determining a virtual IP address corresponding to a target domain name, wherein the virtual IP address is an IP address corresponding to a load balancing example, and the load balancing example is used for providing access interfaces of different service systems to the outside; a data processing request is sent to a server in the distributed file system via a load balancing instance corresponding to the virtual IP address.

According to another aspect of the embodiments of the present application, there is also provided a data processing method, including: a server in the distributed file system receives a data processing request from a service system through a load balancing example; and the server in the distributed file system sends an execution result to the service system through the load balancing instance, wherein the execution result is obtained after the data processing request is executed.

According to another aspect of the embodiments of the present application, there is also provided an apparatus for data transmission, including: the extraction module is used for acquiring a target domain name from the domain name resolution record, wherein the target domain name is used for representing a network access between the distributed file system and different service systems; the determining module is used for determining a virtual IP address corresponding to the target domain name, wherein the virtual IP address is an IP address corresponding to a load balancing example, and the load balancing example is used for providing access interfaces of different service systems to the outside; and the sending module is used for sending the data processing request to the server in the distributed file system through the load balancing instance corresponding to the virtual IP address.

According to another aspect of the embodiments of the present application, there is also provided a data processing system, including: the service system is used for sending a service processing request to the load balancing example on the load balancing server; the load balancing server is used for running a load balancing example which is used for providing access interfaces of different service systems for the outside and receiving service processing requests; and the server of the distributed file system is used for receiving the data processing request forwarded by the load balancing instance and returning the execution result of the data processing request through the load balancing instance.

According to another aspect of the embodiments of the present application, there is also provided a storage medium, where the storage medium includes a stored program, and when the program runs, a device on which the storage medium is located is controlled to execute any one of the above-mentioned methods for data transmission.

According to another aspect of the embodiments of the present application, there is also provided an electronic device, including: a processor; and a memory coupled to the processor for providing instructions to the processor for processing the following processing steps: acquiring a target domain name from a domain name resolution record, wherein the target domain name is used for representing a network access between a distributed file system and different service systems; determining a virtual IP address corresponding to a target domain name, wherein the virtual IP address is an IP address corresponding to a load balancing example, and the load balancing example is used for providing access interfaces of different service systems to the outside; a data processing request is sent to a server in the distributed file system via a load balancing instance corresponding to the virtual IP address.

In the embodiment of the application, a target domain name is obtained from a domain name resolution record, wherein the target domain name is used for representing a network access between a distributed file system and different service systems; then determining a virtual IP address corresponding to the target domain name, wherein the virtual IP address is an IP address corresponding to a load balancing example, and the load balancing example is used for providing access interfaces of different service systems to the outside; and finally, sending a data processing request to a server in the distributed file system through a load balancing instance corresponding to the virtual IP address. Compared with the prior art, in the scheme, the cloud service of the distributed file system abstracts different network paths into domain names, and the purpose of accessing data in the instance of the distributed file system is achieved by determining the virtual IP address corresponding to the load balancing instance associated with the target domain name and using the load balancing instance as an interface of different service systems to send a request to a target server in the distributed file system, so that the technical problem that the service deployment is repeated because the data in the instance of the distributed file system only supports the service system access in a single network environment is solved.

Drawings

The accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the application and together with the description serve to explain the application and not to limit the application. In the drawings:

fig. 1 is a block diagram of a hardware structure of a computer terminal (or a mobile device) for implementing a method for data transmission according to a first embodiment of the present application;

fig. 2 is a schematic diagram of a computer terminal (or mobile device) as a client terminal according to a first embodiment of the present application;

FIG. 3 is a flowchart of an alternative data transmission method according to an embodiment of the present application;

FIG. 4 is a block diagram illustrating an example of an alternative different business system sharing distributed file system according to the first embodiment of the present application shown in FIG. 3;

FIG. 5 is a timing diagram illustrating an alternative business system exchanging data with a distributed file system according to a first embodiment of the present application;

FIG. 6 is a flow chart of an alternative method of data processing according to the second embodiment of the present application;

fig. 7 is a schematic diagram of an alternative data transmission apparatus according to a third embodiment of the present application;

FIG. 8 is a schematic diagram of an alternative data processing apparatus according to a fourth embodiment of the present application;

FIG. 9 is a block diagram of an alternative data processing system in accordance with a fifth embodiment of the present application; and

fig. 10 is a block diagram of an alternative computer terminal according to a sixth embodiment of the present application.

Detailed Description

In order to make the technical solutions better understood by those skilled in the art, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only partial embodiments of the present application, but not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.

It should be noted that the terms "first," "second," and the like in the description and claims of this application and in the drawings described above are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used is interchangeable under appropriate circumstances such that the embodiments of the application described herein are capable of operation in sequences other than those illustrated or described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.

First, some terms or terms appearing in the description of the embodiments of the present application are applicable to the following explanations:

distributed File System (DFS): it is meant that the physical storage resources managed by the file system are not necessarily directly connected to the local node, but are connected to the node via a computer network. The design of the distributed file system is based on a client/server model. A typical network may include multiple servers for access by multiple users.

The Private network (VPC) is a customized Private network created by a user based on a Cloud service platform, and two layers of logic isolation are performed between different Private networks. A user may create and manage cloud product instances, such as cloud Server (ECS) instances, Load balancing (SLB) instances, and cloud Database (RDS) instances, within a self-created proprietary network.

The classic network, as opposed to the proprietary network, refers to a network environment that employs a traditional network architecture and is not virtualized.

Example 1

In accordance with an embodiment of the present application, there is provided a method embodiment of data transmission, it should be noted that the steps illustrated in the flowchart of the figure may be performed in a computer system such as a set of computer executable instructions, and that while a logical order is illustrated in the flowchart, in some cases the steps illustrated or described may be performed in an order different than here.

The method provided by the first embodiment of the present application may be executed in a mobile terminal, a computer terminal, or a similar computing device. Fig. 1 shows a block diagram of a hardware configuration of a computer terminal (or mobile device) for implementing a data transmission method. As shown in fig. 1, the computer terminal 10 (or mobile device 10) may include one or more (shown as 102a, 102b, … …, 102 n) processors 102 (the processors 102 may include, but are not limited to, processing devices such as a microprocessor MCU, a programmable logic device FPGA, a graphics processor GPU, a network processor NPU, an artificial intelligence AI chip, etc.), a memory 104 for storing data, and a transmission module 106 for communication functions. Besides, the method can also comprise the following steps: a display, an input/output interface (I/O interface), a Universal Serial Bus (USB) port (which may be included as one of the ports of the I/O interface), a network interface, a power source, and/or a camera. It will be understood by those skilled in the art that the structure shown in fig. 1 is only an illustration and is not intended to limit the structure of the electronic device. For example, the computer terminal 10 may also include more or fewer components than shown in FIG. 1, or have a different configuration than shown in FIG. 1.

It should be noted that the one or more processors 102 and/or other data processing circuitry described above may be referred to generally herein as "data processing circuitry". The data processing circuitry may be embodied in whole or in part in software, hardware, firmware, or any combination thereof. Further, the data processing circuit may be a single stand-alone processing module, or incorporated in whole or in part into any of the other elements in the computer terminal 10 (or mobile device). As referred to in the embodiments of the application, the data processing circuit acts as a processor control (e.g. selection of a variable resistance termination path connected to the interface).

The memory 104 may be used to store software programs and modules of application software, such as program instructions/data storage devices corresponding to the data transmission method in the embodiment of the present application, and the processor 102 executes various functional applications and data processing, i.e., implements the data transmission method of the application program, by running the software programs and modules stored in the memory 104. The memory 104 may include high speed random access memory, and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some examples, the memory 104 may further include memory located remotely from the processor 102, which may be connected to the computer terminal 10 via a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.

The transmission module 106 is used to receive or transmit data via a network. Specific examples of the network described above may include a wireless network provided by a communication provider of the computer terminal 10. In one example, the transmission module 106 includes a Network adapter (NIC) that can be connected to other Network devices through a base station to communicate with the internet. In one example, the transmission module 106 may be a Radio Frequency (RF) module, which is used for communicating with the internet in a wireless manner.

The display may be, for example, a touch screen type Liquid Crystal Display (LCD) that may enable a user to interact with a user interface of the computer terminal 10 (or mobile device).

Fig. 1 shows a block diagram of a hardware structure, which may be taken as an exemplary block diagram of not only the computer terminal 10 (or the mobile device) but also the server, and in an alternative embodiment, fig. 2 shows an embodiment of using the computer terminal 10 (or the mobile device) shown in fig. 1 as a client terminal in a block diagram. As shown in FIG. 2, the computer terminal 10 (or mobile device) may be connected or electronically connected to one or more servers 66 via a data network connection. In an alternative embodiment, the computer terminal 10 (or mobile device) may be a mobile computing device or the like. The data network connection may be a local area network connection, a wide area network connection, an internet connection, or other type of data network connection. The computer terminal 10 (or mobile device) may execute to connect to a network service executed by a server (e.g., a secure server) or a group of servers. A web server is a network-based user service such as social networking, cloud resources, email, online payment, or other online applications.

Under the above operating environment, the present application provides a data transmission method as shown in fig. 3. Fig. 3 is a flowchart of an alternative data transmission method according to embodiment 1 of the present application. As shown in fig. 3, the method may be applied in different business systems, and the implementation process of the present application is described in detail from the perspective of the business system, and may include the following steps:

step S302, a target domain name is obtained from the domain name resolution record, where the target domain name is used to represent a network path between the distributed file system and different service systems.

In an alternative, the domain name resolution record may be an implementation manner of a mount point, and the mount point may be an abstraction of a distributed file system server for network paths of different service systems, so as to facilitate a user to access data in an instance of the distributed file system using the network paths.

In an alternative, the target domain name may be a domain name to be accessed by the user.

It should be noted that the domain name resolution record may be a distributed database in which the target domain name and the virtual IP address are mapped to each other, for example, www.wikipedia.org is a domain name, and corresponds to the virtual IP address 208.80.152.2.

In an alternative, the different service systems may be proprietary networks or classical networks.

It should be noted that the logical isolation of the private network is mainly implemented by a logical isolator, which is an isolation component between different networks, and there is still a physical data channel connection between the isolated two ends, but it can be ensured that there is no data channel between the isolated two ends by technical means.

Step S304, determining a virtual IP address corresponding to the target domain name, where the virtual IP address is an IP address corresponding to a load balancing instance, and the load balancing instance is used to provide access interfaces of different service systems to the outside.

In an alternative, the Load balancing (SLB) instance may be created based on a virtual IP address, and located in a network path between the distributed file system and different service systems; the virtual IP addresses are the identification and the attribute of the load balancing examples, one virtual IP address is associated with one load balancing example, and the condition of associating other types of examples does not exist.

The SLB is a load balancing service working in a four-layer network, is responsible for balancing load and forwarding flow, and is communicated with a user client and a real server at the back end, so that a complete network link is provided. The SLB is also a set of software running on a separate set of servers.

In the above steps, after the virtual IP address corresponding to the target domain name is determined, the load balancing instance corresponding to the target domain name is determined.

Step S306, sending a data processing request to a server in the distributed file system via the load balancing instance corresponding to the virtual IP address.

In an alternative, the server may be a server that can respond to the data processing request, and may be one of a plurality of servers of a distributed file system.

In the above steps, after the service system sends the data processing request to the virtual IP address, the load balancing instance corresponding to the virtual IP address receives the request, and forwards the request to a certain server in the server list in the distributed file system, and the server executes the corresponding operation.

In an optional embodiment, the distributed file system cloud service respectively opens different network paths for the service system of the proprietary network and the service system of the classical network, and can simultaneously support the proprietary network service system and the classical network service system to share the distributed file system instance. When a user needs to access a Wikipedia website in a classic network environment, a service system of the classic network extracts a target domain name from a domain name resolution record, the target domain name represents a network path between a distributed file system and the classic network, then a virtual IP address corresponding to the target domain name is determined, for example 208.80.152.2, since a load balancing example is created based on the virtual IP address, the steps are equal to determining a load balancing example corresponding to the target domain name, and finally a target server in the distributed file system is determined by the load balancing example and a data processing request is sent to the target server. When a user needs to access other domain names in the environment of a proprietary network, the execution process of the user is similar to that of a classical network, and the difference is only that the target domain name extracted from the domain name resolution record represents a network path between the distributed file system and the proprietary network.

Optionally, after sending the data processing request to the server in the distributed file system via the load balancing instance corresponding to the virtual IP address in step S306, the method may further include:

step S308, receiving, by the load balancing instance, an execution result returned by the server in the distributed file system, where the execution result is obtained after the data processing request is executed.

In the scheme, the load balancing server is communicated with the user client and the real service server at the back end, so that a complete network link is provided.

It should be noted that SLB refers to a load balancing product, and for a group of servers, each server has a real IP address; for the above, the external service is provided through 1 virtual IP address. Some clients do not want to know how many servers the server side has, or cannot know how many servers the server side has due to network isolation, and load balancing is to meet the requirement, namely, a layer of abstraction is added between the client and the real server to provide a virtual IP address externally to serve as a unique access entrance of the back-end service; and carrying out traffic forwarding between the client and the real server.

In the above steps, after the load balancing instance corresponding to the virtual IP address sends a data processing request to the server in the distributed file system, the server executes the data processing request, and then returns the execution result to the load balancing instance, and returns the execution result to the service system through the load balancing instance.

Optionally, the selecting, by the load balancing instance, a target server from servers in the distributed file system according to the load balancing policy, and the sending, in step S306, the data processing request to the server in the distributed file system through the load balancing instance corresponding to the virtual IP address may include: and sending the data processing request to the target server via the load balancing instance corresponding to the virtual IP address.

In an alternative, the load balancing policy may adopt polling, weighted minimum number of connections, minimum response time, and the like. The load balancing strategy can reduce the impact on the service when a single server is abnormal, and improve the availability of the service. Meanwhile, by combining the elastic expansion service and dynamically adjusting the back-end server, the service can be quickly and elastically adjusted (expanded or contracted) so as to quickly cope with the development of the service.

In the above steps, the load balancing instance selects a target server from a plurality of servers of the distributed file system according to the load balancing policy, and then sends a data processing request to the target server through the load balancing instance corresponding to the virtual IP address.

In one embodiment of the present application, a target server is selected by a load balancing instance from a list of servers maintained by the load balancing instance. The load balancing instance maintains a list of servers, the servers in the list of servers being servers in the distributed file system.

In an alternative, the load balancing instance may manage a plurality of servers in the distributed file system, each server having a real IP address, and the load balancing instance may provide external services through a virtual IP.

In an alternative, the server list may be registered with real IP addresses of backend servers of the distributed file system cloud service.

In the above steps, after receiving the service of the data processing request, the load balancing instance forwards the request to a certain server in the server list.

Optionally, the service system may include: a service system of a proprietary network and a service system of a classical network; the private network is a private network of a tenant on the cloud, and the networks of different tenants are isolated from each other; a classical network is a network that is not isolated by a virtual network.

In an alternative, the isolation may be logical isolation.

It should be noted that, in the classical network, the cloud automatically allocates the IP address, which has a certain regularity and a high possibility of being attacked. The private network is an isolated secure network under the default condition because of the self-defined local area network IP address, and new services of cloud product users are often deployed in the private network, but the situation that part of services are deployed or are left in the classical network also exists.

In an optional embodiment of the present application, different types of networks have different load balancing instances, for example, in a case that the service system is a service system of a private network, the load balancing instance includes a first load balancing instance of the private network, at this time, an IP address can be applied from an IP address space of the private network, and an association relationship between the applied IP address and the first load balancing instance is established.

Before step S302 is executed to obtain the target domain name from the domain name resolution record, the distributed file system cloud service may open a network path of a private network, and in an alternative, the association relationship may be established in the following manner: an IP address IPvpc is applied in an IP address space of a private network, the IPvpc is used as a virtual IP address, and a load balancing example is created based on the virtual IP address.

In addition, after the load balancing example is created, the real IP address of a back-end server of the cloud service of the distributed file system can be registered in a server list of the load balancing example, a domain name resolution record is added in the domain name system, and a domain name is resolved to a virtual IP of the load balancing example, wherein the domain name is the implementation mode of a mounting point; the mounting point domain name is provided for the user, and the service system of the user can access the distributed file system instance through the mounting point domain name.

In another optional embodiment of the present application, different types of networks have different load balancing instances, for example, in a case that the service system is a service system of a classical network, the load balancing instance includes a second load balancing instance of the classical network, and at this time, an IP address can be applied from an IP address space of the classical network, and an association relationship between the applied IP address and the second load balancing instance is established.

Before step S302 is executed to obtain the target domain name from the domain name resolution record, the distributed file system cloud service may open a network path of a classical network, and in an alternative, the association relationship may be established in the following manner: an IP address IPclassic is applied in an IP address space of a classical network, the IPclassic is used as a virtual IP address, and a load balancing instance is created based on the virtual IP address.

Fig. 4 is a schematic structural diagram of an example of sharing a distributed file system by different business systems according to a first embodiment of the present application. As shown in fig. 4, the cloud service of the distributed file system opens a network access of the private network for the service system of the private network, and opens a network access of the classical network for the service system of the classical network, and developers only need to apply for IP addresses from IP address spaces of the private network and the classical network in advance and establish an association relationship between the IP addresses and respective load balancing instances, so as to achieve the purpose of supporting the private network service system and the classical network service system to share the distributed file system instance at the same time, and implement data sharing of the same distributed file system instance by the service system in different network environments.

Fig. 5 is a timing diagram of a business system exchanging data with a distributed file system according to a first embodiment of the present application. As shown in fig. 5, the timing diagram is divided into two phases of establishing a network path and accessing a distributed file system instance.

In the stage of establishing a network access, firstly, applying for an IP address in an IP address space of a service system; secondly, the IP address is used as a virtual IP address, and a load balancing example is created; thirdly, registering a back-end server IP of the distributed file system into a server list of the load balancing example; adding a domain name resolution record in the domain name system, and resolving the domain name to the virtual IP address of the load balancing instance; and fifthly, the domain name is used as a mounting point to be provided for a service system.

In the stage of accessing the distributed file system instance, a network module of a business system analyzes a domain name to obtain a virtual IP address of a load balancing instance; the service system sends a data processing request to a virtual IP address, and a load balancing server corresponding to the virtual IP address receives the request of the service system; thirdly, the load balancing server forwards the request to a target server in the distributed file system; receiving the data processing request by the target server, and executing the request; the target server returns the execution result to the load balancing server; sixthly, the load balancing server returns the execution result to the service system.

It is easy to note that the above-described method of the present application can be divided into two parts: a management control part and a data service part. In the management control part, namely the part for opening network paths of different service systems, the network types need to be distinguished; in the management service part, the network types do not need to be distinguished.

In the embodiment of the application, a target domain name is obtained from a domain name resolution record, wherein the target domain name is used for representing a network access between a distributed file system and different service systems; then determining a virtual IP address corresponding to the target domain name, wherein the virtual IP address is an IP address corresponding to a load balancing example, and the load balancing example is used for providing access interfaces of different service systems to the outside; and finally, sending a data processing request to a server in the distributed file system through a load balancing instance corresponding to the virtual IP address. Compared with the prior art, in the scheme, the cloud service of the distributed file system abstracts different network paths into domain names, sends requests to target servers in the distributed file system by determining virtual IP addresses corresponding to load balancing examples associated with target domain names and using the load balancing examples as interfaces of different service systems, and then receives execution results returned by the servers in the distributed file system through the load balancing examples to achieve the purpose of accessing data in the distributed file system examples; selecting a target server from a server list of the distributed file system through a load balancing strategy; the incidence relation between the applied virtual IP address and the respective load balancing examples is established in the proprietary network and the classical network in advance, so that a foundation is laid for getting through a network path, and the technical problem that the service deployment is repeated because the data in the distributed file system examples only support the service system access of a single network environment is solved.

It should be noted that, for simplicity of description, the above-mentioned method embodiments are described as a series of acts or combination of acts, but those skilled in the art will recognize that the present application is not limited by the order of acts described, as some steps may occur in other orders or concurrently depending on the application. Further, those skilled in the art should also appreciate that the embodiments described in the specification are preferred embodiments and that the acts and modules referred to are not necessarily required in this application.

Through the above description of the embodiments, those skilled in the art can clearly understand that the method according to the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but the former is a better implementation mode in many cases. Based on such understanding, the technical solutions of the present application may be embodied in the form of a software product, which is stored in a storage medium (e.g., ROM/RAM, magnetic disk, optical disk) and includes instructions for enabling a terminal device (e.g., a mobile phone, a computer, a server, or a network device) to execute the method of the embodiments of the present application.

Example 2

According to an embodiment of the present application, there is also provided a data processing method, as shown in fig. 6, the method may be applied to a server side in a distributed file system, and the detailed description of the implementation process of the present application from the perspective of a server in the distributed file system may include the following steps:

step S602, the server in the distributed file system receives a data processing request from the service system through the load balancing instance.

In an alternative, the server is a service server capable of responding to the data processing request, and may be one of a plurality of servers of a distributed file system.

In an alternative, the service system may be a proprietary network or a classical network.

Step S604, the server in the distributed file system sends an execution result to the service system via the load balancing instance, where the execution result is a result obtained after the data processing request is executed.

In one alternative, the load balancing instance connects the user client with the real back-end service server, thereby providing a complete network link.

It should be noted that SLB refers to a load balancing product, and for a group of service servers, each service server has a real IP address; for the above, the external service is provided through 1 virtual IP address. Some clients do not want to know how many service servers there are at the server, or cannot know how many service servers there are at the server due to network isolation, and load balancing meets the requirement, namely, a layer of abstraction is added between the client and the real service server to provide a virtual IP address externally to serve as a unique access entry of a back-end service; and carrying out flow forwarding between the client and the real service server.

Optionally, the load balancing instance is used to provide access interfaces of different service systems to outside, and before the server in the distributed file system performs step S602 to receive a data processing request from a service system through the load balancing instance, the load balancing instance may be created based on the following manner:

step S6011, the service system obtains a target domain name from the domain name resolution record, where the target domain name is used to indicate a network path between the distributed file system and different service systems.

In an alternative, the domain name resolution record may be an implementation manner of a mount point, and the mount point may abstract network paths of different service systems for a distributed file system cloud service, so as to facilitate a user to access data in a distributed file system instance using the network paths.

It should be noted that the domain name resolution record may be a distributed database in which the target domain name and the virtual IP address are mapped to each other, for example, www.wikipedia.org is a domain name, and corresponds to the IP address 208.80.152.2.

Step S6012, the virtual IP address corresponding to the target domain name is determined, and a load balancing example is created based on the virtual IP address.

In one alternative, the load balancing instances are located in network paths between the distributed file system and different business systems. (ii) a The virtual IP addresses are the identification and the attribute of the load balancing examples, one virtual IP address is associated with one load balancing example, and the condition of associating other types of examples does not exist.

In the above steps, after the virtual IP address corresponding to the target domain name is determined, the load balancing instance corresponding to the target domain name is determined. In the above steps, after the service system sends the data processing request to the virtual IP address, the load balancing instance corresponding to the virtual IP address receives the request, and forwards the request to a certain server in the server list in the distributed file system, the server executes the data processing request, then returns the execution result to the load balancing instance, and returns the execution result to the service system through the load balancing instance.

Optionally, the server in the distributed file system is determined by a load balancing instance according to a load balancing policy.

And the load balancing example selects a target server from a plurality of servers of the distributed file system according to the load balancing strategy, and then sends a data processing request to the target server through the load balancing example corresponding to the virtual IP address.

Optionally, the server in the distributed file system is selected from a server list maintained by the load balancing instance through the load balancing instance.

In an alternative, the load balancing instance may manage a plurality of service servers in the distributed file system, each service server has a real IP address, and the load balancing instance may provide services to the outside through a virtual IP.

In an alternative, the server list may be registered with real IP addresses of backend servers of the distributed file system cloud service. After receiving the service of the data processing request, the load balancing example forwards the request to a certain server in the server list.

In an alternative, the isolation may be logical isolation.

Optionally, if the load balancing instance includes a first load balancing instance of the proprietary network, the method may further include: and under the condition that the service system is a service system of a private network, applying for an IP address from an IP address space of the private network, and establishing an incidence relation between the applied IP address and the first load balancing instance.

Before the server in the distributed file system receives the data processing request from the service system through the load balancing instance in step S602, the cloud service of the distributed file system may open a network path of a private network, and in an alternative, the association relationship may be established in the following manner: an IP address IPvpc is applied in an IP address space of a private network, the IPvpc is used as a virtual IP address, and a load balancing example is created based on the virtual IP address.

Optionally, if the load balancing instance comprises a second load balancing instance of the classical network, the method may further comprise: and under the condition that the service system is the service system of the classical network, applying for the IP address from the IP address space of the classical network, and establishing an incidence relation between the applied IP address and the second load balancing instance.

Before the server in the distributed file system receives the data processing request from the service system through the load balancing instance in step S602, the cloud service of the distributed file system may open a network path of a classic network, and in an alternative, the association relationship may be established in the following manner: an IP address IPclassic is applied in an IP address space of a classical network, the IPclassic is used as a virtual IP address, and a load balancing instance is created based on the virtual IP address.

It is easy to note that the above-described method of the present application can equally be divided into two parts: a management control part and a data service part. In the management control part, namely the part for opening network paths of different service systems, the network types need to be distinguished; in the management service part, the network types do not need to be distinguished.

In the embodiment of the application, a server in a distributed file system first receives a data processing request from a service system through a load balancing instance, and then sends an execution result to the service system through the load balancing instance, wherein the execution result is a result obtained after the data processing request is executed. Compared with the prior art, in the scheme, the distributed file system cloud service takes the load balancing example as an interface of different business systems, receives the data processing request from the business system through the load balancing example, receives the execution result returned by the server in the distributed file system through the load balancing example, and sends the execution result to the business system, so that the purpose of accessing the data in the distributed file system example is achieved; selecting a target server from a server list of the distributed file system through a load balancing strategy; the incidence relation between the applied virtual IP address and the respective load balancing examples is established in the proprietary network and the classical network in advance, so that a foundation is laid for getting through a network path, and the technical problem that the service deployment is repeated because the data in the distributed file system examples only support the service system access of a single network environment is solved.

It should be noted that, reference may be made to the relevant description in embodiment 1 for optional or preferred embodiments of this embodiment, but the present invention is not limited to the disclosure in embodiment 1, and is not described herein again.

Example 3

According to an embodiment of the present application, there is also provided an apparatus for data transmission, as shown in fig. 7, the apparatus 700 includes: an acquisition module 702, a determination module 704, and a sending module 706.

The obtaining module 702 is configured to obtain a target domain name from a domain name resolution record, where the target domain name is used to indicate a network path between a distributed file system and different service systems.

A determining module 704, configured to determine a virtual IP address corresponding to the target domain name, where the virtual IP address is an IP address corresponding to a load balancing instance, and the load balancing instance is used to provide access interfaces of different external service systems.

A sending module 706, configured to send a data processing request to a server in the distributed file system via the load balancing instance corresponding to the virtual IP address.

Optionally, the apparatus further comprises: and the return module is used for receiving an execution result returned by the server in the distributed file system through the load balancing instance after the data processing request is sent to the server in the distributed file system through the load balancing instance corresponding to the virtual IP address, wherein the execution result is a result obtained after the data processing request is executed.

Optionally, the load balancing instance selects a target server from servers of the distributed file system according to a load balancing policy, and the sending module may include: and the sending submodule is used for sending the data processing request to the target server through the load balancing instance corresponding to the virtual IP address.

Optionally, the apparatus may further include: and the selection module is used for selecting a target server from the server list maintained by the load balancing example through the load balancing example.

Optionally, if the load balancing instance includes a first load balancing instance of the private network, the apparatus may further include: and the first association module is used for applying for the IP address from the IP address space of the proprietary network and establishing the association relationship between the applied IP address and the first load balancing example under the condition that the service system is the service system of the proprietary network.

Optionally, if the load balancing instance comprises a second load balancing instance of a classical network, the apparatus may further comprise: and the second association module is used for applying for the IP address from the IP address space of the classical network and establishing the association relationship between the applied IP address and the second load balancing example under the condition that the service system is the service system of the classical network.

It should be noted here that the acquiring module 702, the determining module 704 and the sending module 706 correspond to steps S302 to S306 in embodiment 1, and the three modules are the same as the corresponding steps in the implementation example and application scenario, but are not limited to the disclosure in embodiment 1. It should be noted that the above modules may be operated in the computer terminal 10 provided in embodiment 1 as a part of the apparatus.

Example 4

According to an embodiment of the present application, there is also provided an apparatus for data processing, as shown in fig. 8, the apparatus 800 includes: a receiving module 802 and a sending module 804.

The receiving module 802 is configured to receive, by a server in the distributed file system, a data processing request from a service system through a load balancing instance.

A sending module 804, configured to send, by a server in the distributed file system, an execution result to the service system via the load balancing instance, where the execution result is a result obtained after the data processing request is executed.

Optionally, the load balancing example is configured to provide access interfaces of different service systems to outside, and the apparatus may further include: the creating module is configured to create a load balancing instance before a server in the distributed file system receives a data processing request from the service system through the load balancing instance, where the creating module may include: and the extraction module is used for acquiring a target domain name from the domain name resolution record by the service system, wherein the target domain name is used for representing a network access between the distributed file system and different service systems. And the determining module is used for determining the virtual IP address corresponding to the target domain name and creating a load balancing example based on the virtual IP address.

Optionally, if the load balancing instance includes a first load balancing instance of the private network, the apparatus may further include: and the first association module is used for applying for the IP address from the IP address space of the private network and establishing the association relationship between the applied IP address and the first load balancing example under the condition that the service system is the service system of the private network.

It should be noted here that the receiving module 802 and the sending module 804 correspond to steps S602 to S604 in embodiment 2, and the two modules are the same as the corresponding steps in the implementation example and application scenarios, but are not limited to the disclosure in embodiment 2. It should be noted that the above modules may be operated in the computer terminal 10 provided in embodiment 1 as a part of the apparatus.

Example 5

According to an embodiment of the present application, there is also provided a data processing system, as shown in fig. 9, the system including: a business system 902, a load balancing server 904, and a server 906 of a distributed file system.

The service system 902 is configured to send a service processing request to a load balancing instance on a load balancing server.

And the load balancing server 904 is configured to run a load balancing instance, where the load balancing instance is configured to provide an access interface for different external service systems and receive a service processing request.

And the server 906 of the distributed file system is used for receiving the data processing request forwarded by the load balancing instance and returning the execution result of the data processing request through the load balancing instance.

Optionally, the load balancing instance is created based on: the service system acquires a target domain name from the domain name resolution record, wherein the target domain name is used for representing a network access between the distributed file system and different service systems; the service system determines a virtual IP address corresponding to the target domain name and creates a load balancing instance based on the virtual IP address.

Optionally, the load balancing instance selects a target server from servers of the distributed file system according to a load balancing policy; sending a data processing request to a server in the distributed file system via a load balancing instance corresponding to the virtual IP address, comprising: a data processing request is sent to the server via a load balancing instance corresponding to the virtual IP address.

Optionally, the load balancing instance selects the target server from a list of servers maintained by the load balancing instance.

Optionally, the service system includes: a service system of a proprietary network and a service system of a classical network; the private network is a private network of a tenant on the cloud, and the networks of different tenants are isolated from each other; a classical network is a network that is not isolated by a virtual network.

Optionally, the load balancing example includes: a first load balancing instance of the proprietary network; and under the condition that the service system is a service system of a private network, applying for an IP address from an IP address space of the private network, and establishing an incidence relation between the applied IP address and the first load balancing instance.

Optionally, the load balancing example includes: a second load balancing instance of the classical network; and under the condition that the service system is the service system of the classical network, applying for the IP address from the IP address space of the classical network, and establishing an incidence relation between the applied IP address and the second load balancing instance.

In an embodiment of the present application, a data processing system includes: the service system is used for sending a service processing request to the load balancing example on the load balancing server; the load balancing server is used for running a load balancing example which is used for providing access interfaces of different service systems for the outside and receiving service processing requests; and the server of the distributed file system is used for receiving the data processing request forwarded by the load balancing instance and returning the execution result of the data processing request through the load balancing instance. Compared with the prior art, in the scheme, the distributed file system cloud service takes the load balancing example as an interface of different business systems, receives the data processing request from the business system through the load balancing example, receives the execution result returned by the server in the distributed file system through the load balancing example, and sends the execution result to the business system, so that the purpose of accessing the data in the distributed file system example is achieved; selecting a target server from a server list of the distributed file system through a load balancing strategy; the incidence relation between the applied virtual IP address and the respective load balancing examples is established in the proprietary network and the classical network in advance, so that a foundation is laid for getting through a network path, and the technical problem that the service deployment is repeated because the data in the distributed file system examples only support the service system access of a single network environment is solved.

Example 6

The embodiment of the application can provide a computer terminal, and the computer terminal can be any one computer terminal device in a computer terminal group. Optionally, in this embodiment, the computer terminal may also be replaced with a terminal device such as a mobile terminal.

Optionally, in this embodiment, the computer terminal may be located in at least one network device of a plurality of network devices of a computer network.

In this embodiment, the computer terminal may execute program codes of the following steps in the data transmission method of the application program: acquiring a target domain name from a domain name resolution record, wherein the target domain name is used for representing a network access between a distributed file system and different service systems; determining a virtual IP address corresponding to a target domain name, wherein the virtual IP address is an IP address corresponding to a load balancing example, and the load balancing example is used for providing access interfaces of different service systems to the outside; a data processing request is sent to a server in the distributed file system via a load balancing instance corresponding to the virtual IP address.

Optionally, fig. 10 is a block diagram of a computer terminal according to an embodiment of the present application. As shown in fig. 10, the computer terminal a may include: one or more (only one shown) processors 102 and memory 104.

The memory may be configured to store software programs and modules, such as program instructions/modules corresponding to the data transmission method and apparatus in the embodiments of the present application, and the processor executes various functional applications and data processing by running the software programs and modules stored in the memory, that is, the data transmission method is implemented. The memory may include high speed random access memory, and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some examples, the memory may further include memory located remotely from the processor, which may be connected to the computer terminal a via a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.

The processor can call the information and the application program stored in the memory through the transmission module to execute the following steps: acquiring a target domain name from a domain name resolution record, wherein the target domain name is used for representing a network access between a distributed file system and different service systems; determining a virtual IP address corresponding to a target domain name, wherein the virtual IP address is an IP address corresponding to a load balancing example, and the load balancing example is used for providing access interfaces of different service systems to the outside; a data processing request is sent to a server in the distributed file system via a load balancing instance corresponding to the virtual IP address.

Optionally, the processor may further execute the program code of the following steps: after a data processing request is sent to a server in the distributed file system through a load balancing instance corresponding to the virtual IP address, an execution result returned by the server in the distributed file system is received through the load balancing instance, wherein the execution result is a result obtained after the data processing request is executed.

Optionally, the processor may further execute the program code of the following steps: the selecting, by the load balancing instance, a target server from servers in the distributed file system according to the load balancing policy, and sending a data processing request to the server in the distributed file system through the load balancing instance corresponding to the virtual IP address may include: and sending the data processing request to the target server via the load balancing instance corresponding to the virtual IP address.

Optionally, the processor may further execute the program code of the following steps: a target server is selected by the load balancing instance from a list of servers maintained by the load balancing instance.

Optionally, the processor may further execute the program code of the following steps: the service system can comprise a service system of a proprietary network and a service system of a classical network; the private network is a private network of a tenant on the cloud, and the networks of different tenants are isolated from each other; a classical network is a network that is not isolated by a virtual network.

Optionally, the processor may further execute the program code of the following steps: if the load balancing instance comprises a first load balancing instance of the proprietary network, the method may further comprise: and under the condition that the service system is a service system of a private network, applying for an IP address from an IP address space of the private network, and establishing an incidence relation between the applied IP address and the first load balancing instance.

Optionally, the processor may further execute the program code of the following steps: if the load balancing instance comprises a second load balancing instance of a classical network, the method may further comprise: and under the condition that the service system is the service system of the classical network, applying for the IP address from the IP address space of the classical network, and establishing an incidence relation between the applied IP address and the second load balancing instance.

It can be understood by those skilled in the art that the structure shown in fig. 10 is only an illustration, and the computer terminal may also be a terminal device such as a smart phone (e.g., an Android phone, an iOS phone, etc.), a tablet computer, a palmtop computer, a Mobile Internet Device (MID), a PAD, and the like. Fig. 10 does not limit the structure of the electronic device. For example, the computer terminal 10 may also include more or fewer components (e.g., network interfaces, display devices, etc.) than shown in FIG. 10, or have a different configuration than shown in FIG. 10.

Those skilled in the art will appreciate that all or part of the steps in the methods of the above embodiments may be implemented by a program instructing hardware associated with the terminal device, where the program may be stored in a computer-readable storage medium, and the storage medium may include: flash disks, Read-Only memories (ROMs), Random Access Memories (RAMs), magnetic or optical disks, and the like.

Example 7

Embodiments of the present application also provide a storage medium. Optionally, in this embodiment, the storage medium may be configured to store program codes executed by the data transmission or processing method provided in the first or second embodiment.

Optionally, in this embodiment, the storage medium may be located in any one of computer terminals in a computer terminal group in a computer network, or in any one of mobile terminals in a mobile terminal group.

Optionally, in this embodiment, the storage medium is configured to store program code for performing the following steps: acquiring a target domain name from a domain name resolution record, wherein the target domain name is used for representing a network access between a distributed file system and different service systems; determining a virtual IP address corresponding to a target domain name, wherein the virtual IP address is an IP address corresponding to a load balancing example, and the load balancing example is used for providing access interfaces of different service systems to the outside; a data processing request is sent to a server in the distributed file system via a load balancing instance corresponding to the virtual IP address.

In the embodiment of the application, different network paths are abstracted into domain names by the cloud service of the distributed file system by running program codes stored in a storage medium, a request is sent to a target server in the distributed file system by determining a virtual IP address corresponding to a load balancing instance associated with the target domain name and using the load balancing instance as an interface of different service systems, and then an execution result returned by the server in the distributed file system is received by the load balancing instance, so that the aim of accessing data in the instance of the distributed file system is fulfilled; selecting a target server from a server list of the distributed file system through a load balancing strategy; the incidence relation between the applied virtual IP address and the respective load balancing examples is established in the proprietary network and the classical network in advance, so that a foundation is laid for getting through a network path, and the technical problem that the service deployment is repeated because the data in the distributed file system examples only support the service system access of a single network environment is solved.

It should be noted that, reference may be made to the relevant description in embodiment 1 for alternative or preferred embodiments of this embodiment, and details are not described here again.

The above-mentioned serial numbers of the embodiments of the present application are merely for description and do not represent the merits of the embodiments.

In the above embodiments of the present application, the descriptions of the respective embodiments have respective emphasis, and for parts that are not described in detail in a certain embodiment, reference may be made to related descriptions of other embodiments.

In the embodiments provided in the present application, it should be understood that the disclosed technology can be implemented in other ways. The above-described embodiments of the apparatus are merely illustrative, and for example, the division of the units is only one type of division of logical functions, and there may be other divisions when actually implemented, for example, a plurality of units or components may be combined or may be integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, units or modules, and may be in an electrical or other form.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.

The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application may be substantially implemented or contributed to by the prior art, or all or part of the technical solution may be embodied in a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a removable hard disk, a magnetic or optical disk, and other various media capable of storing program codes.

The foregoing is only a preferred embodiment of the present application and it should be noted that those skilled in the art can make several improvements and modifications without departing from the principle of the present application, and these improvements and modifications should also be considered as the protection scope of the present application.

Claims

1. A data transmission method, comprising:

acquiring a target domain name from a domain name resolution record, wherein the target domain name is used for representing a network access between a distributed file system and different service systems;

determining a virtual IP address corresponding to the target domain name, wherein the virtual IP address is an IP address corresponding to a load balancing instance, and the load balancing instance is used for providing access interfaces of different service systems to the outside;

sending the data processing request to a server in a distributed file system via a load balancing instance corresponding to the virtual IP address.

2. The method of claim 1, wherein after sending the data processing request to a server in a distributed file system via a load balancing instance corresponding to the virtual IP address, the method further comprises:

and receiving an execution result returned by the server in the distributed file system through the load balancing example, wherein the execution result is obtained after the data processing request is executed.

3. The method of claim 1,

the method further comprises the following steps: the load balancing example selects a target server from the servers of the distributed file system according to a load balancing strategy;

sending the data processing request to a server in a distributed file system via a load balancing instance corresponding to the virtual IP address, comprising: sending the data processing request to the target server via a load balancing instance corresponding to the virtual IP address.

4. The method of claim 3, further comprising:

selecting, by the load balancing instance, the target server from a list of servers maintained by the load balancing instance.

5. The method of claim 1, wherein the business system comprises: a service system of a proprietary network and a service system of a classical network; the private network is a private network of a tenant on the cloud, and the networks of different tenants are isolated from each other; the classical network is a network without virtual network isolation.

6. The method of claim 5, wherein the load balancing instance comprises: a first load balancing instance of the proprietary network; the method further comprises the following steps:

and under the condition that the service system is a service system of a proprietary network, applying for an IP address from an IP address space of the proprietary network, and establishing an association relation between the applied IP address and the first load balancing instance.

7. The method of claim 5, wherein the load balancing instance comprises: a second load balancing instance of the classical network; the method further comprises the following steps:

and under the condition that the service system is a service system of a classic network, applying for an IP address from an IP address space of the classic network, and establishing an association relation between the applied IP address and the second load balancing instance.

8. A data processing method, comprising:

a server in the distributed file system receives a data processing request from a service system through a load balancing example;

and the server in the distributed file system sends an execution result to the service system through the load balancing instance, wherein the execution result is a result obtained after the data processing request is executed.

9. The method of claim 8, wherein the load balancing instance is used for providing access interfaces of different service systems, and is created based on the following ways:

the service system acquires a target domain name from the domain name resolution record, wherein the target domain name is used for representing a network access between the distributed file system and different service systems;

and determining a virtual IP address corresponding to the target domain name, and creating the load balancing example based on the virtual IP address.

10. The method of claim 8, wherein the business system comprises: a service system of a proprietary network and a service system of a classical network; the private network is a private network of a tenant on the cloud, and the networks of different tenants are isolated from each other; the classical network is a network without virtual network isolation.

11. The method of claim 10, wherein the load balancing instance comprises: a first load balancing instance of the proprietary network; the method further comprises the following steps:

and under the condition that the service system is a service system of a private network, applying for an IP address from an IP address space of the private network, and establishing an association relation between the applied IP address and the first load balancing instance.

12. The method of claim 10, wherein the load balancing instance comprises: a second load balancing instance of the classical network; the method further comprises the following steps:

13. A data transmission apparatus, comprising:

the extraction module is used for acquiring a target domain name from the domain name resolution record, wherein the target domain name is used for representing a network access between the distributed file system and different service systems;

a determining module, configured to determine a virtual IP address corresponding to the target domain name, where the virtual IP address is an IP address corresponding to a load balancing instance, and the load balancing instance is used to provide access interfaces of different external service systems;

a sending module, configured to send the data processing request to a server in a distributed file system via a load balancing instance corresponding to the virtual IP address.

14. A data processing system, comprising:

the service system is used for sending a service processing request to the load balancing example on the load balancing server;

the load balancing server is used for operating the load balancing example, and the load balancing example is used for providing access interfaces of different service systems for the outside and receiving the service processing request;

and the server of the distributed file system is used for receiving the data processing request forwarded by the load balancing instance and returning the execution result of the data processing request through the load balancing instance.

15. A storage medium, characterized in that the storage medium comprises a stored program, wherein when the program runs, a device in which the storage medium is located is controlled to execute the method for transmitting data according to any one of claims 1 to 7.

16. An electronic device, comprising:

a processor; and

a memory coupled to the processor for providing instructions to the processor for processing the following processing steps:

acquiring a target domain name from a domain name resolution record, wherein the target domain name is used for representing a network access between a distributed file system and different service systems; determining a virtual IP address corresponding to the target domain name, wherein the virtual IP address is an IP address corresponding to a load balancing instance, and the load balancing instance is used for providing access interfaces of different service systems to the outside; sending the data processing request to a server in a distributed file system via a load balancing instance corresponding to the virtual IP address.