CN114500352B - Plug-in hot updating system and method for medical internet of things message routing device - Google Patents
Plug-in hot updating system and method for medical internet of things message routing device Download PDFInfo
- Publication number
- CN114500352B CN114500352B CN202111624690.4A CN202111624690A CN114500352B CN 114500352 B CN114500352 B CN 114500352B CN 202111624690 A CN202111624690 A CN 202111624690A CN 114500352 B CN114500352 B CN 114500352B
- Authority
- CN
- China
- Prior art keywords
- plug
- class
- routing device
- message routing
- ins
- 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.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 22
- 230000000007 visual effect Effects 0.000 claims abstract description 11
- 238000012544 monitoring process Methods 0.000 claims description 6
- 238000004140 cleaning Methods 0.000 claims description 3
- 238000012217 deletion Methods 0.000 claims description 3
- 230000037430 deletion Effects 0.000 claims description 3
- 238000011282 treatment Methods 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000010586 diagram Methods 0.000 description 1
- 230000010354 integration Effects 0.000 description 1
- 238000002955 isolation Methods 0.000 description 1
- 230000001360 synchronised effect Effects 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/56—Routing software
- H04L45/563—Software download or update
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
- G06F8/656—Updates while running
-
- 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/44—Arrangements for executing specific programs
- G06F9/445—Program loading or initiating
- G06F9/44521—Dynamic linking or loading; Link editing at or after load time, e.g. Java class loading
- G06F9/44526—Plug-ins; Add-ons
-
- 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/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0803—Configuration setting
- H04L41/0813—Configuration setting characterised by the conditions triggering a change of settings
- H04L41/082—Configuration setting characterised by the conditions triggering a change of settings the condition being updates or upgrades of network functionality
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Signal Processing (AREA)
- Computer Networks & Wireless Communication (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Health & Medical Sciences (AREA)
- Medical Informatics (AREA)
- General Health & Medical Sciences (AREA)
- Computing Systems (AREA)
- Computer Security & Cryptography (AREA)
- Information Transfer Between Computers (AREA)
- Stored Programmes (AREA)
Abstract
The invention discloses a plug-in hot updating system and a method for a medical internet of things message routing device; the plug-in hot updating system comprises a life cycle management module, a plug-in loader, a life cycle monitor, a plug-in processor, a plug-in synchronizer and a class loading manager; the invention can update the plug-in unit of the message routing device of the medical internet of things based on visual convenient stream calculation without stopping, can expand service functions in a non-stop and non-restarting mode, effectively reduces system unavailability and data loss caused by service expansion, and can support plug-in hot update. The system and the method can effectively expand the service capacity on line and dynamically expand the access equipment aiming at the medical internet of things field, and can effectively prevent service unavailability caused by restarting.
Description
Technical Field
The invention belongs to the technical field of plug-in upgrade, and particularly relates to a plug-in hot updating system and method for a medical internet of things message routing device.
Background
The invention relates to a medical internet of things message routing device based on visual convenient stream calculation, which provides a set of technology which can be realized or expanded by a third party and can be used for expanding plug-ins or replacing plug-ins. The approximate implementation scheme of the prior art and the invention is a dubbo spi mechanism, and the main function of the scheme is to define the full-limit name of the implementation class of the interface in a configuration file, and a server reads the configuration file and loads the implementation class. Thus, the implementation class can be dynamically replaced for the interface at the time of operation. The scheme can not load the implementation class of the interface which is not defined by the service and can not be updated thermally, so the scheme lacks support for the data integration capability of the medical internet of things message routing device based on the visualized convenient stream calculation and greatly reduces the user experience of users. And is not suitable for targeted processing of unstructured data in different fields.
In the patent of 'medical internet of things message routing device and method based on visual convenient flow calculation', it is described that the message routing device is formed by combining components with different fine granularity, so that the plug-ins cannot be dynamically updated and loaded, and because the plug-ins comprise both front-end forms and rear-end business logic, the invention mainly solves the problem that the plug-ins in the original patent cannot be updated thermally.
Medical internet of things message routing device and method based on visual convenient stream calculation: the patent number ZL 202010892002.1 is the patent
Plug-in: the node described in the patent of 'medical internet of things message routing device and method based on visual convenient flow calculation' is a fine-grained service function and has a front-end form and a rear-end service logic
PluginLifecircle: lifecycle management for plug-in function modules
PluginLoader: plug-in loader
PluginLifecycleListener: lifecycle monitor for plug-in function module
PluginHandler: plug-in processor
NodeSyncronizer: plug-in synchronizer
ClassLoaderManager: class loading manager
Storage: storage management (flow center of message routing device)
JVM: java virtual machine, providing operation environment for message router system and plug-in hot update system.
Spi: SPI is a service provision discovery mechanism built in JDK
Disclosure of Invention
Aiming at the fact that nodes in the medical internet of things message routing device and method based on visual convenient flow calculation cannot be updated online, the expansion of service functions after the medical internet of things equipment is accessed is limited. The invention provides a plug-in hot updating system and a method for a medical internet of things message routing device.
The invention utilizes the hot updating technology of the self-developed class loader to realize that one class loader instance loads only one plug-in, so as to realize plug-in isolation and realize the on-line expansion of the message routing device node. After loading is successful, the message routing device in the patent of the medical internet of things message routing device and method based on visual convenient flow calculation reloads the form and the business logic in the plug-in, so that the business logic of the front-end form and the back-end is expanded and updated on line.
A plug-in hot updating system for a medical internet of things message routing device comprises a life cycle management module, a plug-in loader, a life cycle monitor, a plug-in processor, a plug-in synchronizer and a class loading manager.
The life cycle management module: the system module is used for managing the life cycle of the whole plug-in hot updating system module and controlling the starting and closing of the system module.
Plug-in loader: classifying (adding, modifying and deleting) events of uploading plug-ins, and assigning plug-ins to corresponding plug-in processors according to different event types;
Life cycle monitor: the method is used for monitoring the actions of adding, updating and deleting the plug-in when the plug-in hot updating system runs, and notifying the plug-in synchronizer according to the event type after the event type is processed.
Plug-in processor: for handling plug-ins provided in a plug-in loader. And when the plug-in is uploaded or updated, the class loader corresponding to the plug-in is obtained from the class loading manager to load the plug-in. When a plug-in is deleted, the class loader for that plug-in is removed from the class loading manager.
Plug-in synchronizer: and synchronizing the plug-in, notifying a message routing device using the plug-in, and delivering the message to a plug-in processor for loading or cleaning.
Class loading manager: and managing class loaders corresponding to all plug-ins, and completing the functions of adding new class loaders, deleting existing class loaders and inquiring class loaders.
A plug-in hot updating method for a medical internet of things message routing device comprises the following steps:
step (1), uploading plug-ins;
and starting the plug-in hot updating system through the life cycle management module, and uploading the plug-in the form of jar packets to the plug-in hot updating system on a flow visual configuration interface of the message routing device.
Step (2), loading the plug-in by the plug-in loader and assigning the plug-in to the plug-in processor for processing,
The plug-in loader loads the plug-ins and classifies events of uploading the plug-ins, and the plug-ins are assigned to corresponding plug-in processors according to different event types. The event types comprise addition, update and deletion.
And (3) respectively carrying out different treatments by different plug-in processors according to the event types of the uploading plug-ins.
When the event type is newly added, the plug-in processor loads the plug-in by creating a class loader instance, adds the class loader instance into a class loading manager, analyzes front-end files and back-end files in the plug-in by the created class loader instance, loads the analyzed files into a Java Virtual Machine (JVM), stores the analyzed files into a flow center of the message routing device, and when the loading is completed, instantiates and executes the message routing device according to the programmed content when the flow of the message routing device is executed.
When the event type is updated, the plug-in processor firstly cleans up the existing class loader instance in the medical internet of things message routing device, then establishes a class loader instance to load the plug-in, analyzes the front-end file and the back-end file in the plug-in through the newly established class loader instance, loads the analyzed files into a Java Virtual Machine (JVM), and simultaneously updates the newly established class loader instance into a class loading manager and stores the newly established class loader instance into a flow center of the message routing device.
When the event type is delete, the plug-in processor needs to delete the class loader instance that loaded the current plug-in and clean up the data information of the current plug-in the flow center of the message routing device.
And (4) monitoring whether the plug-in is loaded by using the life cycle monitor, notifying the plug-in synchronizer according to the event type after the event type is processed, and notifying other message routing device modules needing to use the plug-in to load or clean by the plug-in synchronizer.
The invention has the following beneficial effects:
the invention can update the plug-in unit of the message routing device of the medical internet of things based on visual convenient stream calculation without stopping, can expand service functions in a non-stop and non-restarting mode, effectively reduces system unavailability and data loss caused by service expansion, and can support plug-in hot update.
The system and the method can effectively expand the service capacity on line and dynamically expand the access equipment aiming at the medical internet of things field, and can effectively prevent service unavailability caused by restarting.
Drawings
FIG. 1 is a flow chart of a method according to an embodiment of the present invention;
fig. 2 is a schematic diagram of a system structure according to an embodiment of the invention.
Detailed Description
The process according to the invention is further described below with reference to the accompanying drawings and examples.
The plug-in module itself needs to have a life cycle (PluginLifecircle) with two functions of starting and closing, which correspond to the functions of starting and closing the plug-in module respectively. Then, when using plug-in upload, a plug-in module function must be started, and when uploading a plug-in, a plug-in loader (PluginLoader) is required to load the plug-in, the plug-in loader classifies (adds and updates) the event of uploading the plug-in, and the plug-in loader assigns the plug-in to the corresponding plug-in processor (PluginHandler) for processing according to different classifications. The add-in handler of the new and update event obtains the class loader corresponding to the add-in from the class loader management module (ClassLoaderManager) to load the add-in, where the add-in is updated to jvm and stored to the flow center of the message routing device. After this step is done, a lifecycle monitor (PluginLifecycleListener) is used to monitor whether the plug-in completes loading, if so, the event is monitored, and the plug-in synchronizer is given according to the event type, and the plug-in is synchronized into another service and then loaded again, so that the concept of the cluster is met. The insert may be used at this point.
As shown in fig. 2, a plug-in hot update system for a medical internet of things message routing device includes a lifecycle management module (PluginLifecircle), a plug-in loader (PluginLoader), a lifecycle listener (PluginLifecycleListener), a plug-in processor (PluginHandler), a plug-in synchronizer (NodeSyncronizer), and a class loading manager (ClassLoaderManager).
The life cycle management module (PluginLifecircle): the system module is used for managing the life cycle of the whole plug-in hot updating system module and controlling the starting and closing of the system module.
Plug-in loader (PluginLoader): classifying (adding, modifying and deleting) events of uploading plug-ins, and assigning plug-ins to corresponding plug-in processors according to different event types;
Lifecycle listener (PluginLifecycleListener): the method is used for monitoring the actions of adding, updating and deleting the plug-in when the plug-in hot updating system runs, and notifying the plug-in synchronizer according to the event type after the event type is processed.
Plug-in processor (PluginHandler): for handling plug-ins provided in a plug-in loader. And when the plug-in is uploaded or updated, the class loader corresponding to the plug-in is obtained from the class loading manager to load the plug-in. When a plug-in is deleted, the class loader for that plug-in is removed from the class loading manager.
Plug-in synchronizer (NodeSyncronizer): and synchronizing the plug-in, notifying a message routing device using the plug-in, and delivering the message to a plug-in processor for loading or cleaning.
Class loading manager (ClassLoaderManager): and managing class loaders corresponding to all plug-ins, and completing the functions of adding new class loaders, deleting existing class loaders and inquiring class loaders.
As shown in fig. 1, a plug-in hot updating method for a medical internet of things message routing device comprises the following steps:
step (1), uploading plug-ins;
and starting the plug-in hot updating system through the life cycle management module, and uploading the plug-in the form of jar packets to the plug-in hot updating system on a flow visual configuration interface of the message routing device.
Step (2), loading the plug-in by the plug-in loader and assigning the plug-in to the plug-in processor for processing,
The plug-in loader loads the plug-ins and classifies events of uploading the plug-ins, and the plug-ins are assigned to corresponding plug-in processors according to different event types. The event types comprise addition, update and deletion.
And (3) respectively carrying out different treatments by different plug-in processors according to the event types of the uploading plug-ins.
When the event type is newly added, the plug-in processor loads the plug-in by creating a class loader instance, adds the class loader instance into a class loading manager, analyzes front-end files and back-end files in the plug-in by the created class loader instance, loads the analyzed files into a Java Virtual Machine (JVM), stores the analyzed files into a flow center of the message routing device, and when the loading is completed, instantiates and executes the message routing device according to the programmed content when the flow of the message routing device is executed.
When the event type is updated, the plug-in processor firstly cleans up the existing class loader instance in the medical internet of things message routing device, then establishes a class loader instance to load the plug-in, analyzes the front-end file and the back-end file in the plug-in through the newly established class loader instance, loads the analyzed files into a Java Virtual Machine (JVM), and simultaneously updates the newly established class loader instance into a class loading manager and stores the newly established class loader instance into a flow center of the message routing device.
When the event type is delete, the plug-in processor needs to delete the class loader instance that loaded the current plug-in and clean up the data information of the current plug-in the flow center of the message routing device.
And (4) monitoring whether the plug-in is loaded by using the life cycle monitor, notifying the plug-in synchronizer according to the event type after the event type is processed, and notifying other message routing device modules needing to use the plug-in to load or clean by the plug-in synchronizer.
Claims (2)
1. A plug-in hot updating system for a medical internet of things message routing device is characterized by comprising a life cycle management module, a plug-in loader, a life cycle monitor, a plug-in processor, a plug-in synchronizer and a class loading manager;
The life cycle management module: the system module is used for managing the life cycle of the whole plug-in hot updating system module and controlling the starting and closing of the system module;
plug-in loader: classifying events of the uploading plug-ins, wherein the event classification comprises adding, modifying and deleting, and the plug-ins are assigned to corresponding plug-in processors according to different event types;
life cycle monitor: the plug-in hot update system is used for monitoring the actions of adding, updating and deleting the plug-ins when the plug-in hot update system runs, and notifying the plug-in synchronizer according to the event type after the event type is processed;
plug-in processor: for processing plug-ins provided in a plug-in loader; when the plug-in is uploaded or updated, a class loader corresponding to the plug-in is obtained from a class loading manager to load the plug-in; when a plug-in is deleted, removing a class loader of the plug-in from a class loading manager;
plug-in synchronizer: synchronizing the plug-in, notifying a message routing device using the plug-in, and delivering the message to a plug-in processor for loading or cleaning;
Class loading manager: and managing class loaders corresponding to all plug-ins, and completing the functions of adding new class loaders, deleting existing class loaders and inquiring class loaders.
2. A plug-in hot updating method for a medical internet of things message routing device is characterized by comprising the following steps:
step (1), uploading plug-ins;
starting a plug-in hot updating system through a life cycle management module, and uploading a plug-in a jar packet form to the plug-in hot updating system on a message routing device flow visual configuration interface;
Step (2), loading the plug-in by the plug-in loader and assigning the plug-in to the plug-in processor for processing,
The plug-in loader loads plug-ins and classifies events of uploading the plug-ins, and the plug-ins are assigned to corresponding plug-in processors according to different event types; the event types comprise addition, update and deletion;
step (3), different plug-in processors respectively process according to event types of the uploading plug-ins;
Step (4), monitoring whether the plug-in is loaded or not by using a life cycle monitor, notifying a plug-in synchronizer according to the event type after the event type is processed, and synchronously notifying other message routing device modules needing to use the plug-in by the plug-in synchronizer to load or clean;
the specific method of the step (3) is as follows:
When the event type is newly increased, the plug-in processor loads the plug-in by creating a class loader instance, adds the class loader instance into a class loading manager, analyzes front-end files and back-end files in the plug-in by the created class loader instance, loads the analyzed files into a Java virtual machine, stores the analyzed files into a flow center of the message routing device, and when the loading is completed, instantiates and executes the process according to the programmed content when the flow of the message routing device is executed;
when the event type is updated, the plug-in processor firstly cleans the existing class loader instance in the medical internet of things message routing device, then establishes a class loader instance to load the plug-in, analyzes the front-end file and the back-end file in the plug-in through the newly established class loader instance, loads the analyzed files into the Java virtual machine, and simultaneously updates the newly established class loader instance into a class loading manager and stores the newly established class loader instance into a flow center of the message routing device;
When the event type is delete, the plug-in processor needs to delete the class loader instance that loaded the current plug-in and clean up the data information of the current plug-in the flow center of the message routing device.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111624690.4A CN114500352B (en) | 2021-12-28 | 2021-12-28 | Plug-in hot updating system and method for medical internet of things message routing device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111624690.4A CN114500352B (en) | 2021-12-28 | 2021-12-28 | Plug-in hot updating system and method for medical internet of things message routing device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN114500352A CN114500352A (en) | 2022-05-13 |
| CN114500352B true CN114500352B (en) | 2024-05-07 |
Family
ID=81495635
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111624690.4A Active CN114500352B (en) | 2021-12-28 | 2021-12-28 | Plug-in hot updating system and method for medical internet of things message routing device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114500352B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115268983B (en) * | 2022-08-09 | 2023-04-07 | 清华大学 | Hot repair method and device for embedded Internet of things equipment vulnerability |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103218220A (en) * | 2013-02-25 | 2013-07-24 | 上海谐宇网络科技有限公司 | Dynamic pluggable component based-Internet of things middleware system |
| CN109918148A (en) * | 2019-02-21 | 2019-06-21 | 上海伊巢网络科技有限公司 | The component dynamic pluggable system of Internet of things middleware |
| CN112802591A (en) * | 2021-01-26 | 2021-05-14 | 创业慧康科技股份有限公司 | LUA-based thermal updating method for medical instrument data acquisition equipment |
| CN113726579A (en) * | 2021-09-02 | 2021-11-30 | 国网信息通信产业集团有限公司 | Method and device for realizing power Internet of things communication protocol plug-in |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8910138B2 (en) * | 2012-05-23 | 2014-12-09 | Oracle International Corporation | Hot pluggable extensions for access management system |
| US10805155B1 (en) * | 2019-06-14 | 2020-10-13 | Tesla Viet Nam Technology Company Limited | Intelligent plug-and-play point-to-multipoint internet of things (IoT) platform and method of managing the same |
-
2021
- 2021-12-28 CN CN202111624690.4A patent/CN114500352B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103218220A (en) * | 2013-02-25 | 2013-07-24 | 上海谐宇网络科技有限公司 | Dynamic pluggable component based-Internet of things middleware system |
| CN109918148A (en) * | 2019-02-21 | 2019-06-21 | 上海伊巢网络科技有限公司 | The component dynamic pluggable system of Internet of things middleware |
| CN112802591A (en) * | 2021-01-26 | 2021-05-14 | 创业慧康科技股份有限公司 | LUA-based thermal updating method for medical instrument data acquisition equipment |
| CN113726579A (en) * | 2021-09-02 | 2021-11-30 | 国网信息通信产业集团有限公司 | Method and device for realizing power Internet of things communication protocol plug-in |
Also Published As
| Publication number | Publication date |
|---|---|
| CN114500352A (en) | 2022-05-13 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| KR101438982B1 (en) | System and method of utilizing a framework for information routing in large-scale distributed systems using swarm intelligence | |
| US10511506B2 (en) | Method and device for managing virtualized network function | |
| CN1755720A (en) | Methods and systems for caching and synchronizing project data | |
| KR101871383B1 (en) | Method and system for using a recursive event listener on a node in hierarchical data structure | |
| CN112463366B (en) | Cloud-native-oriented micro-service automatic expansion and contraction capacity and automatic fusing method and system | |
| CN109656742B (en) | Node exception handling method and device and storage medium | |
| Babaoğlu et al. | System support for partition-aware network applications | |
| CN111930706B (en) | Remote call-based distributed network file storage system and method | |
| CN108427619B (en) | Log management method and device, computing equipment and storage medium | |
| CN113268308B (en) | Information processing method, device and storage medium | |
| CN114500352B (en) | Plug-in hot updating system and method for medical internet of things message routing device | |
| CN113220422B (en) | Method and system for modifying Pod network interface based on operation of CNI plug-in K8s | |
| WO2006013992A1 (en) | Network system, management computer, cluster management method, and computer program | |
| CN112506870A (en) | Data warehouse increment updating method and device and computer equipment | |
| CN112988679A (en) | Log collection control method and device, storage medium and server | |
| CN112965839A (en) | Message transmission method, device, equipment and storage medium | |
| CN116627721A (en) | Cloud primary database recovery method, device and storage medium based on hybrid cloud | |
| WO2024021469A1 (en) | System operation and maintenance management method and apparatus, and electronic device | |
| CN115801563A (en) | Method and application for dynamically collecting cluster logs | |
| CN113849450A (en) | Information processing method and information processing device | |
| CN106599323A (en) | Method and apparatus for realizing distributed pipeline in distributed file system | |
| CN111290767B (en) | Container group updating method and system with service quick recovery function | |
| WO2017219982A1 (en) | Cache clear method and apparatus | |
| CN115225645B (en) | Service updating method, device, system and storage medium | |
| CN114911577A (en) | Method, device, equipment and storage medium for setting network isolation rule |
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 |