Data reading method and device, electronic equipment and storage medium

Abstract

The invention relates to a data reading method and device, electronic equipment and a storage medium. The method comprises the following steps: receiving a data reading request, wherein the data reading request comprises index information of a target object; acquiring a synchronization state of the target object; in response to the fact that the first synchronization is not completed, determining the main site as a target site, and determining the first local storage bucket as a target data address; reading the target object data from the first local storage bucket according to the index information; in response to the completion of the first synchronization, obtaining a deletion state of the target object and a deletion strategy of the object storage system; determining a target site and a target data address corresponding to the target site according to the deletion strategy and the deletion state; and reading the target object data from the target data address of the target site according to the index information. By adopting the method, it can be ensured that data obtained by a user on different sites are always kept consistent and are objects of the latest version.

Description

Technical Field

[0001] The present application relates to the field of object storage technology, and in particular to a data reading method, device, electronic device and storage medium. Background Art

[0002] With the rapid development of cloud computing technology and the advent of the big data era, distributed object storage services with the characteristics of security, reliability, elastic capacity, ease of use, high performance, and low cost have been widely used in enterprise application systems. In order to enhance user experience, current object storage service providers achieve high availability of the system through asynchronous replication of multiple copies of data. Among them, asynchronous replication technology: focuses on availability. When a user requests to update data, the primary site can respond to the user directly after processing the request without waiting for the slave site to complete synchronization. That is, the slave site will synchronize data asynchronously, and the user's update operation will not be blocked due to the failure of the slave site to complete data synchronization.

[0003] This method ensures the availability of the system, but when data is not synchronized between sites, the data obtained by users on different sites may be inconsistent or outdated. This problem will cause trouble to users and greatly reduce user satisfaction.

[0004] Therefore, there is an urgent need to propose a data reading method, device, electronic device and storage medium that can ensure that the data obtained by users on different sites is always consistent and the latest version of the object. Summary of the invention

[0005] Based on this, it is necessary to provide a data reading method, device, electronic device and storage medium for the above technical problems, which can ensure that the data obtained by users on different sites is always consistent and the latest version of the object.

[0006] In a first aspect, a data reading method is provided, which is applied to an object storage system, wherein the object storage system includes a master site and a slave site, and the master site includes a first local storage bucket. The method includes:

[0007] receiving a data read request, wherein the data read request includes index information of a target object;

[0008] Obtain the synchronization status of the target object between the master site and the slave site, where the synchronization status includes the first synchronization completed and the first synchronization incomplete;

[0009] In response to the synchronization status being that the first synchronization is not completed, determining the primary site as the target site, and determining the first local storage bucket as the target data address corresponding to the target site;

[0010] Reading target object data from the first local storage bucket according to the index information to respond to the data read request;

[0011] In response to the synchronization status being that the first synchronization is completed, obtaining a deletion status of the target object and a deletion policy of the object storage system;

[0012] Determine the target site and the target data address corresponding to the target site according to the deletion policy and the deletion status;

[0013] The target object data is read from the target data address of the target site according to the index information in response to the data read request.

[0014] In one embodiment, determining a target site and a target data address corresponding to the target site according to a deletion policy and a deletion status includes:

[0015] Determine a first target metadata address of the master site and a second target metadata address of the slave site according to the deletion policy and the deletion status;

[0016] Reading first target object metadata from a first target metadata address according to the index information, and reading second target object metadata from a second target metadata address, wherein the first target object metadata includes a first modification time of the target object, and the second target object metadata includes a second modification time of the target object;

[0017] Compare the first modification time with the second modification time to obtain a time comparison result;

[0018] In response to the first modification time being later than the second modification time, taking the primary site as the target site, and determining a target data address corresponding to the primary site according to a deletion policy and a deletion status;

[0019] In response to the first modification time being earlier than the second modification time, the slave site is used as the target site, and the target data address corresponding to the slave site is determined according to the deletion policy and the deletion status.

[0020] In one embodiment, the slave site includes a second local storage bucket, and determining the target site and the target data address corresponding to the target site according to the deletion policy and the deletion status includes:

[0021] In response to the deletion policy being synchronous deletion and the target object not being deleted in both the primary site and the secondary site, determining the first local storage bucket as the first target metadata address, and determining the second local storage bucket as the second target metadata address;

[0022] Reading the first target object metadata from the first local storage bucket according to the index information, and reading the second target object metadata from the second local storage bucket;

[0023] Compare the first modification time with the second modification time to obtain a time comparison result;

[0024] In response to the first modification time being later than the second modification time, determining the primary site as the target site and determining the first local storage bucket as the target data address;

[0025] Reading target object data from the first local storage bucket according to the index information to respond to the data read request;

[0026] In response to the first modification time being earlier than the second modification time, determining the slave site as the target site and determining the second local storage bucket as the target data address;

[0027] The target object data is read from the second local storage bucket according to the index information to respond to the data read request.

[0028] In one embodiment, the master site further includes a first secondary storage bucket, the slave site includes a second local storage bucket and a second secondary storage bucket, and determining the target site and the target data address corresponding to the target site according to the deletion policy and the deletion status includes:

[0029] In response to the deletion policy being hierarchical deletion, and the target object being deleted in the primary site but not deleted in the secondary site, determining the first local storage bucket as the first target metadata address, and determining the second local storage bucket as the second target metadata address;

[0030] Reading the first target object metadata from the first local storage bucket according to the index information, and reading the second target object metadata from the second local storage bucket;

[0031] Compare the first modification time with the second modification time to obtain a time comparison result;

[0032] In response to the first modification time being later than the second modification time, determining the primary site as the target site, and determining the first secondary storage bucket as the target data address corresponding to the primary site;

[0033] Reading target object data from the first secondary storage bucket according to the index information to respond to the data read request;

[0034] In response to the first modification time being earlier than the second modification time, determining the slave site as the target site, and determining the second local storage bucket as the target data address corresponding to the slave site;

[0035] The target object data is read from the second local storage bucket according to the index information to respond to the data read request.

[0036] In one embodiment, the master site further includes a first secondary storage bucket, the slave site includes a second local storage bucket and a second secondary storage bucket, and determining the target site and the target data address corresponding to the target site according to the deletion policy and the deletion status includes:

[0037] In response to the deletion policy being hierarchical deletion and the target object being deleted in both the primary site and the secondary site, determining the first local storage bucket as a first target metadata address, and determining the second local storage bucket as a second target metadata address;

[0038] Reading the first target object metadata from the first local storage bucket according to the index information, and reading the second target object metadata from the second local storage bucket;

[0039] Compare the first modification time with the second modification time to obtain a time comparison result;

[0040] In response to the first modification time being later than the second modification time, determining the primary site as the target site, and determining the first secondary storage bucket as the target data address corresponding to the primary site;

[0041] Reading target object data from the first secondary storage bucket according to the index information to respond to the data read request;

[0042] In response to the first modification time being earlier than the second modification time, determining the slave site as the target site, and determining the second secondary storage bucket as the target data address corresponding to the slave site;

[0043] The target object data is read from the second secondary storage bucket according to the index information to respond to the data read request.

[0044] In one embodiment, the master site further includes a first secondary storage bucket, the slave site includes a second local storage bucket and a second secondary storage bucket, and determining the target site and the target data address corresponding to the target site according to the deletion policy and the deletion status includes:

[0045] In response to the deletion policy being archive deletion, and the target object being deleted in the primary site but not deleted in the secondary site, determining the first secondary storage bucket as the first target metadata address, and determining the second local storage bucket as the second target metadata address;

[0046] Reading the first target object metadata from the first secondary storage bucket according to the index information, and reading the second target object metadata from the second local storage bucket;

[0047] Compare the first modification time with the second modification time to obtain a time comparison result;

[0048] In response to the first modification time being later than the second modification time, determining the primary site as the target site, and determining the first secondary storage bucket as the target data address corresponding to the primary site;

[0049] Reading target object data from the first secondary storage bucket according to the index information to respond to the data read request;

[0050] In response to the first modification time being earlier than the second modification time, determining the slave site as the target site, and determining the second local storage bucket as the target data address corresponding to the slave site;

[0051] The target object data is read from the second local storage bucket according to the index information to respond to the data read request.

[0052] In one embodiment, the master site further includes a first secondary storage bucket, the slave site includes a second local storage bucket and a second secondary storage bucket, and determining the target site and the target data address corresponding to the target site according to the deletion policy and the deletion status includes:

[0053] In response to the deletion policy being archive deletion and the target object being deleted in both the primary site and the secondary site, determining the first secondary storage bucket as a first target metadata address, and determining the second secondary storage bucket as a second target metadata address;

[0054] Reading the first target object metadata from the first secondary storage bucket according to the index information, and reading the second target object metadata from the second secondary storage bucket;

[0055] Compare the first modification time with the second modification time to obtain a time comparison result;

[0056] In response to the first modification time being later than the second modification time, determining the primary site as the target site, and determining the first secondary storage bucket as the target data address corresponding to the primary site;

[0057] Reading target object data from the first secondary storage bucket according to the index information to respond to the data read request;

[0058] In response to the first modification time being earlier than the second modification time, determining the slave site as the target site, and determining the second secondary storage bucket as the target data address corresponding to the slave site;

[0059] The target object data is read from the second secondary storage bucket according to the index information to respond to the data read request.

[0060] In a second aspect, a data reading device is provided, the device comprising:

[0061] A receiving module, the receiving module is used to receive a data reading request, wherein the data reading request includes index information of a target object;

[0062] A first acquisition module, the first acquisition module is used to acquire the synchronization status of the target object between the master site and the slave site, wherein the synchronization status includes the first synchronization completed and the first synchronization incomplete;

[0063] a first determination module, the first determination module being used to determine the primary site as the target site and the first local storage bucket as the target data address in response to the synchronization status being that the first synchronization is not completed;

[0064] A first reading module, the first reading module is used to read the target object data from the first local storage bucket according to the index information to respond to the data reading request;

[0065] A second acquisition module, the second acquisition module is used to obtain a deletion policy of the object storage system and a deletion status of the target object in response to the synchronization status being that the first synchronization is completed;

[0066] A second determination module, the second determination module is used to determine the target site and the target data address corresponding to the target site according to the deletion policy and the deletion status;

[0067] The second reading module is used to read the target object data from the target data address on the target site according to the index information to respond to the data reading request.

[0068] In a third aspect, an electronic device is provided, comprising one or more processors; and a memory associated with the one or more processors, the memory being used to store program instructions, which, when read and executed by the one or more processors, execute the steps of any one of the methods in the first aspect described above.

[0069] In a fourth aspect, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the steps of any one of the methods in the first aspect are performed.

[0070] In a fifth aspect, a computer program product is provided, comprising a computer program, which, when executed by a processor, implements the steps of any one of the methods in the first aspect.

[0071] The above-mentioned data reading method, device, electronic device and storage medium, when the synchronization status is that the first synchronization is not completed, takes the main site as the target site and the first local storage bucket as the target data address corresponding to the target site; when the synchronization status is that the first synchronization is completed, determines the target site and the target data address corresponding to the target site according to the deletion policy and the deletion status; reads the target object data from the target data address of the target site according to the index information to respond to the data reading request, so that the data obtained by the user on different sites is always consistent and is the latest version of the object. BRIEF DESCRIPTION OF THE DRAWINGS

[0072] Figure 1 A schematic diagram of a flow chart of a data reading method in an embodiment;

[0073] Figure 2 This is a flowchart of a data reading method when the deletion strategy is synchronous deletion;

[0074] Figure 3 This is a flowchart of a data reading method when the first synchronization is completed and the deletion policy is hierarchical deletion;

[0075] Figure 4 This is a flowchart of a data reading method when the first synchronization is completed and the deletion policy is archive deletion;

[0076] Figure 5 is a structural block diagram of a data reading device in one embodiment;

[0077] Figure 6 FIG. 4 is a diagram showing the internal structure of an electronic device in one embodiment. DETAILED DESCRIPTION

[0078] In order to make the purpose, technical solution and advantages of the present application more clearly understood, the present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0079] Embodiment 1

