Object storage multi-site synchronous alarm method, system, terminal and storage medium

Abstract

The present invention provides an object storage multi-site synchronization alarm method, system, terminal and storage medium, including: obtaining the user storage bucket information of the target site, and retrieving the source bucket information corresponding to the user storage bucket; respectively collecting all the fragmentation marks of the user storage bucket and all the fragmentation marks of the corresponding source bucket, and performing consistency comparison between the two; collecting the current state of the data synchronization process, in the completed state of the data synchronization process, if the consistency comparison result is that the two are different, generating an alarm prompt for the inconsistent user storage bucket and the corresponding source bucket; in the execution state of the data synchronization process, multiple collections of all the fragmentation marks of the user storage bucket and all the fragmentation marks of the corresponding source bucket, and generating an alarm prompt according to the update of the two marks. The present invention can monitor the synchronization status of each bucket between multiple sites, make the multi-site function more perfect and commercialized, and improve the market competitiveness of the company's distributed object storage products.

Description

Technical Field

[0001] The present invention relates to the technical field of object storage, and in particular to an object storage multi-site synchronous alarm method, system, terminal and storage medium. Background Art

[0002] Object storage is a general term used to describe methods of solving and processing discrete units. Objects will no longer have a hierarchical structure in a layer structure and are characterized by extended metadata. In object storage, a bucket is the carrier of an object, which can be understood as a "container" for storing objects, and the "container" has no upper limit on capacity. Objects are stored in buckets in a flat structure, without the concept of folders and directories. Users can choose to store objects in a single or multiple buckets. Most of the buckets used by users correspond to one or more source buckets. When users perform data operations on the buckets they use, the object storage system needs to perform data synchronization and synchronize the updated data of the user's bucket in the source bucket. Data synchronization is a key link to ensure the data security, consistency and stability of object storage.

[0003] In object storage, there is a command to check the multi-site synchronization status. This command is used to check whether all cluster objects have been synchronized. This command can only check whether the data of the site has been synchronized so far. Due to the large statistical granularity, as long as there is data written to this cluster, the command will always be displayed as being in the synchronization state. Buckets that are abnormally missed or have not been synchronized for a long time will not be displayed. Summary of the invention

[0004] In view of the above-mentioned deficiencies in the prior art, the present invention provides an object storage multi-site synchronous alarm method, system, terminal and storage medium to solve the above-mentioned technical problems.

[0005] In a first aspect, the present invention provides an object storage multi-site synchronization alarm method, comprising:

[0006] Get the user bucket information of the target site and retrieve the source bucket information corresponding to the user bucket;

[0007] Collect all shard tags of the user bucket and all shard tags of the corresponding source bucket respectively, and compare the two for consistency;

[0008] The current status of the data synchronization process is collected. When the data synchronization process is completed, if the consistency comparison result is different, an alarm prompt is generated for the inconsistent user storage bucket and the corresponding source bucket.

[0009] When the data synchronization process is in progress, all shard tags of the user bucket and all shard tags of the corresponding source bucket are collected multiple times, and an alarm is generated based on the update status of the two tags.

[0010] Furthermore, the user bucket information of the target site is obtained, and the source bucket information corresponding to the user bucket is retrieved, including:

[0011] Traversing the sites in the object storage system as target sites;

[0012] Retrieve the bucket information of all users on the target site and aggregate it into user bucket information;

[0013] Retrieve the source bucket information corresponding to each user bucket.

[0014] Furthermore, all shard tags of the user storage bucket and all shard tags of the corresponding source bucket are collected respectively, and the consistency comparison between the two is performed, including:

[0015] Save all shard tags of the user bucket to the first list;

[0016] Save all shard tags corresponding to the source bucket to the second list;

[0017] According to the mapping relationship between the user storage bucket and the corresponding source bucket, the fragmentation tags in the first list and the second list are compared for consistency.

[0018] Furthermore, when the data synchronization process is in progress, all shard tags of the user storage bucket and all shard tags of the corresponding source bucket are collected multiple times, and an alarm is generated according to the update status of the two tags, including:

[0019] When the data synchronization process is in progress, all shard tags of the user bucket and all shard tags of the corresponding source bucket are collected twice;

[0020] All the shard marks of the user storage bucket collected previously and all the shard marks of the corresponding source bucket are used as the first comparison data;

[0021] All shard marks of the user storage bucket collected later and all shard marks of the corresponding source bucket are used as second comparison data;

[0022] The consistency of the second comparison data and the first comparison data is compared to determine whether there is an incremental mark in the second comparison data relative to the first comparison data, and if there is no incremental mark, an alarm prompt is generated for the user storage bucket and the corresponding source bucket.

[0023] Furthermore, before comparing the second comparison data with the first comparison data for consistency, the method further includes:

[0024] Determine whether the source bucket information corresponding to the user bucket collected later is consistent with the source bucket information collected previously:

[0025] If yes, then a consistency comparison between the second comparison data and the first comparison data is performed;

[0026] If not, all shard tags of the user storage bucket and all shard tags of the corresponding source bucket are collected again after waiting for a specified period of time, and the update status of the two tags is obtained based on the collected tag data.

[0027] In a second aspect, the present invention provides an object storage multi-site synchronization alarm system, comprising:

[0028] An information acquisition unit, used to acquire user bucket information of a target site and retrieve source bucket information corresponding to the user bucket;

[0029] A tag comparison unit is used to collect all shard tags of the user storage bucket and all shard tags of the corresponding source bucket, and compare the two for consistency;

[0030] The first processing unit is used to collect the current state of the data synchronization process, and in the completed state of the data synchronization process, if the consistency comparison result is that the two are different, generate an alarm prompt for the inconsistent comparison of the user storage bucket and the corresponding source bucket;

[0031] The second processing unit is used to collect all the fragmentation marks of the user storage bucket and all the fragmentation marks of the corresponding source bucket for multiple times when the data synchronization process is being executed, and generate an alarm prompt according to the update status of the two marks.

[0032] Furthermore, the information acquisition unit is used to:

[0033] Traversing the sites in the object storage system as target sites;

[0034] Retrieve the bucket information of all users on the target site and aggregate it into user bucket information;

[0035] Retrieve the source bucket information corresponding to each user bucket.

[0036] Further, the label comparison unit is used for:

[0037] Save all shard tags of the user bucket to the first list;

[0038] Save all shard tags corresponding to the source bucket to the second list;

[0039] According to the mapping relationship between the user storage bucket and the corresponding source bucket, the fragmentation tags in the first list and the second list are compared for consistency.

[0040] Furthermore, the second processing unit is used for:

[0041] When the data synchronization process is in progress, all shard tags of the user bucket and all shard tags of the corresponding source bucket are collected twice;

[0042] All the shard marks of the user storage bucket collected previously and all the shard marks of the corresponding source bucket are used as the first comparison data;

[0043] All shard marks of the user storage bucket collected later and all shard marks of the corresponding source bucket are used as second comparison data;

[0044] The consistency of the second comparison data and the first comparison data is compared to determine whether there is an incremental mark in the second comparison data relative to the first comparison data, and if there is no incremental mark, an alarm prompt is generated for the user storage bucket and the corresponding source bucket.

[0045] Further, before comparing the second comparison data with the first comparison data for consistency, the second processing unit is further configured to:

[0046] Determine whether the source bucket information corresponding to the user bucket collected later is consistent with the source bucket information collected previously:

[0047] If yes, then a consistency comparison between the second comparison data and the first comparison data is performed;

[0048] If not, all shard tags of the user storage bucket and all shard tags of the corresponding source bucket are collected again after waiting for a specified period of time, and the update status of the two tags is obtained based on the collected tag data.

[0049] In a third aspect, a terminal is provided, including:

[0050] processor, memory, wherein:

[0051] The memory is used to store computer programs.

[0052] The processor is used to call and run the computer program from the memory, so that the terminal executes the above-mentioned terminal method.

[0053] According to a fourth aspect, a computer storage medium is provided, wherein the computer-readable storage medium stores instructions, and when the instructions are executed on a computer, the computer executes the methods described in the above aspects.

[0054] The beneficial effect of the present invention is that the object storage multi-site synchronization alarm method, system, terminal and storage medium provided by the present invention collect the user storage bucket information of the site of the object storage, and further retrieve the source bucket information corresponding to the user storage bucket, and then detect the user storage bucket and the corresponding source bucket that have not achieved data synchronization according to the state of the data synchronization process in the object storage system, combined with the shard mark of the user storage bucket and the shard mark of the corresponding source bucket. The present invention can monitor the synchronization status of each bucket between multiple sites, and provides an alarm function for problems such as long-term non-synchronization and slow synchronization, so that the multi-site function is more perfect and commercialized, and the market competitiveness of the company's distributed object storage products is improved.

[0055] In addition, the invention has a reliable design principle, a simple structure and a very broad application prospect. BRIEF DESCRIPTION OF THE DRAWINGS

[0056] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, for ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0057] Figure 1 is a schematic flow chart of a method according to an embodiment of the present invention.

[0058] Figure 2 is a schematic block diagram of a system according to an embodiment of the present invention.

[0059] Figure 3 A schematic diagram of the structure of a terminal provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0060] In order to enable those skilled in the art to better understand the technical solutions in the present invention, the technical solutions in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of the present invention.

[0061] The key terms appearing in the present invention are explained below.

[0062] Object storage, also known as object-based storage, is a general term used to describe an approach to addressing and processing discrete units called objects. Like files, objects contain data, but unlike files, objects are not hierarchical in a hierarchy. Each object is at the same level in a flat address space called a storage pool, and one object does not belong to another object at a lower level. Both files and objects have metadata related to the data they contain, but objects are characterized by extended metadata. Each object is assigned a unique identifier, allowing a server or end user to retrieve the object without having to know the physical address of the data. This approach helps to automate and simplify data storage in cloud computing environments. Object storage is often compared to valet parking at a fine dining restaurant. When a customer needs valet parking, he hands over the keys and receives a receipt in return. The customer does not need to know where his car is parked or how many times the waiter will move his car while he is dining. In this metaphor, the unique identifier of a storage object represents the customer's receipt. Since object storage will be spread across many nodes and the latest data is not always available, this will become a problem of eventual consistency of object storage. All data storage involves three elements referred to as CAP: consistency, availability, and partitioning. If only a write operation is performed to change an object, but someone is accessing the object from another node. The nodes may be in different physical locations because object storage supports a large geographical expansion. New users may be reading the object, but it is an old version. This is the eventual consistency problem of object storage, and there is no timely synchronization at this time. This will become a problem, especially when using object storage for collaboration. Manufacturers have done a good job of ensuring the consistency of object storage, such as Joyent and its Manta storage service, which will not support reading old content once the object is changed. You have to wait, but what you read will be consistent.

[0063] The Ceph Object Gateway stores bucket index data in the index_pool pool. The default value is default.rgw.buckets.index. Sometimes, users like to put multiple objects (hundreds of thousands to millions of objects) in a bucket. If you do not use the gateway management interface to set a quota for the maximum objects in each bucket, the bucket index may suffer severe performance degradation when users put a large number of objects in a bucket. In Ceph 0.94, the bucket index can be sharded to prevent performance bottlenecks when a large number of objects are allowed in each bucket. The rgw_override_bucket_index_max_shards setting allows you to set the maximum number of shards per bucket. The default value is 0, which means that bucket index sharding is turned off by default.

[0064] Figure 1 is a schematic flow chart of a method according to an embodiment of the present invention. Figure 1 The execution subject may be an object storage multi-site synchronization alarm system.

[0065] like Figure 1 As shown, the method includes:

[0066] Step 110, obtaining the user bucket information of the target site, and retrieving the source bucket information corresponding to the user bucket;

[0067] Step 120, respectively collect all the shard tags of the user storage bucket and all the shard tags of the corresponding source bucket, and compare the two for consistency;

[0068] Step 130, collecting the current state of the data synchronization process, and in the completed state of the data synchronization process, if the consistency comparison result is that the two are different, generating an alarm prompt for the inconsistent comparison of the user storage bucket and the corresponding source bucket;

[0069] Step 140, while the data synchronization process is being executed, all shard marks of the user storage bucket and all shard marks of the corresponding source bucket are collected multiple times, and an alarm prompt is generated according to the update status of the two marks.

[0070] To facilitate understanding of the present invention, the object storage multi-site synchronization alarm method provided by the present invention is further described below based on the principle of the object storage multi-site synchronization alarm method of the present invention and the process of alarming the object storage multi-site synchronization in the embodiment.

[0071] This embodiment obtains the source bucket of the current bucket on the current site, compares the last marker of the corresponding bucket shard, and starts a special thread during the object storage system startup process to perform the following alarm processing. Specifically, the object storage multi-site synchronization alarm method includes:

[0072] S1. Obtain the user bucket information of the target site, and retrieve the source bucket information corresponding to the user bucket.

[0073] Traverse the sites in the object storage system as the target site; retrieve the bucket information of all users on the target site and summarize it as user bucket information; retrieve the source bucket information corresponding to each user bucket.

[0074] Specifically, all buckets under all users on the current site are obtained, all source buckets of each user bucket are obtained, and a user bucket has more than one source bucket. A mapping relationship between the user bucket and the corresponding source bucket information is constructed.

[0075] S2. Collect all shard tags of the user storage bucket and all shard tags of the corresponding source bucket respectively, and compare the two for consistency.

[0076] All shard tags of the user bucket are saved in the first list; all shard tags of the corresponding source bucket are saved in the second list; and according to the mapping relationship between the user bucket and the corresponding source bucket, the shard tags in the first list and the second list are compared for consistency.

[0077] Based on the user bucket information and the corresponding source bucket information obtained in step S1, all shard marks of the user bucket and all shard marks of the corresponding source bucket are collected respectively, wherein the shard mark Marker is the mark bit of the synchronized object.

[0078] For ease of comparison, the shard tags of all user buckets are saved in the first list, and the shard tags of all source buckets are saved in the second list. According to the mapping relationship between user buckets and source buckets, the shard tags in the first list and the second list are compared for consistency.

[0079] S3. The current state of the data synchronization process is collected. When the data synchronization process is completed, if the consistency comparison result is different, an alarm prompt is generated for the inconsistent user storage bucket and the corresponding source bucket.

[0080] Since data is continuously updated during the data synchronization process, it is necessary to determine whether data synchronization is currently being performed.

[0081] If the data synchronization process is not currently being executed, if the shard marks of the user bucket and the corresponding source bucket are consistent, it means that the user bucket and the corresponding source bucket have completed data synchronization. If the shard marks of the user bucket and the corresponding source bucket are inconsistent, it means that the user bucket and the corresponding source bucket have not completed data synchronization, and a synchronization alarm prompt for the user bucket and the corresponding source bucket needs to be generated.

[0082] S4. When the data synchronization process is in progress, all shard tags of the user storage bucket and all shard tags of the corresponding source bucket are collected multiple times, and an alarm is generated according to the update status of the two tags.

[0083] When the data synchronization process is in progress, all shard tags of the user bucket and all shard tags of the corresponding source bucket are collected twice.

[0084] Determine whether the source bucket information corresponding to the user storage bucket collected later is consistent with the source bucket information collected last time: if so, perform a consistency comparison between the second comparison data and the first comparison data; if not, wait for a specified period of time and collect all the shard tags of the user storage bucket and all the shard tags of the corresponding source bucket again, and obtain the update status of the two tags based on the collected tag data.

[0085] All the shard marks of the user storage bucket collected last time and all the shard marks of the corresponding source bucket are used as the first comparison data; all the shard marks of the user storage bucket collected later and all the shard marks of the corresponding source bucket are used as the second comparison data; the consistency of the second comparison data and the first comparison data is compared to determine whether there is an incremental mark in the second comparison data relative to the first comparison data, and if there is no incremental mark, an alarm prompt is generated for the user storage bucket and the corresponding source bucket.

[0086] If the data synchronization process in the object storage system is not completed and is in the execution state, the data is constantly updated, so you need to execute the following method:

[0087] After obtaining the user bucket information and the corresponding source bucket information once, and collecting all the shard tags of the user bucket and all the shard tags of the corresponding source bucket, obtain all the source buckets of the user bucket again. If it is found that the corresponding source bucket of a user bucket is inconsistent with the source bucket obtained last time, no comparison will be made this time, and the source bucket information of the user bucket will be updated, and the marker records of the user bucket and the source bucket will be updated, and wait for the next comparison.

[0088] If the source bucket corresponding to the user bucket is consistent with the source bucket obtained last time, the marker pair obtained this time is compared with the marker pair obtained last time (mainly comparing whether the incremental markers of the local records obtained twice have changed, because the markers of the source bucket shard may change with new writes). If the two markers are inconsistent, it means that the bucket shard is being synchronized. If the two markers are consistent, an alarm is directly issued.

[0089] The alarm information generated in steps S3 and S4 is directly written to the disk, waiting for query by the upper-layer software.

[0090] The present invention can monitor the synchronization status of each bucket between multiple sites, and provides an alarm function for problems such as long-term asynchrony and slow synchronization, so as to make the multi-site function more complete and commercialized, and improve the market competitiveness of the company's distributed object storage products.

[0091] The specific execution process of this embodiment is as follows:

[0092] 1. Get all buckets under all users on the current site.

[0093] 2. Get all source buckets for each bucket. A bucket may have more than one source bucket.

[0094] 3. Compare the markers of each bucket shard of the current bucket and the source bucket. If the markers are the same, the synchronization is normal.

[0095] 4. If the markers are different, determine whether synchronization is in progress. If synchronization is completed, issue an alarm directly. If synchronization is still in progress, obtain all source buckets of the current bucket again. If it is found that it is inconsistent with the source bucket obtained last time, no comparison will be made this time. The source bucket information of the current bucket will be updated, and the marker records of the current bucket and the source bucket will be updated, waiting for the next comparison.

[0096] If it is consistent with the source bucket obtained last time, the marker pair obtained this time is compared with the marker pair obtained last time (mainly comparing whether the incremental markers of the local records obtained twice have changed, because the markers of the source bucket shard may change with new writes). If the two markers are inconsistent, it means that the bucket shard is being synchronized. If the two markers are consistent, an alarm is directly issued.

[0097] 5. The alarm information is directly written to the disk and waits for the management software to query and display.

[0098] like Figure 2 As shown, the system 200 includes:

[0099] The information acquisition unit 210 is used to acquire the user bucket information of the target site and retrieve the source bucket information corresponding to the user bucket;

[0100] The tag comparison unit 220 is used to collect all the shard tags of the user storage bucket and all the shard tags of the corresponding source bucket, and compare the two for consistency;

[0101] The first processing unit 230 is used to collect the current state of the data synchronization process, and in the completed state of the data synchronization process, if the consistency comparison result is that the two are different, generate an alarm prompt for comparing the inconsistent user storage bucket and the corresponding source bucket;

[0102] The second processing unit 240 is used to collect all the fragmentation marks of the user storage bucket and all the fragmentation marks of the corresponding source bucket for multiple times when the data synchronization process is being executed, and generate an alarm prompt according to the update status of the two marks.

[0103] Optionally, as an embodiment of the present invention, the information acquisition unit is used to:

[0104] Traversing the sites in the object storage system as target sites;

[0105] Retrieve the bucket information of all users on the target site and aggregate it into user bucket information;

[0106] Retrieve the source bucket information corresponding to each user bucket.

[0107] Optionally, as an embodiment of the present invention, the label comparison unit is used to:

[0108] Save all shard tags of the user bucket to the first list;

[0109] Save all shard tags corresponding to the source bucket to the second list;

[0110] According to the mapping relationship between the user storage bucket and the corresponding source bucket, the fragmentation tags in the first list and the second list are compared for consistency.

[0111] Optionally, as an embodiment of the present invention, the second processing unit is used for:

[0112] When the data synchronization process is in progress, all shard tags of the user bucket and all shard tags of the corresponding source bucket are collected twice;

[0113] All the shard marks of the user storage bucket collected previously and all the shard marks of the corresponding source bucket are used as the first comparison data;

[0114] All shard marks of the user storage bucket collected later and all shard marks of the corresponding source bucket are used as second comparison data;

[0115] The consistency of the second comparison data and the first comparison data is compared to determine whether there is an incremental mark in the second comparison data relative to the first comparison data, and if there is no incremental mark, an alarm prompt is generated for the user storage bucket and the corresponding source bucket.

[0116] Figure 3 The present invention provides a schematic diagram of the structure of a terminal 300 provided in an embodiment of the present invention. The terminal 300 can be used to execute the object storage multi-site synchronization alarm method provided in an embodiment of the present invention.

[0117] The terminal 300 may include: a processor 310, a memory 320 and a communication unit 330. These components communicate via one or more buses. Those skilled in the art will appreciate that the server structure shown in the figure does not limit the present invention, and it may be a bus structure or a star structure, and may include more or fewer components than shown in the figure, or combine certain components, or arrange the components differently.

[0118] The memory 320 can be used to store the execution instructions of the processor 310, and the memory 320 can be implemented by any type of volatile or non-volatile storage terminal or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic disk or optical disk. When the execution instructions in the memory 320 are executed by the processor 310, the terminal 300 can perform some or all of the steps in the following method embodiments.

[0119] The processor 310 is the control center of the storage terminal, and uses various interfaces and lines to connect various parts of the entire electronic terminal. It runs or executes software programs and / or modules stored in the memory 320, and calls data stored in the memory to perform various functions of the electronic terminal and / or process data. The processor can be composed of an integrated circuit (IC), for example, it can be composed of a single packaged IC, or it can be composed of a plurality of packaged ICs with the same or different functions. For example, the processor 310 can include only a central processing unit (CPU). In the embodiment of the present invention, the CPU can be a single computing core or multiple computing cores.

[0120] The communication unit 330 is used to establish a communication channel so that the storage terminal can communicate with other terminals, receive user data sent by other terminals or send user data to other terminals.

[0121] The present invention also provides a computer storage medium, wherein the computer storage medium may store a program, and when the program is executed, the program may include some or all of the steps in each embodiment provided by the present invention. The storage medium may be a magnetic disk, an optical disk, a read-only memory (ROM) or a random access memory (RAM).

[0122] Therefore, the present invention collects the user bucket information of the object storage site, and further retrieves the source bucket information corresponding to the user bucket, and then detects the user bucket and the corresponding source bucket that have not achieved data synchronization based on the state of the data synchronization process in the object storage system, combined with the shard mark of the user bucket and the shard mark of the corresponding source bucket. The present invention can monitor the synchronization status of each bucket between multiple sites, and provides an alarm function for problems such as long-term asynchrony and slow synchronization, so that the multi-site function is more perfect and commercialized, and the market competitiveness of the company's distributed object storage products is improved. The technical effects that can be achieved by this embodiment can be found in the description above, and will not be repeated here.

[0123] Those skilled in the art can clearly understand that the technology in the embodiments of the present invention can be implemented by means of software plus a necessary general hardware platform. Based on this understanding, the technical solution in the embodiments of the present invention, in essence or in other words, the part that contributes to the prior art, can be embodied in the form of a software product, which is stored in a storage medium such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a disk or an optical disk, and other media that can store program codes, including several instructions for enabling a computer terminal (which can be a personal computer, a server, or a second terminal, a network terminal, etc.) to perform all or part of the steps of the methods described in each embodiment of the present invention.

[0124] In this specification, the same or similar parts between the various embodiments can be referred to each other. In particular, for the terminal embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the description in the method embodiment.

[0125] In the several embodiments provided by the present invention, it should be understood that the disclosed systems and methods can be implemented in other ways. For example, the system embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of systems or units, which can be electrical, mechanical or other forms.

[0126] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0127] In addition, each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0128] Although the present invention has been described in detail by referring to the accompanying drawings and in combination with the preferred embodiments, the present invention is not limited thereto. Without departing from the spirit and essence of the present invention, a person of ordinary skill in the art may make various equivalent modifications or substitutions to the embodiments of the present invention, and these modifications or substitutions shall be within the scope of the present invention. Any person skilled in the art who is familiar with the present technical field can easily think of changes or substitutions within the technical scope disclosed by the present invention, and all of these shall be within the scope of protection of the present invention. Therefore, the scope of protection of the present invention shall be subject to the scope of protection of the claims.

Claims

1. A method for synchronous alarming of object storage multiple sites, characterized in that: include: Get the user bucket information of the target site and retrieve the source bucket information corresponding to the user bucket; Collect all shard tags of the user bucket and all shard tags of the corresponding source bucket respectively, and compare the two for consistency; The current status of the data synchronization process is collected. When the data synchronization process is completed, if the consistency comparison result is different, an alarm prompt is generated for the inconsistent user storage bucket and the corresponding source bucket. When the data synchronization process is in progress, all shard tags of the user bucket and all shard tags of the corresponding source bucket are collected multiple times, and an alarm is generated based on the update status of the two tags; When the data synchronization process is in progress, all shard tags of the user bucket and all shard tags of the corresponding source bucket are collected multiple times, and alarm prompts are generated based on the update status of the two tags, including: When the data synchronization process is in progress, all shard tags of the user bucket and all shard tags of the corresponding source bucket are collected twice; All the shard marks of the user storage bucket collected previously and all the shard marks of the corresponding source bucket are used as the first comparison data; All shard marks of the user storage bucket collected later and all shard marks of the corresponding source bucket are used as second comparison data; The consistency of the second comparison data and the first comparison data is compared to determine whether there is an incremental mark in the second comparison data relative to the first comparison data, and if there is no incremental mark, an alarm prompt is generated for the user storage bucket and the corresponding source bucket.

2. The method according to claim 1, characterized in that: Get the user bucket information of the target site and retrieve the source bucket information corresponding to the user bucket, including: Traversing the sites in the object storage system as target sites; Retrieve the bucket information of all users on the target site and aggregate it into user bucket information; Retrieve the source bucket information corresponding to each user bucket.

3. The method according to claim 1, characterized in that: Collect all the shard tags of the user bucket and all the shard tags of the corresponding source bucket respectively, and compare the two for consistency, including: Save all shard tags of the user bucket to the first list; Save all shard tags corresponding to the source bucket to the second list; According to the mapping relationship between the user storage bucket and the corresponding source bucket, the fragmentation tags in the first list and the second list are compared for consistency.

4. The method according to claim 1, characterized in that: Before comparing the second comparison data with the first comparison data for consistency, the method further includes: Determine whether the source bucket information corresponding to the user bucket collected later is consistent with the source bucket information collected previously: If yes, then a consistency comparison between the second comparison data and the first comparison data is performed; If not, all shard tags of the user bucket and all shard tags of the corresponding source bucket are collected again after waiting for a specified period of time, and the update status of the two tags is obtained based on the collected tag data.

5. An object storage multi-site synchronization alarm system, characterized in that: include: An information acquisition unit, used to acquire user bucket information of a target site and retrieve source bucket information corresponding to the user bucket; A tag comparison unit is used to collect all shard tags of the user storage bucket and all shard tags of the corresponding source bucket, and compare the two for consistency; The first processing unit is used to collect the current state of the data synchronization process, and in the completed state of the data synchronization process, if the consistency comparison result is that the two are different, generate an alarm prompt for the inconsistent comparison of the user storage bucket and the corresponding source bucket; The second processing unit is used to collect all the shard marks of the user storage bucket and all the shard marks of the corresponding source bucket for multiple times when the data synchronization process is in execution, and generate an alarm prompt according to the update status of the two marks; When the data synchronization process is in progress, all shard tags of the user bucket and all shard tags of the corresponding source bucket are collected multiple times, and alarm prompts are generated based on the update status of the two tags, including: When the data synchronization process is in progress, all shard tags of the user bucket and all shard tags of the corresponding source bucket are collected twice; All the shard marks of the user storage bucket collected previously and all the shard marks of the corresponding source bucket are used as the first comparison data; All shard marks of the user storage bucket collected later and all shard marks of the corresponding source bucket are used as second comparison data; The consistency of the second comparison data and the first comparison data is compared to determine whether there is an incremental mark in the second comparison data relative to the first comparison data, and if there is no incremental mark, an alarm prompt is generated for the user storage bucket and the corresponding source bucket.

6. The system according to claim 5, characterized in that The information acquisition unit is used for: Traversing the sites in the object storage system as target sites; Retrieve the bucket information of all users on the target site and aggregate it into user bucket information; Retrieve the source bucket information corresponding to each user bucket.

7. The system according to claim 5, characterized in that The label comparison unit is used for: Save all shard tags of the user bucket to the first list; Save all shard tags corresponding to the source bucket to the second list; According to the mapping relationship between the user storage bucket and the corresponding source bucket, the fragmentation tags in the first list and the second list are compared for consistency.

8. A terminal, characterized in that: include: processor; A memory for storing execution instructions of the processor; The processor is configured to execute the method according to any one of claims 1 to 4.

9. A computer-readable storage medium storing a computer program, characterized in that: When the program is executed by a processor, the method according to any one of claims 1 to 4 is implemented.

Images