CN113835892A - Unified storage device, service management method and module thereof, and readable storage medium - Google Patents
Unified storage device, service management method and module thereof, and readable storage medium Download PDFInfo
- Publication number
- CN113835892A CN113835892A CN202111136026.5A CN202111136026A CN113835892A CN 113835892 A CN113835892 A CN 113835892A CN 202111136026 A CN202111136026 A CN 202111136026A CN 113835892 A CN113835892 A CN 113835892A
- Authority
- CN
- China
- Prior art keywords
- subtask
- service
- module
- task
- execution
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
- 238000007726 management method Methods 0.000 title claims abstract description 147
- 238000012545 processing Methods 0.000 claims abstract description 74
- 238000000034 method Methods 0.000 claims abstract description 53
- 230000015654 memory Effects 0.000 claims description 21
- 230000008569 process Effects 0.000 abstract description 30
- 230000004044 response Effects 0.000 description 9
- 238000010586 diagram Methods 0.000 description 5
- 238000011010 flushing procedure Methods 0.000 description 5
- 238000005516 engineering process Methods 0.000 description 3
- 230000006870 function Effects 0.000 description 3
- 230000000977 initiatory effect Effects 0.000 description 3
- 230000007246 mechanism Effects 0.000 description 3
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 239000007787 solid Substances 0.000 description 2
- 238000003491 array Methods 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000004590 computer program Methods 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 238000010295 mobile communication Methods 0.000 description 1
- 238000005192 partition Methods 0.000 description 1
- 238000003672 processing method Methods 0.000 description 1
- 230000001960 triggered effect Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
- G06F9/5061—Partitioning or combining of resources
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/48—Program initiating; Program switching, e.g. by interrupt
- G06F9/4806—Task transfer initiation or dispatching
- G06F9/4843—Task transfer initiation or dispatching by program, e.g. task dispatcher, supervisor, operating system
- G06F9/485—Task life-cycle, e.g. stopping, restarting, resuming execution
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
- G06F9/5005—Allocation of resources, e.g. of the central processing unit [CPU] to service a request
- G06F9/5027—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resource being a machine, e.g. CPUs, Servers, Terminals
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention relates to a unified storage device and a service management method, a module and a readable storage medium thereof, wherein the method comprises the steps of firstly obtaining tasks to be processed, wherein the tasks to be processed are tasks executed by a plurality of service modules; then, dividing the task to be processed into a plurality of subtasks according to requirements, wherein the plurality of subtasks have different execution conditions respectively; and then, the subtasks are issued to the management submodules of the corresponding service modules according to the execution conditions, the task execution states fed back by the management submodules are received, and the task completion results to be processed are determined. According to the scheme, a unified volume business processing flow is formulated by arranging a common business management module and business management sub-modules in the business module, so that the volume business flow can be unified and coordinated under the condition that multiple modules need to process volume related business together, the processing flow is simplified, and the business flow can be completed more efficiently and accurately.
Description
Technical Field
The invention relates to the technical field of storage, in particular to a unified storage device, a service management method and module thereof and a readable storage medium.
Background
With the development of computer technology, storage technology has become a key technology. Unified storage is a storage system that can run and manage files and applications on a single device. In the unified storage software architecture, each module related to the IO flow has its own IO flow control logic, and how this module receives IO data sent by an upper layer and how to process the IO data is determined by the control logic of its own module. Under the mechanism, each IO processing module can independently receive and process IO data and complete the whole IO processing flow of the storage device.
However, in some scenarios, the current processing mechanisms may make the overall flow control complex. For example, when the unified storage device is in a certain scenario, it is necessary that each IO processing module performs a disk flushing operation to a lower layer, and according to the current processing flow, each IO processing module first needs to identify a current scenario or event type in its respective configuration management module, and then triggers a service processing flow of this module according to the requirements of the scenario or event, and finally completes a corresponding flushing task.
The above-described flow mainly has the following problems:
firstly, each IO processing module needs to receive a corresponding scene or event respectively and make independent response to the scene/event respectively, and the logic flow becomes more complicated;
secondly, each IO processing module receives events and processes services independently, and the management of time is an unordered state, and if there is a need for processing time of two different modules in the service level, for example, one event needs to be processed and then another event needs to be processed, the current processing mode cannot fulfill the need.
Disclosure of Invention
In view of this, embodiments of the present invention provide a method for managing services of a unified storage device, so as to solve the problems in the prior art that service processing modules are independently managed, the flow is complicated, and mutual cooperation is inconvenient.
According to a first aspect, an embodiment of the present invention provides a service management method for a unified storage device, where the service management module is used in a service management module, the service management module is connected to a plurality of service modules in the unified storage device, each service module is provided with a service management submodule, and includes acquiring a task to be processed, where the task to be processed is a task executed by the plurality of service modules; dividing the task to be processed into a plurality of subtasks according to requirements, wherein the plurality of subtasks have corresponding execution conditions; and issuing the subtasks to the management submodules of the corresponding service modules according to the execution conditions, receiving the task execution state fed back by the management submodules, and determining the task completion result to be processed.
According to the scheme, a unified volume business processing flow is formulated by setting a public business management module and business management sub-modules in the business modules, tasks to be processed are subjected to unified split management in the business management modules, the respective management modules are not required to be configured in each business module to identify the current scene and task time type, only subtasks are received to process the tasks, unified and coordinated management of the volume business flow can be realized under the condition that multiple modules are required to process the relevant business scene of the volume together, the processing flow is simplified, and the business flow can be completed more efficiently and accurately.
With reference to the first aspect, in an optional implementation manner of the first aspect, the issuing the subtasks to the management submodule of the corresponding service module according to the execution condition, receiving a task execution state fed back by the management submodule, and determining the completion result of the task to be processed includes:
when the subtasks are parallel processing tasks, each subtask is sent to a management submodule of a corresponding service module, so that the service module executes the subtask;
and receiving the task execution state fed back by the management submodule, judging whether all subtasks are completed or not, and feeding back a completed result if all subtasks are completed.
With reference to the first aspect, in an optional implementation manner of the first aspect, the execution condition includes an execution timing and/or an execution state of the corresponding related task.
With reference to the first aspect, in an optional implementation manner of the first aspect, the plurality of subtasks at least include a first subtask and a second subtask, and the second subtask is started after the first subtask is executed; the service module at least comprises a first service module and a second service module, wherein the first service module is used for executing a first subtask, and the second service module is used for executing a second subtask.
With reference to the first aspect, in an optional implementation manner of the first aspect, the issuing the subtasks to the management submodule of the corresponding service module according to the execution condition, receiving a task execution state fed back by the management submodule, and determining the completion result of the task to be processed includes:
sending an execution request of a first subtask to a service management submodule of a corresponding first service module, so that the first service module executes the first subtask;
receiving a first subtask execution state, wherein the first subtask execution state is fed back by a service management submodule of the first service module according to a first subtask execution condition;
judging whether a second subtask execution request needs to be sent or not according to the first subtask execution state;
when a second subtask execution request needs to be sent, sending the execution request of the second subtask to a service management submodule of a second service module corresponding to the execution request of the second subtask so that the second service module executes the second subtask;
receiving a second subtask execution state, wherein the second subtask execution state is fed back by the second service module according to a second subtask execution condition;
and judging whether the task to be processed is completed according to the execution state of the second subtask.
With reference to the first aspect, in an optional implementation manner of the first aspect, the task to be processed includes a cluster event or a command line event.
With reference to the first aspect, in an optional implementation manner of the first aspect, the service module includes an IO processing module.
According to a second aspect, an embodiment of the present invention provides a service management module of a unified storage device, where the service management module is connected to multiple service modules in the unified storage device, and each service module is provided with a service management sub-module, including:
an obtaining unit, configured to obtain a task to be processed, where the task to be processed is a task executed by the plurality of service modules;
the dividing unit is used for dividing the task to be processed into a plurality of subtasks according to requirements, and the plurality of subtasks have corresponding execution conditions;
a sending unit, configured to issue the subtasks to the management sub-module of the corresponding service module according to the execution condition, so that the service module executes the subtasks;
and the execution unit is used for receiving the task execution state fed back by the service module and sequentially executing the plurality of subtasks according to the task execution state and the execution condition until the task to be processed is completed.
According to a third aspect, an embodiment of the present invention provides a unified storage device, including a memory and a processor, where the memory and the processor are communicatively connected to each other, and the memory stores computer instructions, and the processor executes the computer instructions, so as to implement the method of the first aspect and the optional embodiments thereof.
According to a fourth aspect, the present invention provides a computer-readable storage medium, which is characterized by storing computer instructions for causing a computer to execute the method of the first aspect and its optional implementation manner.
Drawings
The features and advantages of the present invention will be more clearly understood by reference to the accompanying drawings, which are illustrative and not to be construed as limiting the invention in any way, and in which:
FIG. 1 shows a flow diagram of a traffic management method according to an embodiment of the invention;
fig. 2 shows a flowchart of S3 in the traffic management method according to another embodiment of the present invention;
FIG. 3 is a schematic structural diagram of a traffic management module according to an embodiment of the present invention;
FIG. 4 illustrates a schematic diagram of a unified storage device according to another embodiment of the invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, but not all, embodiments of the present invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
Unified storage is a storage system that can run and manage files and applications on a single device, integrating file-based and block-based access. It is also referred to as multi-protocol storage because it supports different storage protocols to provide data storage for the host system. The current unified storage device generally comprises a redundant structure formed by a plurality of controllers, and a common mode comprises that two controllers, namely two nodes, form an IO processing module, and then a plurality of IO processing modules form a final multi-control cluster. In the unified storage software architecture, each IO processing module is independently controlled, so that the problems of complex control flow and inconvenient coordination management are caused.
Based on this, the present embodiment provides a service management method for a unified storage device, which performs unified coordination and management on IO processing modules in the unified storage device. In the scheme, an independent service management module is arranged to independently manage the volume service flow in the storage server, and mainly manage the IO processing module.
The service management method of the unified storage device in this embodiment is used in the service management module that is separately set, where the service management module is connected to multiple service modules in the unified storage device, and in a specific scheme, the service management is IO service management, the service module is an IO processing module (IO module for short), and a service management submodule is also separately set inside each IO processing module. The service management module is a public module and can be marked as a context module, and the main functions comprise the following aspects:
firstly, a basic data structure for managing a volume service process is set, wherein the basic data structure mainly includes volume service contents (such as a following flushing, an IO service stopping and the like), an IO processing module for uniformly managing corresponding volume services, volume service processing result feedback and the like. And defining which business modules participate in the unified management of which volume business processes through a data structure, and feeding back the results of the business processes in a unified mode, such as completion or failure. A volume here refers to a partition of a dynamic disk for a server, and is also referred to as a storage volume.
And secondly, providing basic external interfaces including initialization interfaces of a business process application end and a response end and the like for the volume business initiating and responding module to create related objects. The application end of the service process is a cluster event management or user command line management module, and the specific IO processing module is a service response end and is responsible for processing the IO process. The service management module is provided with a relevant interface for receiving the task request of the initiating terminal and sending relevant information to the responding terminal.
Related objects in the module can be set through a common interface provided by the service management module, for example, a request task is set in the application end module, a response end module is set to respond to a response task and the like, and meanwhile, objects of specific services are set, for example, flush, pause and the like.
And thirdly, setting processing logics of a service application end and a response end, and determining a uniform volume service flow execution mode and a result judgment mechanism. And after the service response end completes the related service, returning respective result states, and determining a service flow completion result through the logic comprehensive processing related to the service management module. And then informing the business process application end to complete the whole volume business process processing.
By setting the service management module as an independent public module, each IO processing module can acquire a uniform interface, create objects of the same type for processing the volume-related service flows, and can complete normal processing of the volume-related services in the module under the uniform management of the public module.
After the service management module for processing the volume service process is set, an independent sub-module for processing the volume service process needs to be added in each service module, so that the volume service application and response module can use the interface and logic provided by the service management module respectively, and finally, the service process of the whole IO processing module related to the volume is realized. Therefore, the task management submodule is arranged at the management end of the IO processing module, and the IO processing module can timely and orderly process the currently required business process under unified scheduling in the business processing process by utilizing the logic and the interface provided by the business management module and the task management submodule arranged at the respective end.
As shown in fig. 1, the method for managing services of a unified storage device in this embodiment includes:
and S1, acquiring a task to be processed, wherein the task to be processed is a task executed by the plurality of business modules.
The pending task here may be a downward disk-flushing, data issuing, etc. The service process initiating end is usually a cluster event management module or a user command line management module, and the specific IO processing module is usually a service responding end and is responsible for specifically processing the IO process. The cluster event management module or the command line management module of the unified storage device first receives a trigger event which can cause the service flow of the whole module volume, such as a cluster event or a command line event, the cluster event management module or the command line management module initiates a volume-related service request through an application end interface provided by the service management module, and the service management module receives the request to acquire a task to be processed which needs to be executed. The pending task should be a task that requires the entire business layer, not a task for a separate business module.
And S2, dividing the task to be processed into a plurality of subtasks according to requirements, wherein the plurality of subtasks have corresponding execution conditions respectively.
After receiving the task to be processed, the service management module needs to split the task to be processed according to the specific task condition. For example, if the operation is a downward disk-flushing operation that needs to be executed by each IO processing module at the same time, the operation is split into subtasks that each IO module needs to execute. The subtasks can have the same execution condition or different execution conditions, and are reasonably set according to needs.
And S3, issuing the subtasks to the management submodule of the corresponding service module according to the execution condition, receiving the task execution state fed back by the management submodule, and determining the task completion result to be processed.
After the volume service initiates a request, each IO processing module (responding end) registered in the volume service management module receives a corresponding request, that is, a subtask request, through the service management submodule logic of the module, and triggers the volume service process related to the module through the internal logic to execute the subtask.
After the service module (IO processing module) completes the issued subtask (volume service flow task) received by the module, the service module performs logical processing through a state machine in the service module to obtain a task execution state, and the task execution state is used as a processing result (success/failed) of the service flow of the IO processing module and is fed back to the service management module by using the common interface. The service management module arranges each service module (IO processing module) to sequentially execute the corresponding flow according to the logic, confirms the final service flow result, and completes the processing process of the unified volume service flow participated by each IO processing module triggered by the cluster event or the command line event. Therefore, the task event is uniformly managed by the internal logic of the service management module, each IO service module is dispatched to process the corresponding service request in sequence, and the flow of the finished result is confirmed.
In the method, a task to be processed is obtained first, where the task to be processed is a task executed by a plurality of service modules; then, dividing the task to be processed into a plurality of subtasks according to requirements, wherein the plurality of subtasks have corresponding execution conditions; and then, the subtasks are issued to the management submodules of the corresponding service modules according to the execution conditions, the task execution states fed back by the management submodules are received, and the task completion results to be processed are determined. According to the scheme, a unified volume business processing flow is formulated by setting a public business management module and business management sub-modules in the business modules, tasks to be processed are subjected to unified split management in the business management modules, the respective management modules are not required to be configured in each business module to identify the current scene and task time type, only subtasks are received to process the tasks, unified and coordinated management of the volume business flow can be realized under the condition that multiple modules are required to process the relevant business scene of the volume together, the processing flow is simplified, and the business flow can be completed more efficiently and accurately.
The service management method in this embodiment is a scheme for unified management of IO flows in a unified storage field, and is configured with an independent service management module, in which data structures, processing logics, and corresponding interfaces for a volume service application end and a response end are defined respectively, and each service module can use the common module to set up a service management sub-module specially used for volume flow management in a unified manner, so as to manage service flow control of each module volume and finally implement unified scheduling and processing of service flows of volumes in each IO processing module.
As a specific implementation manner, in the step S3, when the sub task is a parallel processing task, the step S3 further includes:
firstly, each subtask is sent to a management submodule of a corresponding service module, so that the service module executes the subtask;
and secondly, receiving the task execution state fed back by the management submodule, judging whether all subtasks are finished or not, and feeding back a finished result if all subtasks are finished.
As another specific implementation manner, when the task to be processed needs to be executed by a plurality of service modules in cooperation with each other, for example, a subsequent service module needs to be determined and started according to an execution state of a first service module, at this time, the execution of the task to be processed has a sequence and a corresponding condition, where the execution condition of the task to be processed includes an execution timing sequence and an execution state of a corresponding related task. The execution time sequence here refers to an execution time requirement or a sequence requirement, and the execution state of the related task refers to one of the starting conditions that the execution result of the other one or more subtasks is taken as the current task, that is, the other one or more subtasks are executed after the execution of the other one or more subtasks is completed.
Taking the example that the task to be processed includes two subtasks, the first subtask is executed first, and the second subtask is started after the first subtask is executed. The corresponding service module comprises a first service module and a second service module, wherein the first service module is used for executing the first subtask, and the second service module is used for executing the second subtask.
In this case, in the step S2, the task to be processed is divided into a first subtask and a second subtask according to the requirement, and the execution condition is that the first subtask is executed first, and the second subtask is executed after the first subtask is executed.
The step S3 further includes the following steps, as shown in fig. 2:
s31, sending the execution request of the first subtask to the service management submodule of the corresponding first service module, where the service management submodule triggers, through internal logic control, the related service processing flow in the first service module to execute the first subtask, and obtains an execution result of the first subtask through internal state machine logic, so as to generate an execution state of the first subtask, where the execution state may be success or failure.
And S32, receiving an execution state of the first subtask, wherein the execution state of the first subtask is fed back by the service management submodule of the first service module according to the execution condition of the first subtask. The step feeds back the execution result of the subtask to the service management module.
And S33, judging whether a second subtask execution request needs to be sent according to the first subtask execution state. Because the execution condition in this embodiment is that the first subtask is executed first, the second subtask is executed after the first subtask is executed. If the first subtask is executed, a second subtask execution request needs to be sent to the second service module, and the process goes to step S34; and if the first subtask is not executed completely, retransmitting the execution request of the first subtask, or interrupting the task processing and setting according to the requirement.
And S34, when the second subtask execution request needs to be sent, sending the execution request of the second subtask to the service management submodule of the corresponding second service module, so that the second service module executes the second subtask. The second subtask is executed in the second service module, and the execution mode is similar to the first subtask and is not described herein again. And after the execution is finished, the second service module feeds back the execution state of the second subtask to the service management module.
And S35, receiving a second subtask execution state, wherein the second subtask execution state is fed back by the second service module according to the second subtask execution condition. The service management module receives the execution result of the second subtask through the step.
And S36, judging whether the task to be processed is completed according to the execution state of the second subtask. If the second subtask is completed, the task to be processed is completed; and if the second subtask is not completed, further resending the second subtask to the second service module, or interrupting the execution, and setting according to the requirement.
It should be noted that, for example, the to-be-processed task includes two subtasks, the to-be-processed task may include more subtasks, each subtask may have different execution conditions, and the service management module may perform unified management and deployment according to each subtask and the corresponding execution condition, so as to implement mutual cooperation between the service modules.
In the service management method of the unified storage device in the above embodiment, each subtask in the to-be-processed task is sequentially processed according to the condition, so that unified coordination and management of the IO processing modules are achieved, each IO processing module may utilize a data structure and a logic interface provided by a common service management module, and utilize a service management submodule of volume service flow management inside the IO processing module, so that unified and coordinated management of a service flow of a single volume in the whole IO module is achieved, and implementation of a volume service flow in a special service scene is efficiently and accurately achieved.
The embodiment of the present invention further provides a service management module of a unified storage device, where the service management module is connected to multiple service modules in the unified storage device, each service module is provided with a service management sub-module, and a structural block diagram of the service management module is shown in fig. 3, and includes:
an obtaining unit 01, configured to obtain a task to be processed, where the task to be processed is a task executed by the plurality of service modules; see step S1 above for details, which are not described herein again.
The processing unit 02 is configured to divide the task to be processed into a plurality of subtasks according to requirements, where the plurality of subtasks have corresponding execution conditions respectively; see step S2 above for details, which are not described herein again.
And the execution unit 03 is configured to issue the subtasks to the management sub-modules of the corresponding service modules according to the execution conditions, receive the task execution state fed back by the management sub-modules, and determine the completion result of the to-be-processed task. See step S3 above for details, which are not described herein again.
The task to be processed comprises a cluster event or a command line event, and the service module comprises an IO processing module.
In an optional implementation manner, the execution unit 03 includes:
the first execution subunit sends each subtask to a management submodule of a corresponding service module when the subtask is a parallel processing task, so that the service module executes the subtask;
and the second execution subunit receives the task execution state fed back by the management submodule, judges whether all subtasks are completed or not, and feeds back a completion result if all subtasks are completed.
In another optional embodiment, the execution condition includes an execution timing and/or an execution state of a corresponding related task. The plurality of subtasks at least comprise a first subtask and a second subtask, and the second subtask is started after the first subtask is executed; the service module at least comprises a first service module and a second service module, wherein the first service module is used for executing a first subtask, and the second service module is used for executing a second subtask.
The execution unit 03 may further include:
the first sub-unit is used for sending an execution request of a first sub-task to a service management sub-module of a corresponding first service module, so that the first service module executes the first sub-task; see step S31 above for details, which are not described herein again.
The second subunit is used for receiving a first subtask execution state, and the first subtask execution state is fed back by the service management submodule of the first service module according to the first subtask execution condition; see step S32 above for details, which are not described herein again.
The third subunit is used for judging whether a second subtask execution request needs to be sent or not according to the execution state of the first subtask; see step S33 above for details, which are not described herein again.
The fourth subunit is configured to, when a second subtask execution request needs to be sent, send the execution request of the second subtask to the service management sub-module of the second service module corresponding to the execution request of the second subtask, so that the second service module executes the second subtask; see step S34 above for details, which are not described herein again.
The fifth subunit is configured to receive an execution state of a second subtask, where the execution state of the second subtask is fed back by the second service module according to an execution condition of the second subtask; see step S35 above for details, which are not described herein again.
And the sixth subunit is configured to determine whether the to-be-processed task is completed according to the execution state of the second sub-task. See step S36 above for details, which are not described herein again.
The service management module of the unified storage device in this embodiment implements unified scheduling and management of volume-related service flows in each module of the storage device in a fixed scene through the common service management module and the service management submodule used in the service module, and ensures high efficiency and accuracy of data services of the storage device.
Fig. 4 is a schematic diagram of a hardware structure of a unified storage device according to an embodiment of the present invention, as shown in fig. 4, the device includes one or more processors 410 and a memory 420, where one processor 410 is taken as an example in fig. 4. The apparatus may further include: an input device 430 and an output device 440.
The processor 410, the memory 420, the input device 430, and the output device 440 may be connected by a bus or other means, such as the bus connection in fig. 4.
The memory 420, which is a non-transitory computer readable storage medium, may be used to store non-transitory software programs, non-transitory computer executable programs, and modules, such as program instructions/modules corresponding to the business management methods in the embodiments of the present application. The processor 410 executes various functional applications of the server and data processing, i.e., a processing method implementing the above-described method embodiments, by executing non-transitory software programs, instructions, and modules stored in the memory 420.
The memory 420 may include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application program required for at least one function; the storage data area may store data used as needed or desired, and the like. Further, the memory 420 may include high speed random access memory, and may also include non-transitory memory, such as at least one magnetic disk storage device, flash memory device, or other non-transitory solid state storage device. In some embodiments, memory 420 may optionally include memory located remotely from processor 410, which may be connected over a network to a processing device operating the list items. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.
The input device 430 may receive input numeric or character information and generate key signal inputs related to user settings and function control. The output device 440 may include a display device such as a display screen.
The one or more modules are stored in the memory 420 and, when executed by the one or more processors 410, perform the method shown in fig. 1-2.
The product can execute the method provided by the embodiment of the invention, and has corresponding functional modules and beneficial effects of the execution method. Details of the technique not described in detail in the present embodiment may be specifically referred to the related description in the embodiments shown in fig. 1-2.
The embodiment of the invention also provides a non-transitory computer storage medium, wherein the computer storage medium stores computer executable instructions, and the computer executable instructions can execute the service management method in any method embodiment. The storage medium may be a magnetic Disk, an optical Disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a Flash Memory (Flash Memory), a Hard Disk (Hard Disk Drive, abbreviated as HDD), a Solid State Drive (SSD), or the like; the storage medium may also comprise a combination of memories of the kind described above.
It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above can be implemented by a computer program, which can be stored in a computer-readable storage medium, and when executed, can include the processes of the embodiments of the methods described above. The storage medium may be a magnetic disk, an optical disk, a read-only memory (ROM), a Random Access Memory (RAM), or the like.
Although the embodiments of the present invention have been described in conjunction with the accompanying drawings, those skilled in the art may make various modifications and variations without departing from the spirit and scope of the invention, and such modifications and variations fall within the scope defined by the appended claims.
Claims (10)
1. A service management method of unified storage equipment is used in a service management module, the service management module is connected with a plurality of service modules in the unified storage equipment, each service module is provided with a service management submodule, and the method is characterized by comprising the following steps:
acquiring tasks to be processed, wherein the tasks to be processed are tasks executed by a plurality of business modules;
dividing the task to be processed into a plurality of subtasks according to requirements, wherein the plurality of subtasks have corresponding execution conditions respectively;
and issuing the subtasks to the management submodules of the corresponding service modules according to the execution conditions, receiving the task execution state fed back by the management submodules, and determining the task completion result to be processed.
2. The method according to claim 1, wherein the issuing the subtasks to the management submodule of the corresponding service module according to the execution condition, receiving the task execution state fed back by the management submodule, and determining the completion result of the task to be processed includes:
when the subtasks are parallel processing tasks, each subtask is sent to a management submodule of a corresponding service module, so that the service module executes the subtask;
and receiving the task execution state fed back by the management submodule, judging whether all subtasks are completed or not, and feeding back a completed result if all subtasks are completed.
3. The method according to claim 1, wherein the execution condition comprises an execution timing and/or an execution status of a corresponding related task.
4. The method of claim 3, wherein the plurality of subtasks includes at least a first subtask and a second subtask, and wherein the second subtask is initiated after the first subtask is executed; the service module at least comprises a first service module and a second service module, wherein the first service module is used for executing a first subtask, and the second service module is used for executing a second subtask.
5. The method according to claim 4, wherein the issuing the subtasks to the management submodule of the corresponding service module according to the execution condition, receiving the task execution state fed back by the management submodule, and determining the completion result of the task to be processed includes:
sending an execution request of a first subtask to a service management submodule of a corresponding first service module, so that the first service module executes the first subtask;
receiving a first subtask execution state, wherein the first subtask execution state is fed back by a service management submodule of the first service module according to a first subtask execution condition;
judging whether a second subtask execution request needs to be sent or not according to the first subtask execution state;
when a second subtask execution request needs to be sent, sending the execution request of the second subtask to a service management submodule of a second service module corresponding to the execution request of the second subtask so that the second service module executes the second subtask;
receiving a second subtask execution state, wherein the second subtask execution state is fed back by the second service module according to a second subtask execution condition;
and judging whether the task to be processed is completed according to the execution state of the second subtask.
6. The method of claim 1 or 2 or 3 or 4 or 5, wherein the task to be processed comprises a cluster event or a command line event.
7. The method of claim 1 or 2 or 3 or 4 or 5, wherein the traffic module comprises an IO processing module.
8. A business management module of unified storage equipment is connected with a plurality of business modules in the unified storage equipment, and each business module is provided with a business management submodule, and the business management module is characterized by comprising:
the service module comprises an acquisition unit, a processing unit and a processing unit, wherein the acquisition unit is used for acquiring tasks to be processed, and the tasks to be processed are tasks executed by a plurality of service modules;
the processing unit is used for dividing the task to be processed into a plurality of subtasks according to requirements, and the plurality of subtasks respectively have corresponding execution conditions;
and the execution unit is used for issuing the subtasks to the management submodules of the corresponding service modules according to the execution conditions, receiving the task execution state fed back by the management submodules and determining the task completion result to be processed.
9. A unified storage device, comprising a memory and a processor, wherein the memory and the processor are communicatively connected to each other, the memory stores computer instructions, and the processor executes the computer instructions to perform the method according to any one of claims 1 to 7.
10. A computer-readable storage medium having stored thereon computer instructions for causing a computer to perform the method of any one of claims 1-7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111136026.5A CN113835892B (en) | 2021-09-27 | 2021-09-27 | Unified storage device, service management method and module thereof, and readable storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111136026.5A CN113835892B (en) | 2021-09-27 | 2021-09-27 | Unified storage device, service management method and module thereof, and readable storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113835892A true CN113835892A (en) | 2021-12-24 |
| CN113835892B CN113835892B (en) | 2024-02-13 |
Family
ID=78970835
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111136026.5A Active CN113835892B (en) | 2021-09-27 | 2021-09-27 | Unified storage device, service management method and module thereof, and readable storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113835892B (en) |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20170286144A1 (en) * | 2016-03-31 | 2017-10-05 | International Business Machines Corporation | Software-defined storage cluster unified frontend |
| CN110673793A (en) * | 2019-09-12 | 2020-01-10 | 苏州浪潮智能科技有限公司 | Storage device node event management method and system, electronic device and storage medium |
| CN113094125A (en) * | 2021-04-21 | 2021-07-09 | 矢量云科信息科技(无锡)有限公司 | Business process processing method, device, server and storage medium |
| CN113238838A (en) * | 2021-04-22 | 2021-08-10 | 中国银联股份有限公司 | Task scheduling method and device and computer readable storage medium |
-
2021
- 2021-09-27 CN CN202111136026.5A patent/CN113835892B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20170286144A1 (en) * | 2016-03-31 | 2017-10-05 | International Business Machines Corporation | Software-defined storage cluster unified frontend |
| CN110673793A (en) * | 2019-09-12 | 2020-01-10 | 苏州浪潮智能科技有限公司 | Storage device node event management method and system, electronic device and storage medium |
| CN113094125A (en) * | 2021-04-21 | 2021-07-09 | 矢量云科信息科技(无锡)有限公司 | Business process processing method, device, server and storage medium |
| CN113238838A (en) * | 2021-04-22 | 2021-08-10 | 中国银联股份有限公司 | Task scheduling method and device and computer readable storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113835892B (en) | 2024-02-13 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| JP6785911B2 (en) | Flexible node configuration methods and systems in local or distributed computer systems | |
| US20170331867A1 (en) | Method, device and system for pushing file | |
| CN110309161B (en) | Data synchronization method and device and server | |
| CN113742031B (en) | Node state information acquisition method and device, electronic equipment and readable storage medium | |
| CN106406905B (en) | Configuration method and system for SETUP option of BIOS of server | |
| WO2016183553A1 (en) | Query dispatch and execution architecture | |
| US9852220B1 (en) | Distributed workflow management system | |
| CN109189758B (en) | Operation and maintenance flow design method, device and equipment, operation method, device and host | |
| WO2022134358A1 (en) | Microservice data processing method, apparatus, microservice processing platform, and medium | |
| WO2022134797A1 (en) | Data fragmentation storage method and apparatus, a computer device, and a storage medium | |
| US11416294B1 (en) | Task processing for management of data center resources | |
| CN111400041A (en) | Server configuration file management method and device and computer readable storage medium | |
| CN111064626A (en) | Configuration updating method, device, server and readable storage medium | |
| US10346192B2 (en) | Method, apparatus, and system for displaying virtual machine name | |
| CN113658351B (en) | Method and device for producing product, electronic equipment and storage medium | |
| CN111294377B (en) | Dependency network request sending method, terminal device and storage medium | |
| CN116521573A (en) | Automatic test method, device, equipment and storage medium | |
| CN103761106A (en) | Process control method and process engine | |
| CN112153114A (en) | Method, system, equipment and medium for time-sharing access to shared device | |
| CN113835892B (en) | Unified storage device, service management method and module thereof, and readable storage medium | |
| CN111200651A (en) | Method, system, device and medium for timed calling of microservice | |
| CN112711466B (en) | Hanging affair inspection method and device, electronic equipment and storage medium | |
| US20230350712A1 (en) | Bmc parameter configuration and effect-taking method and apparatus, device, and medium | |
| CN115268951A (en) | Installation method, device, equipment and storage medium of operating system | |
| CN117149220A (en) | Resource updating method, electronic equipment and system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |