CN109088921B - Write operation processing method and device and computer readable storage medium - Google Patents

Write operation processing method and device and computer readable storage medium Download PDF

Info

Publication number
CN109088921B
CN109088921B CN201810820168.5A CN201810820168A CN109088921B CN 109088921 B CN109088921 B CN 109088921B CN 201810820168 A CN201810820168 A CN 201810820168A CN 109088921 B CN109088921 B CN 109088921B
Authority
CN
China
Prior art keywords
osd
unit
client
write request
write operation
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN201810820168.5A
Other languages
Chinese (zh)
Other versions
CN109088921A (en
Inventor
李彦博
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.)
Guangdong Inspur Smart Computing Technology Co Ltd
Original Assignee
Guangdong Inspur Big Data Research 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 Guangdong Inspur Big Data Research Co Ltd filed Critical Guangdong Inspur Big Data Research Co Ltd
Priority to CN201810820168.5A priority Critical patent/CN109088921B/en
Publication of CN109088921A publication Critical patent/CN109088921A/en
Application granted granted Critical
Publication of CN109088921B publication Critical patent/CN109088921B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/104—Peer-to-peer [P2P] networks
    • H04L67/1044—Group management mechanisms 
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06—Management of faults, events, alarms or notifications
    • H04L41/0631—Management of faults, events, alarms or notifications using root cause analysis; using analysis of correlation between notifications, alarms or events based on decision criteria, e.g. hierarchy, tree or time analysis
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06—Management of faults, events, alarms or notifications
    • H04L41/0654—Management of faults, events, alarms or notifications using network fault recovery
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06—Management of faults, events, alarms or notifications
    • H04L41/069—Management of faults, events, alarms or notifications using logs of notifications; Post-processing of notifications
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • H04L43/0805—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability
    • H04L43/0817—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability by checking functioning
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/56—Provisioning of proxy services
    • H04L67/568—Storing data temporarily at an intermediate stage, e.g. caching
    • H04L67/5681—Pre-fetching or pre-delivering data based on network characteristics

Abstract

The embodiment of the invention discloses a write operation processing method, a write operation processing device and a computer readable storage medium, which are used for receiving data information sent by a client and sending a write request to a target OSD; wherein, the write request carries the encapsulated data information; and judging whether a feedback message sent by the target OSD is received within a preset time. And after receiving the response message about the completion of the write operation, the client side can continue to issue new data information. Therefore, when the feedback message sent by the target OSD is not received within the preset time, in order to not affect the service flow of the client, a response message that the write operation is completed may be sent to the client, so that the client continues to issue the data information. The method effectively ensures that the data of the client is written into the uninterrupted flow, and meets the requirements of the cluster in different application scenes.

Description

