CN110557399A - Management data synchronization method and device, storage equipment and readable storage medium - Google Patents

Abstract

the invention discloses a management data synchronization method and device applied to a master controller, a management data synchronization method and device applied to a slave controller, a storage device and a readable storage medium. In the technical scheme, a multicast technology is utilized, an increasing multicast serial number is designed, multicast messages are processed sequentially, a slave controller determines whether the messages are missing or not according to the multicast serial number, and the missing messages are actively pulled from the master controller under the condition of missing the messages, so that management data synchronization is realized. According to the technical scheme, under the condition of reducing the synchronous workload of the master controller, the consistency of the management data in the slave controller and the master controller is ensured, and the system stability of the multi-controller storage array can be further ensured.

Description

Management data synchronization method and device, storage equipment and readable storage medium

Technical Field

the present invention relates to the field of storage technologies, and in particular, to a method and an apparatus for synchronizing management data, a storage device, and a readable storage medium.

background

with the rapid development of the internet, particularly the development of cloud computing and network networking, users and application data are in a high-speed growth state, and storage arrays are produced and are specially used for storing data.

A multi-controller storage array is a common storage device, and is composed of a master controller and a plurality of slave controllers. The master controller is responsible for managing the storage array, and in order to improve reliability, when the master controller loses management capability (for example, under the conditions of sudden shutdown of the controller and the like), one slave controller is selected as a new master controller and takes over the management task of the master controller, and the old master controller becomes the slave controller. After the switching of the main controller, in order to ensure that the management service is unchanged, the management data of the main controller needs to be synchronized among the controllers.

In the existing data synchronization scheme, a master controller often sends management data to a slave controller, and in order to ensure the consistency of the management data stored in each controller, the master controller needs to use a complex algorithm to ensure the data consistency, and needs to occupy a large part of the performance of the master controller. Specifically, the master controller needs to maintain communication with each slave controller one by one, and constantly verifies whether the management data of the slave controllers are consistent with the latest management data in the master controller, and when the number of the slave controllers is large or the management data is changed frequently, the threads for synchronously managing the data in the master controller occupy the computing resources and the storage resources of the master controller, so as to ensure the consistency of the management data. Due to the synchronous management data occupation performance, the main controller is difficult to guarantee the management quality of the storage array, and in severe cases, the multi-controller storage array cannot provide storage service to the outside, which affects the user experience.

in summary, how to effectively solve the problems of the master controller performance occupation caused by the management data synchronization is a technical problem that needs to be solved urgently by those skilled in the art at present.

Disclosure of Invention

The invention aims to provide two management data synchronization methods and devices, a storage device and a readable storage medium, which reduce the performance of occupying a master controller by sharing a management data synchronization task from the slave controller, can ensure the stability of the storage device such as a multi-controller storage array and is beneficial to improving the user experience.

In order to solve the technical problems, the invention provides the following technical scheme:

A first management data synchronization method, comprising:

the slave controller receives and analyzes a management data synchronous message multicast by the master controller after the management data changes, and obtains a multicast serial number;

Determining whether a missing target multicast sequence number without processing record exists by using the multicast sequence number;

If yes, sending the target multicast serial number to the main controller, and receiving a target management data synchronous message corresponding to the target multicast serial number and sent by the main controller;

If not, processing the management data synchronous message without the corresponding processing record according to the multicast sequence number sequence so as to synchronize the management data.

preferably, the method further comprises the following steps:

And after the main controller is determined to be switched, clearing the management data synchronized with the main controller so as to synchronize the management data of the new main controller.

Preferably, the determining the master controller switching includes:

receiving and analyzing a main controller switching message sent by a target controller to obtain a multicast serial number and a main controller ID;

and when the ID of the main controller is inconsistent with the main controller, determining that the target controller is the new main controller.

preferably, the determining whether there is a missing and non-processing recorded target multicast sequence number using the multicast sequence number includes:

judging whether the multicast serial numbers are continuous or not;

if not, determining the missing multicast sequence number, and determining the missing multicast sequence number as the target multicast sequence number when the missing multicast sequence number has no corresponding processing record.

Preferably, the processing the management data synchronization packet without the corresponding processing record according to the multicast sequence number sequence to synchronize the management data includes:

Screening out the management data synchronous message without the corresponding processing record by utilizing the processing record;

sequencing the screened management data synchronous messages by using the multicast serial number;

And sequentially analyzing the management data synchronous messages according to the arrangement sequence to obtain the management data content.

Preferably, the sending the target multicast sequence number to the master controller includes:

and sending a reissue application message carrying the target multicast serial number to the main controller.

preferably, the step of processing the management data synchronization packet without the corresponding processing record according to the multicast sequence number sequence to synchronize management data includes:

determining a management data type corresponding to the classified management data synchronous message; wherein the management data types comprise volumes, hosts and fans;

and synchronizing the management data corresponding to the management data type by using the management data content carried by the classified management data synchronization message.

a second management data synchronization method, comprising:

after the management data change, the master controller multicasts a management data synchronization message to each slave controller; the management data synchronous message comprises a multicast serial number;

receiving a missing target multicast sequence number which is sent from a controller and has no processing record;

And supplementing the target management data synchronous message corresponding to the target multicast serial number to the slave controller so that the slave controller processes the management data synchronous message without the corresponding processing record according to the multicast serial number sequence to synchronize management data.

Preferably, receiving the missing and record-not-processed target multicast sequence number sent from the controller includes:

And receiving and analyzing the reissue application message sent by the slave controller to obtain the target multicast serial number.

Preferably, the supplementing the target management data synchronization packet corresponding to the target multicast sequence number to the slave controller includes:

And independently transmitting the target management data synchronous message to the slave controller.

Preferably, after the management data changes, multicasting a management data synchronization packet to each slave controller, including:

after the management data are changed, determining the type of the management data to be synchronized; wherein the management data types comprise volumes, hosts and fans;

generating a classified management data synchronous message matched with the type of the management data;

And multicasting the classified management data synchronous message to each slave controller so that each slave controller can synchronize the management data according to the type of the management data.

A storage device, comprising:

a plurality of controllers, each of the controllers comprising:

A memory for storing a computer program;

A processor for implementing the steps of the target method when executing the computer program;

The slave controllers among the plurality of controllers, the target method executed being the above-described first management data synchronization method;

The target method executed by the master controller among the plurality of controllers is the above-described second management data synchronization method.

The first management data synchronization device is applied to a slave controller and comprises:

the management data synchronous message receiving module is used for receiving and analyzing the management data synchronous message multicast by the main controller after the management data changes, and acquiring a multicast serial number;

The message checking module is used for determining whether a missing target multicast serial number without processing record exists by using the multicast serial number;

the message missing processing module is used for sending the target multicast serial number to the main controller and receiving a target management data synchronous message corresponding to the target multicast serial number which is sent by the main controller again if the target multicast serial number exists;

And the data synchronization module is used for processing the management data synchronization message without the corresponding processing record according to the multicast serial number sequence if the target multicast serial number does not exist so as to synchronize the management data.

The second management data synchronizer, applied to the main controller, includes:

The management data synchronous message multicast module is used for multicasting the management data synchronous messages to each slave controller after the management data changes; the management data synchronous message comprises a multicast serial number;

the missing message determining module is used for receiving the missing target multicast serial number which is sent from the controller and has no processing record;

and the message retransmission module is used for retransmitting the target management data synchronous message corresponding to the target multicast serial number to the slave controller so that the slave controller processes the management data synchronous message without the corresponding processing record according to the multicast serial number sequence to synchronize management data.

a readable storage medium having stored thereon a computer program which, when executed by a processor, carries out the steps of the first or second management data synchronization method described above.

the first management data synchronization method provided by the embodiment of the invention is applied to the slave controller in the storage device, the management data synchronization message received by the slave controller automatically verifies whether the message is missing or not according to the multicast serial number, and actively asks for the target management data synchronization message corresponding to the target multicast serial number from the master controller after determining that the missing and recorded target multicast serial number exists. Then, after determining that the multicast serial numbers are continuous, processing the management data synchronous messages without corresponding processing records according to the multicast serial number sequence, and then realizing synchronous management of data with the main controller. In the process, the slave controllers transfer the original management data synchronization verification operation to the slave controllers for processing, and the master controller only needs to multicast the management data synchronization message and passively reissue the target management data synchronization message which is not received by the individual slave controllers. Therefore, the management data synchronization task of the master controller is shared to each slave controller, the problem of resource occupation of the master controller can be avoided, the management quality of the storage array of the master controller can be guaranteed, and the stability of the storage device can be further guaranteed.

correspondingly, the second management data synchronization method provided by the embodiment of the invention is applied to the master controller in the storage device, and the master controller multicasts a management data synchronization message to each slave controller after the management data changes; then, only the missing target multicast sequence number which is sent by the individual slave controller and has no processing record needs to be passively waited; and then supplementing the target management data synchronous message corresponding to the target multicast serial number to the slave controller. Therefore, compared with the existing main controller which needs to carry out end-to-end communication on each slave controller and repeatedly confirms whether the management data are successfully synchronized, the method can greatly reduce the pressure of the main controller on the synchronization of the management data, reduce the calculation and storage performance of the main controller, save more resources for processing the management task of the storage array, and ensure the stability of the storage equipment.

Accordingly, embodiments of the present invention further provide two management data synchronization apparatuses, storage devices, and readable storage media corresponding to the two management data synchronization methods, which have the above technical effects and are not described herein again.

drawings

In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.

FIG. 1 is a flowchart illustrating a first method for managing data synchronization according to an embodiment of the present invention;

FIG. 2 is a flowchart illustrating a second method for managing data synchronization according to an embodiment of the present invention;

FIG. 3 is a flowchart illustrating an implementation of a method for managing data synchronization according to an embodiment of the present invention;

FIG. 4 is a schematic structural diagram of a memory device according to an embodiment of the present invention;

fig. 5 is a schematic structural diagram of a controller in a storage device according to this embodiment;

FIG. 6 is a schematic structural diagram of a first management data synchronization apparatus according to an embodiment of the present invention;

Fig. 7 is a schematic structural diagram of a second management data synchronization apparatus according to an embodiment of the present invention.

Detailed Description

in order that those skilled in the art will better understand the disclosure, the invention will be described in further detail with reference to the accompanying drawings and specific embodiments. It is to be understood that the described embodiments are merely exemplary of the invention, and not restrictive of the full scope of the invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.

The first embodiment is as follows:

referring to fig. 1, fig. 1 is a flowchart illustrating a first method for managing data synchronization according to an embodiment of the present invention, the method including the following steps:

s101, the slave controller receives and analyzes the multicast management data synchronous message after the management data of the master controller changes, and a multicast serial number is obtained.

the slave controller is a slave controller in a storage device such as a multi-controller storage matrix, namely, the slave controller is managed by a master controller. In the embodiment of the invention, each slave controller needs to synchronize management data, and each slave controller can adopt the same synchronization operation to synchronize the management data with the master controller.

In the embodiment of the present invention, after the master controller determines that the management data changes, the master controller may send a management data synchronization packet to each slave controller in a multicast manner, where the management data synchronization packet includes, but is not limited to, a multicast serial number and management data content, where the multicast serial number is a serial number sent by the packet. That is, a multicast group may be set for the master controller and each slave controller in advance, and then the master controller multicasts the management data sync packet to the multicast group, so that each slave controller in the multicast group can receive the management data sync packet.

after receiving the management data synchronization message from the slave controller, the slave controller can analyze the management data synchronization message according to the protocol of the management data synchronization message to obtain the multicast serial number of each management data synchronization message.

and S102, determining whether the target multicast sequence number which is missing and has no processing record exists by using the multicast sequence number.

In the embodiment of the invention, after the management data synchronization message is processed, the processing record of the management data synchronization message can be recorded. For example, after processing one management data sync message, the multicast serial number corresponding to the management data sync message may be added to the processed message table/queue, so that it may be determined which management data sync messages have been processed by querying the processed message table/queue; and a processing variable can be set independently, and after each management data synchronous message is processed, the multicast serial number corresponding to the management data synchronous message is assigned to the processing variable, so that the management data message corresponding to which specific multicast serial number is processed currently can be determined by inquiring the processing variable.

The target multicast sequence number is the management data synchronization message corresponding to the missing, and simultaneously, the management data synchronization message corresponding to the target multicast sequence number is also the unprocessed management data synchronization message. That is, when a missing packet belongs to a processed packet, the missing packet can be ignored.

specifically, determining the target multicast sequence number includes:

step one, judging whether multicast serial numbers are continuous or not;

and step two, if not, determining the missing multicast sequence number, and determining the missing multicast sequence number as the target multicast sequence number when the missing multicast sequence number has no corresponding processing record.

for convenience of description, the above two steps will be described in combination.

After obtaining the multicast sequence numbers, it is first determined whether the received multicast sequence numbers are consecutive. Specifically, if n management data synchronization messages received and processed historically and m management data synchronization messages are received currently, it is determined whether the multicast sequence numbers of the m management data synchronization messages received and the n management data synchronization messages received and processed historically are consecutive and whether the multicast sequence numbers of the m management data synchronization messages received and processed currently are consecutive. For example, 10 management data synchronization messages which are received historically and processed, 2 management data synchronization messages which are received currently with multicast message serial numbers from 00000 to 00010 and with multicast message serial numbers of 000009 and 000012 can be missing from a newly received management data synchronization message, that is, two currently received management data synchronization messages are not continuous.

After the received multicast sequence number is determined to be discontinuous, whether the management data synchronization message corresponding to the missing multicast sequence number is processed is further determined. For example, when the received management data sync message is missing, but the missing management data sync message is a processed message, the missing management data sync message can be ignored.

in other embodiments of the present invention, when determining the target multicast sequence number, the multicast sequence number interval corresponding to the unprocessed management data packet may be determined first, and then it may be further determined whether a missing target multicast sequence number occurs between the received management data synchronization packets within the multicast sequence number interval. The multicast sequence number interval may be greater than the multicast sequence number corresponding to the processed multicast sequence number. For example, when the processed packet number is 6, the multicast number interval may be (6 ∞), and when the newly received multicast number is 7, 9, 10, it can be seen that 6 and 7 are consecutive, but 7 and 9 are not consecutive, and the multicast number 8 is indeed found, so the multicast number 8 can be determined as the target multicast number.

It should be noted that, after receiving one or more management data synchronization packets, the number of the determined target multicast sequence numbers may be 0, or may also be 1 or more, and the number of the target multicast sequence numbers is determined according to the actual situation. When the number of the target multicast sequence numbers is 0, that is, the target multicast sequence numbers do not exist, and when the number of the target multicast sequence numbers is greater than 0, the target multicast sequence numbers are determined to exist.

after determining whether the target multicast sequence number exists, executing subsequent steps according to a determination result, specifically, if the determination result is yes, executing step S103; if the judgment result is no, step S104 is executed.

S103, sending the target multicast serial number to the main controller, and receiving the target management data synchronous message corresponding to the target multicast serial number which is sent by the main controller again.

To ensure consistency of the management data, the target multicast sequence number may be sent to the master controller after finding that there is a missing and unprocessed target multicast sequence number.

The sending of the target multicast sequence number to the master controller may specifically be sending a reissue application message carrying the target multicast sequence number to the master controller. The reissue application message includes, but is not limited to, the number of missing multicast sequence numbers and each target multicast sequence number. For example, the reissue application message may further include data content carried by a common message such as a slave controller ID and an integrity check code.

After receiving the target multicast serial number, the master controller can reissue a target management data synchronization message corresponding to the target multicast to the slave controller.

s104, processing the management data synchronous messages without corresponding processing records according to the multicast sequence number sequence so as to synchronize the management data.

Considering that management data synchronous messages corresponding to different multicast serial numbers may be adjusted for the same management data, in order to avoid destroying the internal logic relationship of the common management data synchronous message to the management data processing, when the management data synchronous messages are processed, the management data synchronous messages without corresponding processing records may be processed in sequence according to the multicast serial numbers, so as to realize synchronous management of the data with the main controller.

wherein, processing the management data synchronization message to synchronize the management data comprises:

step one, screening out management data synchronous messages without corresponding processing records by using the processing records;

step two, utilizing the multicast serial number to sequence the screened management data synchronous messages;

And step three, analyzing the management data synchronous messages in sequence according to the arrangement sequence to obtain the management data content.

For convenience of description, the above three steps will be described in combination.

firstly, screening out the management data synchronous messages without corresponding processing records according to the processing records. Specifically, when the processing record is a processing variable, the management data synchronization packet with the multicast serial number greater than the current value of the processing variable can be screened out to be processed. When the processing record is the processed message table/queue, the unprocessed management data synchronous message can be screened out by traversing and inquiring the processed message table/queue.

and then, sequencing the screened to-be-processed management data synchronous messages according to the multicast serial number.

after sequencing, the management data synchronous messages can be sequentially analyzed according to the sequencing order, and the management data content can be obtained. The analysis process can obtain the management data content from the management data synchronous message according to the preset specific format definition of the management data synchronous message. For example, in the management data synchronization inclusion, it is possible to sequentially record: multicast serial number, main controller ID, subsequent data length, full data mark, data number and data content part; the data content part is management data content, and the data content may specifically be: ID of data 1, detailed content length of data 1, detailed content of data 1, …, ID of data n, detailed content length of data n, detailed content of data n. Of course, in other embodiments of the present invention, the specific data content of the management data synchronization packet and the position sequence in the packet may be adjusted.

The first management data synchronization method provided by the embodiment of the invention is applied to the slave controller in the storage device, the management data synchronization message received by the slave controller automatically verifies whether the message is missing or not according to the multicast serial number, and actively asks for the target management data synchronization message corresponding to the target multicast serial number from the master controller after determining that the missing and recorded target multicast serial number exists. Then, after determining that the multicast serial numbers are continuous, processing the management data synchronous messages without corresponding processing records according to the multicast serial number sequence, and then realizing synchronous management of data with the main controller. In the process, the slave controllers transfer the original management data synchronization verification operation to the slave controllers for processing, and the master controller only needs to multicast the management data synchronization message and passively reissue the target management data synchronization message which is not received by the individual slave controllers. Namely, the management data synchronization task of the master controller is shared to each slave controller, so that the problem of resource occupation of the master controller can be avoided, the management quality of the storage array of the master controller can be guaranteed, and the stability of the storage equipment can be further guaranteed.

It should be noted that, based on the first embodiment, the embodiment of the present invention further provides a corresponding improvement scheme. In the preferred/improved embodiment, the same steps as those in the above embodiment or corresponding steps may be referred to each other, and corresponding advantageous effects may also be referred to each other, which are not described in detail in the preferred/improved embodiment herein.

Preferably, consider the situation in which the master controller may suddenly shut down, malfunction, etc. and the slave controllers may not be able to continue to be managed by the multi-controller storage array. At this time, by switching the master controller and the slave controller, one slave controller can be selected from the slave controllers to take over the management work of the master controller, so that the slave controller becomes a new master controller. That is, when the master-slave switching occurs, all slave controllers need to perform management data synchronization with the new master controller, so that the master-slave switching can be smoothly performed when the master-slave switching is required subsequently.

In the embodiment of the present invention, in order to keep the slave controller and the new master controller synchronized with the management data after the master-slave switching, on the basis of the first embodiment, the following steps may be further performed:

After determining the master controller switch, the management data synchronized with the master controller is cleared to synchronize the management data of the new master controller.

that is, after the slave controller determines that the controller is switched, the slave controller actively requests the management data synchronized with the original master controller so as to synchronize the management data with the new master controller.

The specific process of determining the switching of the main controller comprises the following steps:

step one, receiving and analyzing a main controller switching message sent by a target controller to obtain a multicast serial number and a main controller ID;

And step two, when the ID of the main controller is inconsistent with the main controller, determining the target controller as a new main controller.

When master-slave switching occurs or a multi-controller storage array is established (namely, when a cluster is established), the new master controller can send master controller switching messages to all slave controllers. The host controller handover message may include, but is not limited to: multicast sequence number, master controller ID. For example, the master controller switching message may further include an original master controller ID, a subsequent data length, and a master-slave switching flag.

and when the main controller ID in the main controller switching message is inconsistent with the original main controller, determining that the target controller is a new main controller. Preferably, if the master controller switching message has a master-slave switching flag, the target controller sending the master controller switching message may be directly considered as the new master controller.

Preferably, in order to enable the slave controller to synchronize the management data with the master controller more quickly and accurately, the management data to be synchronized can be classified, and the slave controller performs classified storage and synchronization when storing the management data. Specifically, the management data may be classified in advance, and the management data types may include, but are not limited to, volume, host, and fan. For example, the management data type may be further specifically subdivided into management data corresponding to different volumes and management data corresponding to different hosts. When defining the management data synchronous message, the management data type can be set in the management data synchronous message, so that the management data synchronous message is a classified management data synchronous message. The step S104 processes the management data synchronization packet without the corresponding processing record according to the multicast sequence number sequence to synchronize the management data, which may specifically include:

step one, determining a management data type corresponding to a classification management data synchronous message; the management data types comprise volumes, hosts and fans;

And step two, synchronizing the management data corresponding to the management data type by using the management data content carried by the classified management data synchronization message.

For convenience of description, the above two steps will be described in combination.

After determining that the management data changes, the master controller writes the specific type of the management data into the message when adding the multicast serial number and the management data content into the management data synchronous message, so that the classified management data message can be obtained, and the classified management data synchronous message is sent to each slave controller in a multicast mode.

after receiving the categorized management data synchronization packet from the controller, the method described in the first embodiment determines the categorized management data synchronization packet to be processed, and then determines the management data type and the categorized management data from the categorized management data synchronization packet, and processes the stored management data corresponding to the management data type by using the categorized management data content.

Example two:

Referring to fig. 2, fig. 2 is a flowchart illustrating a second method for synchronizing management data according to an embodiment of the present invention, which is mutually related to the method for synchronizing management data disclosed in the first embodiment of the present invention, and includes the following steps:

s201, after the management data change, the master controller multicasts the management data synchronous message to each slave controller.

The management data synchronization message includes a multicast sequence number.

In order to realize that the master controller sends the management data synchronous message to the slave controllers in a multicast mode, the master controller and the slave controllers can be processed to be arranged in the same multicast group.

The specific implementation process of how the main controller determines that the management data changes may be referred to as an existing determination process, which is not described in detail herein.

After determining that the management data changes, the master controller may multicast a management data synchronization packet to the slave controllers in order to synchronize the management data stored by each slave controller with the master controller. In order to avoid destroying the logical relationship between the management data synchronization messages, the management data synchronization messages can be numbered, that is, different management data messages can include multicast serial numbers, so that the slave controller can process the received management data synchronization messages in sequence according to the multicast serial numbers.

