CN110830531A - Resource request processing method and device, storage system, electronic device and storage device - Google Patents

Abstract

The application discloses a method and a device for processing a resource request, a storage system, an electronic device and a storage device, wherein the method comprises the following steps: the method comprises the steps that a storage device receives a first resource request for requesting to acquire data from a previous storage device, wherein the storage device is a source station of the previous storage device, and the first resource request at least carries identification information of the previous storage device; and if the storage device determines that the data is not stored, determining whether to send a second resource request for requesting to acquire the data to a subsequent storage device according to the identification information carried by the first resource request, wherein the subsequent storage device is a source station of the storage device, so that a cycle back source phenomenon occurring in the resource request is avoided.

Description

Resource request processing method and device, storage system, electronic device and storage device

Technical Field

The present application relates to the field of computer applications, and in particular, to a method and an apparatus for processing a resource request, and a distributed storage system, an electronic device, and a storage device.

Background

The cloud storage is an important service in the cloud, and various storage devices are integrated through application software through cluster application, a grid technology or a distributed file system and the like, so that data storage and service access are provided for the outside. For data storage, a number of problems need to be faced when transitioning from one physical environment and a single array to a fully virtualized, highly dynamic storage environment, with data migration being the most fundamental and critical step in cloud storage.

In the prior art, one of the methods pertaining to the live migration is that a user can return to a source by configuring a mirror image in a cloud storage system, so as to implement data live migration of multiple data centers or storage centers, for example: all data of a user are in a Beijing data center, but the user has data of a storage part in Hangzhou and Shenzhen aiming at a service scene, so that serial retrace from Shenzhen to Hangzhou and from Hangzhou to Beijing can be configured, but a configuration of error from Beijing re-mirroring to Shenzhen exists in the configured retrace process, and the configuration mode causes data migration to enter a dead cycle. Similarly, another data live migration mode is that a user has data in both the two cloud storage systems, and mirror image return sources are configured in both the two cloud storage systems to each other, so that the user can obtain the data regardless of which cloud storage system the user accesses, however, in this scenario, the phenomenon that the data return sources from each other still exists, so that the data live migration enters a dead cycle.

Disclosure of Invention

The application provides a resource request processing method, which aims to solve the problem that in the prior art, when data is subjected to live migration, a cycle back source occurs. The application further provides a processing device for the resource request and a processing system for the resource request.

The application provides a method for processing a resource request, which comprises the following steps:

receiving, by a storage device, a first resource request requesting to acquire data from a previous storage device, where the storage device is a source station of the previous storage device, and the first resource request carries at least identification information of the previous storage device;

and if the storage device determines that the data is not stored, determining whether to send a second resource request for requesting to acquire the data to a subsequent storage device according to the identification information carried by the first resource request, wherein the subsequent storage device is a source station of the storage device.

In some embodiments, the determining, according to the identification information carried in the first resource request, whether to send a second resource request requesting to acquire the data to a subsequent storage device includes:

and judging whether the identification information carried by the first resource request comprises the identification information of the storage device, if not, sending the second resource request, wherein the second resource request comprises the identification information carried by the first resource request and the identification information of the storage device.

In some embodiments, said sending said second resource request is followed by:

in response to the first resource request, returning the data or a status code indicating that the data is not present that the subsequent storage device returned in response to the second resource request.

In some embodiments, the determining, according to the identification information carried in the first resource request, whether to send a second resource request requesting to acquire the data to a subsequent storage device includes:

and judging whether the identification information carried by the first resource request comprises the identification information of the storage device, if so, not sending the second resource request.

In some embodiments, after determining not to send the second resource request, comprising:

in response to the first resource request, returning information indicating that the data does not exist or information indicating that the request failed.

In some embodiments, the first and second resource requests comprise a non-standard header field comprising the identification information.

In some embodiments, the method further comprises:

the method further comprises the following steps:

the storage equipment receives an acquisition request which is sent by a client and requests to acquire the data;

and if the storage device determines that the data is not stored, sending a third resource request for requesting to acquire the data to the subsequent storage device, wherein the third resource request comprises the identification information of the storage device.

In some embodiments, before determining whether to send a second resource request requesting to acquire the data to a second storage device according to the identification information carried in the first resource request, the method further includes:

if the first resource request does not carry the identification information of the prior storage device, the storage device judges whether the first resource request meets a pre-configured back-to-source condition or not;

and if the back-source condition is met, the storage equipment sends a second resource request for acquiring the data to the subsequent storage equipment.

In some embodiments, the preconfigured feed-back condition comprises at least one of:

the source IP address of the resource request is a specific network segment;

the general header field of the resource request is a specific value;

the request parameters of the resource request include specific parameters.

In some embodiments, the storage device comprises an object-based storage device.

The present application further provides a device for processing a resource request, including:

a receiving unit, configured to receive, at a storage device, a first resource request requesting to acquire data from a previous storage device, where the storage device is a source station of the previous storage device, and the first resource request carries at least identification information of the previous storage device;

the judging unit is used for judging whether the storage equipment stores the data or not, and if not, the determining unit is started;

the determining unit is configured to determine, at the storage device, whether to send a second resource request requesting to acquire the data to a subsequent storage device according to the identification information carried in the first resource request, where the subsequent storage device is a source station of the storage device.

The present application also provides a distributed storage system, which includes a plurality of storage devices, where the storage devices include the apparatus for processing resource requests as described above.

The present application further provides an electronic device, comprising:

a processor;

a memory for storing a program for processing network platform generated data, which program, when read and executed by said processor, performs the steps of the processing method according to the resource request as described above.

The storage device is used for storing network platform generated data and a program for processing the network platform generated data;

the program, when read and executed by the processor, performs the steps of the processing method according to the resource request as described above.

Compared with the prior art, the method has the following advantages:

according to the resource request processing method, a storage device receives a first resource request for acquiring data from a previous storage device, the first resource request at least carries identification information of the previous storage device, and under the condition that the storage device does not store the data, whether a second resource request for acquiring the data is sent to a subsequent storage device is determined according to the identification information carried by the first resource request, so that the storage device receiving the first resource request can judge whether the storage device can continuously send the resource request to the subsequent storage device serving as a storage device source station according to the identification information carried in the first resource request, and further the occurrence of a cyclic resource request is avoided.

The application also provides a distributed storage system, which comprises a plurality of storage devices, wherein the storage devices can execute the processing method of the resource request, and whether to send a second resource request is determined by judging the identification information carried in the first resource request among the plurality of storage devices, so that the infinite circulation of the resource request is avoided.

Drawings

FIG. 1 is a flowchart of an embodiment of a method for processing a resource request provided herein;

fig. 2 is a schematic structural diagram of an embodiment of a device for processing a resource request provided in the present application;

FIG. 3 is a flow chart illustrating a resource request processing method from a sending side according to the present application;

fig. 4 is a flowchart of a first embodiment of configuring, by a sending side, identification information carried in a resource request processing method provided by the present application;

fig. 5 is a flowchart of a second embodiment of configuring identification information carried in a resource request by a sending side in a method for processing a resource request provided by the present application;

fig. 6 is a schematic structural diagram of a transmitting side in a resource request processing apparatus provided in the present application;

fig. 7 is a schematic structural diagram of a first embodiment of configuring identification information carried in a resource request by a sending side in a resource request processing apparatus provided in the present application;

fig. 8 is a schematic structural diagram of a second embodiment of configuring identification information carried in a resource request by a sending side in a resource request processing apparatus provided in the present application;

FIG. 9 is a flow chart illustrating a method for processing a resource request from a receiving side according to the present application;

FIG. 10 is a schematic structural diagram of an embodiment of a receiving side of a resource request processing apparatus provided in the present application;

FIG. 11 is a block diagram of a system for processing resource requests provided herein;

FIG. 12 is a schematic structural diagram of a first embodiment of a system for processing resource requests provided in the present application;

fig. 13 is a schematic structural diagram of a second embodiment of a resource request processing system according to the present application.