Write operation processing method and device and computer readable storage medium
Technical Field
The present invention relates to the field of cluster system technologies, and in particular, to a write operation processing method and apparatus, and a computer-readable storage medium.
Background
The cluster system includes a plurality of nodes, each node often includes a plurality of hard disks, and one hard disk corresponds to one Object-based Storage Device (OSD).
The OSDC is an intermediary through which the OSD interacts with the client. When the cluster runs, the client sends data information to the OSD, the data information is received by the OSDC, and the OSDC packages the data information and then sends the data information to the OSD. After receiving the data information, the OSD processes the data information, for example, sending the data information to a backup OSD or performing a disk-dropping operation on the data information. After the OSD has finished processing the data, a message is sent to the OSDC to inform the OSDC that the write operation is complete. After receiving the message, the OSDC notifies the client of the response message that the operation is completed by calling the callback function, so that the client continues to send new data information to the OSD.
Corresponding to the client, the combination of the OSDC and the OSD may be collectively referred to as an OSD terminal. After the client sends the data information, the client needs to wait for the response of the OSD terminal and then continues to send new data information to the OSD terminal. When the OSD fails, the client cannot receive the response of the OSD terminal, and the client stops sending data information to the OSD terminal, and the data writing is interrupted, so that the client cuts off the service.
Therefore, how to effectively ensure the normal operation of the client service is a problem to be solved by technical personnel in the field.
Disclosure of Invention
The embodiment of the invention aims to provide a write operation processing method, a write operation processing device and a computer readable storage medium, which can effectively ensure the normal operation of a client service.
To solve the foregoing technical problem, an embodiment of the present invention provides a write operation processing method, including:
receiving data information sent by a client, and sending a write request to a target OSD; wherein, the write request carries encapsulated data information;
judging whether a feedback message sent by the target OSD is received within a preset time;
if not, sending a response message that the write operation is completed to the client so that the client can continue to issue the data information.
Optionally, after sending the response message that the write operation is completed to the client, the method further includes:
acquiring running state change information;
traversing all the link tables to acquire a write request to be processed, wherein the write request is not provided with a feedback message in a preset time;
and sending the write request to be processed to a specific OSD according to the current running state information corresponding to each OSD and the OSD pointed by the write request to be processed.
Optionally, after sending the pending write request to the specific OSD, the method further includes:
judging whether a feedback message sent by the specific OSD is received within a preset time;
if so, deleting the write request to be processed from the corresponding link table;
and if not, displaying prompt information of the specific OSD fault.
Optionally, after the determining whether the feedback message sent by the target OSD is received within the preset time, the method further includes:
and when the feedback message sent by the target OSD is not received within the preset time, displaying the prompt message of the fault of the target OSD.
The embodiment of the invention also provides a write operation processing device, which comprises a receiving unit, a sending unit, a judging unit and a feedback unit;
the receiving unit is used for receiving data information sent by a client;
the sending unit is used for sending a write request to the target OSD; wherein, the write request carries encapsulated data information;
the judging unit is used for judging whether a feedback message sent by the target OSD is received within a preset time; if not, triggering the feedback unit;
and the feedback unit is used for sending a response message that the write operation is completed to the client so as to facilitate the client to continue to issue the data information.
Optionally, the system further comprises an obtaining unit and a traversing unit;
the acquisition unit is used for acquiring running state change information;
the traversal unit is used for traversing all the link tables to acquire the write request to be processed, wherein the write request is not provided with the feedback message in the preset time;
the sending unit is further configured to send the pending write request to a specific OSD according to the current operating state information corresponding to each OSD and the OSD to which the pending write request is directed.
Optionally, the system further comprises a deleting unit and a displaying unit;
the judging unit is also used for judging whether a feedback message sent by the specific OSD is received within a preset time; if yes, triggering the deleting unit; if not, triggering the display unit;
the deleting unit is used for deleting the write request to be processed from the corresponding link table;
and the display unit is used for displaying the prompt message of the specific OSD fault.
Optionally, the system further comprises a prompt unit;
and the prompting unit is used for displaying the prompting information of the fault of the target OSD when the feedback message sent by the target OSD is not received within the preset time.
An embodiment of the present invention further provides a write operation processing apparatus, including:
a memory for storing a computer program;
a processor for executing the computer program to implement the steps of the write operation processing method as described above.
The embodiment of the present invention further provides a computer-readable storage medium, where a computer program is stored on the computer-readable storage medium, and when the computer program is executed by a processor, the steps of the above-mentioned write operation processing method are implemented.
According to the technical scheme, the data information sent by the client is received, and the write request is sent to the target OSD; wherein, the write request carries the encapsulated data information; and judging whether a feedback message sent by the target OSD is received within a preset time. And after receiving the response message about the completion of the write operation, the client side can continue to issue new data information. Therefore, when the feedback message sent by the target OSD is not received within the preset time, in order to not affect the service flow of the client, a response message that the write operation is completed may be sent to the client, so that the client continues to issue the data information. The method effectively ensures that the data of the client is written into the uninterrupted flow, and meets the requirements of the cluster in different application scenes.
Drawings
In order to illustrate the embodiments of the present invention more clearly, the drawings that are needed in the embodiments will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and that other drawings can be obtained by those skilled in the art without inventive effort.
Fig. 1 is a flowchart of a write operation processing method according to an embodiment of the present invention;
FIG. 2 is a schematic structural diagram of a write operation processing apparatus according to an embodiment of the present invention;
fig. 3 is a schematic hardware structure diagram of a write operation processing apparatus according to an embodiment of the present invention.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments of the present invention without any creative work belong to the protection scope of the present invention.
In order that those skilled in the art will better understand the disclosure, the invention will be described in further detail with reference to the accompanying drawings and specific embodiments.
Next, a write operation processing method provided by an embodiment of the present invention is described in detail. Fig. 1 is a flowchart of a write operation processing method according to an embodiment of the present invention, where the method includes:
s101: and receiving data information sent by the client and sending a write request to the target OSD.
Wherein, the write request carries the encapsulated data information.
When the cluster runs, the client sends data information to the designated OSD, and for convenience of description, the designated OSD may be referred to as a target OSD.
In practical application, data information sent by a client is firstly transmitted to an OSDC, the OSDC encapsulates the received data information, and sends the encapsulated data information to a target OSD as a write request, so that the target OSD processes the data information.
The client may send multiple data messages pointing to different OSDs to the OSDC simultaneously, and accordingly, the number of target OSDs may be multiple. Each target OSD handles write requests in a similar manner, and in the embodiment of the present invention, a description is given by taking one target OSD as an example.
S102: and judging whether a feedback message sent by the target OSD is received within a preset time.
The preset time can be set according to the time spent by the OSD processing the write request, and in the embodiment of the invention, the specific value of the preset time is not limited as long as the preset time does not cause the service cutoff of the client. The client service interruption includes the condition that the data information transmission is suspended due to the fact that the client waits for the response message overtime.
When the target OSD is in a normal operation state, the target OSD can smoothly complete the operation corresponding to the write request, namely the write operation, within a preset time, and after the target OSD completes the write operation, a feedback message is sent to the OSDC to inform that the write operation of the OSDC is completed.
When the OSDC does not receive the feedback message sent by the target OSD within the preset time, it indicates that the target OSD may have a fault, and at this time, the cluster system may wait for the target OSD to recover from the fault, and then the target OSD continues to process the write operation or reselects another OSD to perform the write operation. Whether waiting for the recovery of the target OSD or selecting other OSDs to process the write operation takes a long time, and in the period of time, the client does not send new data information to the OSD because the client does not receive a response message that the write operation is completed, thereby causing the cut-off of the client service. And the service interruption will not be suitable for some scenes with higher service requirements.
In order to ensure normal processing of the client service, in the embodiment of the present invention, when the OSDC does not receive the feedback message sent by the target OSD within the preset time, S103 may be executed.
S103: and sending a response message that the write operation is completed to the client so that the client can continuously send the data information.
After receiving the response message, the client defaults to the completion of the write operation, and therefore new data information is continuously sent to the OSDC.
When the client transmits data information to the OSDC, a corresponding callback function is generated, so that when the OSDC sends a response message to the client, the client can be informed that the write operation is completed by calling the callback function.
According to the technical scheme, the data information sent by the client is received, and the write request is sent to the target OSD; wherein, the write request carries the encapsulated data information; and judging whether a feedback message sent by the target OSD is received within a preset time. And after receiving the response message about the completion of the write operation, the client side can continue to issue new data information. Therefore, when the feedback message sent by the target OSD is not received within the preset time, in order to not affect the service flow of the client, a response message that the write operation is completed may be sent to the client, so that the client continues to issue the data information. The method effectively ensures that the data of the client is written into the uninterrupted flow, and meets the requirements of the cluster in different application scenes.
In order to ensure the smooth execution of the write operation, in the embodiment of the present invention, a suitable OSD may be selected to execute the write operation according to the operation state information of each OSD.
Specifically, the running state change information may be acquired after a response message that the write operation is completed is sent to the client.
The cluster system is provided with a Monitor (Monitor), which may be abbreviated as MON. The MON may monitor the operating state of each OSD, and a storage device list (OSDMAP) is set in the cluster system, and the OSDMAP records the operating state information corresponding to each OSD.
In practical applications, when the operating state of one or some OSDs changes, the MON may send the state change information to the OSDC, so that the OSDC can timely know which OSDs can operate normally and which OSDs are in a fault state.
The state change information may include two types of information, that is, the OSD is changed from the normal state to the downtime state, or the downtime state is changed to the normal state.
When one or some OSD is or are disconnected, the running state information of the OSD is changed into a downtime state from a normal state, and in order to avoid that the OSDC continuously sends a write request to the OSD after the downtime, the MON sends the state change information to the OSDC.
For example, the cluster system includes 10 OSDs, which are OSD1-OSD10 in sequence. Assuming that the OSD10 is disconnected, after the MON detects that the OSD10 is disconnected, the running state information of the OSD10 in the OSDMAP is modified from the normal state to the downtime state, and the state change information from the normal state to the downtime state is sent to the OSDC, so that the OSDC can know the state change condition of the OSD10 in time.
In particular implementations, the OSDC may maintain an available list of OSDs, i.e., the list records OSDs that may function properly. When the running state change information received by the OSDC records that some or some OSD changes from the normal state to the down state, the OSD is deleted from the list, and when the running state change information records that some or some OSD changes from the down state to the normal state, the OSD is added into the list.
When receiving the running state change information, the OSDC can timely acquire the running state change condition of the OSD so as to select a proper OSD to execute the write operation.
Specifically, the OSDC may traverse all link tables to obtain pending write requests for which no feedback message is obtained at a preset time. And sending the write request to be processed to a specific OSD according to the current running state information corresponding to each OSD and the OSD pointed by the write request to be processed.
There is a corresponding communication link between the OSDC and each OSD, one for each communication link, i.e., one for each OSD, with all the operations associated with that OSD being recorded in the link table. By querying the link table, the write request to be processed for which no feedback message is obtained in the preset time can be obtained.
In practical applications, when the target OSD fails, an OSD in a master-slave backup relationship with the target OSD may be selected as a specific OSD to perform a write operation instead of the target OSD. When two OSD's in master-slave backup relation are both faulty, other OSD's that can work normally can be selected as specific OSD's to execute write operation.
The manner of selecting a specific OSD is similar to the manner of selecting another OSD to replace the faulty OSD to continue working when the OSD fails in the prior art, and the detailed process thereof is not described herein again.
In practical applications, it is considered that, during the process of processing the write operation, the selected specific OSD may fail due to the node power failure or other factors, so that the write operation cannot be completed smoothly. For this case, it may be further determined whether a feedback message transmitted by a specific OSD is received within a preset time after the pending write request is transmitted to the specific OSD.
When a feedback message sent by a specific OSD is received within a preset time, it indicates that the specific OSD has completed the write operation, and at this time, the pending write request may be deleted from the corresponding link table.
When the feedback message sent by the specific OSD is not received within the preset time, the fault of the specific OSD is possibly caused, and in order to remind a manager to timely process the fault condition, prompt information of the fault of the specific OSD can be displayed.
In specific implementation, prompt information of specific OSD faults can be displayed through a display screen so as to play a role in timely reminding.
Similar to the prompt message for displaying the specific OSD fault, when the feedback message sent by the target OSD is not received within the preset time, the prompt message for displaying the target OSD fault can be displayed.
By displaying the prompt information, the management personnel can be timely reminded when the OSD fails, so that the management personnel can timely process the failed OSD, the management personnel can recover to a normal state as soon as possible, the management personnel can be put into use, and the resource utilization rate of the cluster system is improved.
Fig. 2 is a schematic structural diagram of a write operation processing apparatus according to an embodiment of the present invention, where the apparatus includes a receiving unit 21, a sending unit 22, a judging unit 23, and a feedback unit 24;
a receiving unit 21, configured to receive data information sent by a client;
a transmitting unit 22 for transmitting a write request to the target OSD; wherein, the write request carries the encapsulated data information;
a judging unit 23, configured to judge whether a feedback message sent by a target OSD is received within a preset time; if not, the feedback unit 24 is triggered;
and the feedback unit 24 is configured to send a response message that the write operation is completed to the client, so that the client continues to issue the data information.
Optionally, the system further comprises an obtaining unit and a traversing unit;
the acquisition unit is used for acquiring running state change information;
the traversal unit is used for traversing all the link tables to acquire the write request to be processed, of which the feedback message is not acquired in preset time;
the sending unit is further configured to send the pending write request to the specific OSD according to the current operating state information corresponding to each OSD and the OSD to which the pending write request is directed.
Optionally, the system further comprises a deleting unit and a displaying unit;
the judging unit is also used for judging whether a feedback message sent by a specific OSD is received within the preset time; if yes, triggering a deleting unit; if not, triggering the display unit;
a deletion unit for deleting the pending write request from the corresponding link table;
and the display unit is used for displaying prompt information of specific OSD faults.
Optionally, the system further comprises a prompt unit;
and the prompting unit is used for displaying the prompting information of the fault of the target OSD when the feedback message sent by the target OSD is not received within the preset time.
The description of the features in the embodiment corresponding to fig. 2 may refer to the related description of the embodiment corresponding to fig. 1, and is not repeated here.
According to the technical scheme, the data information sent by the client is received, and the write request is sent to the target OSD; wherein, the write request carries the encapsulated data information; and judging whether a feedback message sent by the target OSD is received within a preset time. And after receiving the response message about the completion of the write operation, the client side can continue to issue new data information. Therefore, when the feedback message sent by the target OSD is not received within the preset time, in order to not affect the service flow of the client, a response message that the write operation is completed may be sent to the client, so that the client continues to issue the data information. The method effectively ensures that the data of the client is written into the uninterrupted flow, and meets the requirements of the cluster in different application scenes.
Fig. 3 is a schematic diagram of a hardware structure of a write operation processing apparatus 30 according to an embodiment of the present invention, where the write operation processing apparatus 30 includes:
a memory 31 for storing a computer program;
a processor 32 for executing the computer program to implement the steps of the write operation processing method as described above.
The embodiment of the invention also provides a computer-readable storage medium, on which a computer program is stored, and when being executed by a processor, the computer program realizes the steps of the above write operation processing method.
The above details describe a write operation processing method, a write operation processing device, and a computer-readable storage medium according to embodiments of the present invention. The embodiments are described in a progressive manner in the specification, each embodiment focuses on differences from other embodiments, and the same and similar parts among the embodiments are referred to each other. The device disclosed by the embodiment corresponds to the method disclosed by the embodiment, so that the description is simple, and the relevant points can be referred to the method part for description. It should be noted that, for those skilled in the art, it is possible to make various improvements and modifications to the present invention without departing from the principle of the present invention, and those improvements and modifications also fall within the scope of the claims of the present invention.
Those of skill would further appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or combinations of both, and that the various illustrative components and steps have been described above generally in terms of their functionality in order to clearly illustrate this interchangeability of hardware and software. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.
The steps of a method or algorithm described in connection with the embodiments disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module may reside in Random Access Memory (RAM), memory, Read Only Memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art.

Claims (8)

1. A write operation processing method, comprising:
receiving data information sent by a client, and sending a write request to a target OSD; wherein, the write request carries encapsulated data information;
judging whether a feedback message sent by the target OSD is received within a preset time;
if not, sending a response message that the write operation is completed to the client so that the client can continuously send data information;
after the sending of the response message to the client that the write operation is completed, the method further includes:
acquiring running state change information;
traversing all the link tables to acquire a write request to be processed, wherein the write request is not provided with a feedback message in a preset time;
and sending the write request to be processed to a specific OSD according to the current running state information corresponding to each OSD and the OSD pointed by the write request to be processed.
2. The method of claim 1, further comprising, after the sending the pending write request to a particular OSD:
judging whether a feedback message sent by the specific OSD is received within a preset time;
if so, deleting the write request to be processed from the corresponding link table;
and if not, displaying prompt information of the specific OSD fault.
3. The method according to any of claims 1-2, wherein after the determining whether the feedback message sent by the target OSD is received within a preset time, the method further comprises:
and when the feedback message sent by the target OSD is not received within the preset time, displaying the prompt message of the fault of the target OSD.
4. A write operation processing device is characterized by comprising a receiving unit, a sending unit, a judging unit and a feedback unit;
the receiving unit is used for receiving data information sent by a client;
the sending unit is used for sending a write request to the target OSD; wherein, the write request carries encapsulated data information;
the judging unit is used for judging whether a feedback message sent by the target OSD is received within a preset time; if not, triggering the feedback unit;
the feedback unit is used for sending a response message that the write operation is completed to the client so that the client can continue to issue data information;
the system also comprises an acquisition unit and a traversal unit;
the acquisition unit is used for acquiring running state change information;
the traversal unit is used for traversing all the link tables to acquire the write request to be processed, wherein the write request is not provided with the feedback message in the preset time;
the sending unit is further configured to send the pending write request to a specific OSD according to the current operating state information corresponding to each OSD and the OSD to which the pending write request is directed.
5. The device of claim 4, further comprising a deletion unit and a presentation unit;
the judging unit is also used for judging whether a feedback message sent by the specific OSD is received within a preset time; if yes, triggering the deleting unit; if not, triggering the display unit;
the deleting unit is used for deleting the write request to be processed from the corresponding link table;
and the display unit is used for displaying the prompt message of the specific OSD fault.
6. The device according to any one of claims 4-5, further comprising a prompting unit;
and the prompting unit is used for displaying the prompting information of the fault of the target OSD when the feedback message sent by the target OSD is not received within the preset time.
7. A write operation processing apparatus, comprising:
a memory for storing a computer program;
a processor for executing the computer program to implement the steps of the write operation processing method according to any one of claims 1 to 3.
8. A computer-readable storage medium, characterized in that a computer program is stored on the computer-readable storage medium, which computer program, when being executed by a processor, carries out the steps of the write operation processing method according to any one of claims 1 to 3.
CN201810820168.5A 2018-07-24 2018-07-24 Write operation processing method and device and computer readable storage medium Active CN109088921B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201810820168.5A CN109088921B (en) 2018-07-24 2018-07-24 Write operation processing method and device and computer readable storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201810820168.5A CN109088921B (en) 2018-07-24 2018-07-24 Write operation processing method and device and computer readable storage medium

