WO2019210580A1

WO2019210580A1 - Access request processing method, apparatus, computer device, and storage medium

Info

Publication number: WO2019210580A1
Application number: PCT/CN2018/095684
Authority: WO
Inventors: 杨勇; 宋剑锋
Original assignee: 平安科技（深圳）有限公司
Priority date: 2018-05-04
Filing date: 2018-07-13
Publication date: 2019-11-07
Also published as: CN108762917A

Abstract

An access request processing method, an apparatus, a computer device, and a storage medium, which are applied to a remote multi-Cognos cluster environment, wherein each Cognos cluster shares a data storage space, and a load balancing server manages the Cognos clusters of a plurality of different regions. The processing method comprises the following steps: a load balancing server receiving an access request (S1); the load balancing server determining a target Cognos cluster from among managed Cognos clusters of a plurality of different regions, the target Cognos cluster being any Cognos cluster among the Cognos clusters that are in a normal state (S2); the load balancing server sending the access request to the target Cognos cluster such that the target Cognos cluster processes the access request (S3). The present invention overcomes the defect wherein a user is unable to access data when a cluster is abnormal.

Description

Access request processing method, device, computer device, and storage medium

This application claims priority to Chinese Patent Application No. 2018104215528, entitled "Access Request Processing Method, Apparatus, System, Computer Equipment, and Storage Media", filed on May 4, 2018, the entire contents of which is incorporated herein by reference. This is incorporated herein by reference.

Technical field

The present application relates to the field of computer technologies, and in particular, to an access request processing method, apparatus, computer device, and storage medium.

Background technique

Cognos is a data model that is service-oriented on top of the BI (Business Intelligence) core platform and is the only solution that delivers complete business intelligence capabilities from a single product and on a single, reliable architecture. It provides a seamlessly integrated solution for reporting, analysis, scorecards, dashboards, etc., by providing all system and data resources to simplify the way companies work with their employees. At present, the use of Cognos clusters in the industry is mostly local multi-machine deployment, and there are no multi-region large cluster deployment cases. The expansion capability of a local single cluster is limited, and it cannot meet the requirements of real-time handover of remote disaster recovery.

As the cluster grows, there will be pressure bottlenecks in the Cognos cluster, causing various anomalies in the system. After the system is abnormal, you need to restart the cluster environment. The restart process takes a long time to complete. During this process, the cluster is unavailable. After the disaster occurs, there is data loss, the system is not available for a long time, and the disaster tolerance is poor. When the cluster is unavailable, the user cannot access the data, and the system cannot respond to the user's access request.

technical problem

The main purpose of the present application is to provide an access request processing method, apparatus, computer device, and storage medium, which overcome the defect that the user cannot access data when the cluster is abnormal.

Technical solution

To achieve the above object, the present application provides an access request processing method, where the method is applied to an off-site multi- Cognos cluster environment, each Cognos cluster shares a data storage space, and the load balancing server manages a plurality of Cognos clusters in different regions, and the method include:

The load balancing server receives the access request;

Determining, by the load balancing server, a target Cognos cluster in a plurality of Cognos clusters in different regions, where the target Cognos cluster is any one of the Cognos clusters in a normal state;

The load balancing server sends the access request to the target Cognos cluster to cause the target Cognos cluster to process the access request.

The application also provides an access request processing device, where the device is applied to an off-site multi-collusion cluster environment, and each Cognos cluster shares a data storage space, and the device includes:

a receiving unit, configured to receive an access request;

a determining unit, configured to determine a target Cognos cluster in a plurality of different geographical regions of the Cognos cluster, where the target Cognos cluster is any one of the Cognos clusters in a normal state;

And a sending unit, configured to send the access request to the target Cognos cluster, so that the target Cognos cluster processes the access request.

The application further provides a computer device comprising a memory and a processor, the memory storing computer readable instructions, the processor executing the computer readable instructions to implement the steps of any of the methods described above.

The present application also provides a computer non-transitory readable storage medium having stored thereon computer readable instructions that, when executed by a processor, implement the steps of any of the methods described above.

Beneficial effect

The access request processing method, device, computer device and storage medium provided in the application are applied to a remote multi- Cognos cluster environment, each Cognos cluster shares a data storage space, and the load balancing server manages a plurality of Cognos clusters in different regions; the load balancing server receives Accessing the request; the load balancing server determines a target Cognos cluster in a plurality of Cognos clusters of different regions, the target Cognos cluster is any one of the Cognos clusters in a normal state; the load balancing server uses the access Sending a request to the target Cognos cluster, so that the target Cognos cluster processes the access request, overcoming the defect that the user cannot access the data when the cluster is abnormal, and ensuring that each user's access request can be responded; avoiding the cluster There is a risk of data loss after the disaster occurs and the system is unavailable for a long time.

DRAWINGS

1 is a schematic diagram of steps of an access request processing method in an embodiment of the present application;

2 is a schematic diagram of specific steps of step S2 in an embodiment of the present application;

3 is a structural block diagram of an access request processing apparatus in an embodiment of the present application;

4 is a block diagram showing the structure of a determining unit in an embodiment of the present application;

FIG. 5 is a schematic diagram of steps of an access request processing method in another embodiment of the present application; FIG.

6 is a structural block diagram of an access request processing apparatus in another embodiment of the present application;

7 is a block diagram showing the workflow of an access request processing system in another embodiment of the present application;

FIG. 8 is a schematic block diagram showing the structure of a computer device according to an embodiment of the present application.

BEST MODE FOR CARRYING OUT THE INVENTION

Referring to FIG. 1 , an access request processing method is provided in the embodiment of the present application. The method is applied to an off-site multi- Cognos cluster environment. Each Cognos cluster shares a data storage space, and the load balancing server manages a plurality of Cognos clusters in different regions. In this embodiment, each of the above-mentioned Cognos clusters provides services independently, and the running environment is completely the same. Each Cognos cluster maps its IP address to the same load balancing server, that is, points multiple different Cognos clusters. The same load balancing server enables the load balancing server to perform unified and balanced management on each Cognos cluster. When users everywhere access the load balancing server over the network, the load balancing server can load balance and then distribute the access request to one of the above Cognos clusters. The load balancing server is mainly used to balance the load (work tasks) and distribute them to multiple clusters for execution, such as web server (web server), FTP server (communication protocol server), enterprise critical application server, and other mission-critical servers. All belong to the load balancing server, the F5 load balancing server (a specific product specification) used in this embodiment.

In this embodiment, the running environments of the Cognos clusters are consistent, and are deployed in various areas. The Cognos cluster is set to multiple, which is convenient for reducing the pressure of the Cognos cluster. Each Cognos cluster is independent of each other. When any one of the Cognos clusters is abnormal, the Cognos clusters in other regions can still work normally, and will not affect the stability of the Cognos clusters in other regions. By deploying multiple places and achieving different activities, the pressure on a single Cognos cluster can be greatly reduced.

The monitoring process is configured on the above-mentioned Cognos cluster. The monitoring process is used to monitor the status attribute of the Cognos cluster in which it is located, and determine whether the Cognos cluster is in a normal state. When an abnormal state occurs, an exception notification (such as mail or phone, etc.) is issued to the bound administrative user. The above abnormal state, including hardware exceptions, such as CPU, memory usage, etc., also includes software exceptions, such as operating system crashes.

The above access request processing method includes the following steps:

Step S1: The load balancing server receives the access request.

After the above-mentioned Cognos cluster and the load balancing server are deployed (constituting a system), the load balancing server can receive the user's access request when the load balancing server is running, and the access request is a data access request of the user to the Cognos cluster.

Step S2, the load balancing server determines a target Cognos cluster in a plurality of Cognos clusters in different regions, and the target Cognos cluster is any one of the Cognos clusters in a normal state;

In this step, after receiving the access request, the load balancing server sends a control signal to each of the above-mentioned Cognos clusters to detect whether the current Cognos cluster is abnormal through the monitoring process set on the Cognos cluster. The Cognos cluster sends the detection result to the above. The load balancing server, after receiving the detection result, facilitates balancing management of the above Cognos cluster. For example, the load balancing server selects any one of the Cognos clusters in the normal state as a target Cognos cluster according to a preset manner. The load balancing server can also disable the service port of the Cognos cluster in an abnormal state so that it is no longer served.

Step S3: The load balancing server sends the access request to the target Cognos cluster, so that the target Cognos cluster processes the access request.

After determining the target Cognos cluster, the load balancing server may send an access request to the target Cognos cluster to cause the target Cognos cluster to process the access request. Enables the user's access request to be responsive, easy to access to the data they want, and avoids the unavailability of the entire system.

In the foregoing step S2, it is detected whether each of the Cognos clusters is in a normal state, and the Cognos cluster in the normal state can be accessed, and one of the Cognos clusters in the normal state is selected as the target Cognos cluster according to a preset manner. In step S3, the received access request sent by the user through the network is distributed to one of the target Cognos clusters in a normal state. In this embodiment, when any one of the Cognos clusters has an abnormal state, the load balancing server will not distribute the user's access request to the abnormal cluster of the Cognos cluster. Because it is distributed to the Cognos cluster in the normal state, it can ensure that the user's access request is responded, and the data required by the user can be accessed to avoid the unavailability of the entire system.

Specifically, in a specific embodiment, a Cognos cluster is deployed in Shenzhen, Guangzhou, and Shanghai, and each Cognos cluster runs in a consistent environment. When an abnormal state of the Cognos cluster in Guangzhou is detected, the Cognos clusters in Shenzhen and Shanghai are detected. In the normal state, when receiving a user's access request, you can choose to distribute the access request to any of the clusters in Shenzhen or Shanghai. According to the preset method of determining the target Cognos cluster, the Cognos cluster selected in the final clusters in Shenzhen and Shanghai will be different. For example, if the default mode is random distribution, it can be in Shenzhen and Shanghai. Select a Cognos cluster randomly among the Cognos clusters; if the default method is to select the Cognos cluster closest to the user's address information, select a Cognos cluster closest to the user's address from the Cognos clusters in Shenzhen and Shanghai.

In an embodiment, the step S3 after the load balancing server sends the access request to the target Cognos cluster to process the access request by the target Cognos cluster includes:

When the load balancing server acquires that the target Cognos cluster is in an abnormal state, the access request is sent to any other Cognos cluster in a normal state.

If the target Cognos cluster is in an abnormal state, in order to prevent the user's access request from being unresponsive, any other Cognos cluster selected from the other Cognos clusters is used as the target Cognos cluster of the access request.

When the load balancing server obtains that the target Cognos cluster is in an abnormal state, the service port of the target Cognos cluster in the abnormal state is disabled.

In this embodiment, when it is detected that the target Cognos cluster is in an abnormal state, the target Cognos cluster service port only needs to be disabled. After the service port is disabled, the load balancing server will not distribute the request, and the access request sent by the user will only be Send it to other normal Cognos clusters for processing. In another embodiment, the task of distributing the access request to the target Cognos cluster may also be disabled by the load balancing server such that the user's access request is no longer distributed to the target Cognos cluster. Both of the above methods can not continue to distribute requests on the Cognos cluster where the exception occurs, but distribute the request to other normal Cognos clusters; avoid data loss after the disaster occurs on the Cognos cluster, and the system is unavailable for a long time. risk. In the above step S2, it is determined that in the target Cognos cluster, if one of the Cognos clusters is detected to be in an abnormal state, the same manner can be performed as described above.

Preferably, in an embodiment, when an abnormality occurs in a Cognos cluster, the repair tool is used to repair, or the Cognos cluster is automatically restarted. During the restart, the Cognos cluster service port is closed and set to be unavailable. status. After the Cognos cluster returns to normal, the Cognos cluster automatically opens the service port, resumes use, and sends a signal to restore the normal state to the load balancing server to make a prompt. After receiving the above signal, the load balancing server can redistribute the access request to the On the Cognos cluster.

In an embodiment, in the step S1, the step of the load balancing server receiving the access request further includes:

Obtain the address information of the user; and cooperate with the off-site distribution analysis tool on the load balancing server to analyze the address information of the access user.

In one embodiment, the foregoing manner of determining the target Cognos cluster is to select a Cognos cluster that is closest to the user address information. Step S2 of determining, by the foregoing load balancing server, the target Cognos cluster in the coordinated clusters of the multiple different regions, including:

According to the user's address information, the Cognos cluster that is closest to the user's address information and in a normal state is matched as the target Cognos cluster.

For example, a Cognos cluster is deployed in three regions of Shenzhen, Guangzhou, and Shanghai, and the address information of the accessed users is Guangzhou. If the above three Cognos clusters are in a normal state, the Guangzhou Cognos cluster is automatically selected as the target Cognos cluster; if the Guangzhou Cognos cluster is in an abnormal state, the Shenzhen Cognos cluster is used as the target Cognos cluster.

In another embodiment, a user address-cluster mapping table is further configured, and the mapping table stores a Cognos cluster list corresponding to the user address information, and the Cognos cluster included in the Cognos cluster list corresponding to the user address information may be For example, for users in Guangzhou, the corresponding list of Cognos clusters can be Guangzhou. For users in Dongguan, the corresponding list of Cognos clusters can include Guangzhou and Shenzhen.

Specifically, referring to FIG. 2, the step S2 of determining, by the load balancing server, the target Cognos cluster in the plurality of different regions of the Cognos cluster, includes:

Step S21: Matching, according to the address information of the user, a Cognos cluster corresponding to the address information in a preset user address-cluster mapping table;

According to the preset user address-cluster mapping table and the obtained user address information, the Cognos cluster list corresponding to the user address information may be matched. The list includes at least one Cognos cluster.

Step S22: Select a Cognos cluster in a normal state as the target Cognos cluster according to the matching result and the matched state of the Cognos cluster.

After the Cognos cluster is matched in the user address-cluster mapping table, the matching Cognos cluster may be in an abnormal state. In this case, it is unreasonable to send the access request to the Cognos cluster. Therefore, it needs to be detected. Whether the matched Cognos cluster is in a normal state; finally, select a target Cognos cluster suitable for distributing access requests, which is the last Cognos cluster that needs to process access requests.

Specifically, in one embodiment, the matching result matched by the user address-cluster mapping table is a Cognos cluster, and according to the matching result and the status of the matched Cognos cluster, a Cognos cluster in a normal state is selected as the cluster. Step S22 of the target Cognos cluster includes:

If one of the matched Cognos clusters is in a normal state, the matched Cognos cluster is selected as the target Cognos cluster. The access request is then distributed to the target Cognos cluster; if the matched Cognos cluster is in an abnormal state, the access request is randomly distributed to any other Cognos cluster in a normal state. In other embodiments, if the matched Cognos cluster is in an abnormal state, the access request may be distributed to a Cognos cluster closest to the user's address, and the specific process is not described herein.

In another embodiment, the matching result matched according to the foregoing user address-cluster mapping table includes multiple Cognos clusters, and includes priorities of multiple of the Cognos clusters; according to the matching result and the Cognos cluster Status, step S22 of selecting a Cognos cluster in a normal state as the target Cognos cluster, including:

According to the priorities of the multiple Cognos clusters, a Cognos cluster with the highest priority and the highest priority is selected as the target Cognos cluster, and the intercepted access request is distributed to the target Cognos cluster.

In this embodiment, the results of the matching Cognos cluster list may include multiple Cognos clusters, such as Cognos clusters A, B, and C, and the priority of the Cognos cluster A is higher than that of the Cognos cluster B. The priority of the Cognos cluster B is higher than that of the Cognos cluster. C; If the Cognos cluster A is abnormal and the Cognos clusters B and C are normal, select Cognos cluster B as the target Cognos cluster.

In still another embodiment, the load balancing server periodically updates the user address-cluster mapping table.

Specifically, which of the Cognos clusters in the localities are in a normal state and which are in an abnormal state, at this time, all the abnormal Cognos clusters located in the user address-cluster mapping table are all removed, and the updated user address-cluster mapping is obtained. The table then directly matches the result according to the user address-cluster mapping table and the user's address information, and uses the matched Cognos cluster or the matched highest priority Cognos cluster as the target Cognos cluster.

In the above embodiment, NAS (Network) is mounted on each of the Cognos clusters. Attached Storage, NAS is the shared data storage. All the Cognos clusters that have the NAS can access the data in the shared data storage space. It does not need to be stored in every Cognos cluster, which greatly saves storage resources. . The above-mentioned target Cognos cluster generates a log file for processing data for the access request and transmits it to the shared data storage space.

Before the step S1 of receiving the access request by the load balancing server, the method includes:

In step S11, the data in the shared data storage space is extracted into the cube file, and the cube file is synchronously distributed to the NAS mounted on each of the Cognos clusters. This process ensures that the data on multiple sets of Cognos clusters is completely consistent. Each Cognos cluster provides services to users at the same time, which greatly enhances system high availability and robustness. In this embodiment, the data on each Cognos cluster is the same, and even if one of the Cognos clusters is abnormal, other Cognos clusters can still provide services to improve system disaster tolerance.

In this embodiment, a large amount of data is stored in the shared data storage space, and the data is extracted from the shared data storage space and loaded into the cube file, and the cube files that are extracted from the shared data storage space are simultaneously published to each Cognos. Clustered on the NAS. Brushing the cube file is a special off-line analysis tool of Cognos, that is, the data cube. By extracting the data from the shared data storage space and loading it into the cube file in advance, the user can query the required data by accessing the cube file.

In this embodiment, the data is extracted from the shared data storage space and loaded into the cube file, and the user can query the required data by accessing the cube file on the NAS, and the process improves the data access when the large data volume and the user are concurrently accessed. effectiveness.

In an embodiment, the extracting the data in the shared data storage space into the cube file and distributing the cube file to the NAS mounted on each of the Cognos clusters before the step S11 includes:

Step S101: Import data uploaded by any one of the Cognos clusters into a shared data storage space.

In this embodiment, there may be a certain amount of report data uploaded by users in various local Cognos clusters. These data are not available on other Cognos clusters. In order to achieve unified data on all Cognos clusters, the load balancing server will be arbitrary. The data uploaded on one of the Cognos clusters is imported into the shared data storage space. Then, the data in the shared data storage space is extracted into the cube file by the above step S11, and the cube file is synchronously distributed to the NAS mounted on each of the Cognos clusters. I will not repeat them here.

The embodiment of the present application further provides an access request processing device, where the device is applied to a remote multi- Cognos cluster environment, and each Cognos cluster shares a data storage space. In this embodiment, each of the foregoing Cognos clusters independently provides services, and The running environment is the same. Each Cognos cluster maps its IP address to the same load balancing server. That is, multiple different Cognos clusters are directed to the same load balancing server, so that the load balancing server unifies each Cognos cluster. Balance management. When users everywhere access the load balancing server over the network, the load balancing server can load balance and then distribute the access request to one of the above Cognos clusters. The load balancing server is mainly used to balance the load (work tasks) and distribute them to multiple clusters for execution, such as web server (web server), FTP server (communication protocol server), enterprise critical application server, and other mission-critical servers. All belong to the load balancing server, the F5 load balancing server (a specific product specification) used in this embodiment.

Referring to FIG. 3, the above access request processing apparatus includes:

The receiving unit 10 is configured to receive an access request.

The determining unit 20 is configured to determine a target Cognos cluster in a plurality of different regions of the Cognos cluster, where the target Cognos cluster is any one of the Cognos clusters in a normal state.

In this embodiment, after the receiving unit 10 receives the access request, the determining unit 20 sends a control signal to each of the above-mentioned Cognos clusters, and detects whether the current Cognos cluster is abnormal through the monitoring process set on the Cognos cluster, and the above-mentioned Cognos cluster detects The result is sent to the determining unit 20, and after the determining unit 20 receives the detection result, it is convenient to perform balancing management on the Cognos cluster. For example, the determining unit 20 selects any one of the Cognos clusters in the normal state as a target Cognos cluster in a preset manner. In this process, the determining unit 20 can also disable the service port of the Cognos cluster in an abnormal state so that it no longer provides services.

The sending unit 30 is configured to send the access request to the target Cognos cluster, so that the target Cognos cluster processes the access request.

After the determining unit 20 determines the target Cognos cluster, the sending unit 30 may send an access request to the target Cognos cluster to cause the target Cognos cluster to process the access request. Enables the user's access request to be responsive, easy to access to the data they want, and avoids the unavailability of the entire system.

It is detected whether each of the Cognos clusters is in a normal state, the Cognos cluster representation in the normal state can be accessed, and the determining unit 20 selects one of the Cognos clusters in the normal state as the target Cognos cluster according to a preset manner. The convenient sending unit 30 distributes the received access request sent by the user through the network to one of the target Cognos clusters in a normal state. In this embodiment, when any one of the Cognos clusters has an abnormal state, the sending unit 30 will not distribute the user's access request to the Cognos cluster of the abnormal state. Because it is distributed to the Cognos cluster in the normal state, it can ensure that the user's access request is responded, and the data required by the user can be accessed to avoid the unavailability of the entire system.

In an embodiment, the access request processing apparatus further includes:

And a forwarding unit, configured to send the access request to any other Cognos cluster in a normal state when the target Cognos cluster is in an abnormal state.

In this embodiment, when it is detected that the target Cognos cluster is in an abnormal state, the target Cognos cluster service port only needs to be disabled. After the service port is disabled, the sending unit 30 will not distribute the request, and the access request sent by the user will only be Send it to other normal Cognos clusters for processing. In another embodiment, the task of distributing the access request to the target Cognos cluster may also be disabled by the load balancing server such that the user's access request is no longer distributed to the target Cognos cluster. Both of the above methods can not continue to distribute requests on the Cognos cluster where the exception occurs, but distribute the request to other normal Cognos clusters; avoid data loss after the disaster occurs on the Cognos cluster, and the system is unavailable for a long time. risk. When the determining unit 20 determines that the target Cognos cluster is in an abnormal state, it can also be processed in the above manner.

In an embodiment, the obtaining unit 10 further acquires address information of the user; and cooperates with the off-site distribution analysis tool on the load balancing server to analyze the address information of the accessed user.

In one embodiment, the determining unit 20 determines that the target Cognos cluster is preset by selecting a Cognos cluster that is closest to the user address information. The determining unit 20 is specifically configured to:

In another embodiment, a user address-cluster mapping table is further configured, and the mapping table stores a list of Cognos clusters corresponding to the user address information, and the Cognos cluster included in the Cognos cluster list corresponding to the user address information may be For example, for users in Guangzhou, the corresponding list of Cognos clusters can be Guangzhou. For users in Dongguan, the corresponding list of Cognos clusters can include Guangzhou and Shenzhen.

Specifically, referring to FIG. 4, in an embodiment, the determining unit 20 includes:

The matching sub-unit 201 is configured to match, according to the address information of the user, a Cognos cluster corresponding to the address information in a preset user address-cluster mapping table;

According to the preset user address-cluster mapping table and the obtained address information of the user, the matching sub-unit 201 can match the Cognos cluster list corresponding to the user address information. The list includes at least one Cognos cluster.

The selecting sub-unit 202 is configured to select a Cognos cluster in a normal state as the target Cognos cluster according to the matching result and the matched state of the Cognos cluster.

After the matching sub-unit 201 matches the Cognos cluster in the user address-cluster mapping table, the matching Cognos cluster may be in an abnormal state. In this case, it is unreasonable to send the access request to the Cognos cluster. It is also necessary to detect whether the matched Cognos cluster is in a normal state; finally, the selection sub-unit 202 selects a target Cognos cluster suitable for distributing the access request, which is the last Cognos cluster that needs to process the access request.

In an embodiment, the matching sub-unit 201 is a Cognos cluster according to the matching result matched by the user address-cluster mapping table, and the selecting sub-unit 202 is specifically used to:

In another embodiment, the matching sub-unit 201 includes a plurality of Cognos clusters according to the matching result matched by the user address-cluster mapping table, and includes a plurality of priorities of the Cognos cluster; the selecting sub-unit 202 is specific. Used for:

In this embodiment, the results of the Cognos cluster list matched by the matching sub-unit 201 may include multiple Cognos clusters, such as Cognos clusters A, B, and C, and the priority of the Cognos cluster A is higher than that of the Cognos cluster B, and the priority of the Cognos cluster B is If the Cognos cluster A is abnormal and the Cognos clusters B and C are normal, the selection sub-unit 202 selects Cognos cluster B as the target Cognos cluster.

In still another embodiment, the method further includes an update unit that periodically updates the user address-cluster mapping table.

In the above embodiment, NAS (Network) is mounted on each of the Cognos clusters. Attached Storage, NAS is a shared data storage. All Cognos clusters that have the NAS can access the data in the shared data storage space. No storage is required for each Cognos cluster, which greatly saves storage resources. . The above-mentioned target Cognos cluster generates a log file for the processing data of the access request, and sends it to the shared data storage space.

The access request processing device further includes:

And a synchronization unit, configured to extract data in the shared data storage space into the cube file, and synchronously distribute the cube file to the NAS mounted on each of the Cognos clusters. This process ensures that the data on multiple sets of Cognos clusters is completely consistent. Each Cognos cluster provides services to users at the same time, which greatly enhances system high availability and robustness. In this embodiment, the data on each Cognos cluster is the same, and even if one of the Cognos clusters is abnormal, other Cognos clusters can still provide services to improve system disaster tolerance.

In this embodiment, a large amount of data is stored in the shared data storage space, and the synchronization unit extracts and loads the data from the shared data storage space into the cube file, and simultaneously publishes the cube file that is extracted from the shared data storage space to the cube file. On each NAS of the Cognos cluster. Brushing the cube file is a special off-line analysis tool of Cognos, that is, the data cube. By extracting the data from the shared data storage space and loading it into the cube file in advance, the user can query the required data by accessing the cube file.

In this embodiment, the synchronization unit extracts data from the shared data storage space and loads it into the cube file, and the user can query the required data by accessing the cube file on the NAS, and the process improves the amount of large data and the concurrent access of the user. Data access efficiency.

In an embodiment, the access request processing apparatus further includes:

The import unit is configured to import data uploaded on any one of the Cognos clusters into a shared data storage space.

Referring to FIG. 5, an embodiment of the present application further provides an access request processing method, where the method is applied to an off-site multi- Cognos cluster environment, each Cognos cluster shares a data storage space, and the load balancing server manages multiple different regions of the Cognos cluster. The Cognos cluster environment in this embodiment is the same as the Cognos cluster environment in the foregoing embodiment, and details are not described herein.

In this embodiment, the access request processing method includes:

Step S201, the target Cognos cluster receives an access request sent by the load balancing server, where the access request is sent when the load balancing server determines that the target Cognos cluster is in a normal state;

In this step, the user's access request is sent to the load balancing server, and the load balancing server selects a target Cognos cluster. The target Cognos cluster is a Cognos cluster that is in a normal state in any of the Cognos clusters in each region. For the determination of the target Cognos cluster, refer to the specific implementations of step S2, step S21, and step S22 in the foregoing embodiment, and details are not described herein. When the load balancing server determines the target Cognos cluster in the managed Cognos clusters in multiple regions, it sends the received access request to the Cognos cluster, and the target Cognos cluster receives the access request sent by the load balancing server.

Step S202, the target Cognos cluster processes the access request.

In this embodiment, after receiving the access request, the target Cognos cluster processes the access request. The target Cognos cluster then generates a log file from the access request processing data and sends the log file to the shared data storage space.

For the implementation of other specific functions of the Cognos cluster and the load balancing server in this embodiment, refer to the foregoing method embodiments, and details are not described herein.

Referring to FIG. 6, an embodiment of the present application further provides an access request processing device, where the device is applied to an off-site multiple Cognos cluster environment, each Cognos cluster shares a data storage space, and the load balancing server manages multiple different regions of the Cognos cluster. The Cognos cluster environment in this embodiment is the same as the Cognos cluster environment in the foregoing embodiment, and details are not described herein.

The access request processing apparatus includes:

The receiving module 101 is configured to receive an access request sent by the load balancing server, where the access request is sent when the load balancing server determines that the target Cognos cluster is in a normal state;

The user's access request is sent to the load balancing server, which then selects a target Cognos cluster. The target Cognos cluster is a Cognos cluster that is in a normal state in any of the Cognos clusters in each region. For the determination of the target Cognos cluster, refer to the determining unit 20 in the foregoing device embodiment, and details are not described herein. When the load balancing server determines the target Cognos cluster in the coordinated clusters of the multiple regions, the access request received by the load balancing server is sent to the Cognos cluster, and the receiving module 101 on the target Cognos cluster receives the sent by the load balancing server. Access request.

The processing module 102 is configured to process the access request.

In this embodiment, after the receiving module 101 receives the access request, the processing module 102 processes the access request. Then, the processing module 102 generates a log file by the access request processing data, and sends the log file to the shared data storage space.

For the implementation of the other specific functions of the Cognos cluster and the load balancing server in this embodiment, refer to the foregoing device embodiments, and details are not described herein.

Referring to FIG. 7, an embodiment of the present application further provides an access request processing system, where the system is applied to an off-site multi- Cognos cluster environment, each Cognos cluster shares a data storage space, and the load balancing server manages multiple different regions of the Cognos cluster. The Cognos cluster environment in this embodiment is the same as the Cognos cluster environment in the foregoing embodiment, and details are not described herein.

The load balancing server receives the access request; after the Cognos cluster and the load balancing server are deployed, the load balancing server can receive the user's access request when the load balancing server is running, and the access request is a data access request of the user to the Cognos cluster.

The load balancing server determines a target Cognos cluster in a plurality of Cognos clusters in different regions, and the target Cognos cluster is any one of the Cognos clusters in a normal state.

In this embodiment, the process of determining the target Cognos cluster by the load balancing server refers to the specific implementations of step S2, step S21, and step S22 in the foregoing method embodiment, and details are not described herein.

The load balancing server sends the access request to the target Cognos cluster; the load balancing server determines the target Cognos cluster from the managed Cognos clusters of different regions, and sends the received access request to the target Cognos. Cluster.

The target Cognos cluster receives the access request and processes the access request. The access request processing data generates a log file, and the log file is sent to the shared data storage space.

The other specific functions of the Cognos cluster and the load balancing server included in the access request processing system provided in this embodiment are described in the foregoing method embodiments, and details are not described herein.

Referring to FIG. 8, a computer device is provided in the embodiment of the present application. The computer device may be a server, and its internal structure may be as shown in FIG. 8. The computer device includes a processor, memory, network interface, and shared data storage space connected by a system bus. Among them, the computer designed processor is used to provide calculation and control capabilities. The memory of the computer device includes a non-volatile storage medium, an internal memory. The non-volatile storage medium stores an operating system, computer readable instructions, and a shared data storage space. The internal memory provides an environment for operation of an operating system and computer readable instructions in a non-volatile storage medium. The shared data storage space of the computer device is used to store data such as reports. The network interface of the computer device is used to communicate with an external terminal via a network connection. The computer readable instructions are executed by the processor to implement an access request processing method, and the method is applied to an off-site multi- Cognos cluster environment, and each Cognos cluster shares a data storage space.

The above processor executes the steps of the above access request processing method:

Receiving an access request;

Determining a target Cognos cluster in a plurality of different geographically-managed Cognos clusters, the target Cognos cluster being any one of the normal Cognos clusters;

Sending the access request to the target Cognos cluster to cause the target Cognos cluster to process the access request.

In an embodiment, the access request carries the address information of the user, and the step of determining, by the processor, the target Cognos cluster in the coordinated clusters of the multiple different regions, including:

And matching, according to the address information of the user, a Cognos cluster corresponding to the address information in a preset user address-cluster mapping table;

Based on the matching result and the status of the Cognos cluster, a Cognos cluster in a normal state is selected as the target Cognos cluster.

In an embodiment, after the step of the foregoing processor sending the access request to the target Cognos cluster to enable the target Cognos cluster to process the access request, the method includes:

When the target Cognos cluster is in an abnormal state, the access request is sent to any other Cognos cluster in a normal state.

In an embodiment, after the step of acquiring, by the processor, the target Cognos cluster is in an abnormal state, the method further includes:

Disable the service port of the target Cognos cluster in an abnormal state.

In another embodiment, the processor performs the steps of another access request processing method:

The target Cognos cluster receives an access request sent by the load balancing server, where the access request is sent when the load balancing server determines that the target Cognos cluster is in a normal state;

The target Cognos cluster processes the access request.

In another embodiment, after the step of processing, by the processor, the access request, the method includes:

The target Cognos cluster generates a log file by the access request processing data, and sends the log file to the shared data storage space.

It will be understood by those skilled in the art that the structure shown in FIG. 8 is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation of the computer device to which the present application is applied.

An embodiment of the present application further provides a computer non-transparent readable storage medium, where computer readable instructions are stored, and when the computer readable instructions are executed by the processor, an access request processing method is implemented, specifically:

Receiving an access request;

Disable the service port of the target Cognos cluster in an abnormal state.

In another alternative embodiment, the computer readable instructions are executed by the processor to implement another access request processing method, specifically:

The target Cognos cluster processes the access request.

In summary, the access request processing method, device, system, computer device, and storage medium provided in the embodiments of the present application are applied to an off-site multiple Cognos cluster environment, each Cognos cluster shares a data storage space, and the load balancing server receives an access request. The load balancing server determines a target Cognos cluster in a plurality of Cognos clusters of different regions, the target Cognos cluster is any one of the Cognos clusters in a normal state; the load balancing server sends the access request Giving the target Cognos cluster to the target Cognos cluster to process the access request, overcoming the defect that the user cannot access the data when the Cognos cluster is abnormal, and ensuring that each user's access request can be responded; avoiding the Cognos cluster There is a risk of data loss after the disaster occurs and the system is unavailable for a long time.

The above description is only a preferred embodiment of the present application, and thus does not limit the scope of the patent application, and the equivalent structure or equivalent process transformation of the specification and the drawings of the present application, or directly or indirectly applied to other related The technical field is equally included in the scope of patent protection of the present application.

Claims

An access request processing method is characterized in that: the method is applied to a remote multi- Cognos cluster environment, each Cognos cluster shares a data storage space, and the load balancing server manages a plurality of Cognos clusters in different regions, and the method includes:

The load balancing server receives the access request;

Determining, by the load balancing server, a target Cognos cluster in a plurality of Cognos clusters in different regions, where the target Cognos cluster is any one of the Cognos clusters in a normal state;

The load balancing server sends the access request to the target Cognos cluster to cause the target Cognos cluster to process the access request.
The access request processing method according to claim 1, wherein the access request carries the address information of the user, and the step of the load balancing server determining the target Cognos cluster in the managed Cognos clusters of different regions ,include:

And matching, according to the address information of the user, a Cognos cluster corresponding to the address information in a preset user address-cluster mapping table;

Based on the matching result and the status of the Cognos cluster, a Cognos cluster in a normal state is selected as the target Cognos cluster.
The access request processing method according to claim 1, wherein the load balancing server sends the access request to the target Cognos cluster to cause the target Cognos cluster to process the access request. After that, include:

When the load balancing server acquires that the target Cognos cluster is in an abnormal state, the access request is sent to any other Cognos cluster in a normal state.
The access request processing method according to claim 3, further comprising: after the step of the load balancing server acquiring the target Cognos cluster in an abnormal state, the method further comprising:

Disable the service port of the target Cognos cluster in an abnormal state.
An access request processing apparatus, wherein the apparatus is applied to an off-site multi-collusion cluster environment, and each Cognos cluster shares a data storage space, and the apparatus includes:

a receiving unit, configured to receive an access request;

a determining unit, configured to determine a target Cognos cluster in a plurality of different geographical regions of the Cognos cluster, where the target Cognos cluster is any one of the Cognos clusters in a normal state;

And a sending unit, configured to send the access request to the target Cognos cluster, so that the target Cognos cluster processes the access request.
The access request processing apparatus according to claim 5, wherein the determining unit comprises:

a matching subunit, configured to match, according to the address information of the user, a Cognos cluster corresponding to the address information in a preset user address-cluster mapping table;

The subunit is selected to select a Cognos cluster in a normal state as the target Cognos cluster according to the matching result and the status of the Cognos cluster.
The access request processing apparatus according to claim 5, further comprising:

And a forwarding unit, configured to send the access request to any other Cognos cluster in a normal state when the target Cognos cluster is in an abnormal state.
The access request processing apparatus according to claim 7, wherein the forwarding unit is further configured to:

Disable the service port of the target Cognos cluster in an abnormal state.
A computer device comprising a memory and a processor, the memory storing computer readable instructions, wherein the processor implements an access request processing method when the computer readable instructions are executed, the method being applied to different locations In the Cognos cluster environment, each Cognos cluster shares the data storage space. The processor of the load balancing server manages multiple clusters of Cognos in different regions, including:

Receiving an access request;

Determining a target Cognos cluster in a plurality of different geographically-managed Cognos clusters, the target Cognos cluster being any one of the normal Cognos clusters;

Sending the access request to the target Cognos cluster to cause the target Cognos cluster to process the access request.
The computer device according to claim 9, wherein the access request carries the address information of the user, and the step of the processor determining the target Cognos cluster in the coordinated clusters of the plurality of different regions, including:

And matching, according to the address information of the user, a Cognos cluster corresponding to the address information in a preset user address-cluster mapping table;

Based on the matching result and the status of the Cognos cluster, a Cognos cluster in a normal state is selected as the target Cognos cluster.
The computer device according to claim 9, wherein the processor sends the access request to the target Cognos cluster to enable the target Cognos cluster to process the access request, including :

When the target Cognos cluster is in an abnormal state, the access request is sent to any other Cognos cluster in a normal state.
The computer device according to claim 11, wherein after the step of the processor acquiring the target Cognos cluster in an abnormal state, the method further includes:

Disable the service port of the target Cognos cluster in an abnormal state.
A computer non-volatile readable storage medium having stored thereon computer readable instructions, wherein the computer readable instructions are executed by a processor to implement an access request processing method, the method, the method application In a heterogeneous Cognos cluster environment, each Cognos cluster shares a data storage space, and the processor of the load balancing server manages a plurality of Cognos clusters in different regions, including:

Receiving an access request;

Determining a target Cognos cluster in a plurality of different geographically-managed Cognos clusters, the target Cognos cluster being any one of the normal Cognos clusters;

Sending the access request to the target Cognos cluster to cause the target Cognos cluster to process the access request.
The computer non-volatile readable storage medium according to claim 13, wherein the access request carries address information of a user, and the processor determines a target in a plurality of Cognos clusters managed by different regions. The steps of the Cognos cluster, including:

And matching, according to the address information of the user, a Cognos cluster corresponding to the address information in a preset user address-cluster mapping table;

Based on the matching result and the status of the Cognos cluster, a Cognos cluster in a normal state is selected as the target Cognos cluster.
The computer non-volatile readable storage medium of claim 13, wherein the processor sends the access request to the target Cognos cluster to cause the target Cognos cluster to access the access request After the steps of processing, include:

When the target Cognos cluster is in an abnormal state, the access request is sent to any other Cognos cluster in a normal state.
The computer non-volatile readable storage medium according to claim 15, wherein after the step of the processor acquiring the target Cognos cluster in an abnormal state, the method further comprises:

Disable the service port of the target Cognos cluster in an abnormal state.