Detailed Description

In the following description, numerous specific details are set forth in order to provide a thorough understanding of the present application. This application is capable of implementation in many different ways than those herein set forth and of similar import by those skilled in the art without departing from the spirit of this application and is therefore not limited to the specific implementations disclosed below.

The terminology used in the description herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. The description used in this application and in the appended claims is for example: "a," "an," "first," and "second," etc., are not necessarily limited to a quantity or order, but rather are used to distinguish one type of information from another.

Referring to fig. 1, fig. 1 is a flowchart illustrating a processing method of a resource request (also referred to as a back-source request) according to a first embodiment of the present application, where the processing method includes:

step S101: the storage device receives a first resource request from a prior storage device requesting to obtain data, the storage device being a source station of the prior storage device. The first resource request carries at least identification information of a previous storage device, for example, the first resource request may carry identification information of one or more storage devices, including the previous storage device, that request the respective source station to acquire the data;

step S102: and judging whether the storage device stores the data or not, and if not, executing the step S103.

Step S103: and the storage equipment determines whether to send a second resource request for requesting to acquire the data to the subsequent storage equipment according to the identification information carried by the first resource request, wherein the subsequent storage equipment is a source station of the storage equipment.

It is understood that, in step S102, it is determined whether the storage device stores the data, and if the determination result is yes, step S104 may be directly performed, that is: the data is returned.

Determining whether to send a second resource request for acquiring the data to the subsequent storage device according to the identification information carried by the first resource request, wherein the determining comprises the following steps:

and judging whether the identification information carried by the first resource request comprises the identification information of the storage device, if not, sending a second resource request, wherein the second resource request comprises the identification information carried by the first resource request and the identification information of the storage device.

The identification information of the storage devices may be a non-standard header field agreed in advance in the first resource request, for example, a non-standard header field (e.g., os-tag) for recording the identification information of the storage devices is added in the header of the HTTP request. Identification information for one or more storage devices requesting the respective source station to obtain the data may be obtained by obtaining the contents of the non-standard header field.

It should be noted that, the most common way to acquire the data is through http request, that is, there is a request header when sending the request, and there is a response header when receiving the response, and the information needed for mutual communication between the sending end and the receiving end is transmitted through these "headers", similar to key: value's key-value pair. Usually, a set standard header field is provided in a request header of an http request, and some custom header fields are also reserved, where the custom header fields can be regarded as non-standard header fields.

When the identification information carried by the first resource request does not include the identification information of the storage device, the relevant information may be returned in response to the first resource request, where the relevant information may be the data returned by the subsequent storage device in response to the second resource request if the subsequent storage device stores the data, and the status code indicating that the data does not exist, such as a status code returned 404 by the subsequent storage device in response to the second resource request if the subsequent storage device does not store the data. The prior storage device and the subsequent storage device may be different storage devices or may be the same storage device.

And when judging whether the identification information carried by the first resource request comprises the identification information of the storage equipment, if so, not sending a second resource request.

It will be appreciated that after determining not to send the second resource request, information indicating that the data is not present or that the request failed may be returned in response to the first resource request. The information of the request failure may include information of a reason of the request failure, for example: the identification information carried in the first resource request received by the storage device does not have the identification information of the storage device, so that the second resource request and other similar related information cannot be sent.

In this embodiment, the first resource request and the second resource request may include a non-standard header field, and the non-standard header field may include identification information.

The above description is made on the processing procedure of the resource request in which the non-standard header field is defined in advance, and the processing method of the resource request provided in this embodiment may further include:

the storage equipment receives an acquisition request which is sent by a client and requests to acquire the data;

and judging whether the storage equipment stores the data or not, if not, sending a third resource request for requesting to acquire the data to the subsequent storage equipment, wherein the third resource request comprises the identification information of the storage equipment.

In fact, the data acquisition request is not only sent by the client, but also sent by other devices. The storage device may comprise an object-based storage device.

It should be noted that, for storage devices belonging to the same storage system, it can be easily defined in advance to use a certain non-standard header field to record identification information of storage devices respectively requesting to obtain the same data from respective source stations, thereby implementing a cyclic judgment on resource requests requesting to obtain the same data in the same storage system. Of course, for storage devices belonging to different storage systems, the identification information may also be recorded by using a pre-agreed non-standard header field, thereby implementing a cyclic judgment of resource requests requesting to acquire the same data in different storage systems. However, in more cases, storage devices belonging to different storage systems are serviced by different vendors, and thus it is generally impossible to unify protocols and to agree in advance on non-standard header fields for recording identification information.

In view of this situation, in the embodiment provided in the present application, when determining whether the storage device stores the data, if the determination result is negative, that is, the data is not stored, it may be determined first whether the first resource request at least carries the identification information of the previous storage device, that is, it is determined whether the first resource request includes a non-standard header field agreed in advance. If the first resource request does not carry the identification information of the previous storage device, that is, the first resource request does not include the prepended non-standard header field, the storage device may determine whether to send a second resource request for acquiring the data to a source station of the storage device, that is, the subsequent storage device, by judging whether the first resource request satisfies a pre-configured back-to-source condition, thereby avoiding a resource request cycle problem of requesting to acquire the same data between different storage systems of which protocols are not unified. And if so, sending a second resource request, wherein the second resource request does not carry the identification information of the storage equipment at the moment because the non-standard header field is not agreed between the storage system where the storage equipment is located and the storage system where the subsequent storage equipment is located. If not, the second resource request is not sent, and information indicating the request failure and/or the reason of the request failure may be returned to the storage device sending the first resource request.

The back-to-source condition of the storage device can be configured according to the resource requests from the storage systems where the storage device is located, which allow the storage systems to continue sending resource requests, so that only the resource requests from the storage systems can satisfy the back-to-source condition, and the storage device can continue sending resource requests requesting the same data to its source station.

Or may be configured according to resource requests from storage systems where the storage device is located, and the storage system does not allow the storage device to continue sending resource requests, so that the resource requests from the storage systems do not necessarily satisfy the back-to-source condition, and the storage device does not continue sending resource requests requesting the same data to its source station. For example, if the prior storage device sending the first resource request is also the source of the above-mentioned storage device — the subsequent storage device, i.e., the prior storage device and the subsequent storage device are the same, the storage device and the prior storage device (which is also the subsequent storage device in this case) are mutually the opposite source. In order to avoid the circulation of the resource request between the storage system where the storage device is located and the storage system where the previous storage device is located, the back-to-source condition of the storage device may be configured according to the first resource request sent by the previous storage device, so that the first resource request sent by the previous storage device inevitably does not satisfy the back-to-source condition of the storage device, and thus the storage device does not continue to send a second resource request requesting the same data to the subsequent storage device (which is also the previous storage device at this time), thereby avoiding the circulation.

It can be understood that the initiation of the resource request may be determined according to a determination result that whether the first resource request meets a pre-configured back-to-source condition, that is, when the back-to-source condition is met, the second resource request is sent to a source station of the storage device, that is, the subsequent storage device, without executing a step of determining whether to send the second resource request for acquiring the data to the subsequent storage device according to the identification information carried by the first resource request, and executing the subsequent operation according to a determination result of the identification information. Namely: the initiation of the resource request can be initiated in two forms, one is initiated by judging the identification information of the storage device, and the other is initiated by a back-to-source condition.

In this embodiment, the configuration of the back-source condition may include at least one of the following conditions:

the source IP address of the resource request is a specific network segment;

the generic header field of the resource request is a specific value, wherein the generic header field is a standard header field that is commonly set in the request header, such as: User-Agent, Host, etc.;

the request parameters of the resource request include specific parameters.

Of course, the above configuration of the source return condition is merely an example, and is not limited to the content in practice. For example: one or more of request parameters, request headers, etc. may be set in the http request.

The above description is made on the processing procedure of the resource request without specifying the non-standard header field in advance, and the processing method of the resource request provided in this embodiment may further include:

the storage equipment receives an acquisition request which is sent by a client and requests to acquire the data;

and judging whether the storage equipment stores the data or not, if not, judging whether the acquisition request meets a back-to-source condition or not, and if so, sending a third resource request for requesting to acquire the data to the subsequent storage equipment.

The above is a description of an embodiment of a method for processing a resource request provided in the present application. Corresponding to the foregoing embodiment of the processing method provided as a resource request, the present application also discloses an embodiment of a processing apparatus for a resource request, please refer to fig. 2, since the apparatus embodiment is basically similar to the method embodiment, the description is relatively simple, and related points can be referred to the partial description of the method embodiment. The device embodiments described below are merely illustrative.

As shown in fig. 2, the present application provides a device for processing a resource request, including:

a receivingunit 201, configured to receive, at a storage device, a first resource request requesting to acquire data from a previous storage device, where the storage device is a source station of the previous storage device, and the first resource request carries at least identification information of the previous storage device;

a judgingunit 202, configured to judge whether the storage device stores the data, and if not, enter the determining unit;

a determiningunit 203, configured to determine, at the storage device, according to the identification information carried in the first resource request, whether to send a second resource request requesting to acquire the data to a subsequent storage device, where the subsequent storage device is a source station of the storage device.

It is understood that the judgingunit 202 enters the first returningunit 204 if the judging result is that the storage device stores the data, and the first returningunit 204 can return the data.

Thedetermination unit 203 includes:

the first judging subunit is used for judging whether the identification information carried by the first resource request comprises the identification information of the storage device or not, and entering the sending subunit according to a judgment result;

and when the judgment result shows that the identification information carried by the first resource request does not include the identification information of the storage device, the sending subunit is configured to send a second resource request, where the second resource request includes the identification information carried by the first resource request and the identification information of the storage device.

After transmitting the second resource request, the transmitting subunit includes: a return subunit;

and a return subunit, configured to return, in response to the first resource request, the data returned by the subsequent storage device in response to the second resource request or a status code indicating that the data does not exist.

And when the judgment result is that the identification information carried by the first resource request comprises the identification information of the storage device, the sending subunit is used for not sending the second resource request.

And the return subunit is used for responding to the first resource request and returning information indicating that the data does not exist or information indicating that the request fails.

The first resource request and the second resource request include a non-standard header field, the non-standard header field including identification information.

The judgingunit 202 may include: a source returning condition judgment unit;

and the source returning condition judging unit is used for judging whether the first resource request meets the source returning condition configured in advance or not after judging that the storage equipment does not store the data and if the first resource request does not carry the identification information of the prior storage equipment, and if the first resource request meets the source returning condition configured in advance, entering the sending subunit and sending the second resource request.

And when the judgment result of the source returning condition judgment unit is not satisfied, entering a sending subunit and not sending the second resource request.

The source returning condition judging unit includes: the condition setting subunit is configured to configure the fallback condition in advance, where the preconfigured fallback condition may include at least one of the following conditions:

the source IP address of the resource request is a specific network segment;

the general header field of the resource request is a specific value;

the request parameters of the resource request include specific parameters.

The apparatus for processing a resource request provided by the present application may further include:

a receiving unit configured to receive, at a storage device, an acquisition request requesting acquisition of data, which is transmitted by a client;

and a third resource request sending unit, configured to send, at the storage device, a third resource request requesting to acquire the data to a subsequent storage device when the data is not stored according to the determination result of the determining unit, where the third resource request includes the identification information of the storage device.

The storage device comprises an object-based storage device.

Based on the above description, the present application further provides a distributed storage system, where the system includes a plurality of storage devices, and the storage devices include the processing apparatus for the resource request.

The present application further provides an electronic device, comprising:

a processor;

and the memory is used for storing a program for processing the data generated by the network platform, and the program executes the processing method of the resource request when being read and executed by the processor.

The application also provides a storage device for storing the data generated by the network platform and a program for processing the data generated by the corresponding network platform;

when the program is read and executed by the processor, the processing method of the resource request is executed.

Referring to fig. 3, fig. 3 is a flowchart of an embodiment of a sending side of a resource request processing method provided in the present application.

Firstly, it should be noted that, how to implement the acquisition of data resources, specifically, the resource request processing method provided by the present application implements the acquisition of resource data in a source returning manner adopted in the resource request process, and because there is a situation of circular source returning in the acquisition process, the resource request processing method provided by the present application avoids the generation of a circular phenomenon in the source returning process.

Step S301: when the stored data does not exist, the storage device may generate a resource request for acquiring the data, where the resource request carries information for determining whether to continue sending a resource request for the data.

The resource request is usually a function of a cloud storage product, and means that when a client accesses a cloud storage system to obtain the data, if the data does not exist in the current cloud storage system accessed, the current cloud storage system can synchronously or asynchronously obtain the data from a source station configured by the client, return the data to the client, and write the data into the cloud storage system accessed before while returning, thereby implementing live migration of the data, and when the client can briefly understand that the storage device does not store the obtained data, the client can return to the source station of the storage device to obtain the data. The resource request may be a mirror back-to-source request, and the mirror back-to-source request in the following description is a back-to-source request.

Because, in the cloud storage system or between different cloud storage devices, in order to avoid the occurrence of the cyclic mirror image source returning request in the cloud storage product, the information for judging whether to continue sending the mirror image source returning request for the data is configured in the mirror image source returning request, and the configuration mode may be configured to configure the information for judging whether to continue sending the mirror image source returning request for the data according to the type of the mirror image source returning request sender, that is:

the step of generating a mirror back-to-source request for acquiring data in step S301 includes:

and configuring information carried in the mirror image source returning request for judging whether to continuously send the mirror image source returning request aiming at the data according to the type of the mirror image source returning request sender.

In cloud storage, mirroring back to the source can occur between storage nodes in the same cloud storage system or between storage cloud nodes of different cloud storage systems, so that the generated mirroring back to the source request can configure information carried in the mirroring back to the source request according to the types of different mirroring back to source request senders, where the mirroring back to source request sender may be a previous storage device, a storage device or a subsequent storage device. For example, if the mirror back source request sender is used as the storage device, the mirror back source request receiver is used as the subsequent storage device. For example, if the mirror back source request receiver is used as the storage device, the mirror back source request sender is the previous storage device. The prior storage device and the subsequent storage device may be different devices or may be the same device.

It should be explained that the cyclic mirror back-to-source request may refer to that, in a process of requesting to acquire the data, a user requests to perform a back-and-forth cycle between storage nodes in the same cloud storage system or between storage cloud nodes of different cloud storage systems, and in a general case, when the data is not acquired, the cyclic mirror back-to-source request is trapped. The mirror back-to-source request is exemplified in the same storage system and between different cloud storage systems, that is: the corresponding description is made for different types of storage nodes, which may be a preceding storage device, a storage device, and a succeeding storage device as described above.

First, it should be noted that the mirror image source returning request configured in the sending side of the resource request processing method provided by the present application may be configured according to the type of the mirror image source returning request sending side, and any configuration may be only required to satisfy that the mirror image source returning request is carried in the mirror image source returning request to determine whether to continue sending the mirror image source returning request to a subsequent storage node (which may also be referred to as a subsequent storage device) for obtaining the data. Therefore, the present application provides two embodiments to explain the generation of the mirror-back-source request process, but the two embodiments do not limit the generation process of the mirror-back-source request in the sending side of the resource request processing method provided by the present application, and the following is embodiment one.

Referring to fig. 4 in conjunction with fig. 3, fig. 4 is a flowchart of a first embodiment of information carried in a mirror image return source request configured in a sending side of a resource request processing method according to the present application.

Configuring information carried in the mirror image source returning request and used for judging whether to continuously send the mirror image source returning request aiming at the data information according to the type of the mirror image source returning request sender, wherein the information comprises the following steps:

step S401: when the mirror image source returning request sender is a storage node type in the same cloud storage system, adding identification information of the mirror image source returning request sender in a request head of the mirror image source returning request;

the storage nodes in the same cloud storage system in step S401 may be data storage centers in the same cloud storage system, for example: the data storage centers bucketta, buckettb, buckettc and the like included in the same cloud storage system may be referred to as storage nodes. In general, the cyclic mirroring source back request includes at least two storage nodes, and both the two storage nodes may send mirroring source back requests to the next-level node, for example, the storage system includes bucketta and buckettb, the bucketta may send mirroring source back requests to the buckettb, and the buckettb may also send mirroring source back requests to the bucketta, where the bucketta may be an initial storage node and the buckettb is a terminal storage node. In the sending process of the mirror image source returning request, after bucketta sends the mirror image source returning request to buckettb, if the data is not obtained, buckettb sends the mirror image source returning request to bucketta, and then the mirror image source returning request is sent step by step to cause the obtained data to enter a reciprocating cycle.

For the storage node of this type, the identification information of the sender of the mirror image back-to-source request is added to the request header of the mirror image back-to-source request, which may be adding a header to the HTTP header, where the header includes a key, the key is a field name, the value is a content such as a pre-agreed value or parameter, for example, a bucket name passing through the entire path, such as adding a tag to the HTTP header when the bucket ta is mirrored back to the bucket tb: when mirroring back to source to C, A, B adds tag in HTTP header: and A, B, and so on, namely generating a mirror image back-source request for acquiring the data by taking the name of the storage node on the data path as the identification information.

The header in the HTTP used in the above description explains the addition of the identification information, and actually, other header files may also be used to add the identification information.

Based on the above content, it can be understood that the mirror image source returning request sender provided by the present application may include at least two senders, and the identification information of the current mirror image source returning request sender and the identification information of the superior sender of the current mirror image source returning request sender are used as information for determining whether to continue sending the mirror image source returning request for the data. The identification information may be identification information with recognizable features, and in this embodiment, for example: device information or location information.

In this embodiment, when the number of mirror back source request senders is at least two or more, the information that is generated in the mirror back source request for acquiring the data and used for determining whether to continue sending the mirror back source request for the data may be link identification information on the entire request path.

The storage node that generates the mirror back source request for obtaining the data may be an initial storage node or an intermediate storage node or an end storage node; when the number of the storage nodes is two, the storage nodes comprise an initial storage node and a terminal storage node; when the number of the storage nodes is three, the storage nodes comprise an initial storage node, an intermediate storage node and a tail end storage node; when the number of storage nodes is more than three, the number of intermediate storage nodes may be plural.

When the storage node generating the mirror image back-to-source request for acquiring the data is the initial storage node (the initial storage node may be a first previous storage device receiving the data acquisition request of the client), the initial storage node generating the mirror image back-to-source request for acquiring the data may generate the mirror image back-to-source request for acquiring the data by sending the data acquisition request by the user; when the storage node generating the mirror back-to-source request for acquiring the data is an intermediate storage node (the intermediate storage node may be the storage device), the mirror back-to-source request for acquiring the data may be generated by a mirror back-to-source request for acquiring the data of an initial storage node or a higher intermediate node of the intermediate storage node, and a mirror back-to-source request of a current intermediate storage node is generated; when the storage node that generates the mirror back-to-source request for acquiring the data is the end storage node (the end storage node may be the above-mentioned posterior storage device), the mirror back-to-source request for acquiring the data may be generated by a mirror back-to-source request for acquiring the data of an upper intermediate storage node of the end storage node, and the mirror back-to-source request for acquiring the data of the end storage node is generated.

Step S402: and taking the identification information of the mirror image source returning request sender as the information for judging whether to continuously send the mirror image source returning request aiming at the data.

When the mirror image source returning request sender is a storage node type in the same cloud storage system, adding identification information of the mirror image source returning request sender in a request header of the mirror image source returning request step S401, taking the identification information of the mirror image source returning request sender as information for judging whether to continuously send out the mirror image source returning request for the data, and specifically taking a name of a storage node as the identification information for judging whether to continuously send out the mirror image source returning request for the data in step S402.

The above is a description of the mirror image back-to-source request sender being a storage node in the same cloud storage system, and the following is a description of different cloud storage systems.

Referring to fig. 5 in conjunction with fig. 3, fig. 5 is a flowchart illustrating a second embodiment of configuring information carried in a mirror image source back request in a sending method of a mirror image source back request according to the present application;

configuring information carried in the mirror image source returning request and used for judging whether to continuously send the mirror image source returning request aiming at the data information according to the type of the mirror image source returning request sender, wherein the information comprises the following steps:

step S501: when the mirror image source returning request sender is a cloud node type between different cloud storage systems, adding identification information for judging whether the source returning condition of the mirror image source returning request receiver is met or not in the mirror image source returning request;

in step S501, the identification information added in the mirror image source returning request is used to determine whether the source returning condition of the mirror image source returning request receiver is satisfied, that is, it is determined according to the identification information that the source returning condition satisfied party can trigger the mirror image source returning of the mirror image source returning request receiver.

In step S501, the different cloud storage systems may refer to a cloud node a of the cloud storage a, a cloud node B of the cloud storage B, a cloud node C of the cloud storage C, and the like, and include at least two cloud nodes when performing the mirror image return request.

Under the condition that at least three cloud nodes a, b and c are included, the cloud node b is a source station of the cloud node a, the cloud node c is a source station of the cloud node b, and the cloud node b is used as a storage device, so that the former storage device is the cloud node a, and the latter storage device is the cloud node c. However, in the case that only two cloud nodes are included, for example, only the cloud node a and the cloud node b exist, assuming that the cloud node b is a source station of the cloud node a, the cloud node a is also a source station of the cloud node b, and the cloud node b is used as a storage device, then the previous storage device and the subsequent storage device are the same, that is, the cloud node a.

In the embodiment provided in fig. 5, the information for determining whether to continue sending the mirror image back-to-source request to the data information is carried in the mirror image back-to-source request, which may be a condition that triggers mirror image back-to-source of the cloud node a, for example: configuring the host data content in the cloud node, and triggering mirroring back to the source when the host of the received mirroring back to the source request HTTP includes the preconfigured host data content, for example: the method comprises the steps that a host is configured in advance in a cloud node a to be a.com, and a host head in a mirror image source returning request is generated to be initiated to the cloud node a to configure the a.com, so that the cloud node a can send the mirror image source returning request to a next cloud node b when data are not obtained, the data content of the host is also preset to be b.com by the cloud node b, and the cloud node b can send the mirror image source returning request to the next cloud node by carrying b.com in the host head of the mirror image source returning request HTTP generated by the cloud node a, and so on.

It should be noted that, when the cloud nodes are only the cloud node a and the cloud node b, the identification information in the mirror image source returning request generated by the cloud node b is different from the condition set by the cloud node a for triggering the mirror image source returning request, and therefore, when the cloud node b sends the mirror image source returning request to the cloud node a, the carried information for judging whether the cloud node a can continuously send the mirror image source returning request is different from the trigger condition preset in the cloud node a with respect to the data, and therefore, the cloud node a cannot send the mirror image source returning request any more, or it can be understood that the cloud node a cannot regenerate the mirror image source returning request.

It can be understood that the above description of adding the identification information of the cloud node for different cloud storage is to use a host header of HTTP, and actually, other identification information may be added to other mirror image back-to-source requests, for example, the back-to-source condition is that a source IP conforms to a certain specific network segment, a user-agent header is equal to a certain specific value, information carried in the request includes a certain specific field, and the like, which are not listed one by one here.

Step S502: and adding identification information for judging whether the receiver meets the mirror back-to-source request in the mirror back-to-source request as information for judging whether to continuously send the mirror back-to-source request aiming at the acquired data.

The above content is an illustration of configuring information carried in a mirror source back request for different types of mirror source back request senders when generating a mirror source back request, and whether the mirror source back request sender sends the mirror source back request may determine whether to generate the mirror source back request for acquiring the data according to an acquisition result of acquiring the data, for example: if the user wants to acquire that the data does not exist on the storage node or the cloud node, namely the acquisition result is empty, the storage node or the cloud node generates a mirror image source returning request for acquiring the data from the next-stage storage node or the cloud node.

Similarly, in an embodiment in which the mirror image back-to-source request sender is a cloud node between different cloud storage systems, when the mirror image back-to-source request senders are at least two or more, the information for determining whether to continue sending the mirror image back-to-source request for the data, which is generated in the mirror image back-to-source request for obtaining the data, may be identification information different from other cloud nodes.

The cloud node that generates the mirror back source request to obtain the data may be an initial cloud node or an intermediate cloud node or an end cloud node. When the number of the cloud nodes is two, the cloud nodes comprise an initial cloud node and a terminal cloud node; when the number of the cloud nodes is three, the cloud nodes comprise an initial cloud node, a middle cloud node and a tail end cloud node; when the number of cloud nodes is more than three, the number of intermediate cloud nodes may be plural.

When the cloud node generating the mirror image source returning request for acquiring the data is the initial cloud node, the initial cloud node generating the mirror image source returning request for acquiring the data can generate the mirror image source returning request for acquiring the data by sending the data acquiring request through a user; when the cloud node generating the mirror image source returning request for acquiring the data is the intermediate cloud node, the mirror image source returning request for acquiring the data can be generated through the mirror image source returning request for acquiring the data of the initial cloud node or a superior intermediate cloud node of the intermediate cloud node, and the mirror image source returning request of the current intermediate cloud node is generated; when the cloud node generating the mirror image back-to-source request for acquiring the data is the end cloud node, the mirror image back-to-source request for acquiring the data can be generated through a mirror image back-to-source request for acquiring the data of a higher-level intermediate cloud node of the end cloud node, and the mirror image back-to-source request for acquiring the data of the end cloud node is generated.

It should be noted that the mirror back source request sender may refer to a storage node or a cloud node in this embodiment.

The above is a detailed description of the generation of the mirror image source returning request for acquiring the data in step S301, and after the information for determining whether the data sends the mirror image source returning request is configured in the mirror image source returning request, the mirror image source returning request may be sent to the next-stage storage node in the same cloud storage system after the data is not acquired, or the mirror image source returning request may be sent to the next cloud node between different cloud storage systems, so that after the mirror image source returning request for acquiring the data is generated in step S301, the mirror image source returning request for acquiring the data is sent, that is:

step S302: a mirror back request is issued to obtain the data.

When a mirror image source returning request is made in the same cloud storage system or among different cloud storages, a mirror image source returning request for acquiring the data is sent out, the mirror image source returning request for acquiring the data can be sent out according to the result of acquiring the data, and actually, the mirror image source returning request for acquiring the data can be sent out according to actual requirements instead of being limited to being sent out when the result of acquiring the data is empty (the data is not stored).

The above is a description of an embodiment of a method for processing a resource request provided in the present application, and the present application also discloses an embodiment of a sending side of a device for processing a resource request, which corresponds to the aforementioned embodiment of a sending side of a processing method provided as a mirror resource request, please refer to fig. 6, since the embodiment of the device is basically similar to the embodiment of the method, the description is relatively simple, and related points can be referred to the partial description of the embodiment of the method. The device embodiments described below are merely illustrative.

As shown in fig. 6, fig. 6 is a schematic structural diagram of a sending apparatus for mirroring a resource request according to the present application, where the apparatus includes:

agenerating unit 601, configured to generate a mirror image source returning request for acquiring the data, where the mirror image source returning request carries information used for determining whether to continue sending a mirror image source returning request for the data;

thegeneration unit 601 includes: and the configuration subunit is used for configuring the mirror image source returning request to carry information for judging whether to continuously send the mirror image source returning request aiming at the data according to the type of the mirror image source returning request sender.

For configuring a subunit, a configuration process is described in two embodiments provided in this application, please refer to fig. 7 in combination with fig. 6, where fig. 7 is a schematic structural diagram of a first embodiment of information carried in a request for configuring a mirror resource in a sending device for a mirror resource request provided in this application.

As shown in fig. 7, the configuration subunit includes:

a first addingsubunit 701, configured to add, when the mirror-image source-returning request sender is a storage node type in the same cloud storage system, identification information of the mirror-image source-returning request sender in a request header of the mirror-image source-returning request;

the first addingsubunit 701 is specifically configured to use the identification information of the current mirror back-to-source request sender and the identification information of the upper-level sender of the current mirror back-to-source request sender as information for determining whether to continue sending mirror back-to-source requests for the data.

A first determiningsubunit 702, configured to determine the identification information of the mirror back source request sender as information for determining whether to continue issuing mirror back source requests for the data.

Fig. 7 provides a process of configuring a mirror resource request when the type of a mirror resource request sender is a storage node type in the same cloud storage system.

Fig. 6 is a schematic view, shown in fig. 8, and fig. 8 is a schematic structural diagram of a second embodiment of configuring information carried in a mirror resource request in a sending device of a mirror resource request according to the present application.

The configuration subunit includes:

a second addingsubunit 801, configured to add, in the mirror image source returning request, identification information used for determining whether a source returning condition of a mirror image source returning request receiver is met when the mirror image source returning request sender is a cloud node type between different cloud storage systems;

the specific process of the second addingsubunit 801 may refer to step S501 in the method, and will not be described herein again.

And the second determining subunit is configured to determine, as the information for determining whether to continue issuing the mirror image back-to-source request for obtaining the data, that the identification information added to the mirror image back-to-source request for determining whether the back-to-source condition of the mirror image back-to-source request receiver is satisfied.

Based on the above, the generatingunit 601, in generating the mirror back-to-source request for acquiring data, includes:

and the generation determining subunit is used for determining whether to generate a mirror image back-source request for acquiring the data according to the acquisition result of acquiring the data.

The sendingunit 602 sends a request for generating a mirror image for obtaining the data back to the source.

The transmittingunit 602 includes:

and the sending determination subunit is used for determining whether to send out a mirror image back-source request for acquiring the data or not according to the acquisition result of the data.

The above is a description of a specific procedure of a method and an apparatus for processing a source return request provided by the present application from the perspective of a transmitting side, and the following is a description of a method and an apparatus for processing a source return request provided by the present application from the perspective of a receiving side. As shown in fig. 9, fig. 9 is a flowchart of an embodiment of a processing method for a back source request provided from a receiving side perspective in the present application, where the processing method includes: based on the above description of the sending side, the processing method of the request to source provided by the present application can be understood from the perspective of the receiving side, specifically as follows:

step S901: receiving a mirror image source returning request for acquiring the data, wherein the mirror image source returning request carries information for judging whether to continuously send the mirror image source returning request aiming at the data;

corresponding to the description of the sending side, the receiver that receives the mirror back-to-source request for acquiring the data in step S901 may refer to a storage node or a cloud node, that is, the type of the receiver that receives the mirror back-to-source request is the same as the type of the sender that sends the mirror back-to-source request. As with the back-to-source request on the sending side, the storage node or cloud node may include: the system includes a prior storage device, a storage device, and a subsequent storage device, wherein the storage device is a source of the prior storage device and the subsequent storage device is a source of the storage device. Also, the preceding storage device and the succeeding storage device may be different devices or may be the same device. .

It should be noted that, in this embodiment, descriptions of the received mirror image source returning requests in the same cloud storage type are adopted, that is, a receiver of the mirror image source returning requests when each storage node belongs to the same cloud storage system, or a receiver of the mirror image source returning requests when each cloud node is a cloud node between different cloud storage systems, that is, the receiver of the mirror image source returning requests may be a same type of storage node in the same cloud storage system, or may be different types of cloud nodes between different cloud storage systems.

Receiving a mirror image source returning request for acquiring the data, where the mirror image source returning request carries information for determining whether to continue sending the mirror image source returning request for the data, and receiving information carried in different mirror image source returning requests according to a type of a mirror image source returning request receiver, specifically, the method includes:

when the mirror image source returning request receiver is a storage node type in the same cloud storage system, the received mirror image source returning request carries identification information of all storage nodes through which the mirror image source returning request passes, and a related description process of a sending side may be specifically referred to, which is not described herein again.

It should be noted that, in the storage node types in the same cloud storage system, the storage nodes are the same storage nodes in the same cloud storage system, for example: and the storage node bucket A, the storage node bucket B and the storage node bucket C in the cloud storage system X.

When the mirror image source returning request receiver is a cloud node type between different cloud storage systems, adding identification information for judging whether a source returning condition of the mirror image source returning request receiver is met in the mirror image source returning request, which may specifically refer to a related description process of a sending side and is not described herein again.

It should be noted that, in the types of cloud nodes between different cloud storage systems, the cloud nodes are different cloud nodes between different cloud storage systems, for example: the cloud storage system comprises a cloud node a of a cloud storage system A, a cloud node B of a cloud storage system B, a cloud node C of a cloud storage system C, a cloud storage system which is not used among the cloud storage system A, the cloud storage system B and the cloud storage system C, and correspondingly, different cloud nodes are arranged among the cloud node a, the cloud node B and the cloud node C.

The above is a relatively brief description of the process of receiving the mirror resource request for acquiring the data, and specific contents may refer to the description contents of the sending method of the mirror resource request provided in the present application.

It should be noted that, when the receiver receiving the mirror image source returning request for acquiring the data is a storage node in the same cloud storage system or a cloud node of a different cloud storage component, it is necessary to determine the received mirror image source returning request, and determine whether the mirror image source returning request receiver can continue to send the mirror image source returning request when the data acquisition result is empty, so that the following step S902 needs to be executed.

Step S902: determining whether to continue sending the mirror image back-to-source request according to the information carried in the mirror image back-to-source request and used for judging whether to continue sending the mirror image back-to-source request aiming at the data,

the specific implementation process of step S902 may include:

and determining whether to continuously send the mirror back-to-source request according to the type of the mirror back-to-source request receiver of the mirror back-to-source request. The recipient is the storage device that received the request back to the source.

And the type of the mirror image return source request receiver is the type in the cloud storage or the type between the cloud storages.

When the mirror image source returning request receiver is a storage node in the same cloud storage system, judging whether information carried in the mirror image source returning request for acquiring the data comprises identification information of the current mirror image source returning request receiver or not, and if so, stopping initiating the mirror image source returning request by the mirror image source returning request receiver.

Specifically, when the mirror back source request receiver is a storage node type in the same cloud storage system, for example: if the receiver receiving the mirror image source returning request is bucketB, the bucketB receives the mirror image source returning request from bucketA, the bucketA adds A to a header of HTTP in the bucketB mirror image source returning request, judges whether the information carried in the received mirror image source returning request carries identification information of the bucketB, if the information is not carried, the bucketB continues to send the mirror image source returning request to a next-level storage node, and so on, the bucketC receives the mirror image source returning request from the bucketB, the bucketD receives the mirror image source returning request from the bucketC, the bucketA receives the mirror image source returning request from the bucketD, when bucketta receives a mirror back-to-source request from buckettd, it finds that the contents in the header are a, B, C, D, including the identification information of bucket A, so that the mirror image return source request received by bucket tA includes the identification information of bucket tA itself, and further determining that the cyclic mirror back-to-source condition exists, the bucketta does not continue to initiate the mirror back-to-source request.

Determining whether to continuously send the mirror back-to-source request according to the type of the mirror back-to-source receiver of the mirror back-to-source request, wherein the determining comprises the following steps:

when the mirror image source returning request receiver is of a cloud node type between different cloud storage systems, judging whether information carried in a mirror image source returning request for acquiring the data includes identification information of the current mirror image source returning request receiver or not, and if not, stopping initiating the mirror image source returning request by the mirror image source returning request receiver.

Specifically, when the mirror request receiver is a cloud node type of a different cloud storage system component, for example: when a receiving party receiving the mirror image source returning request is a cloud node B, the cloud node B receives the mirror image source returning request sent by the cloud node A, the cloud node B judges whether a host head in the received mirror image source returning request comprises identification information of b.com, if the host head in the received mirror image source returning request does not comprise the identification information of b.com, the mirror image source returning request is continuously sent to the cloud node C, the cloud node C judges whether the received mirror image source returning request from the cloud node B comprises the identification information of c.com, if the received mirror image source returning request does not comprise the identification information of c.com, the mirror image source returning request is continuously sent to the next cloud node, and the condition that the cloud node A triggers the mirror image source returning request is preset to be a.com identification information, so that the cloud node A can continuously send the mirror image source returning request to the next cloud node only if the received mirror image source returning request comprises the identification information of a.com, and the generation of.

It should be noted that, in the foregoing judgment process, the judgment may be performed only when the storage node or the cloud node receiving the mirror image source return request is an initial node, or may be performed on each storage node or cloud receiving the mirror image source return request, and the processing method for the mirror image resource request provided by the present application mainly aims to avoid a situation that a cyclic mirror image source return request occurs in a storage node in the same cloud storage system or in cloud nodes between different cloud storage systems, so that it is only necessary to perform judgment on the initial storage node or the initial cloud node receiving the mirror image source return request, and the intermediate storage node and/or the end storage node, or the intermediate cloud node and/or the end cloud node may not perform judgment.

The information for determining whether to continue sending the mirror image back-to-source request for the data is carried in the mirror image back-to-source request, and after the determination is completed, if the determination result is that the mirror image back-to-source request is stopped to be initiated, the method may further include:

and receiving returned mirror image back source request failure information.

Specifically, when the receiving party receiving the mirror image source returning request is a storage node in the same cloud storage system, the information of 404 is returned, the returning process may be returning along a mirror image source returning request sending path, and the returned mirror image source returning request failure information may be sent to the user side that acquires the data. When the receiving party of the mirror image back-to-source request is a cloud node between different cloud storage systems, failure information may also be returned along the mirror image back-to-source request sending path, the information that is returned may also be 404 information, and similarly, the returned mirror image back-to-source request failure information may be sent to the user side that acquires the data.

The above is a description of an embodiment of a method for processing a resource request provided by the present application from a receiving side, and accordingly, the present application also discloses a device for processing a resource request, which corresponds to a method of a receiving side, and the following description is referred to, and is relatively simple, and related points may refer to a part of description of an embodiment of a method of a receiving side. The device embodiments described below are merely illustrative.

As shown in fig. 10, fig. 10 is a schematic structural diagram of an embodiment of a processing apparatus for a resource request provided from a receiving side in the present application, where the processing apparatus at the receiving side includes:

areceiving unit 1001, configured to receive a mirror image source returning request for acquiring data, where the mirror image source returning request carries information used for determining whether to continue sending a mirror image source returning request for the data;

thereceiving unit 1001 includes:

and the storage node receiving subunit is used for carrying the identification information of all storage nodes through which the mirror image source returning request passes in the received mirror image source returning request when the mirror image source returning request receiving party is of the storage node type in the same cloud storage system.

The receivingunit 1001 includes:

and the cloud node receiving subunit is used for adding identification information for judging whether the back-to-source condition of the mirror image back-to-source request receiver is met or not in the mirror image back-to-source request when the mirror image back-to-source request receiver is of a cloud node type between different cloud storage systems.

The determiningunit 1002 is configured to determine whether to continue sending the mirror image source returning request according to information that is carried in the mirror image source returning request and is used for determining whether to continue sending the mirror image source returning request for the data.

Thejudgment unit 1002 includes:

and the type judgment subunit is used for determining whether to continuously send the mirror image source returning request according to the type of the mirror image source returning receiver of the mirror image source returning request.

The type judgment subunit includes:

and the storage node type judging subunit is used for judging whether the information carried in the mirror image source returning request for acquiring the data includes the identification information of the current mirror image source returning request receiver or not when the mirror image source returning request receiver is a storage node in the same cloud storage system, and if the information includes the identification information, the mirror image source returning request receiver stops initiating the mirror image source returning request.

The type judgment subunit includes:

and the cloud node type judging subunit is used for judging whether the information carried in the mirror image source returning request for acquiring the data includes the identification information of the current mirror image source returning request receiver or not when the mirror image source returning request receiver is of a cloud node type between different cloud storage systems, and if the information does not include the identification information, stopping initiating the mirror image source returning request by the mirror image source returning request receiver.

In the embodiment of the processing method for the mirror image back-to-source request, the method may further include:

and the return receiving unit is used for receiving the returned mirror image return source request failure information.

The above is a description of a specific process of a resource request processing method (transmitting side and receiving side) and a processing apparatus (transmitting side and receiving side) provided by the present application, and the present application further provides a processing system for mirroring a resource request, as shown in fig. 11, where fig. 11 is a schematic structural diagram of a processing system for a resource request provided by the present application, and the system may include: at least two storage nodes, afirst storage node 1101 and asecond storage node 1102.

Thefirst storage node 1101 generates a first mirror image source returning request for acquiring the data, where the first mirror image source returning request carries information for determining whether to continue sending a mirror image source returning request for the data.

Thesecond storage node 1102 is configured to receive the first mirror image source returning request from thefirst storage node 1101, and generate a second mirror image source returning request according to the first mirror image source returning request, where the second mirror image source returning request carries information used for determining whether a receiver of the second mirror image source returning request continues to send out a mirror image source returning request for acquiring the data;

thefirst storage node 1101 determines whether to continue issuing the mirror back-to-source request according to the received second mirror back-to-source request sent by thesecond storage node 1102.

Two embodiments are provided below for explanation according to different types of thefirst storage node 1101 and thesecond storage node 1102, specifically as follows:

referring to fig. 12, fig. 12 is a schematic structural diagram of a processing system for mirroring a resource request according to a first embodiment of the present disclosure.

Thefirst storage node 1101 generates a first mirror back-to-source request for acquiring the data, where the information carried in the first mirror back-to-source request for determining whether to continue sending the mirror back-to-source request for the data may include:

according to the type of thefirst storage node 1101, thefirst storage node 1101 is configured to generate a first mirror back-to-source request carrying information for determining whether to continue sending mirror back-to-source requests for the data information. Specifically, when thefirst storage node 1101 is a storage node type in the cloud storage system, the identification information of the first storage node is added to a request header of the first mirror image return source request;

and taking the identification information of the first storage node as information for judging whether to continuously send a mirror image back-to-source request aiming at the data.

The specific description process in step S401 may be referred to for adding the identification information of the first storage node in the request header, and is not described here again.

Thesecond storage node 1102 that receives the first mirror image source returning request generates a second mirror image source returning request according to the received first mirror image source returning request, where the second mirror image source returning request carries information used to determine whether the second mirror image source returning request receiver continues to send out a mirror image source returning request for acquiring the data, and the method includes:

according to the type of thefirst storage node 1101, the second mirror image source returning request is configured to carry information for determining whether the receiver of the second mirror image source returning request continuously sends the mirror image source returning request for acquiring the data. Specifically, when the second storage node and the first storage node are of the same storage node type in the cloud storage system, the identification information of the second storage node and the identification information of the first storage node are added to a request header of a second mirror image source returning request;

and taking the identification information of the second storage node and the identification information of the first storage node as information for judging whether to continuously send a mirror image back-to-source request aiming at the data.

As shown in fig. 12, when the first storage node and the second storage node are both storage nodes in the same cloud storage system, storage node bucketta is the first storage node, storage node bucketB is the second storage node, storage node bucktc is the second storage node, storage node bucktodd is the second storage node, and the like, where bucketta is the initial storage node, bucketB and bucktc may be intermediate storage nodes, and bucktodd is the end storage node; that is, the second storage node may be plural, two second storage nodes adjacent to the first storage node may be referred to as an intermediate storage node and an end storage node, respectively, and the intermediate storage node may be plural.

In general, the cyclic mirroring source back request includes at least two storage nodes, and both the two storage nodes may send mirroring source back requests to the next-level node, for example, the storage system includes bucketta and buckettb, the bucketta may send mirroring source back requests to the buckettb, and the buckettb may also send mirroring source back requests to the bucketta, where the bucketta may be an initial storage node and the buckettb is a terminal storage node. In the sending process of the mirror image source returning request, after bucketta sends the mirror image source returning request to buckettb, if the data is not obtained, buckettb sends the mirror image source returning request to bucketta, and then the mirror image source returning request is sent step by step to cause the obtained data to enter a reciprocating cycle.

In fig. 12, five storage nodes in the same cloud storage system are illustrated, that is: the method includes bucketta, buckettb, buckettc and buckettd, wherein bucketta sends a mirror image source return request to buckettb, buckettb sends a mirror image source return request to buckettc, buckettc sends a mirror image source return request to buckettd, and the specific sending process can refer to the description of the sending method of the mirror image source return request provided by the application.

It should be noted that when bucketta sends a mirror-image source-returning request to buckettb, bucketta may trigger bucketta to send a mirror-image source-returning request to buckettb by receiving a request for obtaining the data sent by a user, and it can be understood that when the data obtained by the user exists in bucketta, the mirror-image source-returning request does not need to be sent to buckettb.

Therefore, in order to avoid the occurrence of the cyclic mirror image source returning request, a judgment can be made between the at least two storage nodes, that is, whether the mirror image source returning request received by the initial storage node carries the identification information of the initial storage node, if so, the initial storage node stops sending the mirror image source returning request, and the generation of the cyclic mirror image source returning request is avoided.

In the above, the first storage node and the second storage node are storage node types in the same cloud storage system, and the following description is made on cloud node types in which the first storage node and the second storage node are different cloud storage system components.

Fig. 13 is a schematic structural diagram of a second embodiment of a resource request processing system according to the present application, as shown in fig. 13.

According to the type of the first storage node, configuring the first storage node to generate a first mirror image source returning request carrying information for judging whether to continuously send out a mirror image source returning request aiming at the data information, wherein the information comprises:

when the first storage node is of a cloud node type between cloud storage systems, adding identification information different from the first storage node in a request head of a first mirror image source returning request;

and taking the identification information different from the first storage node as information for judging whether to continuously send the mirror image back to the source for the data.

The method includes the steps that a second storage node receiving a first mirror image source returning request generates a second mirror image source returning request according to the received first mirror image source returning request, and the second mirror image source returning request carries information used for judging whether a second mirror image source returning request receiver continuously sends the mirror image source returning request aiming at the acquired data, and the method includes the following steps:

and according to the type of the first storage node, configuring information which is used for aiming at the acquired data and is carried in the second mirror image source returning request to judge whether a receiver of the second mirror image source returning request continuously sends the mirror image source returning request. When the second storage node is of a cloud node type between cloud storage systems, adding identification information different from the second storage node into a request header of a second mirror image source returning request;

and taking the identification information of the second storage node as information for judging whether to continuously send the mirror image back-to-source request aiming at the data.

Specifically, when the second storage node and the first storage node are of cloud node types between different cloud storage systems, reference may be made to the description in step S301, for example: the cloud node a of the cloud storage A, the cloud node B of the cloud storage B, the cloud node C of the cloud storage C and the like at least comprise two cloud nodes when a mirror image return request is carried out. In the embodiment shown in fig. 13, the cloud node includes: cloud node a and cloud node b, when a host head is configured in cloud node a in advance as a.com, and a generated host head for initiating HTTP in the mirror image source returning request is configured with a.com to cloud node a, cloud node a can send the mirror image source returning request to cloud node b, so that cloud node a can send the mirror image source returning request to the next cloud node b when the data is not obtained, cloud node b also sets the data content of the host head as b.com in advance, when the host head of HTTP generated by cloud node a carries b.com, cloud node b can send the mirror image source returning request to the next cloud node, the host head of HTTP generated by cloud node a carries c.com information, when cloud node a receives the mirror image source returning request from cloud node b, cloud node a is configured with a.com in advance, and therefore cloud node a stops sending the mirror image source returning request to cloud node b, thereby avoiding the occurrence of a request for loop mirroring back to the source. In other words, for cloud nodes of different cloud storage systems, different information for triggering the mirror image back-to-source request may be set for each cloud node, and therefore, when the end cloud node sends the mirror image back-to-source request to the initial cloud node, since the initial cloud node adopts a trigger condition similar to a.com and the mirror image back-to-source request sent by the end cloud node carries c.com, the initial cloud node does not send the mirror image back-to-source request any more.

Similarly, the cloud node a may be a first storage node, the cloud node b may be a second storage node, the cloud nodes b may be multiple, the cloud nodes adjacent to the cloud node a are an intermediate cloud node and a terminal cloud node, and the cloud node a is an initial cloud node.

In the two embodiments, the generating of the mirror back-to-source request by the first storage node may be sending an obtaining request for obtaining the data to the first storage node according to the client, and the first storage node generating the first mirror back-to-source request for obtaining the data according to the obtaining request.

It should be noted here that, in the above two implementations, the cyclic mirroring back-to-source request is described with respect to the initial node and the end node, and actually, the mirroring back-to-source request may occur not only between the end node and the initial node, but also between the intermediate node and the initial node, or only between the intermediate nodes, and therefore, the process of whether to continue issuing the mirroring back-to-source request with respect to the data is not limited to the description of the above embodiment. The initial node may be an initial storage node or an initial cloud node, the end node may be an end storage node or an end cloud node, and the intermediate node is an intermediate storage node or an intermediate cloud node.

The above is a description of a mirrored back-source processing system provided in the present application, and for a more general description of a mirrored back-source processing system, reference may be made to the related descriptions of fig. 1 to fig. 10 for specific processes.

Based on the above, the present application further provides an electronic device, including:

a processor;

a memory for storing a program for processing data generated by the network platform, the program when read and executed by the processor performing the following operations:

generating a mirror image source returning request for acquiring data, wherein the mirror image source returning request carries information for judging whether to continuously send the mirror image source returning request aiming at the data;

and sending a mirror back source request for acquiring the data.

The present application further provides a storage device, comprising: storing data generated by the network platform and a program for processing the data generated by the corresponding network platform;

when the program is read and executed by the processor, the following operations are executed:

generating a mirror image source returning request for acquiring data, wherein the mirror image source returning request carries information for judging whether to continuously send the mirror image source returning request aiming at the data;

and sending a mirror back source request for acquiring the data.

The present application further provides an electronic device, comprising:

a processor;

a memory for storing a program for processing data generated by the network platform, the program when read and executed by the processor performing the following operations:

receiving a mirror image source returning request for acquiring data, wherein the mirror image source returning request carries information for judging whether to continuously send the mirror image source returning request aiming at the data;

and determining whether to continuously send the mirror image source returning request or not according to the information which is carried in the mirror image source returning request and is used for judging whether to continuously send the mirror image source returning request aiming at the data.

The present application further provides a storage device, comprising: storing data generated by the network platform and a program for processing the data generated by the corresponding network platform;

when the program is read and executed by the processor, the following operations are executed:

receiving a mirror image source returning request for acquiring data, wherein the mirror image source returning request carries information for judging whether to continuously send the mirror image source returning request aiming at the data;

and determining whether to continuously send the mirror image source returning request or not according to the information which is carried in the mirror image source returning request and is used for judging whether to continuously send the mirror image source returning request aiming at the data.

In a typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.

The memory may include forms of volatile memory in a computer readable medium, Random Access Memory (RAM) and/or non-volatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of a computer-readable medium.

1. Computer-readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), Read Only Memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), Digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, computer readable media does not include non-transitory computer readable media (transient media), such as modulated data signals and carrier waves.

2. As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.

Although the present application has been described with reference to the preferred embodiments, it is not intended to limit the present application, and those skilled in the art can make variations and modifications without departing from the spirit and scope of the present application, therefore, the scope of the present application should be determined by the claims that follow.

Claims (14)

1. A method for processing resource requests comprises the following steps:

receiving, by a storage device, a first resource request requesting to acquire data from a previous storage device, where the storage device is a source station of the previous storage device, and the first resource request carries at least identification information of the previous storage device;

and if the storage device determines that the data is not stored, determining whether to send a second resource request for requesting to acquire the data to a subsequent storage device according to the identification information carried by the first resource request, wherein the subsequent storage device is a source station of the storage device.

2. The method for processing the resource request according to claim 1, wherein the determining, according to the identification information carried in the first resource request, whether to send a second resource request requesting to acquire the data to a subsequent storage device includes:

and judging whether the identification information carried by the first resource request comprises the identification information of the storage device, if not, sending the second resource request, wherein the second resource request comprises the identification information carried by the first resource request and the identification information of the storage device.

3. The method for processing the resource request according to claim 2, wherein the sending the second resource request comprises:

in response to the first resource request, returning the data or a status code indicating that the data is not present that the subsequent storage device returned in response to the second resource request.

4. The method for processing the resource request according to claim 1, wherein the determining, according to the identification information carried in the first resource request, whether to send a second resource request requesting to acquire the data to a subsequent storage device includes:

and judging whether the identification information carried by the first resource request comprises the identification information of the storage device, if so, not sending the second resource request.

5. The method of claim 4, wherein after determining not to send the second resource request, comprising:

in response to the first resource request, returning information indicating that the data does not exist or information indicating that the request failed.

6. The method of claim 1, wherein the first resource request and the second resource request comprise a non-standard header field, and wherein the non-standard header field comprises the identification information.

7. The method of processing a resource request according to claim 1, wherein the method further comprises:

the storage equipment receives an acquisition request which is sent by a client and requests to acquire the data;

and if the storage device determines that the data is not stored, sending a third resource request for requesting to acquire the data to the subsequent storage device, wherein the third resource request comprises the identification information of the storage device.

8. The method for processing the resource request according to claim 1, wherein before determining whether to send a second resource request requesting to acquire the data to a second storage device according to the identification information carried in the first resource request, the method further includes:

if the first resource request does not carry the identification information of the prior storage device, the storage device judges whether the first resource request meets a pre-configured back-to-source condition or not;

and if the back-source condition is met, the storage equipment sends a second resource request for acquiring the data to the subsequent storage equipment.

9. The method of claim 7, wherein the pre-configured back-to-source condition comprises at least one of:

the source IP address of the resource request is a specific network segment;

the general header field of the resource request is a specific value;

the request parameters of the resource request include specific parameters.

10. The method of claim 1, wherein the storage device comprises an object-based storage device.

11. An apparatus for processing resource requests, comprising:

a receiving unit, configured to receive, at a storage device, a first resource request requesting to acquire data from a previous storage device, where the storage device is a source station of the previous storage device, and the first resource request carries at least identification information of the previous storage device;

the judging unit is used for judging whether the storage equipment stores the data or not, and if not, the determining unit is started;

the determining unit is configured to determine, at the storage device, whether to send a second resource request requesting to acquire the data to a subsequent storage device according to the identification information carried in the first resource request, where the subsequent storage device is a source station of the storage device.

12. A distributed storage system comprising a plurality of storage devices, said storage devices comprising the apparatus for processing resource requests of claim 11.

13. An electronic device, comprising:

a processor;

a memory for storing a program for processing network platform generated data, which program, when read and executed by the processor, performs the method according to any one of claims 1-10.

14. The storage device is used for storing network platform generated data and a program for processing the network platform generated data;

the program, when read and executed by the processor, performs the method of any one of claims 1-10.

Images