WO2018024139A1 - 硬盘管理方法和系统 - Google Patents

硬盘管理方法和系统 Download PDF

Info

Publication number
WO2018024139A1
WO2018024139A1 PCT/CN2017/094488 CN2017094488W WO2018024139A1 WO 2018024139 A1 WO2018024139 A1 WO 2018024139A1 CN 2017094488 W CN2017094488 W CN 2017094488W WO 2018024139 A1 WO2018024139 A1 WO 2018024139A1
Authority
WO
WIPO (PCT)
Prior art keywords
hard disk
server
target
request
managed
Prior art date
Application number
PCT/CN2017/094488
Other languages
English (en)
French (fr)
Inventor
陈伟
汪渭春
林起芊
Original Assignee
杭州海康威视数字技术股份有限公司
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 杭州海康威视数字技术股份有限公司 filed Critical 杭州海康威视数字技术股份有限公司
Priority to EP17836321.4A priority Critical patent/EP3493072A4/en
Priority to US16/322,201 priority patent/US10802716B2/en
Publication of WO2018024139A1 publication Critical patent/WO2018024139A1/zh

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR 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/3034—Monitoring arrangements specially adapted to the computing system or computing system component being monitored where the computing system component is a storage system, e.g. DASD based or network based
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR 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/0604—Improving or facilitating administration, e.g. storage management
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/10—File systems; File servers
    • G06F16/11—File system administration, e.g. details of archiving or snapshots
    • G06F16/122—File system administration, e.g. details of archiving or snapshots using management policies
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/10—File systems; File servers
    • G06F16/17—Details of further file system functions
    • G06F16/176—Support for shared access to files; File sharing support
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR 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/0653—Monitoring storage devices or systems
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR 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/0655—Vertical data movement, i.e. input-output transfer; data movement between one or more hosts and one or more storage devices
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR 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/0671—In-line storage system
    • G06F3/0673—Single storage device
    • G06F3/0674—Disk device
    • G06F3/0676—Magnetic disk device

Definitions

  • the present application relates to the field of monitoring, and in particular to a hard disk management method and system.
  • the client is from the IP.
  • the network performs data reading and writing.
  • the IP network contains multiple object hard disks (the target hard disk 1 and the target hard disk 2 to the target hard disk n are shown in FIG. 1), and the management server MDS (Metadata Service, also known as the metadata server) needs to be managed/ Allocate multiple object hard disks, so that there are more disks to be managed for the management server with the central node.
  • the host side such as the management server MDS
  • the host side needs real-time query, which increases the burden on the management server.
  • the embodiment of the present application provides a hard disk management method and system to at least manage the burden of the server.
  • a hard disk management system comprising: at least one object server, configured to send a first request to a management server, wherein the first request is used to request acquisition of object hard disk information; And after receiving the first request, acquiring object hard disk information corresponding to the object server, and sending the object hard disk information to the object server; the object server is further configured to monitor and manage the object hard disk group pointed to by the object hard disk information.
  • the object disk group includes a plurality of object hard disks
  • the object server includes: a first monitoring unit, configured to monitor an working state of the object hard disk, and report the working state of the object hard disk to the management server; the management unit is configured to receive Determining multiple object hard disks for performing reads when reading and writing requests Write the target hard disk of the request.
  • the management unit is specifically configured to: record the remaining capacity of each object hard disk managed by the object server; and determine the target hard disk with the largest remaining capacity among the plurality of object hard disks managed by the object server as the target object when receiving the read/write request hard disk.
  • the management unit is specifically configured to: record the number of executions of each object hard disk managed by the object server; and determine the target hard disk with the least number of execution times of the plurality of object hard disks managed by the object server as the target object when receiving the read/write request hard disk.
  • the management server includes: a second monitoring unit, configured to monitor an working state of the object server, and, when detecting that the object server is faulty, allocate the object hard disk managed by the object server to another object server for hosting.
  • a second monitoring unit configured to monitor an working state of the object server, and, when detecting that the object server is faulty, allocate the object hard disk managed by the object server to another object server for hosting.
  • a method for managing a hard disk comprising: acquiring a first request, wherein the first request is for requesting acquisition of object hard disk information; and after receiving the first request, acquiring the first request Corresponding object hard disk information; monitoring and managing the object hard disk group pointed to by the object hard disk information through the object server.
  • the target disk group includes a plurality of object disks
  • the object disk group pointed to by the object server monitoring and managing the object disk information includes: monitoring the working state of the object hard disk, and reporting the working state of the object hard disk to the management server; When a read/write request is made, the target object hard disk for executing the read/write request in the plurality of object hard disks is determined.
  • determining a target object hard disk for performing a read/write request in the plurality of object hard disks includes: recording a remaining capacity of each object hard disk managed by the object server; and receiving multiple objects managed by the object server when receiving the read/write request The target hard disk with the largest remaining capacity on the hard disk is determined as the target object hard disk.
  • determining a target object hard disk for performing a read/write request in the plurality of object hard disks includes: performing a number of execution times of each object hard disk managed by the object server; and receiving multiple objects managed by the object server when receiving the read/write request The target hard disk with the least number of executions on the hard disk is determined as the target object hard disk.
  • the method further includes: monitoring an operating state of the object server, and assigning an object hard disk managed by the object server when detecting that the object server is faulty Host other object servers.
  • an embodiment of the present application provides an electronic device, including a processor, and a memory, where the memory is used to store a computer program;
  • the hard disk management method provided by the embodiment of the present application is implemented when the processor is configured to execute a computer program stored in the memory.
  • the embodiment of the present application provides a computer program, which is used to execute the hard disk management method provided by the embodiment of the present application.
  • the embodiment of the present application provides a storage medium for storing a computer program, and the computer program is executed to execute the hard disk management method provided by the embodiment of the present application.
  • the at least one object server is configured to send a first request to the management server, where the first request is used to request acquisition of the target hard disk information, and the management server is configured to acquire the target server after receiving the first request.
  • Corresponding object hard disk information, and the object hard disk information is sent to the object server; the object server is also used to monitor and manage the object hard disk group pointed to by the object hard disk information.
  • the object hard disk can be managed and monitored by at least one object server, and the object hard disk managed by the object server is allocated by the management server, thereby reducing the burden on the management server and solving the problem of heavy burden on the management server in the related art.
  • FIG. 1 is an architectural diagram of a hard disk management system in the related art
  • FIG. 2 is a schematic diagram of a hard disk management system according to an embodiment of the present application.
  • FIG. 3 is a block diagram of a hard disk management system according to an embodiment of the present application.
  • FIG. 4 is a block diagram of another hard disk management system according to an embodiment of the present application.
  • FIG. 5 is a flowchart of a method for managing a hard disk according to an embodiment of the present application.
  • a method embodiment of a hard disk management method is provided. It should be noted that the steps shown in the flowchart of the accompanying drawings may be executed in a computer system such as a set of computer executable instructions, and Although a logical order is shown in the flowcharts, in some cases the steps shown or described may be performed in a different order than the ones described herein.
  • IP Network Interconnection Protocol
  • the hard disk uses simple and universal IP Ethernet technology to transfer data to and from the host.
  • the IP interface makes the interconnection between the host and the hard disk simpler. There is almost no distance limitation.
  • the performance bottleneck that is easy to occur in the traditional SAS/SATA interface disappears, and the scalability of the storage system is greatly enhanced.
  • SAS Serial Attached Small Computer System Interface, short for serial connection small computer system interface
  • SATA Serial Advanced Technology Attachment, short for serial advanced technology attachment
  • MDS Management Server
  • Metadata server Also known as a metadata server, it is a server that organizes and manages spatial information.
  • OSD Object Storage Service
  • Load balancing is a collection of servers in a symmetric manner by multiple servers. Each server has an equivalent status and can provide services separately without the assistance of other servers. Through some load sharing technology, externally sent requests are evenly distributed to a server in a symmetric structure, and the server receiving the request independently responds to the client's request. The balanced load distributes client requests evenly to the server array, providing fast access to critical data and addressing a large number of concurrent access services.
  • FIG. 2 is a schematic structural diagram of a hard disk management system according to an embodiment of the present application. As shown in FIG. 2, the system includes the following:
  • the at least one object server 21 is configured to send a first request to the management server, where the first request is used to request acquisition of the object hard disk information, and the management server 23 is configured to acquire the object corresponding to the object server after receiving the first request.
  • the hard disk information is sent to the object server; the object server is also used to monitor and manage the object hard disk group 25 pointed to by the object hard disk information.
  • the object hard disk can be managed and monitored by at least one object server, and the object hard disk managed by the object server is allocated by the management server, thereby reducing the burden on the management server and solving the burden on the management server in the related art. problem.
  • the object hard disk pointed to by the object hard disk information may be one or more, and the one or more object hard disks are the object hard disks allocated by the management server to the object server for management, and are managed and monitored by the object server.
  • the object hard disk can reduce the burden on the management server.
  • the information about the target hard disk of the entire hard disk management system may be saved to the data table in advance, and after receiving the first request, the management server obtains the object hard disk information corresponding to the target server from the pre-saved data table.
  • the data table can record the address information or serial number of the object hard disk to be managed by each object server.
  • the object hard disk group includes a plurality of object hard disks
  • the object server includes: a first monitoring unit, configured to monitor the working state of the object hard disk, and report the working state of the object hard disk to the management server;
  • a first monitoring unit configured to monitor the working state of the object hard disk, and report the working state of the object hard disk to the management server;
  • the object server can detect the working state of the target hard disk in real time, and report the monitored status to the management server.
  • the working state of the target hard disk may be detected in real time, and the working state of the target hard disk may be periodically detected. This application does not limit this.
  • the management unit is specifically configured to: record the remaining capacity of each object hard disk managed by the object server; and receive the read/write request, the object with the largest remaining capacity of the plurality of object hard disks managed by the object server The hard disk is determined as the target object hard disk.
  • the remaining capacity refers to the remaining data capacity of the target hard disk, for example, the remaining size.
  • the data capacity of the target hard disk is 1 G, and the remaining capacity is 500 M.
  • the target server can determine the target object hard disk using the remaining capacity in the target hard disk, and determine the target hard disk with the largest remaining capacity as the target object hard disk, and can reasonably utilize the capacity in the plurality of target hard disks.
  • the management unit is specifically configured to: record the number of executions of each object hard disk managed by the object server; and when the read and write request is received, perform the least number of executions of the plurality of object hard disks managed by the object server The target hard disk is determined as the target object hard disk.
  • the number of executions is the number of times the target hard disk performs read and write operations.
  • the target server can determine the target object hard disk using the number of executions in the target hard disk, and determine the target hard disk with the largest remaining capacity as the target object hard disk, and can balance the load of the plurality of target hard disks.
  • the object server may determine the target object hard disk using the number of executions in the target hard disk, and determine the target hard disk with the least number of executions as the target object hard disk. This can balance the load of multiple object hard disks.
  • the management server includes: a second monitoring unit, configured to monitor the working state of the object server, and when detecting that the object server is faulty, allocate the object hard disk managed by the object server to another object server for hosting.
  • the OSD server that is, the object server described above
  • the purpose is to monitor and manage part of the disk task, and at the same time undertake part of the computing task, specifically, because the object hard disk can be directly connected to the MDS server.
  • the OSD is then connected to the MDS (the management server described above).
  • the MDS the management server described above
  • the OSD waits for the MDS to start the service, it starts to register with the MDS and applies for managing the IP disk. If the MDS finds that there is an OSD registration, the part of the target hard disk is divided into the OSD from the saved IP table, and the offline and offline services of the target hard disk are subsequently performed. And the read and write services are the responsibility of the OSD.
  • the OSD server (that is, the object server described above may be identified as an OSD) is added to the hard disk management system, and the purpose is to monitor and manage some disk tasks in the hard disk management system, and assume Part of the computing task, specifically, the object hard disk is directly connected to the MDS server (ie, the above-mentioned management server, which can be identified as MDS).
  • the object hard disk can be connected to the OSD first, and the OSD is connected to the OSD.
  • MDS the above management server. After the OSD waits for the MDS to start the service, it starts to register with the MDS and applies for managing the IP disk.
  • the MDS sends the relevant OSD registration, and then part of the target hard disk is divided into the OSD from the saved IP table, and the offline and offline services of the target hard disk are subsequently performed. And the read and write services are the responsibility of the OSD.
  • the OSD After the OSD obtains the IP address list, it will manage the obtained target hard disk and ping the IP address in real time. If the ping fails, the OSD reports the corresponding target hard disk information to the MDS.
  • the OSD After the OSD obtains the IP list, it will manage the obtained object hard disk.
  • the OSD can use the ping command to check whether the connection (network) status of the target hard disk is normal. If the ping fails, the connection status of the target hard disk is detected. If the OSD is normal, the OSD needs to report the corresponding target hard disk information (that is, the target hard disk information of the target hard disk whose connection status is abnormal) to the MDS.
  • the MDS only needs to monitor the load condition of the OSD and allocate the OSD, and the operation of reading and writing and selecting the target hard disk is performed through the OSD.
  • the OSD in the foregoing embodiment may periodically apply to the MDS to manage the disk IP list (that is, the object hard disk information mentioned above), and periodically report the status of the management target hard disk to the MDS (for example, offline or online state); Write must be managed by the OSD to write to the corresponding object hard disk.
  • Other OSDs do not have permission to read and write object hard disks that are not managed by themselves.
  • the target hard disk under the OSD cannot be made. For example, we use the global visibility of the target hard disk.
  • the MDS will assign the unmanaged IP to another OSD for hosting. It is monitored and reported by another OSD and assigned read and write permissions.
  • the embodiment of the present application can utilize the global visibility of the target hard disk.
  • the MDS can allocate the IP disk (ie, the target hard disk) under the faulty OSD management to the OSD except the fault.
  • the other non-faulty OSDs are hosted by the above-mentioned other unbroken OSDs, and the IP disks under the above-mentioned failed OSD management are managed, and the IP disks under the above-mentioned failed OSD management are monitored and managed.
  • the other non-faulty OSDs have read and write permissions to the assigned IP disk under the faulty OSD management.
  • the target hard disk cannot report capacity, load status, and online and offline information, we use the convention to implement a load balancing policy: the target hard disk can only be read and written by the managed OSD server.
  • the amount of data written to the target hard disk is recorded by the OSD to obtain the remaining capacity of the target hard disk.
  • an object hard disk is connected to only one OSD server, and the OSD server counts the reading and writing of the same object hard disk, and any reading and writing operation will increase the counting; when the operation is completed, the counting will be reduced; further, when selecting the disk, according to The capacity is prioritized, and the way of counting is judged at the same time, and the method is selected in such a manner that the counting is the least and the pressure is the smallest.
  • a hard disk management method is provided. As shown in FIG. 5, the method can be implemented by the following steps:
  • Step S501 Acquire a first request, where the first request is used to request to acquire object hard disk information;
  • Step S503 After receiving the first request, acquiring object hard disk information corresponding to the first request;
  • Step S505 The object hard disk group pointed to by the object hard disk information is monitored and managed by the object server.
  • the target hard disk can be managed and monitored by at least one object server, and the object hard disk managed by the object server is allocated by the management server, thereby reducing the burden on the management server and solving the problem of heavy burden on the management server in the related art.
  • the object hard disk pointed to by the object hard disk information may be one or more, and the one or more object hard disks are the object hard disks allocated by the management server to the object server for management, and are managed and monitored by the object server.
  • the object hard disk can reduce the burden on the management server.
  • the data table may be pre-stored, and the information of the target hard disk of the entire hard disk management system is recorded in the data table.
  • the management server After receiving the first request, the management server obtains the object hard disk information corresponding to the target server from the pre-saved data table.
  • the target disk group includes a plurality of object disks
  • the object disk group pointed to by the object server monitoring and managing the object disk information includes: monitoring the working state of the object hard disk, and reporting the working state of the object hard disk to the management server; When a read/write request is made, the target object hard disk for executing the read/write request in the plurality of object hard disks is determined.
  • the object server can detect the working state of the target hard disk in real time, and report the monitored status to the management server.
  • the working state of the target hard disk may be detected in real time, and the working state of the target hard disk may be periodically detected. This application does not limit this.
  • determining a target object hard disk for performing a read/write request in the plurality of object hard disks includes: recording a remaining capacity of each object hard disk managed by the object server; and receiving multiple objects managed by the object server when receiving the read/write request The target hard disk with the largest remaining capacity on the hard disk is determined as the target object hard disk.
  • the remaining capacity refers to the remaining data capacity of the target hard disk, for example, the remaining size.
  • the data capacity of the target hard disk is 1 G, and the remaining capacity is 500 M.
  • the target server can determine the target object hard disk using the remaining capacity in the target hard disk, and determine the target hard disk with the largest remaining capacity as the target object hard disk, and can reasonably utilize the capacity in the plurality of target hard disks.
  • determining a target object hard disk for performing a read/write request in the plurality of object hard disks includes: performing a number of execution times of each object hard disk managed by the object server; and receiving multiple objects managed by the object server when receiving the read/write request The target hard disk with the least number of executions on the hard disk is determined as the target object hard disk.
  • the number of executions is the number of times the target hard disk performs read and write operations.
  • the target server can determine the target object hard disk by using the number of executions in the target hard disk, and determine the target hard disk with the largest remaining capacity as the target object hard disk, and can balance the load of the plurality of target hard disks (such as the IP hard disk).
  • the object server may determine the target object hard disk using the number of executions in the target hard disk, and determine the target hard disk with the least number of executions as the target object hard disk. This can balance the load of multiple object hard disks.
  • the method further includes: monitoring an working state of the object server, and when detecting that the object server is faulty, allocating the object hard disk managed by the object server to another object server for hosting.
  • the embodiment of the present application further provides an electronic device, including a processor and a memory, where the memory is used to store a computer program;
  • the hard disk management method provided by the embodiment of the present application is implemented by the processor, where the hard disk management method may include the following steps:
  • the object disk group pointed to by the object server is monitored and managed by the object server.
  • the processor of the electronic device runs the computer program stored in the memory to perform the hard disk management method provided by the embodiment of the present application, thereby reducing the burden on the management server and solving the management server in the related art. A heavy burden.
  • the electronic device performs the process of implementing the object hard disk group including a plurality of object hard disks, and monitoring, by the object server, the object hard disk group pointed to by the object hard disk information, where the electronic device is specifically configured to:
  • the electronic device is configured to implement the process of determining the target object hard disk used to execute the read/write request in the plurality of object hard disks, specifically:
  • the target hard disk having the largest remaining capacity among the plurality of target hard disks managed by the object server is determined as the target object hard disk.
  • the electronic device is configured to implement the process of determining the target object hard disk used to execute the read/write request in the plurality of object hard disks, specifically:
  • the target hard disk having the least number of executions among the plurality of target hard disks managed by the object server is determined as the target object hard disk.
  • the electronic device is further configured to:
  • the working state of the object server is monitored, and when it is detected that the object server is faulty, the object hard disk managed by the object server is allocated to another object server for hosting.
  • the embodiment of the present application further provides a computer program, which is used to execute the hard disk management method provided by the embodiment of the present application, wherein the hard disk management method may include the following steps:
  • the object disk group pointed to by the object server is monitored and managed by the object server.
  • the computer program can execute the hard disk management method provided by the embodiment of the present application at the time of running, thereby reducing the burden on the management server and solving the problem of heavy burden on the management server in the related art.
  • the computer program is configured to be executed to execute the process that the target disk group includes a plurality of object disks, and the object server monitors and manages the object disk group pointed to by the object disk information, specifically:
  • Upon receiving the read/write request determining a target object hard disk for executing the read/write request among the plurality of object hard disks.
  • the computer program is configured to be executed to perform the process of determining a target object hard disk for executing the read/write request in the plurality of object hard disks, specifically:
  • the target hard disk having the largest remaining capacity among the plurality of target hard disks managed by the object server is determined as the target object hard disk.
  • the computer program is configured to be executed to perform the process of determining a target object hard disk for executing the read/write request in the plurality of object hard disks, specifically:
  • the target hard disk having the least number of executions among the plurality of target hard disks managed by the object server is determined as the target object hard disk.
  • the computer program is configured to be executed to perform the obtaining, after obtaining the first request, further for:
  • the working state of the object server is monitored, and when it is detected that the object server is faulty, the object hard disk managed by the object server is allocated to another object server for hosting.
  • the embodiment of the present application provides a storage medium for storing a computer program, and the computer program is executed to perform the hard disk management method provided by the embodiment of the present application.
  • the hard disk management method may include the following steps:
  • the object disk group pointed to by the object server is monitored and managed by the object server.
  • the storage medium stores a computer program that executes the hard disk management method provided by the embodiment of the present application at runtime, so that the burden of the management server can be reduced.
  • the computer program is configured to be executed to execute the process that the target disk group includes a plurality of object disks, and the object server monitors and manages the object disk group pointed to by the object disk information, specifically:
  • Upon receiving the read/write request determining a target object hard disk for executing the read/write request among the plurality of object hard disks.
  • the computer program is configured to be executed to perform the process of determining a target object hard disk for executing the read/write request in the plurality of object hard disks, specifically:
  • the target hard disk having the largest remaining capacity among the plurality of target hard disks managed by the object server is determined as the target object hard disk.
  • the computer program is configured to be executed to perform the process of determining a target object hard disk for executing the read/write request in the plurality of object hard disks, specifically:
  • the target hard disk having the least number of executions among the plurality of target hard disks managed by the object server is determined as the target object hard disk.
  • the computer program is configured to be executed to perform the obtaining, after obtaining the first request, further for:
  • the working state of the object server is monitored, and when it is detected that the object server is faulty, the object hard disk managed by the object server is allocated to another object server for hosting.
  • the disclosed technical content may be It is achieved in other ways.
  • the device embodiments described above are only schematic.
  • the division of the unit may be a logical function division.
  • there may be another division manner for example, multiple units or components may be combined or may be Integrate into another system, or some features can be ignored or not executed.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, unit or module, and may be electrical or otherwise.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • the above integrated unit can be implemented in the form of hardware or in the form of a software functional unit.
  • the integrated unit if implemented in the form of a software functional unit and sold or used as a standalone product, may be stored in a computer readable storage medium.
  • the technical solution of the present application may be embodied in the form of a software product in the form of a software product, or a part of the technical solution, which is stored in a storage medium.
  • a number of instructions are included to cause a computer device (which may be a personal computer, server or network device, etc.) to perform all or part of the steps of the methods described in various embodiments of the present application.
  • the foregoing storage medium includes: a U disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a removable hard disk, a magnetic disk, or an optical disk, and the like. .

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)
  • Data Mining & Analysis (AREA)
  • Databases & Information Systems (AREA)
  • Computing Systems (AREA)
  • Mathematical Physics (AREA)
  • Quality & Reliability (AREA)
  • Debugging And Monitoring (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

本申请公开了一种硬盘管理方法和系统，以至少解决管理服务器的负担重的问题。其中，该系统包括：至少一个对象服务器，用于向管理服务器发送第一请求，其中，第一请求用于请求获取对象硬盘信息；管理服务器，用于在接收到第一请求之后，从保存的数据表中获取与对象服务器对应的对象硬盘信息，并将对象硬盘信息发送至对象服务器；对象服务器还用于监控和管理对象硬盘信息所指向的对象硬盘组。

Description

硬盘管理方法和系统
本申请要求于2016年8月1日提交中国专利局、申请号为201610632372.5发明名称为“硬盘管理方法和系统”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及监控领域，具体而言，涉及一种硬盘管理方法和系统。
背景技术
目前，在采用有中心管理方式管理对象硬盘时，由于对象硬盘的容量有限，在一个大的云存储的系统下，需要的对象硬盘的磁盘量比较大，如图1所示，客户端从IP网络进行数据读写，IP网络中包含多个对象硬盘(图1中示出了对象硬盘1、对象硬盘2至对象硬盘n)，管理服务器MDS(Metadata Service，又称元数据服务器)需要管理/分配多个对象硬盘，这样对于有中心节点的管理服务器，需要管理的磁盘数量较多。且由于对象硬盘无法提供自己的状态信息，需要主机端(如管理服务器MDS)实时查询，这样加重了管理服务器的负担。
针对上述管理服务器的负担重的问题，目前尚未提出有效的解决方案。
发明内容
本申请实施例提供了一种硬盘管理方法和系统，以至少管理服务器的负担重的问题。
根据本申请的一个方面，提供了一种硬盘管理系统，该系统包括：至少一个对象服务器，用于向管理服务器发送第一请求，其中，第一请求用于请求获取对象硬盘信息；管理服务器，用于在接收到第一请求之后，获取与对象服务器对应的对象硬盘信息，并将对象硬盘信息发送至对象服务器；对象服务器还用于监控和管理对象硬盘信息所指向的对象硬盘组。
可选地，对象硬盘组包括多个对象硬盘，对象服务器包括：第一监控单元，用于监测对象硬盘的工作状态，并向管理服务器上报对象硬盘的工作状态；管理单元，用于在接收到读写请求时，确定多个对象硬盘中用于执行读 写请求的目标对象硬盘。
可选地，管理单元具体用于：记录对象服务器管理的各个对象硬盘的剩余容量；在接收到读写请求时，将对象服务器管理的多个对象硬盘中剩余容量最大的对象硬盘确定为目标对象硬盘。
可选地，管理单元具体用于：记录对象服务器管理的各个对象硬盘的执行次数；在接收到读写请求时，将对象服务器管理的多个对象硬盘中执行次数最少的对象硬盘确定为目标对象硬盘。
可选地，管理服务器包括：第二监控单元，用于监控对象服务器的工作状态，并在检测到对象服务器出现故障时，将对象服务器管理的对象硬盘分配给其他对象服务器进行托管。
根据本申请的一个方面，提供了一种硬盘管理方法，该方法包括：获取第一请求，其中，第一请求用于请求获取对象硬盘信息；在接收到第一请求之后，获取与第一请求对应的对象硬盘信息；通过对象服务器监控和管理对象硬盘信息所指向的对象硬盘组。
可选地，对象硬盘组包括多个对象硬盘，通过对象服务器监控和管理对象硬盘信息所指向的对象硬盘组包括：监测对象硬盘的工作状态，并向管理服务器上报对象硬盘的工作状态；在接收到读写请求时，确定多个对象硬盘中用于执行读写请求的目标对象硬盘。
可选地，确定多个对象硬盘中用于执行读写请求的目标对象硬盘包括：记录对象服务器管理的各个对象硬盘的剩余容量；在接收到读写请求时，将对象服务器管理的多个对象硬盘中剩余容量最大的对象硬盘确定为目标对象硬盘。
可选地，确定多个对象硬盘中用于执行读写请求的目标对象硬盘包括：记录对象服务器管理的各个对象硬盘的执行次数；在接收到读写请求时，将对象服务器管理的多个对象硬盘中执行次数最少的对象硬盘确定为目标对象硬盘。
可选地，在获取第一请求之后，方法还包括：监控对象服务器的工作状态，并在检测到对象服务器出现故障时，将对象服务器管理的对象硬盘分配 给其他对象服务器进行托管。
另一方面，本申请实施例提供了一种电子设备，包括处理器、和存储器，其中，存储器，用于存放计算机程序；
处理器，用于执行存储器上所存放的计算机程序时，实现本申请实施例所提供的所述硬盘管理方法。
另一方面，本申请实施例提供了一种计算机程序，所述计算机程序用于被运行以执行本申请实施例所提供的所述硬盘管理方法。
另一方面，本申请实施例提供了一种存储介质，所述存储介质用于存储计算机程序，所述计算机程序被运行以执行本申请实施例所提供的所述硬盘管理方法。
通过上述实施例，至少一个对象服务器，用于向管理服务器发送第一请求，其中，第一请求用于请求获取对象硬盘信息；管理服务器，用于在接收到第一请求之后，获取与对象服务器对应的对象硬盘信息，并将对象硬盘信息发送至对象服务器；对象服务器还用于监控和管理对象硬盘信息所指向的对象硬盘组。通过上述实施例，可以通过至少一个对象服务器管理和监控对象硬盘，并通过管理服务器分配对象服务器管理的对象硬盘，从而减小了管理服务器的负担，解决了相关技术中管理服务器负担重的问题。
附图说明
此处所说明的附图用来提供对本申请的进一步理解，构成本申请的一部分，本申请的示意性实施例及其说明用于解释本申请，并不构成对本申请的不当限定。在附图中：
图1是相关技术中的一种硬盘管理系统的架构图；
图2是根据本申请实施例的一种硬盘管理系统的示意图；
图3是根据本申请实施例的一种硬盘管理系统的架构图；
图4是根据本申请实施例的另一种硬盘管理系统的架构图；
图5是根据本申请实施例的一种硬盘管理方法的流程图。
具体实施方式
为了使本技术领域的人员更好地理解本申请方案，下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例仅仅是本申请一部分的实施例，而不是全部的实施例。基于本申请中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例，都应当属于本申请保护的范围。
需要说明的是，本申请的说明书和权利要求书及上述附图中的术语“第一”、“第二”等是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。应该理解这样使用的数据在适当情况下可以互换，以便这里描述的本申请的实施例能够以除了在这里图示或描述的那些以外的顺序实施。此外，术语“包括”和“具有”以及他们的任何变形，意图在于覆盖不排他的包含，例如，包含了一系列步骤或单元的过程、方法、系统、产品或设备不必限于清楚地列出的那些步骤或单元，而是可包括没有清楚地列出的或对于这些过程、方法、产品或设备固有的其它步骤或单元。
根据本申请实施例，提供了一种硬盘管理方法的方法实施例，需要说明的是，在附图的流程图示出的步骤可以在诸如一组计算机可执行指令的计算机系统中执行，并且，虽然在流程图中示出了逻辑顺序，但是在某些情况下，可以以不同于此处的顺序执行所示出或描述的步骤。
首先，对本申请涉及的术语解释如下：
对象硬盘：即IP(网络互联协议)硬盘，是提供IP协议接口的硬盘，该硬盘采用简单通用的IP以太网技术来和主机之间传递数据。IP接口使得主机和硬盘之间的互联更加简单，几乎没有距离限制，传统SAS/SATA接口容易产生的性能瓶颈也随之消失，存储系统的扩展性也大大增强了，(其中，SAS是Serial Attached Small Computer System Interface，即串行连接小型计算机系统接口的缩写；SATA是Serial Advanced Technology Attachment，即串行高级技术附件的缩写)；由于用户无需再维护单独的存储连接网络，只需要维护一张IP网络，降低了用户的投入。
管理服务器(MDS)：又称为元数据服务器，是用来组织和管理空间信息的服务器。
对象服务器(OSD，Object Storage Service)：对象存储服务器，这里主要用于管理磁盘的上下线任务及部分计算任务。
负载均衡：负载均衡是由多台服务器以对称的方式组成一个服务器集合，每台服务器都具有等价的地位，都可以单独对外提供服务而无须其他服务器的辅助。通过某种负载分担技术，将外部发送来的请求均匀分配到对称结构中的某一台服务器上，而接收到请求的服务器独立地回应客户的请求。均衡负载能够平均分配客户请求到服务器列阵，籍此提供快速获取重要数据，解决大量并发访问服务问题。
图2是根据本申请实施例的硬盘管理系统的架构示意图，如图2所示，该系统包括如下：
至少一个对象服务器21，用于向管理服务器发送第一请求，其中，第一请求用于请求获取对象硬盘信息；管理服务器23，用于在接收到第一请求之后，获取与对象服务器对应的对象硬盘信息，并将对象硬盘信息发送至对象服务器；对象服务器还用于监控和管理对象硬盘信息所指向的对象硬盘组25。
通过本申请上述实施例，可以通过至少一个对象服务器管理和监控对象硬盘，并通过管理服务器分配对象服务器管理的对象硬盘，从而减小了管理服务器的负担，解决了相关技术中管理服务器负担重的问题。
其中，上述实施例中，对象硬盘信息指向的对象硬盘可以是一个或多个，该一个或多个对象硬盘为管理服务器向该对象服务器分配的让其管理的对象硬盘，通过对象服务器管理和监控对象硬盘可以减小管理服务器的负担。
可选地，可以预先将整个硬盘管理系统的对象硬盘的信息保存到数据表中，管理服务器在接收到第一请求之后，从预先保存的数据表中获取与对象服务器对应的对象硬盘信息。该数据表可以记录每个对象服务器要管理的对象硬盘的地址信息或序号等。
根据本申请的上述实施例，对象硬盘组包括多个对象硬盘，对象服务器包括：第一监控单元，用于监测对象硬盘的工作状态，并向管理服务器上报对象硬盘的工作状态；管理单元，用于在接收到读写请求时，确定多个对象硬盘中用于执行读写请求的目标对象硬盘。
其中，对象服务器可以实时检测对象硬盘的工作状态，并将监测到的状态上报至管理服务器。
在上述实施例中，可以实时检测对象硬盘的工作状态，也可以周期性检测对象硬盘的工作状态，本申请对此不做限定。
在一个可选地实施例中，管理单元具体用于：记录对象服务器管理的各个对象硬盘的剩余容量；在接收到读写请求时，将对象服务器管理的多个对象硬盘中剩余容量最大的对象硬盘确定为目标对象硬盘。
其中，剩余容量指对象硬盘的剩余数据容量，如，剩余大小，例如，对象硬盘的数据容量为1G，剩余容量为500M。
在该实施例中，对象服务器可以使用对象硬盘中剩余容量确定目标对象硬盘，将剩余容量最大的对象硬盘确定为目标对象硬盘，可以合理利用多个对象硬盘中的容量。
在另一个可选地实施例中，管理单元具体用于：记录对象服务器管理的各个对象硬盘的执行次数；在接收到读写请求时，将对象服务器管理的多个对象硬盘中执行次数最少的对象硬盘确定为目标对象硬盘。
其中，执行次数为对象硬盘执行读写操作的次数。
在该实施例中，对象服务器可以使用对象硬盘中执行次数确定目标对象硬盘，将剩余容量最大的对象硬盘确定为目标对象硬盘，可以均衡多个对象硬盘的负载。
也就是说，在上述实施例中，对象服务器可以使用对象硬盘中执行次数确定目标对象硬盘，将执行次数最少的对象硬盘确定为目标对象硬盘。以此可以均衡多个对象硬盘的负载。
需要进一步说明的是，管理服务器包括：第二监控单元，用于监控对象服务器的工作状态，并在检测到对象服务器出现故障时，将对象服务器管理的对象硬盘分配给其他对象服务器进行托管。
下面结合图3对上述实施例进行详细描述，如图2所示，该实施例可以通过如下方案实现：
在系统架构中，添加OSD服务器(即上述的对象服务器)，目的是将监控及管理部分的磁盘任务，同时承担部分的计算任务，具体的，因为对象硬盘是可以直接连接到MDS服务器上的，现在连接到OSD上，OSD再连接到MDS(即上述的管理服务器)。其中，OSD等待MDS启动服务后，开始向MDS注册，并申请管理IP磁盘，MDS发现有OSD注册，则从保存的IP表中划分出部分的对象硬盘给OSD，后续该对象硬盘的上下线服务和读写服务由该OSD负责。
也就是说，本申请实施例中，上述硬盘管理系统中，添加有OSD服务器(即上述的对象服务器，可以标识为OSD)，目的是监控及管理上述硬盘管理系统中部分的磁盘任务，同时承担部分的计算任务，具体的，对象硬盘乐意直接连接到MDS服务器(即上述的管理服务器，可以标识为MDS)上，本申请实施例中，可以将对象硬盘先连接到OSD上，OSD再连接到MDS(即上述的管理服务器)。其中，OSD等待MDS启动服务后，开始向MDS注册，并申请管理IP磁盘，MDS发相关OSD注册，则从保存的IP表中划分出部分的对象硬盘给OSD，后续该对象硬盘的上下线服务和读写服务由该OSD负责。
OSD获取到IP列表后，将管理获取到的对象硬盘，实时ping该IP是否正常，如果ping不通，则有OSD上报对应的对象硬盘信息给MDS。
也就是说，OSD获取到IP列表后，将管理获取到的对象硬盘，OSD可以实时通过ping命令检测对象硬盘的连接(网络)状态是否正常，如果ping不通，即检测到对象硬盘的连接状态不正常，则OSD需要上报对应的对象硬盘信息(即连接状态不正常的对象硬盘的对象硬盘信息)给MDS。
在上述实施例中，MDS只需要监控OSD的负载情况并分配OSD，而读写和挑选对象硬盘的操作，通过OSD进行。
上述实施例中的OSD可以定期向MDS申请管理磁盘IP列表(即上述的对象硬盘信息)，并可以定期向MDS上报管理对象硬盘的状态(如，离线或在线状态)；上述实施例中的读写必须通过管理的OSD才能写入对应的对象硬盘，其它OSD没有权限读写不属于自己管理的对象硬盘。
如图4所示，如果OSD出现故障，会导致该OSD下的对象硬盘无法使 用，我们利用对象硬盘的全局可见性，再另一次OSD申请管理磁盘时，会由MDS将失去管理的IP分配给另一个OSD进行托管。由另一个OSD开始监控和上报，并分配有读写权限。
也就是说，如果OSD出现故障，则可能会出现该OSD下的对象硬盘无法使用，的现象。此时，本申请实施例可以利用对象硬盘的全局可见性，在OSD再一次申请管理磁盘时，MDS可以将出现故障的OSD管理下的IP磁盘(即对象硬盘)分配给除该故障的OSD外的其他未故障OSD，由上述其他未故障OSD对所分配到的上述出现故障的OSD管理下的IP磁盘进行托管，对上述所分配到的上述出现故障的OSD管理下的IP磁盘进行监控和管理，上述其他未故障OSD对所分配到的上述出现故障的OSD管理下的IP磁盘具有读写权限。
进一步地需要说明的是，由于对象硬盘无法上报容量，负载情况，上下线信息，我们利用约定进行负载均衡策略：对象硬盘只能由管理的OSD服务器进行读写。
具体地，由OSD记录写入对象硬盘的数据量，得到对象硬盘的剩余容量。其中，一个对象硬盘只连接一个OSD服务器，该OSD服务器对同一个对象硬盘的读写建立计数，任何读写操作都会使计数增加；操作完成则计数会减少；进一步地，在挑选磁盘时，按照容量优先，同时判断计数的方式，以计数最少则压力最小的方式进行挑选。
根据本申请的一个方面，提供了一种硬盘管理方法，如图5所示，该方法可以通过如下步骤实现：
步骤S501：获取第一请求，其中，第一请求用于请求获取对象硬盘信息；
步骤S503:在接收到第一请求之后，获取与第一请求对应的对象硬盘信息；
步骤S505:通过对象服务器监控和管理对象硬盘信息所指向的对象硬盘组。
在上述实施例中，可以通过至少一个对象服务器管理和监控对象硬盘，并通过管理服务器分配对象服务器管理的对象硬盘，从而减小了管理服务器的负担，解决了相关技术中管理服务器负担重的问题。
其中，上述实施例中，对象硬盘信息指向的对象硬盘可以是一个或多个，该一个或多个对象硬盘为管理服务器向该对象服务器分配的让其管理的对象硬盘，通过对象服务器管理和监控对象硬盘可以减小管理服务器的负担。
可以预先保存数据表，该数据表中记录有整个硬盘管理系统的对象硬盘的信息，管理服务器在接收到第一请求之后，从预先保存的数据表中获取与对象服务器对应的对象硬盘信息。
可选地，对象硬盘组包括多个对象硬盘，通过对象服务器监控和管理对象硬盘信息所指向的对象硬盘组包括：监测对象硬盘的工作状态，并向管理服务器上报对象硬盘的工作状态；在接收到读写请求时，确定多个对象硬盘中用于执行读写请求的目标对象硬盘。
其中，对象服务器可以实时检测对象硬盘的工作状态，并将监测到的状态上报至管理服务器。
在上述实施例中，可以实时检测对象硬盘的工作状态，也可以周期性检测对象硬盘的工作状态，本申请对此不做限定。
可选地，确定多个对象硬盘中用于执行读写请求的目标对象硬盘包括：记录对象服务器管理的各个对象硬盘的剩余容量；在接收到读写请求时，将对象服务器管理的多个对象硬盘中剩余容量最大的对象硬盘确定为目标对象硬盘。
其中，剩余容量指对象硬盘的剩余数据容量，如，剩余大小，例如，对象硬盘的数据容量为1G，剩余容量为500M。
在该实施例中，对象服务器可以使用对象硬盘中剩余容量确定目标对象硬盘，将剩余容量最大的对象硬盘确定为目标对象硬盘，可以合理利用多个对象硬盘中的容量。
可选地，确定多个对象硬盘中用于执行读写请求的目标对象硬盘包括：记录对象服务器管理的各个对象硬盘的执行次数；在接收到读写请求时，将对象服务器管理的多个对象硬盘中执行次数最少的对象硬盘确定为目标对象硬盘。
其中，执行次数为对象硬盘执行读写操作的次数。
在该实施例中，对象服务器可以使用对象硬盘中执行次数确定目标对象硬盘，将剩余容量最大的对象硬盘确定为目标对象硬盘，可以均衡多个对象硬盘(如IP硬盘)的负载。
也就是说，在上述实施例中，对象服务器可以使用对象硬盘中执行次数确定目标对象硬盘，将执行次数最少的对象硬盘确定为目标对象硬盘。以此可以均衡多个对象硬盘的负载。
可选地，在获取第一请求之后，方法还包括：监控对象服务器的工作状态，并在检测到对象服务器出现故障时，将对象服务器管理的对象硬盘分配给其他对象服务器进行托管。
本申请实施例还提供了一种电子设备，包括处理器和存储器，其中，存储器，用于存放计算机程序；
处理器，用于执行存储器上所存放的计算机程序时，实现本申请实施例所提供的硬盘管理方法，其中，该硬盘管理方法可以包括步骤：
获取第一请求，其中，第一请求用于请求获取对象硬盘信息；
在接收到第一请求之后，获取与第一请求对应的对象硬盘信息；
通过对象服务器监控和管理对象硬盘信息所指向的对象硬盘组。
应用本申请实施例，该电子设备的处理器运行存储器中存储的计算机程序，以执行本申请实施例所提供的硬盘管理方法，因此能够实现：减小管理服务器的负担，解决相关技术中管理服务器负担重的问题。
可选地，所述电子设备在执行实现所述对象硬盘组包括多个对象硬盘，通过对象服务器监控和管理对象硬盘信息所指向的对象硬盘组的过程，具体用于：
监测所述对象硬盘的工作状态，并向管理服务器上报所述对象硬盘的工作状态；
在接收到读写请求时，确定所述多个对象硬盘中用于执行所述读写请求 的目标对象硬盘。
可选地，所述电子设备在执行实现所述确定所述多个对象硬盘中用于执行所述读写请求的目标对象硬盘的过程，具体用于：
记录所述对象服务器管理的各个对象硬盘的剩余容量；
在接收到所述读写请求时，将所述对象服务器管理的多个对象硬盘中剩余容量最大的对象硬盘确定为所述目标对象硬盘。
可选地，所述电子设备在执行实现所述确定所述多个对象硬盘中用于执行所述读写请求的目标对象硬盘的过程，具体用于：
记录所述对象服务器管理的各个对象硬盘的执行次数；
在接收到所述读写请求时，将所述对象服务器管理的多个对象硬盘中执行次数最少的对象硬盘确定为所述目标对象硬盘。
可选地，所述电子设备在所述在获取第一请求之后，还用于：
监控对象服务器的工作状态，并在检测到所述对象服务器出现故障时，将所述对象服务器管理的对象硬盘分配给其他对象服务器进行托管。
本申请实施例还提供了一种计算机程序，所述计算机程序用于被运行以执行本申请实施例所提供的硬盘管理方法，其中，硬盘管理方法可以包括步骤：
获取第一请求，其中，第一请求用于请求获取对象硬盘信息；
在接收到第一请求之后，获取与第一请求对应的对象硬盘信息；
通过对象服务器监控和管理对象硬盘信息所指向的对象硬盘组。
应用本申请实施例，可计算机程序在运行时执行本申请实施例所提供的硬盘管理方法，因此能够实现：减小管理服务器的负担，解决相关技术中管理服务器负担重的问题。
可选地，所述计算机程序用于被运行以执行所述对象硬盘组包括多个对象硬盘，通过对象服务器监控和管理对象硬盘信息所指向的对象硬盘组的过程，具体用于：
监测所述对象硬盘的工作状态，并向管理服务器上报所述对象硬盘的工作状态；
在接收到读写请求时，确定所述多个对象硬盘中用于执行所述读写请求的目标对象硬盘。
可选地，所述计算机程序用于被运行以执行所述确定所述多个对象硬盘中用于执行所述读写请求的目标对象硬盘的过程，具体用于：
记录所述对象服务器管理的各个对象硬盘的剩余容量；
在接收到所述读写请求时，将所述对象服务器管理的多个对象硬盘中剩余容量最大的对象硬盘确定为所述目标对象硬盘。
可选地，所述计算机程序用于被运行以执行所述确定所述多个对象硬盘中用于执行所述读写请求的目标对象硬盘的过程，具体用于：
记录所述对象服务器管理的各个对象硬盘的执行次数；
在接收到所述读写请求时，将所述对象服务器管理的多个对象硬盘中执行次数最少的对象硬盘确定为所述目标对象硬盘。
可选地，所述计算机程序用于被运行以执行所述在获取第一请求之后，还用于：
监控对象服务器的工作状态，并在检测到所述对象服务器出现故障时，将所述对象服务器管理的对象硬盘分配给其他对象服务器进行托管。
本申请实施例提供了一种存储介质，所述存储介质用于存储计算机程序，所述计算机程序被运行以执行本申请实施例所提供的硬盘管理方法，其中，硬盘管理方法可以包括步骤：
获取第一请求，其中，第一请求用于请求获取对象硬盘信息；
在接收到第一请求之后，获取与第一请求对应的对象硬盘信息；
通过对象服务器监控和管理对象硬盘信息所指向的对象硬盘组。
应用本申请实施例，存储介质存储有在运行时执行本申请实施例所提供的硬盘管理方法的计算机程序，因此能够实现：减小管理服务器的负担，解 决相关技术中管理服务器负担重的问题。
可选地，所述计算机程序用于被运行以执行所述对象硬盘组包括多个对象硬盘，通过对象服务器监控和管理对象硬盘信息所指向的对象硬盘组的过程，具体用于：
监测所述对象硬盘的工作状态，并向管理服务器上报所述对象硬盘的工作状态；
在接收到读写请求时，确定所述多个对象硬盘中用于执行所述读写请求的目标对象硬盘。
可选地，所述计算机程序用于被运行以执行所述确定所述多个对象硬盘中用于执行所述读写请求的目标对象硬盘的过程，具体用于：
记录所述对象服务器管理的各个对象硬盘的剩余容量；
在接收到所述读写请求时，将所述对象服务器管理的多个对象硬盘中剩余容量最大的对象硬盘确定为所述目标对象硬盘。
可选地，所述计算机程序用于被运行以执行所述确定所述多个对象硬盘中用于执行所述读写请求的目标对象硬盘的过程，具体用于：
记录所述对象服务器管理的各个对象硬盘的执行次数；
在接收到所述读写请求时，将所述对象服务器管理的多个对象硬盘中执行次数最少的对象硬盘确定为所述目标对象硬盘。
可选地，所述计算机程序用于被运行以执行所述在获取第一请求之后，还用于：
监控对象服务器的工作状态，并在检测到所述对象服务器出现故障时，将所述对象服务器管理的对象硬盘分配给其他对象服务器进行托管。
上述本申请实施例序号仅仅为了描述，不代表实施例的优劣。
在本申请的上述实施例中，对各个实施例的描述都各有侧重，某个实施例中没有详述的部分，可以参见其他实施例的相关描述。
在本申请所提供的几个实施例中，应该理解到，所揭露的技术内容，可 通过其它的方式实现。其中，以上所描述的装置实施例仅仅是示意性的，例如所述单元的划分，可以为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，单元或模块的间接耦合或通信连接，可以是电性或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。
所述集成的单元如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对相关技术做出贡献的部分或者该技术方案的全部或部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可为个人计算机、服务器或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、只读存储器(ROM，Read-Only Memory)、随机存取存储器(RAM，Random Access Memory)、移动硬盘、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述仅是本申请的优选实施方式，应当指出，对于本技术领域的普通技术人员来说，在不脱离本申请原理的前提下，还可以做出若干改进和润饰，这些改进和润饰也应视为本申请的保护范围。

Claims (13)

  1. 一种硬盘管理系统，其特征在于，包括：
    至少一个对象服务器，用于向管理服务器发送第一请求，其中，所述第一请求用于请求获取对象硬盘信息；
    所述管理服务器，用于在接收到所述第一请求之后，获取与所述对象服务器对应的对象硬盘信息，并将所述对象硬盘信息发送至所述对象服务器；
    所述对象服务器还用于监控和管理所述对象硬盘信息所指向的对象硬盘组。
  2. 根据权利要求1所述的系统，其特征在于，所述对象硬盘组包括多个对象硬盘，所述对象服务器包括：
    第一监控单元，用于监测所述对象硬盘的工作状态，并向所述管理服务器上报所述对象硬盘的工作状态；
    管理单元，用于在接收到读写请求时，确定所述多个对象硬盘中用于执行所述读写请求的目标对象硬盘。
  3. 根据权利要求2所述的系统，其特征在于，所述管理单元具体用于：
    记录所述对象服务器管理的各个对象硬盘的剩余容量；
    在接收到所述读写请求时，将所述对象服务器管理的多个对象硬盘中剩余容量最大的对象硬盘确定为所述目标对象硬盘。
  4. 根据权利要求2所述的系统，其特征在于，所述管理单元具体用于：
    记录所述对象服务器管理的各个对象硬盘的执行次数；
    在接收到所述读写请求时，将所述对象服务器管理的多个对象硬盘中执行次数最少的对象硬盘确定为所述目标对象硬盘。
  5. 根据权利要求1至4中任意一项所述的系统，其特征在于，所述管理服务器包括：
    第二监控单元，用于监控所述对象服务器的工作状态，并在检测到所述对象服务器出现故障时，将所述对象服务器管理的对象硬盘分配给其他对象 服务器进行托管。
  6. 一种硬盘管理方法，其特征在于，包括：
    获取第一请求，其中，所述第一请求用于请求获取对象硬盘信息；
    在接收到所述第一请求之后，获取与所述第一请求对应的对象硬盘信息；
    通过对象服务器监控和管理对象硬盘信息所指向的对象硬盘组。
  7. 根据权利要求6所述的方法，其特征在于，所述对象硬盘组包括多个对象硬盘，通过对象服务器监控和管理对象硬盘信息所指向的对象硬盘组包括：
    监测所述对象硬盘的工作状态，并向管理服务器上报所述对象硬盘的工作状态；
    在接收到读写请求时，确定所述多个对象硬盘中用于执行所述读写请求的目标对象硬盘。
  8. 根据权利要求7所述的方法，其特征在于，确定所述多个对象硬盘中用于执行所述读写请求的目标对象硬盘包括：
    记录所述对象服务器管理的各个对象硬盘的剩余容量；
    在接收到所述读写请求时，将所述对象服务器管理的多个对象硬盘中剩余容量最大的对象硬盘确定为所述目标对象硬盘。
  9. 根据权利要求7所述的方法，其特征在于，确定所述多个对象硬盘中用于执行所述读写请求的目标对象硬盘包括：
    记录所述对象服务器管理的各个对象硬盘的执行次数；
    在接收到所述读写请求时，将所述对象服务器管理的多个对象硬盘中执行次数最少的对象硬盘确定为所述目标对象硬盘。
  10. 根据权利要求6至9中任意一项所述的方法，其特征在于，在获取第一请求之后，所述方法还包括：
    监控对象服务器的工作状态，并在检测到所述对象服务器出现故障时， 将所述对象服务器管理的对象硬盘分配给其他对象服务器进行托管。
  11. 一种电子设备，其特征在于，包括处理器和存储器，其中，存储器，用于存放计算机程序；
    处理器，用于执行存储器上所存放的计算机程序时，实现权利要求6-10任一项所述的硬盘管理方法。
  12. 一种计算机程序，其特征在于，所述计算机程序用于被运行以执行权利要求6-10任一项所述的硬盘管理方法。
  13. 一种存储介质，其特征在于，所述存储介质用于存储计算机程序，所述计算机程序被运行以执行权利要求6-10任一项所述的硬盘管理方法。
PCT/CN2017/094488 2016-08-01 2017-07-26 硬盘管理方法和系统 WO2018024139A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP17836321.4A EP3493072A4 (en) 2016-08-01 2017-07-26 METHOD AND SYSTEM FOR HARD DISK MANAGEMENT
US16/322,201 US10802716B2 (en) 2016-08-01 2017-07-26 Hard disk management method, system, electronic device, and storage medium

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201610632372.5 2016-08-01
CN201610632372.5A CN107678906B (zh) 2016-08-01 2016-08-01 硬盘管理方法和系统

Publications (1)

Publication Number Publication Date
WO2018024139A1 true WO2018024139A1 (zh) 2018-02-08

Family

ID=61072619

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/094488 WO2018024139A1 (zh) 2016-08-01 2017-07-26 硬盘管理方法和系统

Country Status (4)

Country Link
US (1) US10802716B2 (zh)
EP (1) EP3493072A4 (zh)
CN (1) CN107678906B (zh)
WO (1) WO2018024139A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110109790A (zh) * 2019-05-13 2019-08-09 深圳前海微众银行股份有限公司 服务器硬盘管理方法、装置、设备及计算机可读存储介质
CN110674522A (zh) * 2019-09-27 2020-01-10 苏州浪潮智能科技有限公司 硬盘加密方法、装置、服务器、系统及存储介质

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107025066A (zh) 2016-09-14 2017-08-08 阿里巴巴集团控股有限公司 在基于闪存的存储介质中写入存储数据的方法和装置
CN106875018B (zh) * 2017-01-04 2021-03-30 北京百度网讯科技有限公司 一种超大规模机器自动化维修的方法和装置
CN109032893A (zh) * 2018-07-25 2018-12-18 郑州云海信息技术有限公司 一种存储系统电压监测方法及装置

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20130054968A1 (en) * 2011-08-29 2013-02-28 Salesforce.Com Inc. Methods and systems of data security in browser storage
CN103888499A (zh) * 2012-12-21 2014-06-25 中国科学院深圳先进技术研究院 一种分布式对象处理的方法及系统

Family Cites Families (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP4166516B2 (ja) * 2002-06-14 2008-10-15 株式会社日立製作所 ディスクアレイ装置
US7599941B2 (en) * 2005-07-25 2009-10-06 Parascale, Inc. Transparent redirection and load-balancing in a storage network
US9037828B2 (en) * 2006-07-13 2015-05-19 International Business Machines Corporation Transferring storage resources between snapshot storage pools and volume storage pools in a data storage system
US8543761B2 (en) * 2011-04-08 2013-09-24 Lsi Corporation Zero rebuild extensions for raid
US9514014B2 (en) * 2011-08-17 2016-12-06 EMC IP Holding Company, LLC Methods and systems of managing a distributed replica based storage
CN103176884A (zh) * 2011-12-20 2013-06-26 鸿富锦精密工业（深圳）有限公司 硬盘监视系统及方法
US9104560B2 (en) * 2012-06-13 2015-08-11 Caringo, Inc. Two level addressing in storage clusters
US9092441B1 (en) * 2012-08-08 2015-07-28 Amazon Technologies, Inc. Archival data organization and management
CN104750756B (zh) * 2013-12-31 2018-09-04 中国移动通信集团公司 一种数据操作方法、设备及元数据存储设备
CN105100149A (zh) * 2014-05-13 2015-11-25 中国电信股份有限公司 用于管理文件的方法和系统
CN104199621B (zh) * 2014-08-28 2017-09-12 北京汉龙思琪数码科技有限公司 硬盘管理系统
CN107248931A (zh) * 2017-06-06 2017-10-13 安徽赛福贝特信息技术有限公司 一种基于数据云的安防运维管理平台
CN109117342A (zh) * 2018-08-13 2019-01-01 郑州云海信息技术有限公司 一种服务器及其硬盘健康状态监测系统

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20130054968A1 (en) * 2011-08-29 2013-02-28 Salesforce.Com Inc. Methods and systems of data security in browser storage
CN103888499A (zh) * 2012-12-21 2014-06-25 中国科学院深圳先进技术研究院 一种分布式对象处理的方法及系统

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3493072A4

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110109790A (zh) * 2019-05-13 2019-08-09 深圳前海微众银行股份有限公司 服务器硬盘管理方法、装置、设备及计算机可读存储介质
CN110109790B (zh) * 2019-05-13 2023-04-07 深圳前海微众银行股份有限公司 服务器硬盘管理方法、装置、设备及计算机可读存储介质
CN110674522A (zh) * 2019-09-27 2020-01-10 苏州浪潮智能科技有限公司 硬盘加密方法、装置、服务器、系统及存储介质

Also Published As

Publication number Publication date
US20200019313A1 (en) 2020-01-16
EP3493072A1 (en) 2019-06-05
CN107678906B (zh) 2021-01-29
CN107678906A (zh) 2018-02-09
EP3493072A4 (en) 2019-06-05
US10802716B2 (en) 2020-10-13

Similar Documents

Publication Publication Date Title
WO2018024139A1 (zh) 硬盘管理方法和系统
US11115466B2 (en) Distributed network services
US11310286B2 (en) Mechanism for providing external access to a secured networked virtualization environment
US10924436B2 (en) Method and system for managing workloads in a cluster
US9542404B2 (en) Subpartitioning of a namespace region
US10243780B2 (en) Dynamic heartbeating mechanism
US20200042364A1 (en) Movement of services across clusters
US7587492B2 (en) Dynamic performance management for virtual servers
US9887937B2 (en) Distributed fair allocation of shared resources to constituents of a cluster
US20140032753A1 (en) Computer system and node search method
US20150234846A1 (en) Partitioning file system namespace
US11223519B2 (en) Storage system for network information
WO2013019339A1 (en) Hardware failure mitigation
US20170237809A1 (en) Direct access storage device analyzer
US20180364948A1 (en) Data Processing Method, Related Device, and Storage System
WO2018171728A1 (zh) 服务器、存储系统及相关方法
US8667048B2 (en) Method for managing internet protocol addresses in network
US9432476B1 (en) Proxy data storage system monitoring aggregator for a geographically-distributed environment
US20160034548A1 (en) System and Method for Obtaining Automated Scaling of a Virtual Desktop Environment
Salapura et al. Enabling enterprise-class workloads in the cloud
US20230418638A1 (en) Log level management portal for virtual desktop infrastructure (vdi) components
US10116540B1 (en) System, method, and computer program for managing data objects in a multiprocessor unit telecommunications network
Ferreira et al. Performance evaluation of a private cloud storage infrastructure service for document preservation

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 17836321

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2017836321

Country of ref document: EP

Effective date: 20190301