after the master controller sends the management data synchronization message to the slave controller, the master controller does not need to interact with the slave controller so as to determine that the slave controller completes the management data synchronization. In the embodiment of the invention, the master controller can be in a waiting state after multicasting the management data synchronous message.

S202, receiving the target multicast sequence number which is sent from the controller, is missing and has no processing record.

after receiving the management data synchronization packet from the controller, the management data synchronization packet may be processed according to the management data synchronization method described in the first embodiment. The target multicast sequence number may be sent to the master after the slave finds that there is a missing target multicast sequence number.

specifically, the master controller may receive and analyze the reissue application packet sent by the slave controller to obtain the target multicast sequence number. The number of the target multicast sequence numbers may be one or more.

S203, the target management data synchronous message corresponding to the target multicast serial number is sent to the slave controller additionally, so that the slave controller processes the management data synchronous message without the corresponding processing record according to the multicast serial number sequence to synchronize the management data.

the master controller finds out the target management synchronous message corresponding to the target multicast serial number, and then sends the target management synchronous playing to the slave controller missing the target synchronous management data message. After receiving the target management data synchronous message from the slave controller, the slave controller can continuously judge whether the message is continuous or not, and process the received management data synchronous message under the condition of continuous multicast serial numbers so as to synchronize management data.

Preferably, in order to avoid that the target management data synchronization packet of a certain slave controller which is subject to complementary transmission is multicast to each slave controller in the multicast group and causes interference to the slave controller, the target management data synchronization packet may be separately complementary transmitted to the slave controller when the target management data is complementary transmitted. The target management data message can be complemented to the slave controller lacking the message in an end-to-end communication mode.

The second management data synchronization method provided by the embodiment of the invention is applied to the master controller in the storage device, and the master controller multicasts a management data synchronization message to each slave controller after the management data changes; then, only the missing target multicast sequence number which is sent by the individual slave controller and has no processing record needs to be passively waited; and then supplementing the target management data synchronous message corresponding to the target multicast serial number to the slave controller. Therefore, compared with the existing main controller which needs to carry out end-to-end communication on each slave controller and repeatedly confirms whether the management data are successfully synchronized, the method can greatly reduce the pressure of the main controller on the synchronization of the management data, reduce the calculation and storage performance of the main controller, save more resources for processing the management task of the storage array, and ensure the stability of the storage equipment.

it should be noted that, based on the second embodiment, the embodiment of the present invention further provides a corresponding improvement scheme. In the preferred/improved embodiment, the same steps as those in the above embodiment or corresponding steps may be referred to each other, and corresponding advantageous effects may also be referred to each other, which are not described in detail in the preferred/improved embodiment herein.

Preferably, in order to enable the slave controller to synchronize the management data with the master controller more quickly and accurately, the management data to be synchronized can be classified, and thus, the slave controller performs classified storage and synchronization when storing the management data. Specifically, the management data may be classified in advance, and the management data types may include, but are not limited to, volume, host, and fan. For example, the management data type may be further specifically subdivided into management data corresponding to different volumes and management data corresponding to different hosts. When defining the management data synchronous message, the management data type can be set in the management data synchronous message, so that the management data synchronous message is a classified management data synchronous message.

In order to achieve the above technical effect, the step S201, after the management data changes, multicasting the management data synchronization packet to each slave controller, includes:

Step one, after the management data are changed, determining the type of the management data to be synchronized; the management data types comprise volumes, hosts and fans;

Step two, generating a classified management data synchronous message matched with the type of the management data;

And step three, multicasting the classified management data synchronous message to each slave controller so that each slave controller can synchronously manage data according to the type of the management data.

For convenience of description, the above three steps will be described in combination.

The master control may determine the type of management data to be synchronized after determining that the management data transmission changes. When the management data synchronous message is generated, the management data type is indicated in the management data type in the management data synchronous message, and thus the management data synchronous message is the classified management data synchronous message. Then, the classification management data synchronous message is multicast to each slave controller.

After receiving the synchronous messages of the classified management data, each slave controller can process the classified and stored management data according to the type of the management data so as to keep synchronization with the master controller.

example three:

The management data synchronization method provided in the first embodiment and the second embodiment may be applied to the same multi-controller storage array, that is, the master controller executes the management data synchronization method provided in the second embodiment, and the slave master controller executes the management data synchronization method provided in the second embodiment, and the implementation process includes:

first, management data is classified. Such as volume being one type, host being one type, fan being one type, etc. Each data in each data type has an ID field that is unique within that type of data, e.g., volume 1 has an ID of 0, volume 2 has an ID of 1, and host 1 has an ID of 2.

Secondly, all controllers form a multicast group, when the management data changes, the main controller needs to multicast the changed management data to the multicast group (possibly needs to send a plurality of multicast messages in batch), and the multicast messages can include a main controller ID, a multicast serial number, a type of the management data, a data ID and detailed data content.

Thirdly, after receiving the multicast message from the slave controller, judging whether the message is processed according to the ID of the master controller and the multicast serial number, and if the message is processed, ignoring the message; otherwise, judging whether the multicast serial number is continuous, if not, recording the missing multicast serial number, sending the missing multicast serial number to the main controller in a unicast mode, storing the data received this time, and analyzing the message after the missing multicast message is received again; otherwise, analyzing the message with continuous multicast serial number and unprocessed message, and updating the self management data. And the multicast messages are analyzed in sequence, so that the data consistency with the main controller can be ensured.

And finally, after the cluster is established or the main controller is switched, the main controller is defaulted that all the management data are changed, the main controller multicasts a main controller switching message firstly, then multicasts all the management data, and the multicast sequence number starts from 0 again. After receiving the message of 'main controller switching', the common node clears the self management data and resynchronizes the main controller data.

In order to facilitate understanding of the above implementation process by those skilled in the art, and how to combine the management data synchronization methods provided in the first embodiment and the second embodiment in practical application, detailed descriptions are provided below by taking a specific application scenario as an example.

Referring to fig. 3, fig. 3 is a flowchart illustrating an implementation of a method for managing data synchronization according to an embodiment of the present invention.

First, the management data is classified, e.g., volume is one type, host is one type, fan is one type, and so on. Each data in each data type has an ID field that is unique within that type of data, e.g., volume 1 has an ID of 0, volume 2 has an ID of 1, host 1 has an ID of 0, etc. The invention does not provide a specific classification method and can be automatically divided in the specific implementation. Thus, when the subsequent main controller records the multicast record, the data ID can be recorded without recording the detailed content of the data, and the data volume of the record is reduced.

secondly, all controllers form a multicast group, when the management data of the master controller changes, the master controller needs to multicast the changed management data to the multicast group (possibly, a plurality of multicast messages, namely management data synchronization messages, need to be sent, and each message can send one or more types of data), and records a sending record (including the ID of the master controller, a multicast serial number, the type of the management data, the ID of data 1, the ID of data 2, … and the ID of data n).

the format of the management data synchronization packet (packet 1 in fig. 3, the message type is 0) is as shown in table 1:

TABLE 1

the data content part in the management data synchronization message is as shown in table 2:

TABLE 2

It can be seen that the message format in the multicast management of data includes:

Multicast sequence number: starting from 0, the sequence is increased progressively, and the multicast message sent by the main controller is identified;

main controller ID: the unique identifier of the master controller;

Message type: here, the value 0 represents multicast management data;

The subsequent data length: in this message, the number of bytes following this field.

Data type: the data type of the management data to be transmitted is only one type of data to be transmitted at a time.

Marking the full data: 0 represents this type of management data containing only changes; 1 denotes that all management data of this type are included;

The number of data is as follows: the number of the transmitted management data;

ID of data 1: data ID of the 1 st data;

detailed content length of data 1: 1, the number of bytes of the message occupied by the detailed data content;

Details of data 1: details of the 1 st data;

ID of data n: data ID of nth data;

Detailed content length of data n: the number of bytes of the message occupied by the nth data detailed content;

details of data n: details of the nth data.

the main controller switching message (message 2) is used to inform other controllers that the main controller has been switched (message type is 1), and its specific message format is as shown in table 3:

TABLE 3

a reissue application message (message 3 in fig. 3) for notifying the unreceived master controller of the multicast message, where the specific message format is as shown in table 4:

TABLE 4

Again, as shown in fig. 3, a processing flow after receiving the multicast packet 1 from the controller is shown as follows:

Step1, receiving the multicast message 1, if receiving, then going to the next Step.

Step2, uniquely identifying a message according to the main controller ID and the multicast serial number, judging whether the message is processed, and if so, ignoring; otherwise go to the next step.

Step3, acquiring the multicast sequence number in the message, judging whether the multicast sequence number is continuous with the multicast sequence number processed last time, if not, turning to the next Step; otherwise go to Step 6.

and Step4, assembling the missing multicast serial numbers into a message 3 (namely, a retransmission application message), transmitting the message to the main controller by using unicast, and turning to the next Step.

Step5, saving the currently received message, and turning to Step1 after the message is not processed.

Step6, the received messages with continuous multicast sequence numbers (including those stored but not processed before) are processed in sequence, and the self management data is updated.

Step7 (not shown in the figure), after the master controller receives the message of Step4, it should immediately obtain the corresponding data according to the sending record, and send the multicast message 1 using the missing multicast sequence number. Therefore, the common nodes can be ensured to synchronize the data of the main controller in time.

in the above flow, if there are multiple packet losses in the network, the unprocessed packet in Step5 may not be updated in time, so the slave controller needs to restart the thread, and continuously check whether there is a stored but unprocessed packet in Step 5. If so, indicating that there is a missing multicast sequence number, Step4 is executed.

Finally, after the cluster is established or the master controller is switched, the master controller multicasts the 'master controller switching' message (the same as the master controller switching message in the above) first, then multicasts all the management data, and the multicast sequence number starts from 0 again. After receiving the 'main controller switching' message, the common node clears the self management data and clears the message record and data related to the old main controller.

Therefore, in this embodiment, by using a multicast technology, an increasing multicast sequence number is designed, and multicast packets are sequentially processed, so that the consistency of the management data in the slave controller and the master controller is ensured under the condition of reducing the synchronous workload of the master controller.

example four:

Corresponding to the above method embodiment, an embodiment of the present invention further provides a storage device, and the storage device described below and the management data synchronization method described above may be referred to correspondingly.

referring to fig. 4, the storage device includes:

A plurality of controllers, each controller comprising:

A memory for storing a computer program;

a processor for implementing the steps of the target method when executing the computer program;

From the controller D1 among the plurality of controllers, the target method to be executed is the method of the above-described embodiment one;

the main controller D2 among the plurality of controllers performs the target method as in the above second embodiment.

Specifically, referring to fig. 5, fig. 5 is a schematic diagram of a specific structure of a controller in a storage device according to the present embodiment, where the controller may generate a relatively large difference due to different configurations or performances, and may include one or more processors (CPUs) 322 (e.g., one or more processors) and a memory 332, and one or more storage media 330 (e.g., one or more mass storage devices) storing an application 342 or data 344. Memory 332 and storage media 330 may be, among other things, transient storage or persistent storage. The program stored on the storage medium 330 may include one or more modules (not shown), each of which may include a series of instructions operating on a data processing device. Still further, the central processor 322 may be configured to communicate with the storage medium 330 to execute a series of instruction operations in the storage medium 330 on the controller 301.

The controller 301 may also include one or more power supplies 326, one or more wired or wireless network interfaces 350, one or more input-output interfaces 358, and/or one or more operating systems 341. Such as Windows Server, Mac OS XTM, UnixTM, LinuxTM, FreeBSDTM, etc.

the steps in the management data synchronization method described above may be implemented by the structure of the controller.

example five:

Corresponding to the first method embodiment, the embodiment of the present invention further provides a management data synchronization apparatus applicable to the slave controller, and the management data synchronization apparatus described below and the management data synchronization method described above may be referred to in correspondence with each other.

Referring to fig. 6, the apparatus includes:

a management data synchronization message receiving module 101, configured to receive and analyze a management data synchronization message multicast by a master controller after management data changes, and obtain a multicast serial number;

the message checking module 102 is configured to determine whether a missing target multicast sequence number exists and no processing record exists by using the multicast sequence number;

The message missing processing module 103 is configured to send a target multicast serial number to the master controller if the target multicast serial number exists, and receive a target management data synchronization message corresponding to the target multicast serial number that is retransmitted by the master controller;

and the data synchronization module 104 is configured to, if the target multicast serial number does not exist, process the management data synchronization packet without the corresponding processing record according to the multicast serial number sequence, so as to synchronize the management data.

The first management data synchronization device provided by the embodiment of the invention is applied to the slave controller in the storage device, the management data synchronization message received by the slave controller automatically verifies whether the message is missing or not according to the multicast serial number, and actively asks for the target management data synchronization message corresponding to the target multicast serial number from the master controller after determining that the missing and recorded target multicast serial number exists. Then, after determining that the multicast serial numbers are continuous, processing the management data synchronous messages without corresponding processing records according to the multicast serial number sequence, and then realizing synchronous management of data with the main controller. In the process, the slave controllers transfer the original management data synchronization verification operation to the slave controllers for processing, and the master controller only needs to multicast the management data synchronization message and passively reissue the target management data synchronization message which is not received by the individual slave controllers. Namely, the management data synchronization task of the master controller is shared to each slave controller, so that the problem of resource occupation of the master controller can be avoided, the management quality of the storage array of the master controller can be guaranteed, and the stability of the storage equipment can be further guaranteed.

In one embodiment of the present invention, the method further comprises:

And the master-slave switching processing module is used for clearing the management data synchronized with the master controller after determining that the master controller is switched so as to synchronize the management data of a new master controller.

In a specific embodiment of the present invention, the master-slave switching processing module is specifically configured to receive and analyze a master controller switching message sent by a target controller, and obtain a multicast serial number and a master controller ID; and when the ID of the main controller is inconsistent with the main controller, determining the target controller as a new main controller.

in a specific embodiment of the present invention, the message checking module 102 is specifically configured to determine whether the multicast sequence numbers are consecutive; if not, determining the missing multicast sequence number, and determining the missing multicast sequence number as the target multicast sequence number when the missing multicast sequence number has no corresponding processing record.

In a specific embodiment of the present invention, the data synchronization module 104 is specifically configured to screen out a management data synchronization packet without a corresponding processing record by using the processing record; sequencing the screened management data synchronous messages by using the multicast serial number; and analyzing the management data synchronous messages in sequence according to the arrangement sequence to obtain the management data content.

in a specific embodiment of the present invention, the message missing processing module 103 is specifically configured to send a reissue application message carrying the target multicast sequence number to the master controller.

in a specific embodiment of the present invention, the data synchronization module 104 is specifically configured to determine a management data type corresponding to the classified management data synchronization packet when the management data synchronization packet is the classified management data synchronization packet; the management data types comprise volumes, hosts and fans; and synchronizing the management data corresponding to the management data type by using the management data content carried by the classified management data synchronization message.

Example six:

corresponding to the second method embodiment, the second embodiment of the present invention further provides a management data synchronization apparatus applicable to a host controller, and the management data synchronization apparatus described below and the management data synchronization method described above may be referred to in correspondence with each other.

Referring to fig. 7, the apparatus includes the following modules:

a management data synchronization message multicast module 201, configured to multicast a management data synchronization message to each slave controller after the management data changes; the management data synchronous message comprises a multicast serial number;

A missing message determining module 202, configured to receive a missing target multicast sequence number that is sent from a controller and has no processing record;

the message reissue module 203 is configured to reissue the target management data synchronization message corresponding to the target multicast sequence number to the slave controller, so that the slave controller processes the management data synchronization message without the corresponding processing record according to the multicast sequence number sequence, so as to synchronize the management data.

The second management data synchronization device provided by the embodiment of the invention is applied to the master controller in the storage device, and the master controller multicasts a management data synchronization message to each slave controller after the management data changes; then, only the missing target multicast sequence number which is sent by the individual slave controller and has no processing record needs to be passively waited; and then supplementing the target management data synchronous message corresponding to the target multicast serial number to the slave controller. Therefore, compared with the existing main controller which needs to carry out end-to-end communication on each slave controller and repeatedly confirms whether the management data are successfully synchronized, the device can greatly reduce the pressure of the main controller on the synchronization of the management data, reduce the calculation and storage performance of the main controller, save more resources for processing the management tasks of the storage array, and ensure the stability of the storage equipment.

in a specific embodiment of the present invention, the missing packet determining module 202 is configured to receive and analyze a reissue application packet sent from the controller, and obtain a target multicast sequence number.

In an embodiment of the present invention, the message reissue module 203 is specifically configured to reissue the target management data synchronization message to the slave controller separately.

In a specific embodiment of the present invention, the management data synchronization packet multicast module 201 is specifically configured to determine a type of management data to be synchronized after the management data changes; the management data types comprise volumes, hosts and fans; generating a classified management data synchronous message matched with the type of the management data; and multicasting the classified management data synchronous message to each slave controller so that each slave controller synchronously manages the data according to the type of the management data.

example seven:

corresponding to the above method embodiment, the embodiment of the present invention further provides a readable storage medium, and a readable storage medium described below and a management data synchronization method described above may be referred to in correspondence with each other.

A readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the steps of the method of managing data synchronization of the above-mentioned method embodiments.

The readable storage medium may be a usb disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and various other readable storage media capable of storing program codes.

It is to be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.

those of skill would further appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or combinations of both, and that the various illustrative components and steps have been described above generally in terms of their functionality in order to clearly illustrate this interchangeability of hardware and software. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.

Claims (15)

1. a method for managing data synchronization, comprising:

the slave controller receives and analyzes a management data synchronous message multicast by the master controller after the management data changes, and obtains a multicast serial number;

determining whether a missing target multicast sequence number without processing record exists by using the multicast sequence number;

If yes, sending the target multicast serial number to the main controller, and receiving a target management data synchronous message corresponding to the target multicast serial number and sent by the main controller;

if not, processing the management data synchronous message without the corresponding processing record according to the multicast sequence number sequence so as to synchronize the management data.

2. The management data synchronization method according to claim 1, further comprising:

And after the main controller is determined to be switched, clearing the management data synchronized with the main controller so as to synchronize the management data of the new main controller.

3. the management data synchronization method of claim 2, wherein the determining a master controller switch comprises:

Receiving and analyzing a main controller switching message sent by a target controller to obtain a multicast serial number and a main controller ID;

and when the ID of the main controller is inconsistent with the main controller, determining that the target controller is the new main controller.

4. The method of claim 1, wherein determining whether there is a missing and record-not-processed target multicast sequence number using the multicast sequence number comprises:

judging whether the multicast serial numbers are continuous or not;

if not, determining the missing multicast sequence number, and determining the missing multicast sequence number as the target multicast sequence number when the missing multicast sequence number has no corresponding processing record.

5. The management data synchronization method according to claim 1, wherein processing the management data synchronization packet without the corresponding processing record in the multicast sequence number order to synchronize management data comprises:

Screening out the management data synchronous message without the corresponding processing record by utilizing the processing record;

sequencing the screened management data synchronous messages by using the multicast serial number;

And sequentially analyzing the management data synchronous messages according to the arrangement sequence to obtain the management data content.

6. The management data synchronization method of claim 1, wherein sending the target multicast sequence number to the master controller comprises:

and sending a reissue application message carrying the target multicast serial number to the main controller.

7. the management data synchronization method according to any one of claims 1 to 6, wherein the management data sync message is a classified management data sync message, and the management data sync message having no corresponding processing record is processed in the multicast sequence number order to synchronize management data, comprising:

determining a management data type corresponding to the classified management data synchronous message; wherein the management data types comprise volumes, hosts and fans;

and synchronizing the management data corresponding to the management data type by using the management data content carried by the classified management data synchronization message.

8. A method for managing data synchronization, comprising:

after the management data change, the master controller multicasts a management data synchronization message to each slave controller; the management data synchronous message comprises a multicast serial number;

receiving a missing target multicast sequence number which is sent from a controller and has no processing record;

And supplementing the target management data synchronous message corresponding to the target multicast serial number to the slave controller so that the slave controller processes the management data synchronous message without the corresponding processing record according to the multicast serial number sequence to synchronize management data.

9. the management data synchronization method of claim 8, wherein receiving the missing and record-less target multicast sequence number sent from the controller comprises:

and receiving and analyzing the reissue application message sent by the slave controller to obtain the target multicast serial number.

10. the management data synchronization method according to claim 8, wherein the supplementing the target management data synchronization packet corresponding to the target multicast sequence number to the slave controller includes:

And independently transmitting the target management data synchronous message to the slave controller.

11. the management data synchronization method according to any one of claims 8 to 10, wherein multicasting the management data synchronization packet to each slave controller after the management data is changed comprises:

After the management data are changed, determining the type of the management data to be synchronized; wherein the management data types comprise volumes, hosts and fans;

Generating a classified management data synchronous message matched with the type of the management data;

and multicasting the classified management data synchronous message to each slave controller so that each slave controller can synchronize the management data according to the type of the management data.

12. A storage device, comprising:

a plurality of controllers, each of the controllers comprising:

a memory for storing a computer program;

A processor for implementing the steps of the target method when executing the computer program;

A slave controller of a plurality of said controllers, said target method being performed according to the method of any one of claims 1 to 7;

a master controller of a plurality of said controllers, said target method being performed according to the method of any of claims 8 to 11.

13. a managed data synchronization apparatus, for use with a slave controller, comprising:

the management data synchronous message receiving module is used for receiving and analyzing the management data synchronous message multicast by the main controller after the management data changes, and acquiring a multicast serial number;

The message checking module is used for determining whether a missing target multicast serial number without processing record exists by using the multicast serial number;

the message missing processing module is used for sending the target multicast serial number to the main controller and receiving a target management data synchronous message corresponding to the target multicast serial number which is sent by the main controller again if the target multicast serial number exists;

And the data synchronization module is used for processing the management data synchronization message without the corresponding processing record according to the multicast serial number sequence if the target multicast serial number does not exist so as to synchronize the management data.

14. a management data synchronization device applied to a main controller comprises:

the management data synchronous message multicast module is used for multicasting the management data synchronous messages to each slave controller after the management data changes; the management data synchronous message comprises a multicast serial number;

The missing message determining module is used for receiving the missing target multicast serial number which is sent from the controller and has no processing record;

And the message retransmission module is used for retransmitting the target management data synchronous message corresponding to the target multicast serial number to the slave controller so that the slave controller processes the management data synchronous message without the corresponding processing record according to the multicast serial number sequence to synchronize management data.

15. A readable storage medium, characterized in that it has stored thereon a computer program which, when being executed by a processor, carries out the steps of the method for managing data synchronization according to any one of claims 1 to 11.