[0080] In one embodiment, Figure 1 , Figure 2 As shown, a data reading method is provided, which is applied to an object storage system, the object storage system includes a master site and a slave site, the master site includes a first local storage bucket, and the method includes:

[0081] receiving a data read request, wherein the data read request includes index information of a target object;

[0082] Obtain the synchronization status of the target object between the master site and the slave site, where the synchronization status includes the first synchronization completed and the first synchronization incomplete;

[0083] In response to the synchronization status being that the first synchronization is not completed, determining the primary site as the target site, and determining the first local storage bucket as the target data address corresponding to the target site;

[0084] Reading target object data from the first local storage bucket according to the index information to respond to the data read request;

[0085] In response to the synchronization status being that the first synchronization is completed, obtaining a deletion status of the target object and a deletion policy of the object storage system;

[0086] Determine the target site and the target data address corresponding to the target site according to the deletion policy and the deletion status;

[0087] The target object data is read from the target data address of the target site according to the index information in response to the data read request.

[0088] Specifically, the site that receives the data read request may be the primary site or the secondary site. When the synchronization status is that the first synchronization is not completed, the deletion policy will not be triggered at this time, and if the target object data is not found in the first local storage bucket, the user is prompted that the data reading has failed. When the synchronization status is that the first synchronization is not completed, the primary site is used as the target site, and the first local storage bucket is used as the target data address corresponding to the target site; when the synchronization status is that the first synchronization is completed, the target site and the target data address corresponding to the target site are determined according to the deletion policy and deletion status; the target object data is read from the target data address of the target site according to the index information to respond to the data read request, so that the data obtained by the user on different sites is always consistent and the latest version of the object.

[0089] Furthermore, before receiving a data read request, the method further includes: in response to receiving a user creation request, creating a user on the primary site and / or the secondary site; in response to receiving a bucket creation request, creating a storage bucket under the user of the primary site and / or the secondary site; in response to receiving a bucket creation success signal, uploading a storage object to the storage bucket of the primary site and / or the secondary site. The storage bucket includes a local storage bucket and a secondary storage bucket, and the storage object includes a target object.

[0090] In addition, you can configure the lifecycle management of the storage bucket, and set the back-to-source function for the primary site and the slave site, which can read data from the secondary storage bucket of the corresponding site. The lifecycle management configuration includes a hierarchical deletion strategy: copy the object data and object metadata to the secondary storage bucket of the corresponding site, and then delete the object data in the local storage bucket, and only retain the object metadata and the object's index information locally; and an archive deletion strategy: archive the object data, object metadata, and the object's index information to the secondary storage bucket of the corresponding site, and then delete the object data, object metadata, and the object's index information in the local storage bucket.

[0091] In one embodiment, determining a target site and a target data address corresponding to the target site according to a deletion policy and a deletion status includes:

[0092] Determine a first target metadata address of the master site and a second target metadata address of the slave site according to the deletion policy and the deletion status;

[0093] Reading first target object metadata from a first target metadata address according to the index information, and reading second target object metadata from a second target metadata address, wherein the first target object metadata includes a first modification time of the target object, and the second target object metadata includes a second modification time of the target object;

[0094] Compare the first modification time with the second modification time to obtain a time comparison result;

[0095] In response to the first modification time being later than the second modification time, taking the primary site as the target site, and determining a target data address corresponding to the primary site according to a deletion policy and a deletion status;

[0096] In response to the first modification time being earlier than the second modification time, the slave site is used as the target site, and the target data address corresponding to the slave site is determined according to the deletion policy and the deletion status.

[0097] Specifically, the target metadata address of each site is determined according to the deletion policy and the deletion status; the first modification time and the second modification time are obtained according to the target metadata address; the target site is determined by comparing the first modification time and the second modification time, so that the target object data is the latest version, so as to determine the target data address corresponding to the slave site according to the deletion policy and the deletion status.

[0098] In one embodiment, Figure 2 As shown, the slave site includes a second local storage bucket, and according to the deletion policy and the deletion status, the target site and the target data address corresponding to the target site are determined, including:

[0099] In response to the deletion policy being synchronous deletion and the target object not being deleted in both the primary site and the secondary site, determining the first local storage bucket as the first target metadata address, and determining the second local storage bucket as the second target metadata address;

[0100] Reading the first target object metadata from the first local storage bucket according to the index information, and reading the second target object metadata from the second local storage bucket;

[0101] Compare the first modification time with the second modification time to obtain a time comparison result;

[0102] In response to the first modification time being later than the second modification time, determining the primary site as the target site and determining the first local storage bucket as the target data address;

[0103] Reading target object data from the first local storage bucket according to the index information to respond to the data read request;

[0104] In response to the first modification time being earlier than the second modification time, determining the slave site as the target site and determining the second local storage bucket as the target data address;

[0105] The target object data is read from the second local storage bucket according to the index information to respond to the data read request.

[0106] Specifically, synchronous deletion can also be understood as the primary site and the slave site are not configured with the back-to-source function. When the deletion policy is synchronous deletion and the target object has not been deleted in both the primary site and the slave site, the first modification time and the second modification time in the first local storage bucket and the second local storage bucket are compared to determine the target site; when the slave site is the target site, the target object data in the second local storage bucket is searched and returned; when the primary site is the target site, the target object data in the first local bucket is searched and returned, so that the data obtained by the user on different sites is always consistent and is the latest version of the object.

[0107] In one embodiment, Figure 3 As shown, the master site also includes a first secondary storage bucket, the slave site includes a second local storage bucket and a second secondary storage bucket, and according to the deletion policy and the deletion status, the target site and the target data address corresponding to the target site are determined, including:

[0108] In response to the deletion policy being hierarchical deletion, and the target object being deleted in the primary site but not deleted in the secondary site, determining the first local storage bucket as the first target metadata address, and determining the second local storage bucket as the second target metadata address;

[0109] Reading the first target object metadata from the first local storage bucket according to the index information, and reading the second target object metadata from the second local storage bucket;

[0110] Compare the first modification time with the second modification time to obtain a time comparison result;

[0111] In response to the first modification time being later than the second modification time, determining the primary site as the target site, and determining the first secondary storage bucket as the target data address corresponding to the primary site;

[0112] Reading target object data from the first secondary storage bucket according to the index information to respond to the data read request;

[0113] In response to the first modification time being earlier than the second modification time, determining the slave site as the target site, and determining the second local storage bucket as the target data address corresponding to the slave site;

[0114] The target object data is read from the second local storage bucket according to the index information to respond to the data read request.

[0115] Specifically, there may be a situation where the primary site has not been deleted but the secondary site has been deleted, and the data reading method is the same. When the deletion policy is hierarchical deletion, and the target object has been deleted in the primary site but not deleted in the secondary site, the first modification time in the first local storage bucket and the second modification time in the second local storage bucket are compared to determine the target site; when the secondary site is the target site, the target object data in the second local storage bucket is searched and returned; when the primary site is the target site, the target object data in the first secondary storage bucket is searched and returned, so that the data obtained by users on different sites is always consistent and the latest version of the object.

[0116] In one embodiment, Figure 3 As shown, the master site also includes a first secondary storage bucket, the slave site includes a second local storage bucket and a second secondary storage bucket, and according to the deletion policy and the deletion status, the target site and the target data address corresponding to the target site are determined, including:

[0117] In response to the deletion policy being hierarchical deletion and the target object being deleted in both the primary site and the secondary site, determining the first local storage bucket as a first target metadata address, and determining the second local storage bucket as a second target metadata address;

[0118] Reading the first target object metadata from the first local storage bucket according to the index information, and reading the second target object metadata from the second local storage bucket;

[0119] Compare the first modification time with the second modification time to obtain a time comparison result;

[0120] In response to the first modification time being later than the second modification time, determining the primary site as the target site, and determining the first secondary storage bucket as the target data address corresponding to the primary site;

[0121] Reading target object data from the first secondary storage bucket according to the index information to respond to the data read request;

[0122] In response to the first modification time being earlier than the second modification time, determining the slave site as the target site, and determining the second secondary storage bucket as the target data address corresponding to the slave site;

[0123] The target object data is read from the second secondary storage bucket according to the index information to respond to the data read request.

[0124] Specifically, when the deletion strategy is hierarchical deletion and the target object has been deleted in both the primary site and the secondary site, the first modification time and the second modification time in the first local storage bucket are compared to determine the target site; when the secondary site is the target site, the target object data in the second secondary storage bucket is searched and returned; when the primary site is the target site, the target object data in the first secondary storage bucket is searched and returned, so that the data obtained by the user on different sites is always consistent and is the latest version of the object.

[0125] In one embodiment, Figure 4 As shown, the master site also includes a first secondary storage bucket, the slave site includes a second local storage bucket and a second secondary storage bucket, and according to the deletion policy and the deletion status, the target site and the target data address corresponding to the target site are determined, including:

[0126] In response to the deletion policy being archive deletion, and the target object being deleted in the primary site but not deleted in the secondary site, determining the first secondary storage bucket as the first target metadata address, and determining the second local storage bucket as the second target metadata address;

[0127] Reading the first target object metadata from the first secondary storage bucket according to the index information, and reading the second target object metadata from the second local storage bucket;

[0128] Compare the first modification time with the second modification time to obtain a time comparison result;

[0129] In response to the first modification time being later than the second modification time, determining the primary site as the target site, and determining the first secondary storage bucket as the target data address corresponding to the primary site;

[0130] Reading target object data from the first secondary storage bucket according to the index information to respond to the data read request;

[0131] In response to the first modification time being earlier than the second modification time, determining the slave site as the target site, and determining the second local storage bucket as the target data address corresponding to the slave site;

[0132] The target object data is read from the second local storage bucket according to the index information to respond to the data read request.

[0133] Specifically, there may be a situation where the primary site has not been deleted but the secondary site has been deleted, and the data reading method is the same. When the deletion policy is archive deletion, and the target object has been deleted in the primary site but not deleted in the secondary site, the first modification time and the second modification time in the first secondary storage bucket are compared to determine the target site; when the secondary site is the target site, the target object data in the second local storage bucket is searched and returned; when the primary site is the target site, the target object data in the first secondary storage bucket is searched and returned, so that the data obtained by users on different sites is always consistent and the latest version of the object.

[0134] In one embodiment, Figure 4 As shown, the master site also includes a first secondary storage bucket, the slave site includes a second local storage bucket and a second secondary storage bucket, and according to the deletion policy and the deletion status, the target site and the target data address corresponding to the target site are determined, including:

[0135] In response to the deletion policy being archive deletion and the target object being deleted in both the primary site and the secondary site, determining the first secondary storage bucket as a first target metadata address, and determining the second secondary storage bucket as a second target metadata address;

[0136] Reading the first target object metadata from the first secondary storage bucket according to the index information, and reading the second target object metadata from the second secondary storage bucket;

[0137] Compare the first modification time with the second modification time to obtain a time comparison result;

[0138] In response to the first modification time being later than the second modification time, determining the primary site as the target site, and determining the first secondary storage bucket as the target data address corresponding to the primary site;

[0139] Reading target object data from the first secondary storage bucket according to the index information to respond to the data read request;

[0140] In response to the first modification time being earlier than the second modification time, determining the slave site as the target site, and determining the second secondary storage bucket as the target data address corresponding to the slave site;

[0141] The target object data is read from the second secondary storage bucket according to the index information to respond to the data read request.

[0142] Specifically, when the deletion strategy is hierarchical deletion and the target object has been deleted in both the primary site and the secondary site, the first modification time and the second modification time in the first secondary bucket and the second secondary bucket are compared to determine the target site; when the secondary site is the target site, the target object data in the second secondary bucket is searched and returned; when the primary site is the target site, the target object data in the first secondary bucket is searched and returned, so that the data obtained by the user on different sites is always consistent and is the latest version of the object.

[0143] In one embodiment, Figure 2 As shown, the slave site includes a second local storage bucket, and according to the deletion policy and the deletion status, the target site and the target data address corresponding to the target site are determined, including:

[0144] In response to the deletion policy being synchronous deletion, and the target object having been deleted in the primary site but not deleted in the secondary site, determining the secondary site as the target site, and determining the second local storage bucket as the target data address corresponding to the target site;

[0145] Reading target object data from the second local storage bucket according to the index information to respond to the data read request;

[0146] In response to the deletion policy being synchronous deletion, and the target object not being deleted in the primary site but being deleted in the secondary site, determining the primary site as the target site, and determining the first local storage bucket as the target data address corresponding to the target site;

[0147] Reading target object data from the first local storage bucket according to the index information to respond to the data read request;

[0148] In response to the deletion policy being synchronous deletion and the target object being deleted in both the primary site and the secondary site, the user is prompted that a data read failure has occurred.

[0149] Specifically, when the deletion policy is synchronous deletion, and the target object has been deleted in the primary site but not deleted in the slave site, the slave site will be used as the target site to search and return the target object data in the second local storage bucket; similarly, when the deletion policy is synchronous deletion, and the target object has not been deleted in the primary site but has been deleted in the slave site, the primary site will be used as the target site to search and return the target object data in the first local storage bucket; when the deletion policy is synchronous deletion, and the target object has been deleted in both the primary site and the slave site, the user is prompted that a data reading failure has occurred, so that the data obtained by the user on different sites is always consistent and is the latest version of the object.

[0150] It should be understood that although Figure 1 , Figure 2 , Figure 3 , Figure 4The steps in the flowchart are shown in sequence as indicated by the arrows, but these steps are not necessarily executed in the order indicated by the arrows. Unless otherwise specified in this document, there is no strict order restriction for the execution of these steps, and these steps can be executed in other orders. Moreover, Figure 1 , Figure 2 , Figure 3 , Figure 4 At least part of the steps may include multiple sub-steps or multiple stages. These sub-steps or stages are not necessarily executed at the same time, but can be executed at different times. The execution order of these sub-steps or stages is not necessarily sequential, but can be executed in turn or alternately with other steps or at least part of the sub-steps or stages of other steps.

[0151] Embodiment 2

[0152] In one embodiment, Figure 5 As shown, a data reading device is provided, the device comprising:

[0153] A receiving module, the receiving module is used to receive a data reading request, wherein the data reading request includes index information of a target object;

[0154] A first acquisition module, the first acquisition module is used to acquire the synchronization status of the target object between the master site and the slave site, wherein the synchronization status includes the first synchronization completed and the first synchronization incomplete;

[0155] a first determination module, the first determination module being used to determine the primary site as the target site and the first local storage bucket as the target data address in response to the synchronization status being that the first synchronization is not completed;

[0156] A first reading module, the first reading module is used to read the target object data from the first local storage bucket according to the index information to respond to the data reading request;

[0157] A second acquisition module, the second acquisition module is used to obtain a deletion policy of the object storage system and a deletion status of the target object in response to the synchronization status being that the first synchronization is completed;

[0158] A second determination module, the second determination module is used to determine the target site and the target data address corresponding to the target site according to the deletion policy and the deletion status;

[0159] The second reading module is used to read the target object data from the target data address on the target site according to the index information to respond to the data reading request.

[0160] In one embodiment, the second determining module is further configured to:

[0161] Determine a first target metadata address of the master site and a second target metadata address of the slave site according to the deletion policy and the deletion status;

[0162] Reading first target object metadata from a first target metadata address according to the index information, and reading second target object metadata from a second target metadata address, wherein the first target object metadata includes a first modification time of the target object, and the second target object metadata includes a second modification time of the target object;

[0163] Compare the first modification time with the second modification time to obtain a time comparison result;

[0164] In response to the first modification time being later than the second modification time, taking the primary site as the target site, and determining a target data address corresponding to the primary site according to a deletion policy and a deletion status;

[0165] In response to the first modification time being earlier than the second modification time, the slave site is used as the target site, and the target data address corresponding to the slave site is determined according to the deletion policy and the deletion status.

[0166] In one embodiment, the slave site includes a second local storage bucket, and the second determining module is further configured to:

[0167] In response to the deletion policy being synchronous deletion and the target object not being deleted in both the primary site and the secondary site, determining the first local storage bucket as the first target metadata address, and determining the second local storage bucket as the second target metadata address;

[0168] Reading the first target object metadata from the first local storage bucket according to the index information, and reading the second target object metadata from the second local storage bucket;

[0169] Compare the first modification time with the second modification time to obtain a time comparison result;

[0170] In response to the first modification time being later than the second modification time, determining the primary site as the target site and determining the first local storage bucket as the target data address;

[0171] Reading target object data from the first local storage bucket according to the index information to respond to the data read request;

[0172] In response to the first modification time being earlier than the second modification time, determining the slave site as the target site and determining the second local storage bucket as the target data address;

[0173] The target object data is read from the second local storage bucket according to the index information to respond to the data read request.

[0174] In one embodiment, the master site further includes a first secondary storage bucket, the slave site includes a second local storage bucket and a second secondary storage bucket, and the second determination module is further used to:

[0175] In response to the deletion policy being hierarchical deletion, and the target object being deleted in the primary site but not deleted in the secondary site, determining the first local storage bucket as the first target metadata address, and determining the second local storage bucket as the second target metadata address;

[0176] Reading the first target object metadata from the first local storage bucket according to the index information, and reading the second target object metadata from the second local storage bucket;

[0177] Compare the first modification time with the second modification time to obtain a time comparison result;

[0178] In response to the first modification time being later than the second modification time, determining the primary site as the target site, and determining the first secondary storage bucket as the target data address corresponding to the primary site;

[0179] Reading target object data from the first secondary storage bucket according to the index information to respond to the data read request;

[0180] In response to the first modification time being earlier than the second modification time, determining the slave site as the target site, and determining the second local storage bucket as the target data address corresponding to the slave site;

[0181] The target object data is read from the second local storage bucket according to the index information to respond to the data read request.

[0182] In one embodiment, the master site further includes a first secondary storage bucket, the slave site includes a second local storage bucket and a second secondary storage bucket, and the second determination module is further used to:

[0183] In response to the deletion policy being hierarchical deletion and the target object being deleted in both the primary site and the secondary site, determining the first local storage bucket as a first target metadata address, and determining the second local storage bucket as a second target metadata address;

[0184] Reading the first target object metadata from the first local storage bucket according to the index information, and reading the second target object metadata from the second local storage bucket;

[0185] Compare the first modification time with the second modification time to obtain a time comparison result;

[0186] In response to the first modification time being later than the second modification time, determining the primary site as the target site, and determining the first secondary storage bucket as the target data address corresponding to the primary site;

[0187] Reading target object data from the first secondary storage bucket according to the index information to respond to the data read request;

[0188] In response to the first modification time being earlier than the second modification time, determining the slave site as the target site, and determining the second secondary storage bucket as the target data address corresponding to the slave site;

[0189] The target object data is read from the second secondary storage bucket according to the index information to respond to the data read request.

[0190] In one embodiment, the master site further includes a first secondary storage bucket, the slave site includes a second local storage bucket and a second secondary storage bucket, and the second determination module is further used to:

[0191] In response to the deletion policy being archive deletion, and the target object being deleted in the primary site but not deleted in the secondary site, determining the first secondary storage bucket as the first target metadata address, and determining the second local storage bucket as the second target metadata address;

[0192] Reading the first target object metadata from the first secondary storage bucket according to the index information, and reading the second target object metadata from the second local storage bucket;

[0193] Compare the first modification time with the second modification time to obtain a time comparison result;

[0194] In response to the first modification time being later than the second modification time, determining the primary site as the target site, and determining the first secondary storage bucket as the target data address corresponding to the primary site;

[0195] Reading target object data from the first secondary storage bucket according to the index information to respond to the data read request;

[0196] In response to the first modification time being earlier than the second modification time, determining the slave site as the target site, and determining the second local storage bucket as the target data address corresponding to the slave site;

[0197] The target object data is read from the second local storage bucket according to the index information to respond to the data read request.

[0198] In one embodiment, the master site further includes a first secondary storage bucket, the slave site includes a second local storage bucket and a second secondary storage bucket, and the second determination module is further used to:

[0199] In response to the deletion policy being archive deletion and the target object being deleted in both the primary site and the secondary site, determining the first secondary storage bucket as a first target metadata address, and determining the second secondary storage bucket as a second target metadata address;

[0200] Reading the first target object metadata from the first secondary storage bucket according to the index information, and reading the second target object metadata from the second secondary storage bucket;

[0201] Compare the first modification time with the second modification time to obtain a time comparison result;

[0202] In response to the first modification time being later than the second modification time, determining the primary site as the target site, and determining the first secondary storage bucket as the target data address corresponding to the primary site;

[0203] Reading target object data from the first secondary storage bucket according to the index information to respond to the data read request;

[0204] In response to the first modification time being earlier than the second modification time, determining the slave site as the target site, and determining the second secondary storage bucket as the target data address corresponding to the slave site;

[0205] The target object data is read from the second secondary storage bucket according to the index information to respond to the data read request.

[0206] For the specific definition of the data reading device, please refer to the definition of the data reading method above, which will not be repeated here. Each module in the above-mentioned data reading device can be implemented in whole or in part by software, hardware and a combination thereof. The above-mentioned modules can be embedded in or independent of the processor in the electronic device in the form of hardware, or can be stored in the memory of the electronic device in the form of software, so that the processor can call and execute the operations corresponding to the above modules.

[0207] Embodiment 3

[0208] In one embodiment, an electronic device is provided, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the following steps when executing the computer program:

[0209] receiving a data read request, wherein the data read request includes index information of a target object;

[0210] Obtain the synchronization status of the target object between the master site and the slave site, where the synchronization status includes the first synchronization completed and the first synchronization incomplete;

[0211] In response to the synchronization status being that the first synchronization is not completed, determining the primary site as the target site, and determining the first local storage bucket as the target data address corresponding to the target site;

[0212] Reading target object data from the first local storage bucket according to the index information to respond to the data read request;

[0213] In response to the synchronization status being that the first synchronization is completed, obtaining a deletion status of the target object and a deletion policy of the object storage system;

[0214] Determine the target site and the target data address corresponding to the target site according to the deletion policy and the deletion status;

[0215] The target object data is read from the target data address of the target site according to the index information in response to the data read request.

[0216] When the program instructions are read and executed by one or more processors, they can also perform operations corresponding to the various steps in the above method embodiments. Please refer to the above description and will not be repeated here. Figure 6 , which exemplarily shows the architecture of the electronic device, which may specifically include a processor 610, a video display adapter 611, a disk drive 612, an input / output interface 613, a network interface 614, and a memory 620. The processor 610, the video display adapter 611, the disk drive 612, the input / output interface 613, the network interface 614, and the memory 620 may be communicatively connected via a communication bus 630.

[0217] Among them, the processor 610 can be implemented by a general-purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits, and is used to execute relevant programs to implement the technical solution provided in this application.

[0218] The memory 620 can be implemented in the form of a read-only memory (ROM), a random access memory (RAM), a static storage device, a dynamic storage device, etc. The memory 620 can store an operating system 621 for controlling the operation of the electronic device 600, and a basic input and output system (BIOS) 622 for controlling the low-level operation of the electronic device 600. In addition, a web browser 623, a data storage manager 624, and an icon font processing system 625, etc. can also be stored. The above-mentioned icon font processing system 625 can be an application program that specifically implements the operations of the aforementioned steps in the embodiment of the present application. In short, when the technical solution provided in the present application is implemented by software or firmware, the relevant program code is stored in the memory 620 and is called and executed by the processor 610.

[0219] The input / output interface 613 is used to connect the input / output module to realize information input and output. The input / output module can be configured in the device as a component (not shown in the figure), or it can be externally connected to the device to provide corresponding functions. The input device may include a keyboard, a mouse, a touch screen, a microphone, various sensors, etc., and the output device may include a display, a speaker, a vibrator, an indicator light, etc.

[0220] The network interface 614 is used to connect to a communication module (not shown) to realize communication interaction between the device and other devices. The communication module can realize communication through a wired mode (such as USB, network cable, etc.) or a wireless mode (such as mobile network, WIFI, Bluetooth, etc.).

[0221] The bus 630 comprises a pathway for transmitting information between the various components of the device (eg, the processor 610, the video display adapter 611, the disk drive 612, the input / output interface 613, the network interface 614, and the memory 620).

[0222] In addition, the electronic device 600 can also obtain information on specific collection conditions from the virtual resource object collection condition information database 641 for use in condition judgment, etc.

[0223] It should be noted that, although the electronic device 600 only shows a processor 610, a video display adapter 611, a disk drive 612, an input / output interface 613, a network interface 614, a memory 620, a bus 630, etc., in the specific implementation process, the electronic device may also include other components necessary for normal operation. In addition, it can be understood by those skilled in the art that the above device may also only include components necessary for implementing the solution of the present application, and does not necessarily include all the components shown in the figure.

[0224] It can be seen from the description of the above implementation methods that those skilled in the art can clearly understand that the present application can be implemented by means of software plus a necessary general hardware platform. Based on this understanding, the technical solution of the present application can essentially or in other words, the part that contributes to the prior art can be embodied in the form of a software product, which can be stored in a storage medium such as ROM / RAM, a disk, an optical disk, etc., including several instructions for enabling an electronic device (which can be a personal computer, a cloud server, or a network device, etc.) to execute the methods of various embodiments of the present application or certain parts of the embodiments.

[0225] Embodiment 4

[0226] In one embodiment, a computer readable storage medium is provided, on which a computer program is stored, and when the computer program is executed by a processor, the following steps are implemented:

[0227] receiving a data read request, wherein the data read request includes index information of a target object;

[0228] Obtain the synchronization status of the target object between the master site and the slave site, where the synchronization status includes the first synchronization completed and the first synchronization incomplete;

[0229] In response to the synchronization status being that the first synchronization is not completed, determining the primary site as the target site, and determining the first local storage bucket as the target data address corresponding to the target site;

[0230] Reading target object data from the first local storage bucket according to the index information to respond to the data read request;

[0231] In response to the synchronization status being that the first synchronization is completed, obtaining a deletion status of the target object and a deletion policy of the object storage system;

[0232] Determine the target site and the target data address corresponding to the target site according to the deletion policy and the deletion status;

[0233] The target object data is read from the target data address of the target site according to the index information in response to the data read request.

[0234] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiments can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to memory, storage, database or other media used in the embodiments provided in the present application can include non-volatile and / or volatile memory. Non-volatile memory can include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM) or flash memory. Volatile memory can include random access memory (RAM) or external cache memory. As an illustration and not limitation, RAM is available in many forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous link (Synchlink) DRAM (SLDRAM), memory bus (Rambus) direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM).

[0235] The technical features of the above embodiments may be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0236] The above embodiments only express several implementation methods of the present application, and the descriptions thereof are relatively specific and detailed, but they cannot be understood as limiting the scope of the invention patent. It should be pointed out that, for a person of ordinary skill in the art, several variations and improvements can be made without departing from the concept of the present application, and these all belong to the protection scope of the present application. Therefore, the protection scope of the patent of the present application shall be subject to the attached claims.

[0237] Embodiment 5

[0238] In one embodiment, a computer program product is provided, on which a computer program is stored, and when the computer program is executed by a processor, the following steps are implemented:

[0239] receiving a data read request, wherein the data read request includes index information of a target object;

[0240] Obtain the synchronization status of the target object between the master site and the slave site, where the synchronization status includes the first synchronization completed and the first synchronization incomplete;

[0241] In response to the synchronization status being that the first synchronization is not completed, determining the primary site as the target site, and determining the first local storage bucket as the target data address corresponding to the target site;

[0242] Reading target object data from the first local storage bucket according to the index information to respond to the data read request;

[0243] In response to the synchronization status being that the first synchronization is completed, obtaining a deletion status of the target object and a deletion policy of the object storage system;

[0244] Determine the target site and the target data address corresponding to the target site according to the deletion policy and the deletion status;

[0245] The target object data is read from the target data address of the target site according to the index information in response to the data read request.

[0246] A person skilled in the art can understand that all or part of the processes in the above-mentioned embodiment methods can be implemented by instructing related hardware through a computer program, and the computer program can be stored in a computer program product. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods.

[0247] The technical features of the above embodiments may be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0248] The above embodiments only express several implementation methods of the present application, and the descriptions thereof are relatively specific and detailed, but they cannot be understood as limiting the scope of the invention patent. It should be pointed out that, for a person of ordinary skill in the art, several variations and improvements can be made without departing from the concept of the present application, and these all belong to the protection scope of the present application. Therefore, the protection scope of the patent of the present application shall be subject to the attached claims.

Claims

1. A data reading method, applied to an object storage system, wherein the object storage system includes a master site and a slave site, wherein the master site includes a first local storage bucket, characterized in that: The method comprises: Receiving a data read request, wherein the data read request includes index information of a target object; Acquire the synchronization status of the target object between the master site and the slave site, wherein the synchronization status includes the first synchronization completed and the first synchronization incomplete; In response to the synchronization status being that the first synchronization is not completed, determining the primary site as the target site, and determining the first local storage bucket as the target data address corresponding to the target site; Reading the target object data from the first local storage bucket according to the index information to respond to the data read request; In response to the synchronization status being that the first synchronization has been completed, obtaining a deletion status of the target object and a deletion policy of the object storage system; Determine the target site and the target data address corresponding to the target site according to the deletion policy and the deletion status; The target object data is read from the target data address of the target site according to the index information to respond to the data read request.

2. The method according to claim 1, characterized in that: Determining a target site and a target data address corresponding to the target site according to the deletion policy and the deletion status includes: Determine a first target metadata address of the master site and a second target metadata address of the slave site according to the deletion policy and the deletion status; Reading first target object metadata from a first target metadata address according to the index information, and reading second target object metadata from a second target metadata address, wherein the first target object metadata includes a first modification time of the target object, and the second target object metadata includes a second modification time of the target object; Compare the first modification time with the second modification time to obtain a time comparison result; In response to the first modification time being later than the second modification time, taking the primary site as a target site, and determining a target data address corresponding to the primary site according to the deletion policy and the deletion status; In response to the first modification time being earlier than the second modification time, the slave site is used as the target site, and the target data address corresponding to the slave site is determined according to the deletion policy and the deletion status.

3. The method according to claim 2, characterized in that: The slave site includes a second local storage bucket, and according to the deletion policy and the deletion status, determines the target site and the target data address corresponding to the target site, including: In response to the deletion policy being synchronous deletion, and the target object not being deleted in both the primary site and the secondary site, determining the first local storage bucket as a first target metadata address, and determining the second local storage bucket as a second target metadata address; Reading the first target object metadata from the first local storage bucket according to the index information, and reading the second target object metadata from the second local storage bucket; Compare the first modification time with the second modification time to obtain a time comparison result; In response to the first modification time being later than the second modification time, determining the primary site as a target site and determining the first local storage bucket as a target data address; Reading the target object data from the first local storage bucket according to the index information to respond to the data read request; In response to the first modification time being earlier than the second modification time, determining the slave site as a target site, and determining the second local storage bucket as a target data address; The target object data is read from the second local storage bucket according to the index information to respond to the data read request.

4. The method according to claim 2, characterized in that: The master site further includes a first secondary storage bucket, the slave site includes a second local storage bucket and a second secondary storage bucket, and determining a target site and a target data address corresponding to the target site according to the deletion policy and the deletion status, including: In response to the deletion policy being hierarchical deletion, and the target object having been deleted in the primary site but not deleted in the secondary site, determining the first local storage bucket as a first target metadata address, and determining the second local storage bucket as a second target metadata address; Reading the first target object metadata from the first local storage bucket according to the index information, and reading the second target object metadata from the second local storage bucket; Compare the first modification time with the second modification time to obtain a time comparison result; In response to the first modification time being later than the second modification time, determining the primary site as a target site, and determining the first secondary storage bucket as a target data address corresponding to the primary site; Reading target object data from the first secondary storage bucket according to the index information to respond to the data read request; In response to the first modification time being earlier than the second modification time, determining the slave site as a target site, and determining the second local storage bucket as a target data address corresponding to the slave site; The target object data is read from the second local storage bucket according to the index information to respond to the data read request.

5. The method according to claim 2, characterized in that: The master site further includes a first secondary storage bucket, the slave site includes a second local storage bucket and a second secondary storage bucket, and determining a target site and a target data address corresponding to the target site according to the deletion policy and the deletion status, including: In response to the deletion policy being hierarchical deletion and the target object being deleted in both the primary site and the secondary site, determining the first local storage bucket as a first target metadata address, and determining the second local storage bucket as a second target metadata address; Reading the first target object metadata from the first local storage bucket according to the index information, and reading the second target object metadata from the second local storage bucket; Compare the first modification time with the second modification time to obtain a time comparison result; In response to the first modification time being later than the second modification time, determining the primary site as a target site, and determining the first secondary storage bucket as a target data address corresponding to the primary site; Reading target object data from the first secondary storage bucket according to the index information to respond to the data read request; In response to the first modification time being earlier than the second modification time, determining the slave site as a target site, and determining the second secondary storage bucket as a target data address corresponding to the slave site; The target object data is read from the second secondary storage bucket according to the index information to respond to the data read request.

6. The method according to claim 2, characterized in that: The master site further includes a first secondary storage bucket, the slave site includes a second local storage bucket and a second secondary storage bucket, and determining a target site and a target data address corresponding to the target site according to the deletion policy and the deletion status, including: In response to the deletion policy being archive deletion, and the target object having been deleted in the primary site but not deleted in the secondary site, determining the first secondary storage bucket as a first target metadata address, and determining the second local storage bucket as a second target metadata address; Reading the first target object metadata from the first secondary storage bucket according to the index information, and reading the second target object metadata from the second local storage bucket; Compare the first modification time with the second modification time to obtain a time comparison result; In response to the first modification time being later than the second modification time, determining the primary site as a target site, and determining the first secondary storage bucket as a target data address corresponding to the primary site; Reading target object data from the first secondary storage bucket according to the index information to respond to the data read request; In response to the first modification time being earlier than the second modification time, determining the slave site as a target site, and determining the second local storage bucket as a target data address corresponding to the slave site; The target object data is read from the second local storage bucket according to the index information to respond to the data read request.

7. The method according to claim 2, characterized in that: The master site further includes a first secondary storage bucket, the slave site includes a second local storage bucket and a second secondary storage bucket, and determining a target site and a target data address corresponding to the target site according to the deletion policy and the deletion status, including: In response to the deletion policy being archive deletion and the target object being deleted in both the primary site and the secondary site, determining the first secondary storage bucket as a first target metadata address, and determining the second secondary storage bucket as a second target metadata address; Reading the first target object metadata from the first secondary storage bucket according to the index information, and reading the second target object metadata from the second secondary storage bucket; Compare the first modification time with the second modification time to obtain a time comparison result; In response to the first modification time being later than the second modification time, determining the primary site as a target site, and determining the first secondary storage bucket as a target data address corresponding to the primary site; Reading target object data from the first secondary storage bucket according to the index information to respond to the data read request; In response to the first modification time being earlier than the second modification time, determining the slave site as a target site, and determining the second secondary storage bucket as a target data address corresponding to the slave site; The target object data is read from the second secondary storage bucket according to the index information to respond to the data read request.

8. A data reading device, characterized in that: The device comprises: A receiving module, the receiving module is used to receive a data reading request, wherein the data reading request includes index information of a target object; A first acquisition module, the first acquisition module is used to acquire the synchronization status of the target object between the primary site and the secondary site, wherein the synchronization status includes the first synchronization completed and the first synchronization incomplete; a first determining module, configured to determine the primary site as the target site and the first local storage bucket as the target data address in response to the synchronization status being that the first synchronization is not completed; A first reading module, the first reading module is used to read the target object data from the first local storage bucket according to the index information to respond to the data reading request; a second acquisition module, the second acquisition module being configured to acquire a deletion policy of the object storage system and a deletion status of the target object in response to the synchronization status being that the first synchronization is completed; A second determination module, the second determination module is used to determine the target site and the target data address corresponding to the target site according to the deletion policy and the deletion status; A second reading module, the second reading module is used to read the target object data from the target data address on the target site according to the index information to respond to the data reading request.

9. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 7 are implemented.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 7 are implemented.

Images