Publications (2)

Publication Number Publication Date
CN109088921A CN109088921A (en) 2018-12-25
CN109088921B true CN109088921B (en) 2021-05-28

Family

ID=64838497

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201810820168.5A Active CN109088921B (en) 2018-07-24 2018-07-24 Write operation processing method and device and computer readable storage medium

Country Status (1)

Country Link
CN (1) CN109088921B (en)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112637337B (en) * 2020-12-22 2022-02-22 新华三大数据技术有限公司 Data processing method and device

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102393887B (en) * 2011-06-30 2015-06-17 华为数字技术（成都）有限公司 Application centralized management system and method based on Linux security module (LSM) mechanism
US10003649B2 (en) * 2015-05-07 2018-06-19 Dell Products Lp Systems and methods to improve read/write performance in object storage applications
CN107092521B (en) * 2016-12-30 2020-11-10 北京星选科技有限公司 Distributed task scheduling method, device and system

Also Published As

Publication number Publication date
CN109088921A (en) 2018-12-25

Similar Documents

Publication Publication Date Title
CN110311831B (en) Container cloud-based system resource monitoring method and related equipment
CN111800354B (en) Message processing method and device, message processing equipment and storage medium
EP2723017A1 (en) Method, apparatus and system for implementing distributed auto-incrementing counting
CN106330523A (en) Cluster server disaster recovery system and method, and server node
CN104065526A (en) Server fault alarming method and device thereof
US20170351560A1 (en) Software failure impact and selection system
CN105589756A (en) Batch processing cluster system and method
CN109088921B (en) Write operation processing method and device and computer readable storage medium
CN110196749B (en) Virtual machine recovery method and device, storage medium and electronic device
CN111158608A (en) Hard disk fault processing method and device and distributed system
US20150363949A1 (en) Stadium view visualization
US20110225463A1 (en) Detecting and recovering from process failures
CN106487852B (en) Method, device, terminal equipment and system for realizing client file synchronization
CN108733808B (en) Big data software system switching method, system, terminal equipment and storage medium
US11930292B2 (en) Device state monitoring method and apparatus
US8667340B2 (en) Method and system for distributed processing of alerts
EP3687133B1 (en) System and method for synchronization of media objects between devices operating in a multiroom system
CN116185697A (en) Container cluster management method, device and system, electronic equipment and storage medium
CN111162938A (en) Data processing system and method
CN111130856A (en) Server configuration method, system, equipment and computer readable storage medium
CN112751693A (en) Data processing method and device of distributed storage system and electronic equipment
CN105790975A (en) Service processing operation execution method and device
CN114490003A (en) Distributed job scheduling method of large-scale data and related equipment
CN112817998A (en) Method and system for automatically comparing and synchronizing data of hydropower station
CN112711517A (en) Server performance monitoring method and device, storage medium and terminal

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant