EP4548191A1 - Système et procédés pour services de métadonnées - Google Patents

Système et procédés pour services de métadonnées

Info

Publication number
EP4548191A1
EP4548191A1 EP23845631.3A EP23845631A EP4548191A1 EP 4548191 A1 EP4548191 A1 EP 4548191A1 EP 23845631 A EP23845631 A EP 23845631A EP 4548191 A1 EP4548191 A1 EP 4548191A1
Authority
EP
European Patent Office
Prior art keywords
node
working
list
nodes
target
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.)
Pending
Application number
EP23845631.3A
Other languages
German (de)
English (en)
Other versions
EP4548191A4 (fr
Inventor
Keyao XU
Xin Luo
Wenlong JIANG
Mingwei Zhou
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Zhejiang Dahua Technology Co Ltd
Original Assignee
Zhejiang Dahua Technology Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Zhejiang Dahua Technology Co Ltd filed Critical Zhejiang Dahua Technology Co Ltd
Publication of EP4548191A1 publication Critical patent/EP4548191A1/fr
Publication of EP4548191A4 publication Critical patent/EP4548191A4/fr
Pending legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
    • G06F3/0601—Interfaces specially adapted for storage systems
    • G06F3/0602—Interfaces specially adapted for storage systems specifically adapted to achieve a particular effect
    • G06F3/0614—Improving the reliability of storage systems
    • G06F3/0617—Improving the reliability of storage systems in relation to availability
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/16—Error detection or correction of the data by redundancy in hardware
    • G06F11/20—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements
    • G06F11/202—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements where processing functionality is redundant
    • G06F11/2023—Failover techniques
    • G06F11/2028—Failover techniques eliminating a faulty processor or activating a spare
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/16—Error detection or correction of the data by redundancy in hardware
    • G06F11/20—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements
    • G06F11/202—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements where processing functionality is redundant
    • G06F11/2041—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements where processing functionality is redundant with more than one idle spare processing component
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/16—Error detection or correction of the data by redundancy in hardware
    • G06F11/20—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements
    • G06F11/2053—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements where persistent mass storage functionality or persistent mass storage control functionality is redundant
    • G06F11/2056—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements where persistent mass storage functionality or persistent mass storage control functionality is redundant by mirroring
    • G06F11/2082—Data synchronisation
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
    • G06F3/0601—Interfaces specially adapted for storage systems
    • G06F3/0628—Interfaces specially adapted for storage systems making use of a particular technique
    • G06F3/0629—Configuration or reconfiguration of storage systems
    • G06F3/0632—Configuration or reconfiguration of storage systems by initialisation or re-initialisation of storage systems
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
    • G06F3/0601—Interfaces specially adapted for storage systems
    • G06F3/0628—Interfaces specially adapted for storage systems making use of a particular technique
    • G06F3/0629—Configuration or reconfiguration of storage systems
    • G06F3/0635—Configuration or reconfiguration of storage systems by changing the path, e.g. traffic rerouting, path reconfiguration
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
    • G06F3/0601—Interfaces specially adapted for storage systems
    • G06F3/0628—Interfaces specially adapted for storage systems making use of a particular technique
    • G06F3/0646—Horizontal data movement in storage systems, i.e. moving data in between storage devices or systems
    • G06F3/065—Replication mechanisms
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
    • G06F3/0601—Interfaces specially adapted for storage systems
    • G06F3/0628—Interfaces specially adapted for storage systems making use of a particular technique
    • G06F3/0646—Horizontal data movement in storage systems, i.e. moving data in between storage devices or systems
    • G06F3/0652—Erasing, e.g. deleting, data cleaning, moving of data to a wastebasket
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
    • G06F3/0601—Interfaces specially adapted for storage systems
    • G06F3/0668—Interfaces specially adapted for storage systems adopting a particular infrastructure
    • G06F3/067—Distributed or networked storage systems, e.g. storage area networks [SAN], network attached storage [NAS]
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/30—Monitoring
    • G06F11/3003—Monitoring arrangements specially adapted to the computing system or computing system component being monitored
    • G06F11/3006—Monitoring arrangements specially adapted to the computing system or computing system component being monitored where the computing system is distributed, e.g. networked systems, clusters, multiprocessor systems

Definitions

  • the present disclosure generally relates to metadata services, and more particularly, relates to systems and methods for providing metadata services using a cluster system.
  • Metadata services were an object-oriented repository technology that could be integrated with enterprise information systems or with applications that process metadata.
  • a cluster system which includes multiple metadata nodes, is often used to provide metadata services.
  • the availability of metadata services of a cluster system refers to the ability of the cluster system to provide metadata services when one or more metadata nodes of the cluster system fail (i.e., are abnormal) .
  • the availability of the metadata services is vital for the cluster system. Therefore, it is desirable to provide systems and methods to improve the availability of the metadata services of a cluster system.
  • a cluster system may be provided.
  • the cluster system may include a main node, working nodes, and a management processor.
  • the main node may be configured for providing metadata services.
  • Each working node may be communicatively connected to the main node and configured to send report information to the main node.
  • the working nodes may include one or more first working nodes.
  • the one or more first working nodes may be standby nodes of the main node configured for metadata backup.
  • the management processor may be configured to update a first node list and a second node list based on the report information of each working node.
  • the first node list may relate to the one or more first working nodes
  • the second node list may relate to one or more second working nodes other than the one or more first working nodes among the working nodes.
  • the management processor may determine a target second working node from the second node list, designate the target second working node as a new first working node, and update the first node list and the second node list.
  • the management processor may be part of the main node, or the management processor may be independent from the main node and configured to receive the report information of each of the working nodes from the main node.
  • the management processor in response to detecting that one of the one or more second working nodes is abnormal, may be further configured t remove the abnormal second working node from the second node list.
  • the management processor may update the first node list and the second node list based on the report information of each working node by performing the following operations. For each working node, the management processor may determine, whether the working node is a first working node or a second working node based on the report information of the working node. In response to determining that the working node is a first working node, the management processor may update the first node list based on the report information of the working node. In response to determining that the working node is a second working node, the management processor may update the second node list based on the report information of the working node.
  • the target second working node may be determined from the second node list by performing the following operations. For each second working node in the second node list, the management processor may determine a load of the second working node. Further, the management processor may determine the target second working node based on the load of each second working node.
  • the target second working node may be determined from the second node list by performing the following operations. For each second working node in the second node list, the management processor may determine a probability that the second working node is abnormal based on the report information of the second working node. Further, the management processor may determine the target second working node based on the probability corresponding to each second working node.
  • the management processor in response to detecting that one of the one or more first working nodes is abnormal, to determine the target second working node from the second node list, the management processor may be further configured to perform the following operations. In response to determining that detecting that one of the one or more first working nodes is abnormal, the management processor may determine whether the count of remaining first working nodes in the first node list other than the first working node is smaller than a count threshold. In response to determining that the count of remaining first working nodes in the first node list is smaller than a count threshold, the management processor may determine the target second working node from the second node list.
  • the management processor in response to detecting that the main node is abnormal, may be further configured to, determine a target first working node that performs the metadata services of the main node in place of the main node, and update the first node list and the second node list based on the target first working node.
  • a method implemented on a management processor of a cluster system may be provided.
  • the cluster system may further comprise a main node configured for providing metadata services and working nodes each of which is communicatively connected to the main node and configured to send report information to the main node.
  • the working nodes may include one or more first working nodes.
  • the one or more first working nodes may be standby nodes of the main node configured for metadata backup.
  • the method comprising updating a first node list and a second node list based on the report information of each working node.
  • the first node list may relate to the one or more first working nodes
  • the second node list may relate to one or more second working nodes other than the one or more first working nodes among the working nodes.
  • the method further comprising determining a target second working node from the second node list, designating the target second working node as a new first working node, and updating the first node list and the second node list.
  • a non-transitory computer readable medium may comprise a set of instructions.
  • the set of instructions may be executed by a management processor of a cluster system.
  • the cluster system may further comprise a main node configured for providing metadata services and working nodes each of which is communicatively connected to the main node and configured to send report information to the main node.
  • the working nodes may include one or more first working nodes.
  • the one or more first working nodes may be standby nodes of the main node configured for metadata backup.
  • the method comprising updating a first node list and a second node list based on the report information of each working node.
  • the first node list may relate to the one or more first working nodes
  • the second node list may relate to one or more second working nodes other than the one or more first working nodes among the working nodes.
  • the method further comprising determining a target second working node from the second node list, designating the target second working node as a new first working node, and updating the first node list and the second node list.
  • FIG. 1 is a schematic diagram illustrating an exemplary cluster system according to some embodiments of the present disclosure
  • FIG. 2 is a schematic diagram illustrating an exemplary cluster system 200 according to some embodiments of the present disclosure
  • FIG. 3 is a schematic diagram illustrating exemplary hardware and/or software components of a computing device 300 according to some embodiments of the present disclosure
  • FIG. 4 is a block diagram illustrating an exemplary management processor according to some embodiments of the present disclosure
  • FIG. 5 is a flowchart illustrating an exemplary metadata services process according to some embodiments of the present disclosure
  • FIG. 6 is a schematic diagram illustrating an exemplary updating of a second node list 620 according to some embodiments of the present disclosure
  • FIG. 7 is a schematic diagram illustrating an exemplary updating of a first node list 710 and a second node list 720 according to some embodiments of the present disclosure
  • FIG. 8 is a flowchart illustrating an exemplary process 800 for managing nodes in a cluster system according to some embodiments of the present disclosure.
  • FIG. 9 is a schematic diagram illustrating an exemplary updating of a first node list 910 and a second node list 920 according to some embodiments of the present disclosure.
  • system, ” “engine, ” “unit, ” “module, ” and/or “block” used herein are one method to distinguish different components, elements, parts, section or assembly of different level in ascending order. However, the terms may be displaced by other expressions if they may achieve the same purpose.
  • module, ” “unit, ” or “block, ” as used herein refers to logic embodied in hardware or firmware, or to a collection of software instructions.
  • a module, a unit, or a block described herein may be implemented as software and/or hardware and may be stored in any type of non-transitory computer-readable medium or other storage devices.
  • a software module/unit/block may be compiled and linked into an executable program. It will be appreciated that software modules can be callable from other modules/units/blocks or from themselves, and/or may be invoked in response to detected events or interrupts.
  • Software modules/units/blocks configured for execution on computing devices (e.g., processor 320 as illustrated in FIG.
  • a computer readable medium such as a compact disc, a digital video disc, a flash drive, a magnetic disc, or any other tangible medium, or as a digital download (and can be originally stored in a compressed or installable format that needs installation, decompression, or decryption prior to execution) .
  • Such software code may be stored, partially or fully, on a storage device of the executing computing device, for execution by the computing device.
  • Software instructions may be embedded in firmware, such as an EPROM.
  • hardware modules (or units or blocks) may be included in connected logic components, such as gates and flip-flops, and/or can be included in programmable units, such as programmable gate arrays or processors.
  • one or more standby nodes are usually set up for a main node (also referred to as a primary node) that provides metadata services.
  • the main node also referred to as a primary node
  • the one or more standby nodes can replace the main node to provide the metadata services for the cluster system.
  • the availability of metadata services directly depends on a number of standby nodes that can be used to replace the main node to provide metadata services.
  • the maximum availability of the metadata services depends on the number of the standby nodes. For example, if there are n metadata standby nodes in the cluster system, in order to ensure the normal operation of metadata services, the cluster system can allow up to n metadata nodes to be abnormal, and the maximum availability of the metadata services of the cluster system is limited.
  • the present disclosure provides systems and methods for metadata services using a cluster system.
  • the systems may include a main node, working nodes, and a management processor.
  • the main node may be configured for providing metadata services.
  • Each working node may be communicatively connected to the main node and configured to send report information to the main node.
  • the working nodes may include one or more first working nodes.
  • the one or more first working nodes may be standby nodes of the main node configured for metadata backup.
  • the management processor may be configured to update a first node list and a second node list based on the report information of each working node.
  • the first node list may relate to the one or more first working nodes
  • the second node list may relate to one or more second working nodes other than the one or more first working nodes among the working nodes.
  • the management processor may determine a target second working node from the second node list, designate the target second working node as a new first working node, and update the first node list and the second node list.
  • the availability of metadata services depends not only on the number of standby nodes (i.e., the first working nodes) but also on the number of second working nodes, the maximum availability of the metadata services of the cluster system may be determined based on a sum of the number of the first working nodes and the number of second working nodes.
  • the present systems and methods may greatly improve the availability of metadata services.
  • FIG. 1 is a schematic diagram illustrating an exemplary cluster system 100 according to some embodiments of the present disclosure.
  • the cluster system 100 may include a main node 110, working nodes 120, and a management processor 130.
  • the main node 110, the working nodes 120, and the management processor 130 may be connected each other via a network or directly.
  • the main node 110 may be configured for providing metadata services.
  • the metadata services may include various management services for metadata such as a metadata storage service, a metadata updating service, a metadata collection service, etc.
  • Each working node may be communicatively connected to the main node 110 and configured to send report information to the main node 110.
  • the main node 110 may record, update, and detect the report information reported by each working node in real time.
  • each working node may be capable of providing metadata services.
  • the working nodes 120 may include one or more first working nodes 1201 and one or one or more second working nodes 1202 other than the one or more first working nodes 1201.
  • the one or more first working nodes 1201 may be standby nodes of the main node 110 configured for metadata backup.
  • a first working node refers to a node that is providing metadata services and stores metadata of the cluster system 100.
  • the task (s) , configuration information, or other information relating to metadata services of the main node 110 and the one or more first working nodes 1201 may be synchronized.
  • the metadata may be synchronized to the one or more first working nodes 1201 for storage and backup.
  • the one or more first working nodes 1201 may replace the main node 110 to perform the metadata services of the cluster system 100 when, for example, the main node 110 is abnormal.
  • a node is abnormal refers to that the node cannot operate in accordance with a normal mode.
  • the node may crash when a computer program, such as a software application or an operating system of the node stops functioning properly.
  • the node can not work normally when a hard disk drive has malfunctions.
  • one of the one or more first working nodes 1201 may take over one or more tasks of the main node 110 and perform the task (s) .
  • the one or more first working nodes 1201 may be also configured to work as a working server and perform one or more other tasks (e.g., data computational tasks) of the cluster system 100.
  • the management processor 130 may be independent from the main node 110 and configured to receive the report information of each of the working nodes from the main node 110.
  • the management processor 130 may be configured to monitor and/or manage the nodes (e.g., the main node 110, the one or more first working nodes 1201, the one or one or more second working nodes 1202, etc. ) of the cluster system 100.
  • the management processor 130 may be configured to monitor each node of the cluster system 100 and keep the cluster system 100 operating normally.
  • the management processor 130 may monitor the working nodes of the cluster system 100 via process 500 to ensure that the cluster system 100 includes enough first working nodes (i.e., standby nodes of the main node configured for metadata backup) .
  • the management processor 130 may monitor the main node 110 of the cluster system 100 via process 800 to ensure that the cluster system 100 includes a normal main node for providing metadata services.
  • the management processor 130 may perform the methods of the present disclosure.
  • the process 500 and/or the process 800 may be implemented as a set of instructions (e.g., an application) stored in a storage device.
  • the management processor 130 may execute the set of instructions and may accordingly be directed to perform the process 500 and/or the process 800.
  • a node of the cluster system 100 may include one or more processing units (e.g., single-core processing device (s) or multi-core processing device (s) ) .
  • processing units e.g., single-core processing device (s) or multi-core processing device (s)
  • the management processor 130 may include a central processing unit (CPU) , an application-specific integrated circuit (ASIC) , an application-specific instruction-set processor (ASIP) , a graphics processing unit (GPU) , a physics processing unit (PPU) , a digital signal processor (DSP) , a field programmable gate array (FPGA) , a programmable logic device (PLD) , a controller, a microcontroller unit, a reduced instruction-set computer (RISC) , a microprocessor, or the like, or any combination thereof.
  • CPU central processing unit
  • ASIC application-specific integrated circuit
  • ASIP application-specific instruction-set processor
  • GPU graphics processing unit
  • PPU physics processing unit
  • DSP digital signal processor
  • FPGA field programmable gate array
  • PLD programmable logic device
  • controller a microcontroller unit, a reduced instruction-set computer (RISC) , a microprocessor, or the like, or any combination thereof.
  • RISC reduced instruction
  • the cluster system 100 may include one or more additional components.
  • the cluster system 100 may include a network that can facilitate the exchange of information and/or data in the cluster system 100.
  • one or more components in the cluster system 100 e.g., the main node 110, the working nodes 120, and the management processor 130
  • the network may be any type of wired or wireless network, or a combination thereof.
  • the cluster system 100 may further include a user terminal that enables user interactions between a user and one or more components of the cluster system 100.
  • FIG. 2 is a schematic diagram illustrating an exemplary cluster system 200 according to some embodiments of the present disclosure.
  • the cluster system 200 may be similar to the cluster system 100 as described in FIG. 1, except that the management processor 130 is part of the main node 110.
  • the main node 110 may be configured to monitor each node of the cluster system 100 and keep the cluster system 100 operating normally (e.g., by performing the process 500) .
  • FIG. 3 is a schematic diagram illustrating exemplary hardware and/or software components of a computing device 300 according to some embodiments of the present disclosure.
  • the computing device 300 may be used to implement any component (e.g., the main node 110, a working node 120, and the management processor 130) of the cluster system 100 as described herein.
  • the management processor 130 may be implemented on the computing device 300, via its hardware, software program, firmware, or a combination thereof.
  • only one such computer is shown, for convenience, the computer functions relating to system recovery as described herein may be implemented in a distributed fashion on a number of similar platforms to distribute the processing load.
  • the computing device 300 may include COM ports 350 connected to and from a network connected thereto to facilitate data communications.
  • the computing device 300 may also include a processor (e.g., the processor 320) , in the form of one or more processors (e.g., logic circuits) , for executing program instructions.
  • the processor 320 may include interface circuits and processing circuits therein.
  • the interface circuits may be configured to receive electronic signals from a bus 310, wherein the electronic signals encode structured data and/or instructions for the processing circuits to process.
  • the processing circuits may conduct logic calculations, and then determine a conclusion, a result, and/or an instruction encoded as electronic signals. Then the interface circuits may send out the electronic signals from the processing circuits via the bus 310.
  • the computing device 300 may further include program storage and data storage of different forms including, for example, a disk 370, and a read-only memory (ROM) 330, or a random-access memory (RAM) 340, for various data files to be processed and/or transmitted by the computing device 300.
  • the computing device 300 may also include program instructions stored in the ROM 330, RAM 340, and/or another type of non-transitory storage medium to be executed by the processor 320.
  • the methods and/or processes of the present disclosure may be implemented as the program instructions.
  • the computing device 300 may also include an I/O component 360, supporting input/output between the computer and other components.
  • the computing device 300 may also receive programming and data via network communications.
  • processors 320 are also contemplated; thus, operations and/or method steps performed by one processor 320 as described in the present disclosure may also be jointly or separately performed by the multiple processors.
  • the processor 320 of the computing device 300 executes both step A and step B, it should be understood that step A and step B may also be performed by two different processors 320 jointly or separately in the computing device 300 (e.g., a first processor executes step A and a second processor executes step B or the first and second processors jointly execute steps A and B) .
  • the acquisition module 410 may be configured to obtain information relating to the cluster system 100.
  • the acquisition module 410 may obtain report information of each of working nodes. More descriptions regarding the obtaining of the report information of each of working nodes may be found elsewhere in the present disclosure. See, e.g., operation 510 in FIG. 5, and relevant descriptions thereof.
  • the acquisition module 410 may obtain information relating to the main node. More descriptions regarding the obtaining of the information relating to the main node may be found elsewhere in the present disclosure. See, e.g., operation 810 in FIG. 8, and relevant descriptions thereof.
  • the updating module 420 may be configured to update a first node list and a second node list based on the report information of each working node. In some embodiments, in response to determining that the working node is a first working node, the updating module 42 may update the first node list based on the report information of the first working node. In some embodiments, in response to determining that the working node is a second working node, the updating module 420 may update the second node list based on the report information of the second working node. In some embodiments, in response to detecting that one of the one or more second working nodes is abnormal, the updating module 420 may update the second node list.
  • the updating module 420 may update the first node list and the second node list. More descriptions regarding the updating of the first node list and the second node list may be found elsewhere in the present disclosure. See, e.g., operations 520, 530, and 550 in FIG. 5, and relevant descriptions thereof.
  • the determination module 430 may be configured to determine a target second working node from the second node list. For example, in response to detecting that one of the one or more first working nodes is abnormal, the m determination module 430 may determine a target second working node from the second node list. More descriptions regarding the determination of the target second working node may be found elsewhere in the present disclosure. See, e.g., operation 540 in FIG. 5, and relevant descriptions thereof.
  • the determination module 430 may be also configured to determine whether the main node is abnormal based on the information relating to the main node. In response to determining that the main node is abnormal, the determination module 430 may be configured to determine a target first working node that performs the metadata services of the main node in place of the main node. More descriptions regarding the determination of the target first working node may be found elsewhere in the present disclosure. See, e.g., operation 830 in FIG. 8, and relevant descriptions thereof.
  • the updating module 420 may be also configured to update the first node list and the second node list based on the target first working node. More descriptions regarding the updating of the first node list and the second node list based on the target first working node may be found elsewhere in the present disclosure. See, e.g., operation 840 in FIG. 8, and relevant descriptions thereof.
  • the management processor 130 may include one or more additional modules, such as a storage module (not shown) for storing data.
  • FIG. 5 is a flowchart illustrating an exemplary metadata services process according to some embodiments of the present disclosure.
  • the management processor 130 may obtain report information of each of working nodes.
  • each working node may be communicatively connected to the main node 110 and configured to send report information to the main node 110 periodically or aperiodically.
  • the management processor 130 may obtain the report information of each of working nodes from the main node 110 periodically or aperiodically.
  • the management processor 130 may directly obtain the report information from each working node.
  • the working nodes may include one or more first working nodes 1201 and one or one or more second working nodes 1202 other than the one or more first working nodes 1201.
  • the report information relating to a first working node may include an internet protocol (IP) address of the first working node, a reporting time, a metadata service state of the first working node, a mark indicating that the first working node is a standby node of the main node, a version number of the first working node, or the like, or any combination thereof.
  • IP internet protocol
  • a metadata service state of a node may include an abnormal state and a normal state.
  • the abnormal state of the metadata service state refers to a state in which the node cannot perform metadata services in accordance with a normal mode
  • the normal state of the metadata service state refers to a state in which the node can perform metadata services in accordance with the normal mode
  • the report information relating to each of the one or more second working nodes may include an internet protocol (IP) address of the second working node, a reporting time, or the like, or any combination thereof.
  • IP internet protocol
  • the management processor 130 may update, based on the report information of each working node, a first node list and a second node list.
  • the first node list may relate to the one or more first working nodes.
  • the first node list may include report information of one or more first working nodes.
  • the first node list may be stored as a file, such as a first information configuration file. Merly by way of example, the first node list may include report information of M first working nodes as shown in Table 1 below.
  • the second node list may relate to the one or more second working nodes.
  • the second node list may include report information of one or more second working nodes.
  • the second node list may be stored as a file, such as a second information configuration file.
  • the second node list may include report information of N second working nodes as shown in Table 2 below.
  • the report information of the first working nodes and the report information of the second working nodes may be recorded separately in different lists (i.e., the first node list and the second node list) , which may be convenient for users to query and manage the report information of different nodes.
  • the management processor 130 may determine whether the working node is a first working node or a second working node based on the report information of the working node. For example, the management processor 130 may determine whether the working node is a first working node or a second working node according to the IP address of the working node and IP addresses of different working nodes (which is pre-stored in the management processor 130) . As another example, the management processor 130 may determine whether the report information of the working node includes a mark indicating that the first working node is a standby node of the main node.
  • the management processor 130 may determine that the working node is a first working node. In response to determining that the report information of the working node does not include the mark indicating that the first working node is a standby node of the main node, the management processor 130 may determine that the working node is a second working node.
  • the management processor 130 may update the first node list based on the report information of the first working node.
  • the management processor 130 may update the report information of the first working node in the first node list. For example, the management processor 130 may determine whether there is a record corresponding to the first working node in the first node list according to the IP address of the first working node. In response to determining that there is a record corresponding to the first working node in the first node list, the management processor 130 may update the record of the first working node in the first node list based on the newly received report information of the first working node.
  • the management processor 130 may replace the reporting time in the first node list with the current time. If the metadata service state of the first working node changes, the management processor 130 may update the metadata service state in the first node list. In response to determining that there is no record corresponding to the first working node in the first node list, the management processor 130 may add a record for recording the report information of the first working node into the first node list.
  • the management processor 130 may update the second node list based on the report information of the second working node.
  • the second node list may be updated in a similar manner as how the first list node is updated. For example, in response to determining that there is a record corresponding to the second working node in the second node list, the management processor 130 may update the record of the second working node in the second node list based on the newly received report information. For example, the management processor 130 may the reporting time in the second node list with the current time. In response to determining that there is no record corresponding to the second working node in the second node list, the management processor 130 may add a record for recording the report information of the second working node in the second node list.
  • the management processor 130 may monitor the states of each first working node and each second working node. When there are one or more working nodes are abnormal, the management processor 130 may also update the first node list and the second node list by performing operation 530 and/or operation 540.
  • the management processor 130 in response to detecting that one of the one or more second working nodes is abnormal, the management processor 130 (e.g., the updating module 420) may update the second node list.
  • the management processor 130 may determine whether the second working node is abnormal based on the reporting time of the second working node in the second node list. For example, the management processor 130 may determine whether a difference between the reporting time of the second working node in the second node list and the current time is greater than a first time threshold. In response to determining that the difference between the reporting time of the second working node in the second node list and the current time is greater than the first time threshold (i.e., the second working node has not reported for a long time) , the management processor 130 may determine that the second working node is abnormal.
  • the management processor 130 may update the second node list. Specifically, the management processor 130 may remove the abnormal second working node from the second node list (e.g., by deleting the report information of the abnormal second working node) .
  • FIG. 6 is a schematic diagram illustrating an exemplary updating of a second node list 620 according to some embodiments of the present disclosure. As shown in FIG. 6, in response to detecting that a black second working node 1202 in the second node list 620 is abnormal, the management processor 130 may update the second node list 620 by removing the black second working node 1202 and deleting the report information of the black second working node 1202 from the second node list 620.
  • the management processor 130 in response to detecting that one of the one or more first working nodes is abnormal, the management processor 130 (e.g., the determination module 430) may determine a target second working node from the second node list.
  • the management processor 130 may determine whether the first working node is abnormal based on the reporting time of the first working node in the first node list. For example, the management processor 130 may determine whether a difference between the reporting time of the first working node in the first node list and the current time is greater than a second time threshold. In response to determining that the difference between the reporting time of the first working node in the first node list and the current time is greater than the second time threshold, the management processor 130 may determine that the first working node is abnormal.
  • the first time threshold and the second time threshold may be set manually by a user (e.g., an engineer) according to an experience value or be a default setting of the cluster system 100, such as 5 mins, 10 mins, or a larger or smaller value.
  • the management processor 130 may determine whether the first working node is abnormal according to the metadata service state of the first working node. In response to determining that the metadata service state of the first working node is an abnormal state, the management processor 130 may determine that the first working node is abnormal.
  • the one or one or more second working nodes 1202 may process information and/or data relating to the cluster system 100 other than metadata to perform one or more other tasks of the cluster system 100 other than the metadata services, that is, the second working nodes in the second node list may be performing other tasks other than the metadata services.
  • the second working nodes in the second node list may be performing other tasks other than the metadata services.
  • a load of a second working node is greater than a load threshold, the second working node is not suitable to provide metadata services.
  • the load of the second working node may reflect an amount of tasks processed by the second working node.
  • the management processor 130 may determine the load of the second working node.
  • the management processor 130 may determine the load of the second working node based on a central processing unit (CPU) usage, a memory usage, an input/output (IO) load, a network bandwidth, etc., used by the second working node. For example, the greater the CPU usage used by the second working node is, the greater the load of the second working node may be. Further, the management processor 130 may determine the target second working node based on the load of each second working node. Specifically, the management processor 130 may determine one or more second working nodes with loads smaller than the load threshold, and select one of the one or more second working nides as the target second working node.
  • CPU central processing unit
  • IO input/output
  • the management processor 130 may designate a second working node with the minimum load in the one or more second working nides as the target second working node.
  • the target second working node may have enough load to perform metadata related tasks, and load balancing can be achieved in the cluster system.
  • the management processor 130 may determine a probability that the second working node is abnormal based on the report information of the second working node.
  • the probability that the second working node is abnormal may be also referred to as the abnormal probability corresponding to the second working node.
  • the management processor 130 may determine a time difference between the reporting time of the second working node in the second node list and the current time. Then, the management processor 130 may determine the probability that the second working node is abnormal according to the time difference. Merely by way of example, the smaller the time difference corresponding to a second working node is, the smaller abnormal probability corresponding to the second working node may be.
  • the management processor 130 may determine the target second working node based on the abnormal probability corresponding to each second working node. For example, the management processor 130 may designate a second working node with the minimum abnormal probability as the target second working node.
  • the management processor 130 may obtain feature information of each second working node in the second node list, and determine the target second working node based on the feature information of each second working node using a target node determination model.
  • Exemplary feature information of a second working node may include the reporting time of the second working node in the second node list, the CPU usage, the memory usage, the input/output (IO) load, the network bandwidth, etc., used by the second working node, or the like, or any combination thereof.
  • the feature information of each of the second working nodes in the second node list may be input into the target node determination model, the target node determination model may directly output the target second working node and/or information relating to each second working node.
  • the formation relating to each second working node may be a recommendation score of each second working node.
  • the management processor 130 may designate a second working node with the maximum score as the target second working node.
  • the target node determination model may be a trained machine learning model.
  • the target node determination model may include a deep learning model, such as a Deep Neural Network (DNN) model, a Convolutional Neural Network (CNN) model, a Recurrent Neural Network (RNN) model, a Feature Pyramid Network (FPN) model, etc.
  • DNN Deep Neural Network
  • CNN Convolutional Neural Network
  • RNN Recurrent Neural Network
  • FPN Feature Pyramid Network
  • Exemplary CNN models may include a V-Net model, a U-Net model, a Link-Net model, or the like, or any combination thereof.
  • the management processor 130 may obtain the target node determination model from one or more components of the cluster system 100 (e.g., a storage device, or an external source) via a network.
  • the target node determination model may be previously trained by a computing device, and stored in a storage device of the cluster system 100.
  • the management processor 130 may access the storage device and retrieve the target node determination model.
  • the target node determination model may be generated by training a preliminary model based on a plurality of training samples.
  • each training sample may include sample feature information of a sample second working node and a reference score corresponding to the sample second working node, wherein the reference score can be used as a ground truth (also referred to as a label) for model training.
  • the reference score may be determined by a user or may be automatically determined by a training device.
  • the management processor 130 may determine the target second working node combining a plurality of manners. For example, the management processor 130 may firstly obtain a plurality of candidate second working nodes using the target node determination model. Then, the management processor 130 may determine the target second working node based on the loads of the plurality of candidate second working nodes. As another example, the management processor 130 may firstly determine a plurality of candidate second working nodes with loads smaller than the load threshold. Further, the management processor 130 may determine the target second working node based on the abnormal probabilities corresponding to the plurality of candidate second working nodes. In this way, the determined target second working node may be more accurate.
  • the target second working node selected from the second node list may be more suitable to take over the metadata services, which improves the whole operation efficiency of the cluster system.
  • the management processor 130 may be communicated with a second management processor.
  • the second management processor may be configured to determine a working node from a second cluster system, and designate the working node as the target second working node.
  • the methods of the present disclosure may obtain working nodes from other clusters to add them to the first node list.
  • the maximum availability of the metadata services of the cluster system 100 may be determined based on a sum of the number of the first working nodes, the number of second working nodes, and the working nodes of other cluster systems, which may greatly improve the availability of metadata services.
  • the second management processor may determine the working node from the second cluster system in a similar manner as how to determine the target working node from the second node list, and the descriptions of which are not repeated here.
  • the availability of the metadata services of the cluster system 100 depends on a count (number) of the first working nodes in the first node list.
  • the minimum count of first working nodes in the first node list may be set in advance. When some first working nodes in the first node list are abnormal, the count of first working nodes in the first node list may decrease. However, since some abnormal first working nodes are repaired and re-added into the first node list or some second working node are added from the second node list into the first working node list, etc., the count of first working nodes in the first node list may increase, and may even cause the count of first working nodes in the first node list to be greater than the minimum count, thus causing waste of resources.
  • the management processor 130 may determine whether the count of remaining first working nodes in the first node list other than the first working node is smaller than a count threshold.
  • the count threshold may be set manually by a user (e.g., an engineer) according to an experience value or a default setting of the cluster system 100, such as 3, 5, or a larger or smaller value.
  • the management processor 130 may determine the target second working node from the second node list.
  • the management processor 130 may does not add a second working node from the second node list into the first node list. In this case, the management processor 130 may only update the first node list by removing the abnormal first working node and deleting the report information of the abnormal first working node from the first node list.
  • the management processor 130 may update the first node list and the second node list based on the target second working node.
  • the management processor 130 may directly designate the target second working node as a new first working node.
  • the metadata of the main node may be synchronized to the new first working node.
  • the management processor 130 may update the first node list by performing the following operations.
  • the management processor 130 may remove the abnormal first working node and delete the report information of the abnormal first working node from the first node list.
  • the management processor 130 may add the new first working node and report information of the new first working node into the first node list.
  • the management processor 130 may update the second node list by removing the target second working node and deleting the report information of the target second working node from the second node list.
  • FIG. 7 is a schematic diagram illustrating an exemplary updating of a first node list 710 and a second node list 720 according to some embodiments of the present disclosure.
  • the management processor 130 may determine a grey second working node 1202 from the second node list 720. Then, the management processor 130 may update the first node list 710 by performing the following operations. The management processor 130 may remove the black first working node 1201 and delete the report information of the black first working node 1201 from the first node list 710.
  • the management processor 130 may add the grey second working node 1202 and the report information of the grey second working node 120 into the first node list 710.
  • the management processor 130 may update the second node list 720 by removing the grey second working node 1202 and the report information of the grey second working node 1202 from the second node list 720.
  • the abnormal first working node and the report information of the abnormal first working node may be removed from the first node list and added into a first deleting list.
  • the target second working node and the report information of the target second working node may be removed from the second node list and added into a second deleting list.
  • the management processor 130 may delete the abnormal first working node and the report information of the abnormal first working node from the first deleting list.
  • the management processor 130 may delete the target second working node and the report information of the target second working node form the second deleting list.
  • the management processor 130 may monitor whether the abnormal first working node and the report information of the abnormal first working node are deleted completely.
  • the management processor 130 may also monitor whether the target second working node and the report information of the target second working node are deleted completely.
  • operations 520-550 may be performed in any sequence or simultaneously.
  • the management processor 130 may obtain the latest first node list and/or the latest second node list, and perform the operation based on the latest first node list and/or the latest second node list.
  • operations of the process 500 may be performed multiple times. For example, operations 510 and 520 may be performed each time the main node 110 receives report information from a working node. As another example, operations 540 and 550 may be performed each time the management processor 130 detects an abnormality of a first working node.
  • FIG. 8 is a flowchart illustrating an exemplary process 800 for managing nodes in a cluster system according to some embodiments of the present disclosure.
  • the process 800 may be performed by a management processor 130 independent from the main node.
  • the management processor 130 may obtain information relating to the main node.
  • the information relating to the main node may include an internet protocol (IP) address of the main node, a metadata service state of the main node, a mark indicating that it is a main node, a version number of the main node, or the like, or any combination thereof.
  • the management processor 130 may obtain the information relating to the main node periodically or aperiodically.
  • the management processor 130 may determine whether the main node is abnormal based on the information relating to the main node.
  • the management processor 130 may determine whether the main node is abnormal according to the metadata service state of the main node. In response to determining that the metadata service state of the main node is an abnormal state, the management processor 130 may determine that the main node is abnormal. As another example, the management processor 130 may determine that the main node is abnormal if it haven’t received information from the main node for more than a predetermined period. In response to determining that the main node is abnormal, the management processor 130 may perform operations 830 and 840.
  • the management processor 130 may determine a target first working node that performs the metadata services of the main node in place of the main node.
  • one first working node in the first node list may automatically replace the main node 110 to perform the metadata services of the cluster system 100 according to a preset rule.
  • the management processor 130 may determine the first working node that replaces the main node as the target first working node. For example, when one first working node replaces the main node 110 to perform the metadata services of the cluster system 100, the management processor 130 may update the mark indicating that the first working node is a standby node with a mark indicating that the first working node is a main node.
  • the management processor 130 may determine the target first working node based on the first node list.
  • the management processor 130 may select one first working node from the first node list, and designate the first working node as a new main node (i.e., the target first working node) .
  • the target first working node may be determined based on the load of each first working node, the probability that each first working node is abnormal, or the like, or any combination thereof, which is similar to how the target second working node is selected from the second node list.
  • the management processor 130 may update the first node list and the second node list based on the target first working node.
  • the management processor 130 may update the first node list by performing the following operations.
  • the management processor 130 may remove the target first working node and delete the report information of the target first working node from the first node list.
  • the management processor 130 may determine a reference second working node from the second node list. In some embodiments, the determination of the reference second working node may be performed in a similar manner as that of the target second working node, and the descriptions thereof are not repeated here.
  • the management processor 130 may designate the reference second node as a new first working node, and add the new first working node and the report information of the new first working node into the first node list.
  • the management processor 130 may update the second node list by removing the reference second working node and deleting the report information of the reference second working node from the second node list.
  • FIG. 9 is a schematic diagram illustrating an exemplary updating of a first node list 910 and a second node list 920 according to some embodiments of the present disclosure.
  • the management processor 130 may determine a black first working node 1201 in the first node list 910 that performs the metadata services of the main node 110 in place of the main node 110.
  • the management processor 130 may update the first node list 910 by performing the following operations.
  • the management processor 130 may remove the black first working node 1201 and delete the report information of the black first working node 1201 from the first node list 910.
  • the management processor 130 may determine a gray second working node 1202 from the second node list 920.
  • the management processor 130 may add the gray second working node 1202 and the report information of the gray second working node 1202 into the first node list 910.
  • the management processor 130 may update the second node list 920 by removing the gray second working node 1202 and deleting the report information of the gray second working node 1202 from the second node list 920.
  • the availability of metadata services depends on a number of standby nodes that can be used to replace the main node to provide metadata services.
  • the availability of metadata services depends not only on the number of standby nodes (i.e., the first working nodes) but also on the number of the second working nodes, and the maximum availability of the metadata services of the cluster system may be determined based on a sum of the number of the first working nodes and the number of the second working nodes.
  • the present systems and methods may greatly improve the availability of metadata services.
  • aspects of the present disclosure may be illustrated and described herein in any of a number of patentable classes or context including any new and useful process, machine, manufacture, or composition of matter, or any new and useful improvement thereof. Accordingly, aspects of the present disclosure may be implemented entirely hardware, entirely software (including firmware, resident software, micro-code, etc. ) or combining software and hardware implementation that may all generally be referred to herein as a “unit, ” “module, ” or “system. ” Furthermore, aspects of the present disclosure may take the form of a computer program product embodied in one or more computer readable media having computer readable program code embodied thereon.
  • a computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of carrier wave. Such a propagated signal may take any of a variety of forms, including electro-magnetic, optical, or the like, or any suitable combination thereof.
  • a computer readable signal medium may be any computer readable medium that is not a computer readable storage medium and that may communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.
  • Program code embodied on a computer readable signal medium may be transmitted using any appropriate medium, including wireless, wireline, optical fiber cable, RF, or the like, or any suitable combination of the foregoing.
  • Computer program code for carrying out operations for aspects of the present disclosure may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Scala, Smalltalk, Eiffel, JADE, Emerald, C++, C#, VB. NET, Python or the like, conventional procedural programming languages, such as the “C” programming language, Visual Basic, Fortran 2103, Perl, COBOL 2102, PHP, ABAP, dynamic programming languages such as Python, Ruby and Groovy, or other programming languages.
  • the program code may execute entirely on the user’s computer, partly on the user’s computer, as a stand-alone software package, partly on the user’s computer and partly on a remote computer or entirely on the remote computer or server.
  • the remote computer may be connected to the user’s computer through any type of network, including a local area network (LAN) or a wide area network (WAN) , or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider) or in a cloud computing environment or offered as a service such as a Software as a Service (SaaS) .
  • LAN local area network
  • WAN wide area network
  • SaaS Software as a Service
  • the numbers expressing quantities or properties used to describe and claim certain embodiments of the application are to be understood as being modified in some instances by the term “about, ” “approximate, ” or “substantially. ”
  • “about, ” “approximate, ” or “substantially” may indicate ⁇ 1%, ⁇ 5%, ⁇ 10%, or ⁇ 20%variation of the value it describes, unless otherwise stated.
  • the numerical parameters set forth in the written description and attached claims are approximations that may vary depending upon the desired properties sought to be obtained by a particular embodiment.
  • the numerical parameters should be construed in light of the number of reported significant digits and by applying ordinary rounding techniques. Notwithstanding that the numerical ranges and parameters setting forth the broad scope of some embodiments of the application are approximations, the numerical values set forth in the specific examples are reported as precisely as practicable.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Human Computer Interaction (AREA)
  • Quality & Reliability (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Hardware Redundancy (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

Un système de grappe peut être fourni. Le système de grappe peut comprendre un processeur de gestion, un nœud principal configuré pour fournir des services de métadonnées, et des nœuds de travail étant connectés en communication au nœud principal et configurés pour envoyer des informations de rapport au nœud principal. Le processeur de gestion peut être configuré pour mettre à jour une première liste de nœuds concernant le ou les premiers nœuds de travail configurés pour une sauvegarde de métadonnées et une seconde liste de nœuds relative à un ou plusieurs seconds nœuds de travail autres que le ou les premiers nœuds de travail sur la base des informations de rapport de chaque nœud de travail. En réponse à la détection du fait qu'un nœud parmi le ou les premiers nœuds de travail est anormal, le processeur de gestion peut déterminer un second nœud de travail cible à partir de la seconde liste de nœuds et mettre à jour la première liste de nœuds et la seconde liste de nœuds sur la base du second nœud de travail cible.
EP23845631.3A 2022-07-27 2023-07-27 Système et procédés pour services de métadonnées Pending EP4548191A4 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202210891870.7A CN115268785A (zh) 2022-07-27 2022-07-27 一种应用于分布式存储系统的管理方法、装置及存储介质
PCT/CN2023/109498 WO2024022424A1 (fr) 2022-07-27 2023-07-27 Système et procédés pour services de métadonnées

Publications (2)

Publication Number Publication Date
EP4548191A1 true EP4548191A1 (fr) 2025-05-07
EP4548191A4 EP4548191A4 (fr) 2026-02-25

Family

ID=83770624

Family Applications (1)

Application Number Title Priority Date Filing Date
EP23845631.3A Pending EP4548191A4 (fr) 2022-07-27 2023-07-27 Système et procédés pour services de métadonnées

Country Status (3)

Country Link
EP (1) EP4548191A4 (fr)
CN (1) CN115268785A (fr)
WO (1) WO2024022424A1 (fr)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115268785A (zh) * 2022-07-27 2022-11-01 浙江大华技术股份有限公司 一种应用于分布式存储系统的管理方法、装置及存储介质
CN121128145A (zh) * 2023-07-20 2025-12-12 乐天移动株式会社 标识可接入节点的方法及其实现系统

Family Cites Families (19)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8306951B2 (en) * 2009-09-18 2012-11-06 Oracle International Corporation Automated integrated high availability of the in-memory database cache and the backend enterprise database
US8595184B2 (en) * 2010-05-19 2013-11-26 Microsoft Corporation Scaleable fault-tolerant metadata service
US20130091376A1 (en) * 2011-10-05 2013-04-11 International Business Machines Corporation Self-repairing database system
CN103729436A (zh) * 2013-12-27 2014-04-16 中国科学院信息工程研究所 一种分布式元数据管理方法及系统
CN104283948B (zh) * 2014-09-26 2018-12-07 东软集团股份有限公司 服务器集群系统及其负载均衡实现方法
CN107211003B (zh) * 2015-12-31 2020-07-14 华为技术有限公司 分布式存储系统及管理元数据的方法
CN105975212A (zh) * 2016-04-29 2016-09-28 深圳市永兴元科技有限公司 分布式数据系统失效检测处理方法及装置
CN105912446A (zh) * 2016-04-29 2016-08-31 深圳市永兴元科技有限公司 分布式数据系统失效检测处理方法及装置
CN106331098B (zh) * 2016-08-23 2020-01-21 东方网力科技股份有限公司 一种服务器集群系统
CN110166271B (zh) * 2018-02-14 2023-05-30 北京京东尚科信息技术有限公司 一种检测网络节点异常的方法和装置
CN110633168A (zh) * 2018-06-22 2019-12-31 北京东土科技股份有限公司 一种分布式存储系统的数据备份方法和系统
US10845991B2 (en) * 2018-12-03 2020-11-24 EMC IP Holding Company LLC Shallow memory table for data storage service
CN111464574B (zh) * 2019-01-21 2022-10-21 阿里巴巴集团控股有限公司 调用、加载、注册、管理方法和路由、服务器、节点和介质
US10812320B2 (en) * 2019-03-01 2020-10-20 At&T Intellectual Property I, L.P. Facilitation of disaster recovery protection for a master softswitch
CN111666035B (zh) * 2019-03-05 2023-06-20 阿里巴巴集团控股有限公司 一种分布式存储系统的管理方法及装置
CN112463448B (zh) * 2020-11-27 2022-06-07 苏州浪潮智能科技有限公司 分布式集群数据库同步方法、装置、设备及存储介质
CN112190924A (zh) * 2020-12-04 2021-01-08 腾讯科技（深圳）有限公司 一种数据容灾方法、装置及计算机可读介质
CN114070739B (zh) * 2021-11-11 2024-01-26 杭州和利时自动化有限公司 一种集群部署方法、装置、设备和计算机可读存储介质
CN115268785A (zh) * 2022-07-27 2022-11-01 浙江大华技术股份有限公司 一种应用于分布式存储系统的管理方法、装置及存储介质

Also Published As

Publication number Publication date
CN115268785A (zh) 2022-11-01
WO2024022424A1 (fr) 2024-02-01
EP4548191A4 (fr) 2026-02-25

Similar Documents

Publication Publication Date Title
US11157380B2 (en) Device temperature impact management using machine learning techniques
US8219575B2 (en) Method and system for specifying, preparing and using parameterized database queries
US9886266B2 (en) Updating software based on utilized functions
WO2024022424A1 (fr) Système et procédés pour services de métadonnées
US20230236923A1 (en) Machine learning assisted remediation of networked computing failure patterns
CN111694638B (zh) 规则包加载方法、规则包执行方法及终端设备
CN110574338A (zh) 根本原因发现引擎
US11263093B2 (en) Method, device and computer program product for job management
US10372572B1 (en) Prediction model testing framework
US9134975B1 (en) Determining which computer programs are candidates to be recompiled after application of updates to a compiler
US12524531B2 (en) Continual learning approach for threat detection in zero-trust architectures
US20250141952A1 (en) Intelligently generating and deploying a metric blocklist within a distributed computing system to efficiently manage data metric requests
US20230384750A1 (en) Efficient controller data generation and extraction
CN115373822A (zh) 任务调度方法、任务处理方法、装置、电子设备和介质
EP4363970A1 (fr) Procédé et système de gouvernance de ressources dans un système multilocataire
US11216427B2 (en) Method, electronic device and computer-readable medium for managing metadata
CN113656797B (zh) 行为特征提取方法以及行为特征提取装置
US12153647B2 (en) Scalable capacity forecasting in storage systems using a machine learning model
US10540828B2 (en) Generating estimates of failure risk for a vehicular component in situations of high-dimensional and low sample size data
US11347533B2 (en) Enhanced virtual machine image management system
US11662937B2 (en) Copying data based on overwritten probabilities
US20230177351A1 (en) Accelerating decision tree inferences based on tensor operations
US20200125350A1 (en) Operational file management and storage
US11513862B2 (en) System and method for state management of devices
US20220207388A1 (en) Automatically generating conditional instructions for resolving predicted system issues using machine learning techniques

Legal Events

Date Code Title Description
STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE INTERNATIONAL PUBLICATION HAS BEEN MADE

PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE

17P Request for examination filed

Effective date: 20250130

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC ME MK MT NL NO PL PT RO RS SE SI SK SM TR

RIC1 Information provided on ipc code assigned before grant

Ipc: G06F 3/06 20060101AFI20250904BHEP

Ipc: G06F 11/20 20060101ALI20250904BHEP

Ipc: G06F 11/30 20060101ALI20250904BHEP

DAV Request for validation of the european patent (deleted)
DAX Request for extension of the european patent (deleted)
A4 Supplementary search report drawn up and despatched

Effective date: 20260123

RIC1 Information provided on ipc code assigned before grant

Ipc: G06F 3/06 20060101AFI20260119BHEP

Ipc: G06F 11/20 20060101ALI20260119BHEP

Ipc: G06F 11/30 20060101ALI20260119BHEP