CN115543919A - Archive processing method and device, computer equipment and storage medium - Google Patents

Archive processing method and device, computer equipment and storage medium Download PDF

Info

Publication number
CN115543919A
CN115543919A CN202211391021.1A CN202211391021A CN115543919A CN 115543919 A CN115543919 A CN 115543919A CN 202211391021 A CN202211391021 A CN 202211391021A CN 115543919 A CN115543919 A CN 115543919A
Authority
CN
China
Prior art keywords
target node
node
file
archive
node group
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202211391021.1A
Other languages
Chinese (zh)
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.)
Shenzhen Yuntian Changxiang Information Technology Co ltd
Original Assignee
Shenzhen Yuntian Changxiang Information Technology Co ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Shenzhen Yuntian Changxiang Information Technology Co ltd filed Critical Shenzhen Yuntian Changxiang Information Technology Co ltd
Priority to CN202211391021.1A priority Critical patent/CN115543919A/en
Publication of CN115543919A publication Critical patent/CN115543919A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/10File systems; File servers
    • G06F16/11File system administration, e.g. details of archiving or snapshots
    • G06F16/113Details of archiving
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/07Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/14Error detection or correction of the data by redundancy in operation
    • G06F11/1402Saving, restoring, recovering or retrying
    • G06F11/1446Point-in-time backing up or restoration of persistent data
    • G06F11/1448Management of the data involved in backup or backup restore
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/07Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/14Error detection or correction of the data by redundancy in operation
    • G06F11/1402Saving, restoring, recovering or retrying
    • G06F11/1446Point-in-time backing up or restoration of persistent data
    • G06F11/1458Management of the backup or restore process
    • G06F11/1469Backup restoration techniques
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/10File systems; File servers
    • G06F16/16File or folder operations, e.g. details of user interfaces specifically adapted to file systems
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/10File systems; File servers
    • G06F16/17Details of further file system functions
    • G06F16/178Techniques for file synchronisation in file systems
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/10File systems; File servers
    • G06F16/18File system types
    • G06F16/182Distributed file systems
    • G06F16/184Distributed file systems implemented as replicated file system

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Data Mining & Analysis (AREA)
  • Databases & Information Systems (AREA)
  • Quality & Reliability (AREA)
  • Human Computer Interaction (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

The present application relates to an archive processing method, apparatus, computer device, storage medium, and computer program product. The method comprises the following steps: when an archive event occurs for the target node group, performing an archive write operation at the target node group: storing a first file indicated by the archiving event to a master node in the target node group, and copying the first file from the master node to a slave node in the target node group; performing a file read operation when a file read event occurs for the target node group: selecting a target node in a normal working state from the master node and the slave nodes in the target node group, and reading a second file indicated by the file reading event from the target node; the file writing operation and the file reading operation are mutually exclusive atomic operations. By adopting the method, the reliability of file storage can be improved.

Description

Archive processing method and device, computer equipment and storage medium
Technical Field
The present application relates to the field of archive technologies, and in particular, to an archive processing method, an archive processing apparatus, a computer device, a storage medium, and a computer program product.
Background
With the development of computer technology, cloud applications are implemented. The cloud application is installed and operated on the server, the server is communicated with the local terminal, remote operation of a user on the cloud application installed on the server through the local terminal is received, the cloud application is operated, and pictures, data and the like generated by operation of the cloud application are transmitted to the local terminal. The user remotely logs in the cloud application on the server through the local terminal, and the cloud application archive file of the user is generated in the process that the user uses the cloud application, so that good experience is provided for the user, and the cloud application archive file of the user needs to be stored. The cloud application archive file of the user is usually stored in a single storage location, and the historical cloud application archive file can be acquired from the storage location each time the user logs in the cloud application, so that the user can continue to use the cloud application based on the historical cloud application archive file.
However, in the conventional method, the cloud application archive file of the user is stored in a single point, and when the storage location is abnormal, the archive file will be lost, so that the storage reliability is not high.
Disclosure of Invention
In view of the above, it is necessary to provide an archive processing method, an archive processing apparatus, a computer device, a computer readable storage medium, and a computer program product capable of improving storage reliability in view of the above technical problems.
In a first aspect, the present application provides a method for processing an archive. The method comprises the following steps:
when an archiving event aiming at a target node group occurs, performing archive writing operation on a first archive indicated by the archiving event at the target node group; the archive write operation comprises: storing the first file to a master node in the target node group, and copying the first file from the master node to a slave node in the target node group;
when a file reading event aiming at the target node group occurs, executing a file reading operation of reading a second file indicated by the file reading event from the target node group; the file reading operation comprises: selecting a target node in a normal working state from the master node and the slave nodes in the target node group, and reading the second file from the target node; wherein the archive write operation and the archive read operation are mutually exclusive atomic operations.
In one embodiment, the method further comprises:
acquiring a file type pre-configured for a target node group;
periodically querying an updated archive from a temporary storage node that temporarily stores an archive of the cloud application; the updated profile is of the profile type and has not been stored by the target node group;
and when the updated archive is inquired, triggering an archive event aiming at the target node group.
In one embodiment, the method further comprises:
when any node in the target node group is abnormal, the abnormal node stops working, and a first temporary synchronization table is established for the abnormal node;
when a master node in the target node group writes a file, sequentially adding records to be synchronized for the written file in the first temporary synchronization table until the first temporary synchronization table is deactivated;
and after the abnormal nodes are recovered to be normal, sequentially playing back according to the records to be synchronized in the first temporary synchronization table so as to store the files written into the main node to the nodes recovered to be normal, and stopping the first temporary synchronization table until the playback of the records to be synchronized in the first temporary synchronization table is finished.
In one embodiment, the method further comprises:
and when the master node in the target node group is abnormal, selecting one slave node in a normal working state from the slave nodes in the target node group, and updating the selected slave node as the master node of the target node group.
In one embodiment, the method further comprises:
when the slave nodes in the target node group are abnormal, the abnormal nodes are removed from the target node group;
and when the abnormal node is recovered to be normal, the node recovered to be normal is used as a slave node to rejoin the target node group.
In one embodiment, the method further comprises:
responding to a newly added node event aiming at the target node group, and carrying out file synchronization on a newly added node indicated by the newly added node event; the archive synchronization comprises:
creating a full-scale synchronization table corresponding to the target node group, and adding records of the archives currently stored by the main node in the full-scale synchronization table;
creating a second temporary synchronization table corresponding to the newly added node indicated by the newly added node event, and when the master node in the target node group writes files, sequentially adding to-be-synchronized records aiming at the written files in the second temporary synchronization table until the second temporary synchronization table is stopped;
and after the archives recorded in the full-scale synchronization table are stored in the newly added node, sequentially replaying according to the records to be synchronized in the second temporary synchronization table so as to store the archives written in the main node to the newly added node, and stopping the second temporary synchronization table until the replaying of the records to be synchronized in the second temporary synchronization table is finished.
In one embodiment, the method further comprises:
responding to the capacity expansion event aiming at the target node group, adding nodes in the target node group, stopping the master nodes and the slave nodes in the target node group after carrying out file synchronization aiming at the added nodes, and updating the added nodes to be the master nodes of the target node group;
and adding nodes in the target node group again, and taking the nodes added again as slave nodes of the target node group after carrying out the file synchronization aiming at the added nodes.
In a second aspect, the present application further provides an archive processing apparatus. The device comprises:
the archive writing module is used for executing archive writing operation on a first archive indicated by an archive event in a target node group when the archive event aiming at the target node group occurs; the archive write operation comprises: storing the first file to a master node in the target node group, and copying the first file from the master node to a slave node in the target node group;
the file reading module is used for executing file reading operation of reading a second file indicated by the file reading event from the target node group when the file reading event aiming at the target node group occurs; the file reading operation comprises: selecting a target node in a normal working state from the master node and the slave nodes in the target node group, and reading the second file from the target node; wherein the archive write operation and the archive read operation are mutually exclusive atomic operations.
In a third aspect, the present application also provides a computer device. The computer device comprises a memory storing a computer program and a processor implementing the following steps when executing the computer program:
when an archiving event aiming at a target node group occurs, performing archive writing operation on a first archive indicated by the archiving event at the target node group; the archive write operation comprises: storing the first file to a master node in the target node group, and copying the first file from the master node to a slave node in the target node group;
when a file reading event aiming at the target node group occurs, executing a file reading operation of reading a second file indicated by the file reading event from the target node group; the file reading operation comprises: selecting a target node in a normal working state from the master node and the slave nodes in the target node group, and reading the second file from the target node; wherein the archive write operation and the archive read operation are mutually exclusive atomic operations.
In a fourth aspect, the present application further provides a computer-readable storage medium. The computer-readable storage medium, on which a computer program is stored which, when executed by a processor, carries out the steps of:
when an archive event aiming at a target node group occurs, performing archive writing operation on a first archive indicated by the archive event at the target node group; the archive write operation comprises: storing the first file to a master node in the target node group, and copying the first file from the master node to a slave node in the target node group;
when a file reading event aiming at the target node group occurs, executing a file reading operation of reading a second file indicated by the file reading event from the target node group; the file reading operation comprises the following steps: selecting a target node in a normal working state from the master node and the slave nodes in the target node group, and reading the second file from the target node; wherein the archive write operation and the archive read operation are mutually exclusive atomic operations.
In a fifth aspect, the present application further provides a computer program product. The computer program product comprising a computer program which when executed by a processor performs the steps of:
when an archiving event aiming at a target node group occurs, performing archive writing operation on a first archive indicated by the archiving event at the target node group; the archive write operation comprises: storing the first file to a master node in the target node group, and copying the first file from the master node to a slave node in the target node group;
when a file reading event aiming at the target node group occurs, executing a file reading operation of reading a second file indicated by the file reading event from the target node group; the file reading operation comprises: selecting a target node in a normal working state from the master node and the slave nodes in the target node group, and reading the second file from the target node; wherein the archive write operation and the archive read operation are mutually exclusive atomic operations.
According to the archive processing method, the device, the computer equipment, the storage medium and the computer program product, the archive is stored in the master node and the slave nodes of the target node group to form a plurality of archive backups, and the archive storage reliability is high; any node in the target node group in a normal state can be used as a target node to provide file reading service, and the flexibility is high; the archive writing operation and the archive reading operation of the target node group are mutually exclusive atomic operations, the archive writing operation and the archive reading operation cannot be carried out simultaneously, the incomplete read archives are avoided, and the reliability of archive storage and reading is improved.
Drawings
FIG. 1 is a diagram of an exemplary embodiment of a file processing system;
FIG. 2 is a flowchart illustrating a file processing method according to an embodiment;
FIG. 3 is a flowchart illustrating the steps in one embodiment for handling an abnormal node in a target node group;
FIG. 4 is a flowchart illustrating the steps of file synchronization in one embodiment;
FIG. 5 is a schematic diagram illustrating an interaction between a set of temporary storage nodes and a set of node groups in one embodiment;
FIG. 6 is a block diagram of an embodiment of an archive processing device;
FIG. 7 is a diagram illustrating an internal structure of a computer device according to an embodiment.
Detailed Description
In order to make the objects, technical solutions and advantages of the present application more apparent, the present application is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the present application and are not intended to limit the present application.
The archive processing method provided by the embodiment of the application can be applied to the application environment shown in fig. 1. Wherein the archive processing method is executed on the computer device 102, and has access to at least one node group, and the target node group is one node group of the at least one node group. The node group may be deployed on computer device 102 or may be deployed on another computer device accessible to computer device 102. A node group is a collection of at least two nodes, including one master node and at least one slave node. The node is a communication endpoint in the node group, and may be a virtual program or an entity device. The nodes can store data directly or to a storage device to which the nodes are mapped. The computer device 102 communicates with the temporary storage node 104 or the cloud host 106 through a network, and the computer device 102 may instruct the master node and the slave node to implement respective archive writing in response to an archive event triggered by the temporary storage node 104; the computer device may instruct a target node selected from the master node or the slave nodes to perform an archive read in response to a read file event triggered by the temporary storage node 104 or the cloud host 106.
The computer device 102 may be a terminal, such as a desktop computer, a notebook computer, a smart phone, or a tablet computer; the computer device 102 may be a server, and may be implemented as a stand-alone server or a server cluster composed of a plurality of servers; the computer device 102 may also be a virtual host, virtualized by an independent server or server farm. The temporary storage node 104 may be a terminal, a server, or a virtual host. The cloud host 106 may be a virtual host or a server. The storage device is a variety of devices that can implement information storage, such as a disk, disk array.
In one embodiment, as shown in fig. 2, an archive processing method is provided, which is described as an example of the method applied to the computer device 102 in fig. 1, and includes the following steps:
step 202, when an archive event aiming at the target node group occurs, performing archive writing operation on a first archive indicated by the archive event in the target node group; the file write operation includes: the first file is stored to the master node in the target node group, and the first file is copied from the master node to the slave node in the target node group.
Wherein the target node group is the node group for which the method is implemented. The target node group includes a master node and a slave node. The master node is a node in the target node group that is in the master role. The slave node is a node in the target node group that acts as a slave. In this embodiment, the difference between the master node and the slave node is as follows: when an archive event is triggered in the target node group, the master node is the first node to write the archive, and the slave nodes copy the archive from the master node. Each node in the target node group is independent of the other.
The archive is a record that is created when the computer software is operated and that requires the state to be stored and later reproduced by reading the archive, and may be a game archive or an archive of office software. An archive event is an event that stores an archive. The first file is the file that needs to be stored when the file-archiving event is triggered, and is distinguished from the file that needs to be read when the file-reading event is triggered in the subsequent step 204. The archive write operation is an operation to store an archive by the target node group.
In one embodiment, the computer device may obtain a pre-configured profile type for the target node group, query a profile from the profiles indicated by the profile addition event in response to the profile addition event on the temporary storage node that matches the pre-configured profile type for the target node group, and trigger an archive event for the target node group when the matching profile is queried.
In one embodiment, the temporary storage node may generate a profile indicated by a profile generation event triggered by the cloud host in response to the profile generation event, acquire a profile type pre-configured for the target node group, and determine whether the generated profile belongs to the profile type pre-configured for the target node group, where the generated profile belongs to the profile type pre-configured for the target node group and where any node in the target node group is not providing a read profile or write profile function, trigger a file event for the target node group. Wherein the temporary storage node may communicate with the cloud host.
In one embodiment, a computer device may determine whether a target node group is performing a file write operation or a file read operation in response to an archive event for the target node group, where the target node group is not performing either a file write operation or a file read operation, the file write operation for a first archive indicated by the archive event is performed at the target node group.
In one embodiment, when the target node group has multiple slave nodes, the computer device may copy the first archive from the master node to the multiple slave nodes of the target node group simultaneously after completing storing the first archive to the master node.
Step 204, when a file reading event aiming at the target node group occurs, executing a file reading operation of reading a second file indicated by the file reading event from the target node group; the file reading operation comprises the following steps: selecting a target node in a normal working state from the master node and the slave nodes in the target node group, and reading a second file from the target node; the file writing operation and the file reading operation are mutually exclusive atomic operations.
The file reading event refers to an event of reading a file. The second file is the file that needs to be read when the file reading event is triggered, and is distinguished from the file that needs to be stored when the file archiving event is triggered in step 202. The file read operation is an operation to read a file from the target node group. The exclusive operation means that the file write operation and the file read operation can not be performed simultaneously. Atomic operations refer to operations that are not interrupted by a thread scheduling mechanism. The atomic operation will not be interrupted after it starts and will run to the end.
In one embodiment, in a case where the target node group does not perform the archive write operation nor the archive read operation, the temporary storage node may perform the archive read operation of reading the second archive indicated by the archive read event from the target node group in response to the archive read event for the target node group triggered by the cloud host.
In one embodiment, in a case where the target node group does not perform the file writing operation nor the file reading operation, the cloud host may perform the file reading operation of reading the second file indicated by the file reading event from the target node group in response to the file reading event for the target node group triggered by the terminal through the remote network operation.
In one embodiment, a computer device may detect the operating states of a master node and slave nodes in a target node group in response to a read event for the target node group, determine the master node and slave nodes in normal operating states, and randomly select one of the master node and slave nodes in normal operating states as a target node.
In one embodiment, the computer device may determine a storage location of the second archive by the index information, from which storage location the second archive is read in the target node. The index information is a record capable of quickly retrieving the archive, and for example, the index information may be a record representing an archive number of the archive or a record representing a storage location of the archive, and the like.
In the archive processing method, the archives are stored in the master node and the slave nodes of the target node group to form a plurality of archive backups, so that the reliability of archive storage is high; any node in the target node group in a normal state can be used as a target node to provide file reading service, and the flexibility is high; the archive writing operation and the archive reading operation of the target node group are mutually exclusive atomic operations, the archive writing operation and the archive reading operation cannot be carried out simultaneously, the incomplete read archives are avoided, and the reliability of archive storage and reading is improved.
In an embodiment, the archive processing method further includes a step of periodically querying an updated archive from the temporary storage node according to an archive type pre-configured for the target node group to trigger an archive event, where the step specifically includes: acquiring a file type pre-configured for a target node group; periodically querying an updated archive from a temporary storage node that temporarily stores an archive of the cloud application; the updated archive belongs to the archive type and is not stored by the target node group; when the updated archive is queried, an archive event for the target node group is triggered.
The file types are different types of files divided according to classification bases. The classification is based on, for example, the geographical area to which the archive belongs, or the cloud application to which the archive belongs. A cloud application is software that is installed and run on a server. The temporary storage node is used for mounting to the cloud host when the cloud host starts the cloud application; and also for un-mounting to the cloud host when the cloud application is closed. The periodicity may be at preset time intervals or according to a dynamically changing cycle.
In one embodiment, the temporary storage node may generate a fast lookup table for the archive of the stored cloud application, the fast lookup table recording an archive number of the archive, an archive type of the archive, and an archive record of the archive, the archive record of the archive indicating whether the corresponding archive has been archived to the node group. In this embodiment, the computer device may periodically screen the archive from the fast lookup table of the temporary storage node, and trigger an archive event for the target node group when the type of the archive that belongs to the target node group is pre-configured and the archive record is an archive that is not archived to the node group is screened.
In one embodiment, when a computer device queries an updated archive from a temporary storage node, it may determine an archive that has newly appeared in the temporary storage node since the last query was completed, traverse the newly appeared archive, determine whether the traversed archive is of an archive type and has not been stored by a target node group, and trigger an archive event for the target node group when the traversed archive is of an archive type and has not been stored by the target node group.
In the embodiment, the files in the temporary storage nodes are periodically inquired to find the updated files needing to be stored in the target node group, so that the files are stored in multiple backup in time, and the reliability of file storage is improved; in addition, the target node group stores files of file types which are pre-configured, file distribution can be achieved, the problem of resource waste caused by uneven utilization rate of storage resources of each node group is avoided, and the reliability of file storage is improved.
In one embodiment, as shown in fig. 3, the archive processing method further includes a step of processing an abnormal node in the target node group. Specifically, the step creates a first temporary synchronization table for any abnormal node in the target node group, records the file written into the master node during the abnormal period, and synchronizes the file written into the master node during the abnormal period after the abnormal node recovers to normal. In one embodiment, the step of processing the abnormal node in the target node group specifically includes the following steps 302 to 306.
Step 302, when any node in the target node group is abnormal, the abnormal node stops working, and a first temporary synchronization table is created for the abnormal node.
The exception means that the node cannot work normally. The exception may be a power outage, a network connection interruption, a storage device corruption, an infection with a virus, or otherwise. The temporary synchronization table is a table that temporarily records the archive written to the master node. The first temporary synchronization table is a temporary synchronization table created for an abnormal node when the node is abnormal, and is distinguished from a second temporary synchronization table created for a newly added node when a newly added node event occurs in a target node group.
In one embodiment, a computer device may detect operating states of a master node and a slave node in a target node group in response to an archive event or a read event for the target node group, bring any node in the target node group out of operation upon detecting that the node is in an abnormal operating state, and create a first temporary synchronization table for the abnormal node.
In one embodiment, the first temporary synchronization table may be a memory table that stores data in a memory of the computer device. In this embodiment, when any node in the target node group is abnormal, the computer device may create a first temporary synchronization table for the abnormal node, and allocate a memory space for the first temporary synchronization table.
And step 304, when the master node in the target node group writes the file, sequentially adding the record to be synchronized aiming at the written file in the first temporary synchronization table until the first temporary synchronization table is deactivated.
The record to be synchronized is a record of the file to be synchronized in the temporary synchronization table, and may represent a file number of the file, a storage location of the file, or a content recorded by the file itself.
In one embodiment, the computer device may record an exception time of the node that is in the exception, and from the exception time, whenever a master node in the target node group writes a file, add records to be synchronized for the written file at consecutive locations in the first temporary synchronization table in sequence from a first location where the records to be synchronized are expected to be added to the first temporary synchronization table until the first temporary synchronization table is deactivated.
In one embodiment, during the abnormal operation of the abnormal node, whenever the master node in the target node group writes a file, the computer device may sequentially randomly select an empty location in the first temporary synchronization table where no record to be synchronized is added, and add a record to be synchronized for the written file at the selected empty location in the first temporary synchronization table until the first temporary synchronization table is disabled.
In one embodiment, where the first temporary synchronization table is a memory table, the computer device may store the record to be synchronized into a memory space corresponding to the first temporary synchronization table.
And step 306, after the abnormal node returns to normal, sequentially playing back according to the records to be synchronized in the first temporary synchronization table, so as to store the files written in the master node to the node returning to normal, and stopping the first temporary synchronization table until the playback of the records to be synchronized in the first temporary synchronization table is finished.
Wherein playback refers to reproducing the behavior of the synchronization profile to be recorded in the synchronization recording.
In an embodiment, after the abnormal node is recovered to be normal, the computer device may sequentially record and play back according to the records to be synchronized in the first temporary synchronization table, and when one record to be synchronized is played back, obtain a file represented by the played back record to be synchronized from the files stored by the master node, and store the obtained file to the node recovered to be normal until the playback of the record to be synchronized in the first temporary synchronization table is completed.
In one embodiment, in a case that the first temporary synchronization table is a memory table, the computer device may clear the to-be-synchronized record in the first temporary synchronization table when the playback of the to-be-synchronized record in the first temporary synchronization table is finished, and release a memory space occupied by the to-be-synchronized record.
In one embodiment, in the case that the first temporary synchronization table is a memory table, the computer device may delete the first temporary synchronization table and release the memory space allocated to the first temporary synchronization table when the synchronous recording playback in the first temporary synchronization table is finished.
In this embodiment, the first temporary synchronization table created for any abnormal node in the target node group records the file written into the master node during the abnormal period of the node, so that the file written into the master node during the abnormal period can be synchronized after the node recovers to be normal, and it is ensured that the file stored by the node recovering to be normal is the same as the file stored by other nodes in the target node group after the node joins the target node group again, thereby ensuring the consistency of the file stored by each node in the target node group, and further improving the reliability of reading the file.
In an embodiment, the archive processing method further includes the following steps: when the master node in the target node group is abnormal, selecting a slave node in a normal working state from the slave nodes in the target node group, and updating the selected slave node as the master node of the target node group.
Wherein, updating refers to changing the role of the node.
In one embodiment, when the target node group includes at least two slave nodes in a normal operating state, when the computer device detects that a master node in the target node group is abnormal, the abnormal master node is removed from the target node group, the slave nodes in the normal operating state in the target node group are sorted according to a pre-configured sorting rule, and the slave node arranged at the top is updated to the master node of the target node group. The ordering rule may be a random ordering, or may be an order configured in advance for each slave node.
In the embodiment, a new master node is selected when the master node is abnormal, so that the target node group always comprises one master node, thereby creating conditions for executing archive writing operation in the target node group and further improving the reliability of archive storage.
In an embodiment, the archive processing method further includes the following steps: when the slave nodes in the target node group are abnormal, the abnormal nodes are removed from the target node group; and when the abnormal nodes are recovered to be normal, the nodes recovered to be normal are used as slave nodes to rejoin the target node group.
The elimination means that the abnormal node is not used as a node of the target node group to provide a file writing or file reading service to the outside. The recovery from normal means that the abnormal problem of the abnormal node is repaired, and the abnormal node can be added into the target node group to provide the file writing or file reading service.
In one embodiment, when an abnormal node in the target node group returns to normal, the node which returns to normal may send a signal to the computer device, and after the computer device receives the signal that the node returns to normal, the node which returns to normal may be taken as a slave node to rejoin the target node group.
In one embodiment, the computer device may periodically detect whether the abnormal node is recovered from the abnormal time of the abnormal node in the target node group, and rejoin the node recovered from the abnormal node as the slave node when the abnormal node is recovered.
In the embodiment, when the slave node in the target node group is abnormal, the abnormal node is removed from the target node group, so that errors caused by the fact that the abnormal node cannot provide service when the target node group provides service outwards are avoided; and the node which is recovered to be normal is taken as a slave node to rejoin the target node group, so that the node which is recovered to be normal can provide service to the outside again, and the node resource is fully utilized.
In one embodiment, the file processing method further includes a step of performing file synchronization on the newly added node indicated by the newly added node event in response to the newly added node event for the target node group, where the newly added node event is an event of adding a new node to the target node group. The new node event may specifically be a manual trigger operation or an automatic trigger event. And manually triggering operation such as clicking of a function key of a newly added node aiming at the target node group. The automatic triggering event may be that the time of the abnormal node in the target node group in the abnormal state exceeds a preset time length, or the number of the nodes in the normal state in the target node group is less than or equal to a preset number, or a newly accessed storage device is identified, or an expansion event for the target node group occurs.
In one embodiment, as shown in FIG. 4, the file synchronization specifically includes the following steps 402 to 406.
Step 402, creating a full synchronization table corresponding to the target node group, and adding records of the archive currently stored by the master node in the full synchronization table.
The full quantity synchronization table is a table for recording files stored by the main node before the occurrence of the event of the newly added node.
In one embodiment, a computer device may determine an archive currently stored by a master node, and add a record of the determined archive to a full synchronization table.
In one embodiment, the computer device may determine a time when the new node event occurs, obtain index information of a file stored by the master node before the time when the new node event occurs, and add a record representing the obtained index information in the full-volume synchronization table.
In other embodiments, the computer device may determine a time when the new node event occurs, obtain index information of the archive stored by the master node before the time when the new node event occurs, and determine an identifier of the archive stored by the master node based on the index information, thereby recording the identifier of the archive in the full-volume synchronization table.
Step 404, creating a second temporary synchronization table corresponding to the newly added node indicated by the newly added node event, and adding a record to be synchronized for the written file in the second temporary synchronization table in sequence when the master node in the target node group writes the file until the second temporary synchronization table is deactivated.
The second temporary synchronization table is a temporary synchronization table corresponding to the newly added node indicated by the newly added node event and is distinguished from the first temporary synchronization table created for the abnormal node when the node is abnormal.
In one embodiment, the computer device may record an event occurrence time of the newly added node event, and from the event occurrence time, whenever a master node in the target node group writes a file, add records to be synchronized for the written file at consecutive locations in the second temporary synchronization table in sequence from a first location where the records to be synchronized are expected to be added to the second temporary synchronization table until the second temporary synchronization table is deactivated.
In one embodiment, after a new node event occurs for the target node group, whenever a master node in the target node group writes a file, the computer device may sequentially and randomly select an empty location in the second temporary synchronization table where no record to be synchronized is added, and add a record to be synchronized for the written file at the empty location in the second temporary synchronization table until the second temporary synchronization table is disabled.
In one embodiment, in the case that the second temporary synchronization table is a memory table, the computer device may allocate a memory space for the second temporary synchronization table when creating the second temporary synchronization table, and store the record to be synchronized into the memory space corresponding to the second temporary synchronization table.
Step 406, after the files recorded in the full volume synchronization table are stored in the newly added node, the files are sequentially played back according to the records to be synchronized in the second temporary synchronization table, so that the files written in the master node are stored in the newly added node, and the second temporary synchronization table is deactivated until the playback of the records to be synchronized in the second temporary synchronization table is completed.
In one embodiment, the computer device may obtain all the archives represented by the records in the full volume synchronization table from the master node according to the records in the full volume synchronization table, and store the obtained archives to the newly added node.
In one embodiment, after storing the files recorded in the full volume synchronization table in the newly added node, the computer device may sequentially play back the files according to the records to be synchronized in the second temporary synchronization table, and every time one record to be synchronized is played back, obtain the files represented by the played back records to be synchronized from the files stored in the master node, and store the obtained files in the newly added node, until the playback of the records to be synchronized in the second temporary synchronization table is completed, deactivate the second temporary synchronization table.
In an embodiment, in a case that the second temporary synchronization table is a memory table, the computer device may clear the to-be-synchronized record in the second temporary synchronization table when the playback of the to-be-synchronized record in the second temporary synchronization table is finished, and release a memory space occupied by the to-be-synchronized record.
In one embodiment, in the case that the second temporary synchronization table is a memory table, the computer device may delete the second temporary synchronization table and release the memory space allocated to the second temporary synchronization table when the synchronous recording and playback in the second temporary synchronization table is completed.
In the embodiment, when a node is newly added to a target node group, the file currently stored by the master node is stored to the newly added node through the full-volume synchronization table, so that the file stored by other nodes in the target node group before the newly added time is stored in the newly added node; and the second temporary synchronization table records the file written into the master node from the newly added time to the file synchronization end period of the newly added node, so that the stored file is the same as the files stored by other nodes in the target node group when the file synchronization of the newly added node is ended, the consistency of the files stored by each node in the target node group is ensured, and the reliability of file reading is improved.
In one embodiment, the file processing method further includes a step of updating the newly added node as a master node and adding a new node again to add a slave node in response to a node added to the target node group for file synchronization in response to a capacity expansion event for the target node group, where the step includes: responding to a capacity expansion event aiming at the target node group, adding nodes in the target node group, performing file synchronization aiming at the added nodes, then deactivating the master nodes and the slave nodes in the target node group, and updating the added nodes into the master nodes of the target node group; and adding nodes in the target node group again, and taking the newly added nodes as slave nodes of the target node group after performing file synchronization on the newly added nodes.
The capacity expansion event is an event for expanding the storage capacity of the target node group. The capacity expansion event may specifically be a manual trigger operation or an automatic trigger event. The manual trigger operation may be a click of an expansion function key for the target node group. The automatic triggering event may be that the target node group meets a preset condition, where the preset condition may be that the stored data percentage of any node in the target node group reaches a preset percentage, or may be that the stored data amount of any node in the target node group reaches a preset data amount.
The newly added nodes in the target node group for capacity expansion may be nodes of a newly accessed storage device, or nodes of a certain original node group after being deactivated. The storage device corresponding to the deactivated node is formatted and can be called again.
In one embodiment, the computer device may perform steps 402 through 406 for the newly added node, add the newly added node to the target node group, remove the master nodes and slave nodes in the target node group from the target node group, and update the newly added node to the master node of the target node group.
In the embodiment, by adding nodes to the target node group and storing the files stored in the current target node group to the added nodes, nodes with larger storage capacity can be added to the target node group, the files stored in the original master node and the slave node of the target node group are completely synchronized in the added nodes, and the files are ensured not to be lost; the newly added node is used as a new master node in the target node group, and then the node is newly added to add a new slave node, after the new slave node is added into the target node group, the target node group can be expanded, the problem that the target node group cannot store files due to insufficient storage space is avoided, and therefore the reliability of file storage is improved.
In an embodiment, a specific application scenario of the archive processing method is provided, as shown in fig. 5, a schematic diagram of an interaction relationship between a temporary storage node set and a node group set, where a temporary storage node belongs to the temporary storage node set, a target node group belongs to the node group set, and each temporary storage node in the temporary storage node set may communicate with each node group in the node group set; the node group set can be deployed on computer equipment, the temporary storage nodes can communicate with each node group in the node group set through the computer equipment, and the temporary storage nodes can be mounted to a cloud host to store files of cloud games on the cloud host; cloud games can run on the cloud host, a user can remotely operate the cloud host through the terminal and log in the cloud games on the cloud host through a game account, and the cloud host can also communicate with each node group in the node group set through computer equipment.
The cloud host can respond to the login operation of a user on the cloud game on the cloud host through a game account, trigger a file reading event aiming at a target node group, mount the temporary storage node to the cloud host, select the target node in a normal working state from a master node and a slave node in the target node group storing the file of the cloud game, and read the file corresponding to the game account and the cloud game from the target node.
The cloud host can respond to the file storage of the cloud game on the cloud host by a user through a game account, and the file of the game account during the current login of the game is stored in the temporary storage node; and when the game account logs out of the cloud game, the temporary storage node is not mounted to the cloud host.
The computer equipment can periodically screen the archive of the cloud game from the quick lookup table of the temporary storage node; when the files which belong to the cloud game and are not stored by the target node group are screened, an archiving event aiming at the target node group is triggered. The computer device may respond to an archive event for the target node group, store an archive of the cloud game indicated by the archive event to a master node in the target node group, and then copy the archive of the cloud game from the master node to a plurality of slave nodes in the target node group at the same time.
The computer equipment can detect the working states of the master node and the slave nodes in the target node group when a file reading event or an archiving event aiming at the target node group occurs, when the abnormal master node in the target node group is detected, the abnormal master node stops working, the abnormal master node is removed from the target node group, one slave node in a normal working state is selected from the slave nodes in the target node group, and the selected slave node is updated to the master node of the target node group; and when detecting that the slave node in the target node group is abnormal, stopping the abnormal slave node, and removing the abnormal slave node from the target node group.
The computer equipment can create a first temporary synchronization table aiming at an abnormal node when any node in a main node and a slave node in a target node group is abnormal, and when the main node in the target node group writes a file, records to be synchronized aiming at the written file are sequentially added into the first temporary synchronization table until the first temporary synchronization table is stopped; and after the abnormal nodes are recovered to be normal, replaying the abnormal nodes according to the records to be synchronized in the first temporary synchronization table in sequence so as to store the files written into the main node to the nodes recovered to be normal, stopping the first temporary synchronization table until the replay of the records to be synchronized in the first temporary synchronization table is finished, and rejoining the nodes recovered to be normal into the target node group as the slave nodes.
The computer device can respond to the newly added node event aiming at the target node group and carry out file synchronization on the newly added node indicated by the newly added node event; the file synchronization includes: creating a full synchronization table corresponding to the target node group, and adding records of files currently stored by the main node in the full synchronization table; creating a second temporary synchronization table corresponding to the newly added node indicated by the newly added node event, and adding a record to be synchronized aiming at the written file in the second temporary synchronization table in sequence when the master node in the target node group writes the file until the second temporary synchronization table is stopped; and after the archives recorded in the full-volume synchronization table are stored in the newly added node, replaying is sequentially carried out according to the records to be synchronized in the second temporary synchronization table, so that the archives written in the main node are stored in the newly added node, and the second temporary synchronization table is stopped until the replaying of the records to be synchronized in the second temporary synchronization table is finished.
The computer equipment can respond to the capacity expansion event aiming at the target node group, newly add nodes in the target node group, stop the master nodes and the slave nodes in the target node group after performing file synchronization aiming at the newly added nodes, and update the newly added nodes to the master nodes of the target node group; and adding nodes in the target node group again, and taking the newly added nodes as slave nodes of the target node group after performing file synchronization on the newly added nodes.
It should be understood that, although the steps in the flowcharts related to the embodiments as described above are sequentially displayed as indicated by arrows, the steps are not necessarily performed sequentially as indicated by the arrows. The steps are not performed in the exact order shown and described, and may be performed in other orders, unless explicitly stated otherwise. Moreover, at least a part of the steps in the flowcharts related to the embodiments described above may include multiple steps or multiple stages, which are not necessarily performed at the same time, but may be performed at different times, and the execution order of the steps or stages is not necessarily sequential, but may be performed alternately or alternately with other steps or at least a part of the steps or stages in other steps.
Based on the same inventive concept, the embodiment of the present application further provides an archive processing apparatus for implementing the above-mentioned archive processing method. The implementation scheme for solving the problem provided by the device is similar to the implementation scheme described in the above method, so the specific limitations in one or more embodiments of the file processing device provided below can refer to the limitations on the file processing method in the above, and are not described herein again.
In one embodiment, as shown in FIG. 6, there is provided an archive processing apparatus 600 comprising: a profile writing module 610 and a profile reading module 620, wherein:
a file writing module 610, configured to, when an archive event occurs for the target node group, perform a file writing operation on a first file indicated by the archive event in the target node group; the file write operation includes: the first file is stored to the master node in the target node group, and the first file is copied from the master node to the slave node in the target node group.
A file reading module 620, configured to, when a file reading event for the target node group occurs, perform a file reading operation for reading the second file indicated by the file reading event from the target node group; the file reading operation comprises the following steps: selecting a target node in a normal working state from the master node and the slave nodes in the target node group, and reading a second file from the target node; wherein the file write operation and the file read operation are mutually exclusive atomic operations.
In one embodiment, the profile write module 610 is further configured to obtain a profile type pre-configured for the target node group; periodically querying an updated archive from a temporary storage node that temporarily stores an archive of the cloud application; the updated archive belongs to the archive type and is not stored by the target node group; when the updated archive is queried, an archive event for the target node group is triggered.
In one embodiment, the archive processing apparatus 600 further includes an abnormal node recovery module, where the abnormal node recovery module is configured to, when any node in the target node group is abnormal, stop working of the abnormal node, and create a first temporary synchronization table for the abnormal node; when a master node in a target node group writes a file, sequentially adding records to be synchronized aiming at the written file in a first temporary synchronization table until the first temporary synchronization table is stopped; and after the abnormal nodes are recovered to be normal, sequentially playing back according to the records to be synchronized in the first temporary synchronization table so as to store the files written into the main node to the nodes recovered to be normal, and stopping the first temporary synchronization table until the playback of the records to be synchronized in the first temporary synchronization table is finished.
In one embodiment, the abnormal node recovery module is further configured to, when an abnormality occurs in a master node in the target node group, select a slave node in a normal operating state from the slave nodes in the target node group, and update the selected slave node as the master node of the target node group.
In one embodiment, the abnormal node recovery module is further configured to, when a slave node in the target node group is abnormal, remove the abnormal node from the target node group; and when the abnormal nodes are recovered to be normal, the nodes recovered to be normal are used as slave nodes to rejoin the target node group.
In one embodiment, the file processing apparatus 600 further includes a node adding module, configured to perform file synchronization on the added node indicated by the added node event in response to the added node event for the target node group; the file synchronization includes: creating a full synchronization table corresponding to the target node group, and adding records of files currently stored by the main node in the full synchronization table; creating a second temporary synchronization table corresponding to the newly added node indicated by the newly added node event, and adding a record to be synchronized aiming at the written record in the second temporary synchronization table when the master node in the target node group writes the file until the second temporary synchronization table is stopped; and after the archives recorded in the full-volume synchronization table are stored in the newly added node, replaying the archives according to the records to be synchronized in the second temporary synchronization table in sequence so as to store the archives written into the main node to the newly added node, and stopping the second temporary synchronization table until the replays of the records to be synchronized in the second temporary synchronization table are finished.
In one embodiment, the node adding module is further configured to add a node in the target node group in response to an expansion event for the target node group, disable the master node and the slave node in the target node group after performing file synchronization for the added node, and update the added node to the master node of the target node group; and adding nodes in the target node group again, and taking the newly added nodes as slave nodes of the target node group after performing file synchronization on the newly added nodes.
The archive processing device stores the archive to the master node and the slave node of the target node group to form a plurality of archive backups, and the archive storage reliability is high; any node in a normal state in the target node group can be used as a target node to provide file reading service, and the flexibility is high; the archive writing operation and the archive reading operation of the target node group are mutually exclusive atomic operations, and the archive writing operation and the archive reading operation cannot be performed simultaneously, so that the incomplete reading of archives is avoided, and the reliability of archive storage and reading is improved.
The modules in the above-mentioned archive processing device can be wholly or partially implemented by software, hardware and their combination. The modules can be embedded in a hardware form or independent of a processor in the computer device, and can also be stored in a memory in the computer device in a software form, so that the processor can call and execute operations corresponding to the modules.
In one embodiment, a computer device is provided, which may be a terminal, a server or a virtual host, and its internal structure diagram may be as shown in fig. 7. The computer device comprises a processor, a memory, an Input/Output (I/O) interface and a communication interface. The processor, the memory and the input/output interface are connected through a system bus, and the communication interface is connected to the system bus through the input/output interface. Wherein the processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program, and a database. The internal memory provides an environment for the operation of an operating system and computer programs in the non-volatile storage medium. The database of the computer device is used for storing the files required to be stored when the file processing method is executed. The input/output interface of the computer device is used for exchanging information between the processor and an external device. The communication interface of the computer device is used for connecting and communicating with an external terminal through a network. The computer program is executed by a processor to implement a file processing method.
Those skilled in the art will appreciate that the architecture shown in fig. 7 is merely a block diagram of some of the structures associated with the disclosed aspects and is not intended to limit the computing devices to which the disclosed aspects apply, as particular computing devices may include more or less components than those shown, or may combine certain components, or have a different arrangement of components.
In an embodiment, a computer device is provided, comprising a memory and a processor, the memory having stored therein a computer program, the processor implementing the steps of the above method embodiments when executing the computer program.
In an embodiment, a computer-readable storage medium is provided, on which a computer program is stored, which computer program, when being executed by a processor, carries out the steps of the above-mentioned method embodiments.
In an embodiment, a computer program product is provided, comprising a computer program which, when executed by a processor, carries out the steps in the method embodiments described above.
It should be noted that, the user information (including but not limited to user equipment information, user personal information, etc.) and data (including but not limited to data for analysis, stored data, displayed data, etc.) referred to in the present application are information and data authorized by the user or sufficiently authorized by each party, and the collection, use and processing of the related data need to comply with the relevant laws and regulations and standards of the relevant country and region.
It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above can be implemented by hardware instructions of a computer program, which can be stored in a non-volatile computer-readable storage medium, and when executed, can include the processes of the embodiments of the methods described above. Any reference to memory, databases, or other media used in the embodiments provided herein can include at least one of non-volatile and volatile memory. The nonvolatile Memory may include a Read-Only Memory (ROM), a magnetic tape, a floppy disk, a flash Memory, an optical Memory, a high-density embedded nonvolatile Memory, a resistive Random Access Memory (ReRAM), a Magnetic Random Access Memory (MRAM), a Ferroelectric Random Access Memory (FRAM), a Phase Change Memory (PCM), a graphene Memory, and the like. Volatile Memory can include Random Access Memory (RAM), external cache Memory, and the like. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM), among others. The databases involved in the embodiments provided herein may include at least one of relational and non-relational databases. The non-relational database may include, but is not limited to, a block chain based distributed database, and the like. The processors referred to in the embodiments provided herein may be general purpose processors, central processing units, graphics processors, digital signal processors, programmable logic devices, quantum computing based data processing logic devices, etc., without limitation.
All possible combinations of the technical features in the above embodiments may not be described for the sake of brevity, but should be considered as being within the scope of the present disclosure as long as there is no contradiction between the combinations of the technical features.
The above-mentioned embodiments only express several embodiments of the present application, and the description thereof is more specific and detailed, but not construed as limiting the scope of the present application. It should be noted that, for a person skilled in the art, several variations and modifications can be made without departing from the concept of the present application, which falls within the scope of protection of the present application. Therefore, the protection scope of the present application shall be subject to the appended claims.

Claims (10)

1. An archive processing method, characterized in that the method comprises:
when an archive event aiming at a target node group occurs, performing archive writing operation on a first archive indicated by the archive event at the target node group; the archive write operation comprises: storing the first file to a master node in the target node group, and copying the first file from the master node to a slave node in the target node group;
when a file reading event aiming at the target node group occurs, executing a file reading operation of reading a second file indicated by the file reading event from the target node group; the file reading operation comprises: selecting a target node in a normal working state from the master node and the slave nodes in the target node group, and reading the second file from the target node; wherein the archive write operation and the archive read operation are mutually exclusive atomic operations.
2. The method of claim 1, further comprising:
acquiring a file type pre-configured for a target node group;
periodically querying an updated archive from a temporary storage node that temporarily stores an archive of the cloud application; the updated profile is of the profile type and has not been stored by the target node group;
and when the updated archive is inquired, triggering an archive event aiming at the target node group.
3. The method of claim 1, further comprising:
when any node in the target node group is abnormal, the abnormal node stops working, and a first temporary synchronization table is established for the abnormal node;
when a master node in the target node group writes a file, sequentially adding records to be synchronized for the written file in the first temporary synchronization table until the first temporary synchronization table is deactivated;
and when the abnormal node is recovered to be normal, replaying the abnormal node according to the record to be synchronized in the first temporary synchronization table in sequence so as to store the file written into the main node to the node recovered to be normal, and stopping the first temporary synchronization table until the replay of the record to be synchronized in the first temporary synchronization table is finished.
4. The method of claim 3, further comprising:
and when the master node in the target node group is abnormal, selecting one slave node in a normal working state from the slave nodes in the target node group, and updating the selected slave node as the master node of the target node group.
5. The method of claim 3, further comprising:
when the slave nodes in the target node group are abnormal, the abnormal nodes are removed from the target node group;
and when the abnormal node is recovered to be normal, the node recovered to be normal is used as a slave node to rejoin the target node group.
6. The method of any of claims 1 to 5, further comprising:
responding to a newly added node event aiming at the target node group, and carrying out file synchronization on a newly added node indicated by the newly added node event; the archive synchronization comprises:
creating a full synchronization table corresponding to the target node group, and adding records of archives currently stored by the master node in the full synchronization table;
creating a second temporary synchronization table corresponding to the newly added node indicated by the newly added node event, and adding a record to be synchronized aiming at the written file in the second temporary synchronization table in sequence when the master node in the target node group writes the file until the second temporary synchronization table is stopped;
and after the files recorded in the full-volume synchronization table are stored in the newly added node, replaying the files according to the records to be synchronized in the second temporary synchronization table in sequence so as to store the files written into the main node to the newly added node, and stopping the second temporary synchronization table until the replays of the records to be synchronized in the second temporary synchronization table are finished.
7. The method of claim 6, further comprising:
responding to the capacity expansion event aiming at the target node group, adding nodes in the target node group, stopping the master nodes and the slave nodes in the target node group after carrying out file synchronization aiming at the added nodes, and updating the added nodes to be the master nodes of the target node group;
and adding nodes in the target node group again, and taking the nodes added again as slave nodes of the target node group after carrying out the file synchronization aiming at the added nodes.
8. An archive processing device, characterized in that the device comprises:
the archive writing module is used for executing archive writing operation on a first archive indicated by an archive event in a target node group when the archive event aiming at the target node group occurs; the archive write operation comprises: storing the first file to a master node in the target node group, and copying the first file from the master node to a slave node in the target node group;
the file reading module is used for executing file reading operation of reading a second file indicated by the file reading event from the target node group when the file reading event aiming at the target node group occurs; the file reading operation comprises: selecting a target node in a normal working state from the master node and the slave nodes in the target node group, and reading the second file from the target node; wherein the archive write operation and the archive read operation are mutually exclusive atomic operations.
9. A computer device comprising a memory and a processor, the memory storing a computer program, characterized in that the processor, when executing the computer program, implements the steps of the method of any of claims 1 to 7.
10. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the steps of the method of any one of claims 1 to 7.
CN202211391021.1A 2022-11-07 2022-11-07 Archive processing method and device, computer equipment and storage medium Pending CN115543919A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202211391021.1A CN115543919A (en) 2022-11-07 2022-11-07 Archive processing method and device, computer equipment and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202211391021.1A CN115543919A (en) 2022-11-07 2022-11-07 Archive processing method and device, computer equipment and storage medium

Publications (1)

Publication Number Publication Date
CN115543919A true CN115543919A (en) 2022-12-30

Family

ID=84719979

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202211391021.1A Pending CN115543919A (en) 2022-11-07 2022-11-07 Archive processing method and device, computer equipment and storage medium

Country Status (1)

Country Link
CN (1) CN115543919A (en)

Similar Documents

Publication Publication Date Title
US10261719B2 (en) Volume and snapshot replication
CN108241555B (en) Backup and recovery method and device of distributed database and server
US9645892B1 (en) Recording file events in change logs while incrementally backing up file systems
CN103238140B (en) Based on the system and method quoting management in the storage system of deduplication for easily extensible
JP5539683B2 (en) Scalable secondary storage system and method
US7257690B1 (en) Log-structured temporal shadow store
CN100472463C (en) Method and apparatus for performing operations on selected data in a storage area
US11093387B1 (en) Garbage collection based on transmission object models
CN111506251B (en) Data processing method and device, SMR storage system and storage medium
US11151030B1 (en) Method for prediction of the duration of garbage collection for backup storage systems
US10628298B1 (en) Resumable garbage collection
US10146633B2 (en) Data recovery from multiple data backup technologies
US10976942B2 (en) Versioning a configuration of data storage equipment
US10838825B2 (en) Implementing snapshot sets for consistency groups of storage volumes
CN110147203B (en) File management method and device, electronic equipment and storage medium
JPWO2010116608A1 (en) Data insertion system
CN111638995A (en) Metadata backup method, device and equipment and storage medium
CN111309245B (en) Hierarchical storage writing method and device, reading method and device and system
CN113885809B (en) Data management system and method
CN104679893A (en) Information retrieval method based on big data
CN111143116A (en) Method and device for processing bad blocks of disk
CN113253932A (en) Read-write control method and system for distributed storage system
US7600151B2 (en) RAID capacity expansion interruption recovery handling method and system
CN111400273B (en) Database capacity expansion method and device, electronic equipment and machine-readable storage medium
CN115454717B (en) Database real-time backup method and device, computer equipment and storage medium

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