Request processing method and device, equipment and storage medium

Abstract

The invention discloses a request processing method and device, equipment and a storage medium, which are applied to a back-end server, and the method comprises the following steps: determining a first long connection link in an idle state from a pre-constructed first connection pool, and receiving a target request sent by a message server through the first long connection link; distributing the target request to a corresponding service module in a back-end server, and processing the target request by using the service module to obtain a processed target request; determining a second long connection link in an idle state from a pre-constructed second connection pool, and sending the processed target request to a message server through the second long connection link. According to the application, the target request sent by the message server is received through the first long connection link in the first connection pool, the processed target request is returned through the second long connection link in the second connection pool, and the long connection link is multiplexed based on the pre-constructed connection pool, so the pressure of the message server is reduced, and the request processing efficiency is improved.

Description

technical field [0001] The present invention relates to the field of computer technology, in particular to a request processing method, device, equipment and storage medium. Background technique [0002] In the architecture of the existing storage management software, modules are split according to different functions of the backend. Each module of all nodes in the cluster maintains a long connection with a message service of a single message service node. In this way, the pressure on a single message service node is very high. Big. However, except for performance and cache modules that collect information regularly, other business modules are basically inactive. When there are no commands for CLI and front-end page operations, the module connection is in the "empty running" state, wasting connection resources. At the same time, after processing the request, each module temporarily applies to create a new connection to send the processing result. Every time a processing req...

AI Technical Summary

Problems solved by technology

However, except for the modules that collect information regularly, such as performance and cache, other business modules are basically inactive. When there is no request command for CLI and front-end page operations, the module connection is in the "empty running" state, wasting connection resources.

At the same time, after processing the request, each module temporarily applies to create a new connection to send the processing result. Every time a processing request is received, a new connection is created. The resource overhead is very large. When there are many nodes and modules, the single message service Nodes cause a lot of pressure, reducing the efficiency of request response

Images