WO2021046935A1 - Management data synchronization method and apparatus, storage device and readable storage medium - Google Patents

Abstract

A management data synchronization method and apparatus applied to a master controller, and a management data synchronization method and apparatus applied to a slave controller, and a storage device and a readable storage medium. According to the method, multicast technology is used to design progressively increasing multicast serial numbers and sequentially process multicast messages, and a slave controller determines, by means of the multicast serial numbers, whether messages are missing, and insofar as the messages are missing, actively pulls missing messages from a master controller, such that management data synchronization is realized. According to the method, insofar as the synchronization workload of the master controller is reduced, the consistency of management data in the slave controller and the master controller is ensured, and the system stability of a multi-controller storage array can be further ensured.

Description

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

This application claims the priority of the Chinese patent application filed to the Chinese Patent Office on September 12, 2019, the application number is 201910866500.6, and the invention title is "Management data synchronization method, device, storage device and readable storage medium". All of them The content is incorporated in this application by reference.

Technical field

The present invention relates to the field of storage technology, in particular to two management data synchronization methods, devices, storage devices and readable storage media.

Background technique

With the rapid development of the Internet, especially the development of cloud computing and network networking, user and application data are showing rapid growth, and storage arrays have emerged to store data.

A multi-controller storage array is a commonly used storage device that consists of a master controller and multiple slave controllers. The master controller is responsible for managing the storage array. In order to improve reliability, when the master controller loses its management capability (such as a sudden shutdown of the controller), a slave controller will be selected as the new master controller and take over the management of the master controller Task, the old master controller becomes the slave controller. After the main controller is switched, in order to ensure that the management service remains unchanged, the management data of the main controller needs to be synchronized between the controllers.

At present, the data synchronization scheme is often that the master controller sends management data to the slave controller. Each time data is sent, in order to ensure the consistency of the management data stored by each controller, the master controller needs to use complex algorithms to ensure data consistency. Occupies a large part of the performance of the main controller. Specifically, the master control needs to maintain communication with each slave controller one by one, and constantly verify whether the management data of the slave controller is consistent with the latest management data in the master controller. There are more slave controllers or management data changes. When it is more frequent, the threads used to synchronize the management data in the main control will occupy the computing resources and storage resources of the main controller to ensure the consistency of the management data. Due to the synchronization management data occupancy performance, it is difficult for the main controller to guarantee the management quality of the storage array. In severe cases, the multi-controller storage array may not be able to provide external storage services and affect user experience.

In summary, how to effectively solve the problem of the synchronization of the management data occupying the performance of the main controller is a technical problem urgently needed to be solved by those skilled in the art.

Summary of the invention

The purpose of the present invention is to provide two management data synchronization methods, devices, storage devices, and readable storage media. By sharing management data synchronization tasks from the controller, the performance of the main controller is reduced, and the multi-controller storage array can be guaranteed. The stability of storage devices is conducive to improving user experience.

In order to solve the above technical problems, the present invention provides the following technical solutions:

The first management data synchronization method includes:

The slave controller receives and parses the management data synchronization message multicasted by the master controller after the management data changes, and obtains the multicast sequence number;

Using the multicast sequence number to determine whether there is a target multicast sequence number that is missing and has no processing record;

If yes, send the target multicast sequence number to the main controller, and receive a target management data synchronization message corresponding to the target multicast sequence number reissued by the main controller;

If not, the management data synchronization messages without corresponding processing records are processed in the order of the multicast sequence number to synchronize the management data.

Preferably, it also includes:

After it is determined that the main controller is switched, the management data that has been synchronized with the main controller is cleared, so as to synchronize the management data of the new main controller.

Preferably, the determining the main controller switching includes:

Receive and parse the master controller switching message sent by the target controller to obtain the multicast sequence number and master controller ID;

When the main controller ID is inconsistent with the main controller, it is determined that the target controller is the new main controller.

Preferably, using the multicast sequence number to determine whether there is a target multicast sequence number that is missing and has no processing record includes:

Judging whether the multicast sequence number is continuous;

If not, the missing multicast sequence number is determined, and when there is no corresponding processing record for the missing multicast sequence number, it is determined that the missing multicast sequence number is the target multicast sequence number.

Preferably, processing the management data synchronization message without corresponding processing records in the order of the multicast sequence number to synchronize the management data includes:

Use processing records to filter out management data synchronization messages without corresponding processing records;

Order the filtered management data synchronization messages by using the multicast sequence number;

The management data synchronization message is sequentially parsed according to the sequence to obtain the management data content.

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

Sending a reissuance request message carrying the target multicast sequence number to the main controller.

Preferably, the management data synchronization message is a classified management data synchronization message, and the management data synchronization message without corresponding processing records is processed in the order of the multicast sequence number to synchronize the management data, including:

Determine the management data type corresponding to the classified management data synchronization message; wherein, the management data type includes volume, host, and fan;

The management data corresponding to the management data type is synchronized by using the management data content carried in the classification management data synchronization message.

The second method of managing data synchronization includes:

After the management data changes, the master controller multicasts a management data synchronization message to each slave controller; the management data synchronization message includes a multicast sequence number;

Receive the missing and no-processed target multicast sequence number sent from the controller;

Re-send 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 corresponding processing records in the order of the multicast sequence number To synchronize management data.

Preferably, receiving the missing and unprocessed target multicast sequence number sent from the controller includes:

Receiving and analyzing the reissuance request message sent by the slave controller to obtain the target multicast sequence number.

Preferably, re-sending the target management data synchronization message corresponding to the target multicast sequence number to the slave controller includes:

The target management data synchronization message is separately reissued to the slave controller.

Preferably, after the management data changes, multicasting the management data synchronization message to each slave controller includes:

After the management data changes, determine the management data type to be synchronized; wherein, the management data type includes volume, host, and fan;

Generating a classification management data synchronization message matching the management data type;

Multicast the classification management data synchronization message to each of the slave controllers, so that each of the slave controllers synchronizes the management data according to the management data type.

A storage device including:

A plurality of controllers, each of the controllers includes:

Memory, used to store computer programs;

The processor is used to implement the steps of the target method when the computer program is executed;

The target method executed by the slave controller of the plurality of controllers is the same as the above-mentioned first management data synchronization method;

The target method executed by the main controller of the plurality of controllers is the same as the above-mentioned second management data synchronization method.

The first management data synchronization device, applied to the slave controller, includes:

The management data synchronization message receiving module is used to receive and parse the management data synchronization message multicasted by the main controller after the management data changes, and obtain the multicast sequence number;

A message checking module, configured to use the multicast sequence number to determine whether there is a target multicast sequence number that is missing and has no processing record;

The message missing processing module is configured to send the target multicast sequence number to the main controller if the target multicast sequence number exists, and receive the corresponding target multicast sequence number reissued by the main controller Target management data synchronization message;

The data synchronization module is configured to, if there is no target multicast sequence number, process the management data synchronization messages without corresponding processing records in the order of the multicast sequence numbers to synchronize the management data.

The second type of management data synchronization device, applied to the main controller, includes:

The management data synchronization message multicast module is configured to multicast a management data synchronization message to each slave controller after the management data changes; the management data synchronization message includes a multicast sequence number;

The missing message determination module is used to receive the missing target multicast sequence number sent from the controller without processing records;

The message reissue module is used 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 non-corresponding processing records in the order of the multicast sequence number The management data synchronization message is used to synchronize the management data.

A readable storage medium on which a computer program is stored, and when the computer program is executed by a processor, the steps of the above-mentioned first or second method for managing data synchronization are realized.

The first management data synchronization method provided by the embodiment of the present invention is applied to the slave controller in the storage device, the management data synchronization message received from the controller is verified by the multicast sequence number whether the message is missing or missing, and After determining that there is a target multicast sequence number that is missing or missing and has no processing record, it actively asks the main controller for the target management data synchronization message corresponding to the target multicast sequence number. Then, after determining that the multicast sequence numbers are continuous, the management data synchronization messages without corresponding processing records are processed in the order of the multicast sequence numbers to realize the synchronization of the management data with the main controller. In this process, the slave controller transfers the original management data synchronization verification operation from itself for processing, and the master controller only needs to multicast the management data synchronization message, and passively reissue the target management that was not received by the individual slave controllers. The data synchronization message is sufficient. That is, it realizes that the management data synchronization task of the master controller is shared to each slave controller, which can avoid the problem of resource occupation of the master controller, can guarantee the quality of the storage array management of the master controller, and further ensure the stability of the storage device .

Correspondingly, the master controller in the storage device applies the second management data synchronization method provided by the embodiment of the present invention. After the management data changes, the master controller multicasts a management data synchronization message to each slave controller; Then it is only necessary to passively wait for the missing and unprocessed target multicast sequence numbers sent by the individual slave controllers; then, the target management data synchronization messages corresponding to the target multicast sequence numbers are reissued to the slave controllers. It can be seen that, compared with the existing master controller that needs to communicate end-to-end with each slave controller and repeatedly confirm whether the management data is successfully synchronized, this method can greatly reduce the pressure of the master controller's management data synchronization. Reduce the calculation and storage performance of the main controller, save more resources to process storage array management tasks, and ensure the stability of the storage device.

Correspondingly, the embodiment of the present invention also provides two management data synchronization devices, storage devices, and readable storage media corresponding to the above two management data synchronization methods, which have the above technical effects, and will not be repeated here.

Description of the drawings

In order to explain the embodiments of the present invention or the technical solutions in the prior art more clearly, the following will briefly introduce the drawings that need to be used in the description of the embodiments or the prior art. Obviously, the drawings in the following description are only These are some embodiments of the present invention. For those of ordinary skill in the art, other drawings can be obtained based on these drawings without creative work.

Figure 1 is an implementation flowchart of the first management data synchronization method in an embodiment of the present invention;

2 is an implementation flowchart of a second management data synchronization method in an embodiment of the present invention;

3 is a schematic diagram of a specific implementation process of a method for managing data synchronization in an embodiment of the present invention;

4 is a schematic structural diagram of a storage device in an embodiment of the present invention;

FIG. 5 is a schematic diagram of a specific structure of a controller in a storage device provided by this embodiment;

6 is a schematic structural diagram of a first management data synchronization device in an embodiment of the present invention;

Fig. 7 is a schematic structural diagram of a second management data synchronization device in an embodiment of the present invention.

detailed description

In order to enable those skilled in the art to better understand the solution of the present invention, the present invention will be further described in detail below with reference to the accompanying drawings and specific embodiments. Obviously, the described embodiments are only a part of the embodiments of the present invention, rather than all the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those of ordinary skill in the art without creative work shall fall within the protection scope of the present invention.

Example one:

Please refer to Figure 1. Figure 1 is an implementation flowchart of a first management data synchronization method in an embodiment of the present invention. The method includes the following steps:

S101. The slave controller receives and parses the management data synchronization message multicasted by the master controller after the management data changes, and obtains the multicast sequence number.

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

In the embodiment of the present invention, after the master controller determines that the management data has changed, it can send a management data synchronization message to each slave controller in a multicast manner. The management data synchronization message includes but is not limited to the multicast sequence number, Manage data content, where the multicast sequence number is the sequence number of the message sent. In order to facilitate data synchronization, the management data synchronization message can be numbered in sequence. In other words, a multicast group can be set up in advance for the master controller and each slave controller, and then the master controller multicasts management data synchronization messages to the multicast group. In this way, each slave controller in the multicast group is The management data synchronization message can be received.

After receiving the management data synchronization message from the controller, the management data synchronization message can be parsed according to the protocol of the management data synchronization message to obtain the multicast sequence number of each management data synchronization message.

S102: Use the multicast sequence number to determine whether there is a target multicast sequence number that is missing and has no processing record.

In the embodiment of the present invention, after processing the management data synchronization message, the processing record of the management data synchronization message may be recorded. For example, after processing a management data synchronization message, the multicast sequence number corresponding to the management data synchronization message can be added to the processed message table/queue. In this way, the processed message table/queue can be queried. Determine which management data synchronization messages have been processed; you can also set a processing variable separately. After each management data synchronization message is processed, the multicast sequence number corresponding to the management data synchronization message is assigned to the processing variable. By querying the processing variable, the management data message corresponding to the specific multicast sequence number that has been processed can be determined.

Among them, the target multicast sequence number is not only corresponding to the missing management data synchronization message, but also needs to satisfy that its corresponding management data synchronization message is an unprocessed management data synchronization message. In other words, when the missing message is a processed message, the missing message can be ignored.

Specifically, the target multicast sequence number is determined, including:

Step 1: Determine whether the multicast sequence number is continuous;

Step 2: If no, determine the missing multicast sequence number, and when there is no corresponding processing record for the missing multicast sequence number, determine the missing multicast sequence number as the target multicast sequence number.

For ease of description, the above two steps are combined for description below.

After obtaining the multicast sequence number, first determine whether the received multicast sequence number is continuous. Specifically, if n historically received and processed management data synchronization messages are received, and m management data synchronization messages are currently received, it is determined that the m management data synchronization messages received are the same as the historically received and processed management data synchronization messages. Whether the multicast sequence numbers of the n management data synchronization messages are continuous, and whether the currently received multicast sequence numbers are continuous. For example, there are a total of 10 management data synchronization messages received and processed in history. The multicast message sequence number ranges from 00000 to 00010, and two more management data synchronization messages are currently received. The multicast message sequence numbers are 000009 and 000012. The newly received management data synchronization message is missing, that is, the two currently received management data synchronization messages are not continuous.

After determining that the received multicast sequence numbers are not continuous, it is further determined whether the management data synchronization message corresponding to the missing multicast sequence number has been processed. For example, when the received management data synchronization message is missing, but the missing management data synchronization message is a processed message, the missing management data synchronization message can be ignored at this time.

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 message may also be determined first, and then the management data that has been received in the multicast sequence number interval is further determined Whether there are missing target multicast sequence numbers between synchronization messages. Among them, the interval of the multicast sequence number may be a multicast sequence number greater than that corresponding to the processed multicast sequence number. For example, when the sequence number of the processed message is 6, the multicast sequence number interval can be (6.∞). When the newly received multicast sequence number is 7, 9, 10, it can be seen that 6 and 7 are continuous, but 7 and 9 are not Continuous, the multicast sequence number 8 is confirmed, so the multicast sequence number 8 can be determined as the target multicast sequence number.

It should be noted that after receiving one or more management data synchronization messages, the number of determined target multicast sequence numbers can be 0, or one or more, and the number of target multicast sequence numbers is based on actual conditions. Resulted from the judgment. When the number of target multicast sequence numbers is 0, that is, there is no target multicast sequence number, and when the number of target multicast sequence numbers is greater than 0, it is determined that there is a target multicast sequence number.

After determining whether there is a target multicast sequence number, the subsequent steps can be executed according to the judgment result. Specifically, if the judgment result is yes, step S103 is executed; if the judgment result is no, step S104 is executed.

S103: Send the target multicast sequence number to the main controller, and receive the target management data synchronization message corresponding to the target multicast sequence number reissued by the main controller.

In order to ensure the consistency of the management data, after discovering that there is a missing and unprocessed target multicast sequence number, the target multicast sequence number can be sent to the main controller.

Wherein, sending the target multicast sequence number to the main controller may be specifically sending a reissuance request message carrying the target multicast sequence number to the main controller. Among them, the reissuance application message includes, but is not limited to, the number of missing multicast sequence numbers and each target multicast sequence number. For example, the reissuance application message may also include the data content in common messages such as the slave controller ID and the integrity check code.

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

S104: Process the management data synchronization messages without corresponding processing records in the order of the multicast sequence number to synchronize the management data.

Considering that the management data synchronization messages corresponding to different multicast sequence numbers may be adjusted for the same management data, in order to avoid destroying the internal logical relationship of the management data processing by the public management data synchronization messages, when processing the management data synchronization messages , The management data synchronization messages without corresponding processing records can be processed in sequence according to the multicast sequence number, so as to realize the synchronization of management data with the main controller.

Among them, processing the management data synchronization message to synchronize the management data includes:

Step 1: Use processing records to filter out management data synchronization messages without corresponding processing records;

Step 2: Use the multicast sequence number to sort the filtered management data synchronization messages in order;

Step 3: Analyze the management data synchronization message in sequence according to the arrangement order to obtain the content of the management data.

For ease of description, the above three steps are combined for description below.

First, filter out management data synchronization messages without corresponding processing records based on processing records. Specifically, when the processing record is a processing variable, the management data synchronization message whose multicast sequence number is greater than the current value of the processing variable can be filtered out to be processed. When the processing record is the processed message table/queue, the processed message table/queue can be traversed to filter out the unprocessed management data synchronization messages.

Then, sort the filtered management data synchronization messages to be processed according to the multicast sequence number.

After sorting, the management data synchronization message can be parsed in sequence according to the sort order to obtain the management data content. Among them, in the parsing process, the management data content can be obtained from the management data synchronization message according to the specific format definition of the preset management data synchronization message. For example, in the management data synchronization include, you can record sequentially: multicast sequence number, main controller ID, subsequent data length, full data mark, data number, data content part; among them, the data content part is the management data content, data content It can be specifically: the ID of data 1, the detailed content length of data 1, the detailed content of data 1,..., the ID of data n, the detailed content length of data n, and the detailed content of data n. Of course, in other embodiments of the present invention, the specific data content of the management data synchronization message and the position sequence in the message can be adjusted.

The first management data synchronization method provided by the embodiment of the present invention is applied to the slave controller in the storage device, the management data synchronization message received from the controller is verified by the multicast sequence number whether the message is missing or missing, and After determining that there is a target multicast sequence number that is missing or missing and has no processing record, it actively asks the main controller for the target management data synchronization message corresponding to the target multicast sequence number. Then, after determining that the multicast sequence numbers are continuous, the management data synchronization messages without corresponding processing records are processed in the order of the multicast sequence numbers to realize the synchronization of the management data with the main controller. In this process, the slave controller transfers the original management data synchronization verification operation from itself for processing, and the master controller only needs to multicast the management data synchronization message, and passively reissue the target management that was not received by the individual slave controllers. The data synchronization message is sufficient. That is, sharing the management data synchronization task of the master controller to each slave controller can avoid the problem of resource occupation of the master controller, guarantee the management quality of the storage array of the master controller, and further ensure the stability of the storage device.

It should be noted that, based on the first embodiment described above, the embodiment of the present invention also provides a corresponding improvement scheme. In the preferred/improved embodiments, the same steps as those in the above-mentioned embodiments or corresponding steps can be referred to each other, and the corresponding beneficial effects can also be referred to each other, which will not be repeated in the preferred/improved embodiments herein.

Preferably, it is considered that the multi-controller storage array may have the situation that the main controller suddenly shuts down, malfunctions, etc., and cannot continue to manage the slave controller. At this time, by switching between the master and slave controllers, one of the slave controllers can be selected to take over the management of the master controller and become the new master controller. That is, when a master-slave switch occurs, all slave controllers need to synchronize management data with the new master controller, so that the subsequent master-slave switch can be successfully switched.

In the embodiment of the present invention, in order to synchronize the management data between the slave controller and the new master controller after the master-slave switchover, on the basis of the first embodiment, the following steps can be performed:

After confirming that the main controller is switched, clear the management data that has been synchronized with the main controller to synchronize the management data of the new main controller.

That is, after the slave controller determines that the controller is switched, it actively resigns the management data that has been synchronized with the original master controller in order to synchronize the management data with the new master controller.

Among them, the specific process of determining the main controller switching includes:

Step 1: Receive and parse the master controller switching message sent by the target controller to obtain the multicast sequence number and master controller ID;

Step 2: When the ID of the main controller is inconsistent with the main controller, determine that the target controller is the new main controller.

When a master-slave switch occurs, or when a multi-controller storage array is established (that is, when a cluster is established), the new master controller can send a master controller switch message to each slave controller. The main controller switching message may include, but is not limited to: a multicast sequence number, and the main controller ID. For example, the master controller switching message may also include the original master controller ID, subsequent data length, and master-slave switching flag.

When the main controller ID in the main controller switching message is inconsistent with the original main controller, it can be determined that the target controller is the new main controller. Preferably, if the main controller switching message has a master-slave switching flag, it can be directly considered that the target controller sending the main controller switching message is the new main controller.

Preferably, in order to facilitate the slave controller to synchronize the management data with the master controller faster and more accurately, the management data to be synchronized can also be classified, and the slave controller performs classified storage and synchronization when storing the management data. Specifically, the management data can be classified in advance, and the management data types can include, but are not limited to, volumes, hosts, and fans. For example, the management data type can also be specifically subdivided into management data corresponding to different volumes and management data corresponding to different hosts. When defining the management data synchronization message, the management data type can be set in the management data synchronization message. In this way, the management data synchronization message is a classified management data synchronization message. The above step S104 processes the management data synchronization messages without corresponding processing records in the order of the multicast sequence number to synchronize the management data, which may specifically include:

Step 1: Determine the management data type corresponding to the classified management data synchronization message; wherein, the management data type includes volume, host, and fan;

Step 2: Use the management data content carried in the classification management data synchronization message to synchronize the management data corresponding to the management data type.

For ease of description, the above two steps are combined for description below.

After determining that the management data has changed, the main controller adds the multicast serial number and management data content to the management data synchronization message, and then writes the specific type of management data into the message, so that the classified management management data message can be obtained , And send the classification management data synchronization message to each slave controller through multicast.

After receiving the classification management data synchronization message from the controller, after determining the classification management data synchronization message to be processed with reference to the method described in the first embodiment, the management data type can be determined from the classification management data synchronization message. And classification management data, and use the classification management data content to process the stored management data corresponding to the management data type.

Embodiment two:

Please refer to Figure 2. Figure 2 is an implementation flowchart of the second management data synchronization method in an embodiment of the present invention. This method and the management data synchronization method disclosed in the first embodiment can be cross-referenced, and include the following steps:

S201: After the management data changes, the master controller multicasts a management data synchronization message to each slave controller.

Among them, the management data synchronization message includes the multicast sequence number.

In order to realize that the master controller sends management data synchronization messages to the slave controllers in a multicast manner, the master controller and the slave controllers can be processed to be set in the same multicast group.

For the specific implementation process of how the main controller determines the change of the management data, please refer to the existing determination process, which will not be repeated here.

After the master controller determines that the management data has changed, in order to keep the management data stored by each slave controller synchronized with the master controller, the master controller can multicast management data synchronization messages to the slave controllers at this time. In order to avoid destroying the logical relationship between the management data synchronization messages, each management data synchronization message can be numbered, that is, different management data messages can include a multicast sequence number, so that the controller can pair the received messages according to the multicast sequence number. Manage data synchronization messages for sequential processing.

After the master controller sends the management data synchronization message to the slave controller, there is no need to interact with the slave controller to determine that the slave controller completes the management data synchronization. In the embodiment of the present invention, after the main controller multicasts the management data synchronization message, it can be in a waiting state.

S202: Receive a target multicast sequence number that is missing and has no processing record sent from the controller.

After receiving the management data synchronization message from the controller, the management data synchronization message can be processed according to the management data synchronization method described in the first embodiment. After the slave controller finds that there is a missing target multicast sequence number, it can send the target multicast sequence number to the master controller.

Specifically, the master controller may receive and parse the reissuance request message sent by the slave controller to obtain the target multicast sequence number. Among them, the number of target multicast sequence numbers can be one or more.

S203: Re-send 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 corresponding processing records in the order of the multicast sequence number to synchronize the management data.

The master controller finds out the target management synchronization message corresponding to the target multicast sequence number, and then reissues the target management synchronization playback to the slave controller that lacks the target synchronization management data message. After receiving the target management data synchronization message from the controller, it can continue to determine whether the message is continuous, and in the case of continuous multicast sequence numbers, process the received management data synchronization message to synchronize the management data.

Preferably, in order to avoid reissuing the target management data synchronization message of a certain slave controller being multicast to each slave controller in the multicast group, causing interference to the slave controllers, when the target management data is reissued , The target management data synchronization message can be separately reissued to the slave controller. That is, the end-to-end communication mode can be used to reissue the target management data message to the slave controller that lacks the message.

The master controller in the storage device applies the second management data synchronization method provided by the embodiment of the present invention. After the management data changes, the master controller multicasts the management data synchronization message to each slave controller; then only Passively wait for the missing and unprocessed target multicast sequence numbers sent by individual slave controllers; then, re-send the target management data synchronization message corresponding to the target multicast sequence number to the slave controller. It can be seen that compared with the existing master controller that requires end-to-end communication between each slave controller and repeatedly confirming whether the management data is successfully synchronized, this method can greatly reduce the pressure of the master controller's management data synchronization, and Reduce the calculation and storage performance of the main controller, save more resources to process storage array management tasks, and ensure the stability of the storage device.

It should be noted that, based on the second embodiment above, the embodiment of the present invention also provides a corresponding improvement scheme. In the preferred/improved embodiments, the same steps as those in the above-mentioned embodiments or corresponding steps can be referred to each other, and the corresponding beneficial effects can also be referred to each other, which will not be repeated in the preferred/improved embodiments herein.

Preferably, in order to facilitate the slave controller to synchronize the management data with the master controller faster and more accurately, the management data to be synchronized can also be classified. In this way, the slave controller performs classified storage and synchronization when storing the management data. Specifically, the management data can be classified in advance, and the management data types can include, but are not limited to, volumes, hosts, and fans. For example, the management data type can also be specifically subdivided into management data corresponding to different volumes and management data corresponding to different hosts. When defining the management data synchronization message, the management data type can be set in the management data synchronization message. In this way, the management data synchronization message is a classified management data synchronization message.

In order to achieve the above technical effect, the above step S201 multicasts a management data synchronization message to each slave controller after the management data changes, including:

Step 1. After the management data changes, determine the type of management data to be synchronized; among them, the type of management data includes volume, host, and fan;

Step 2: Generate a classification management data synchronization message matching the management data type;

Step 3: Multicast the classified management data synchronization message to each slave controller, so that each slave controller synchronizes the management data according to the management data type.

For ease of description, the above three steps are combined for description below.

After determining the management data transmission change, the main control can determine the type of management data to be synchronized. When the management data synchronization message is generated, the management data type in the management data synchronization message indicates the management data type, so that the management data synchronization message is a classified management data synchronization message. Then, multicast the classification management data synchronization message to each slave controller.

After each slave controller receives the classified management data synchronization message, the classified management data can be processed according to the management data type to keep synchronization with the main controller.

Example three:

The management data synchronization method provided by the above-mentioned first embodiment and the above-mentioned second embodiment can be applied to the same multi-controller storage array, that is, the master controller executes the management data synchronization method provided by the above two, and the slave master The device executes the management data synchronization method provided in the foregoing embodiment, and the implementation process is as follows:

First, classify the management data. For example, the volume is of one type, the host is of one type, and the fan is of one type. Each data in each data type has an ID field, and the ID field is unique in this type of data. For example, the ID of volume 1 is 0, the ID of volume 2 is 1, and the ID of host 1 is 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 (it may be necessary to send multiple multicast messages in batches). The multicast messages can include the master Controller ID, multicast serial number, management data type, data ID, data details.

Once again, after receiving the multicast message from the controller, it judges whether the message has been processed according to the ID of the main controller and the multicast sequence number. If it has been processed, ignore it; otherwise, judge whether the multicast sequence number is continuous, if not, Write down the missing multicast sequence number, and send it unicast to the main controller, save the data received this time, and parse the message after the missing multicast message is received again; otherwise, the parsed multicast sequence number is continuous For the unprocessed messages, update its own management data. Sequential analysis of multicast messages can ensure data consistency with the main controller.

Finally, when the cluster is established or the main controller is switched, all management data is changed by default. The main controller first multicasts the "main controller switching" message, and then multicasts all management data, and the multicast sequence number starts from 0 again. . After the ordinary node receives the "main controller switching" message, it clears its own management data and resynchronizes the main controller data.

In order to facilitate those skilled in the art to understand the foregoing implementation process and how to specifically combine the management data synchronization methods provided in the foregoing Embodiment 1 and Embodiment 2 in practical applications, specific application scenarios are used as an example to describe in detail below.

Please refer to FIG. 3, which is a schematic diagram of a specific implementation process of a management data synchronization method in an embodiment of the present invention.

First, classify the management data, such as one type of volume, one type of host, one type of fan, and so on. Each data in each data type has an ID field, and the ID field is unique in this type of data. For example, the id of volume 1 is 0, the id of volume 2 is 1, the id of host 1 is 0, and so on. The present invention does not provide a specific classification method, and can be classified by itself during specific implementation. In this way, when the subsequent main controller records the multicast record, it can record the data ID without having to record the detailed content of the data, reducing the amount of recorded data.

Secondly, all controllers form a multicast group. When the management data of the main controller changes, the main controller needs to multicast the changed management data to the multicast group (it may be necessary to send multiple multicast messages, that is, management data synchronization messages , Each message can send one or more types of data), and write down the sending record (including the main controller ID, multicast serial number, management data type, data 1 ID, data 2 ID, ..., data n's ID).

Among them, the format of the management data synchronization message (message 1 in Figure 3, the message type is 0) is shown in Table 1:

Table 1

Among them, the data content part of the management data synchronization message is shown in Table 2:

Table 2

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

Multicast sequence number: it can start from 0 and increase in order to identify the multicast message sent by the main controller;

Main controller ID: the unique identification of the main controller;

Message type: the value 0 here means multicast management data;

Subsequent data length: the number of bytes following this field in this message.

Data Type: The data type of the management data sent. Only one type of data can be sent at a time.

Full data mark: 0 means that it only contains the changed management data of this type; 1 means that it contains all the management data of this type;

Number of data: the number of management data sent;

ID of data 1: the data ID of the first data;

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

The detailed content of data 1: the detailed content of the first data;

ID of data n: the data ID of the nth data;

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

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 1). The specific message format is shown in Table 3:

table 3

The reissuance application message (message 3 in Figure 3) is used to notify the host controller of the unreceived multicast message. The specific message format is shown in Table 4:

Table 4

Again, as shown in Figure 3, the processing flow after receiving multicast message 1 from the controller is shown as follows:

Step1. Receive multicast message 1. If received, go to the next step.

Step2. Identify a message uniquely according to the ID of the main controller and the multicast sequence number, and judge whether the message has been processed. If it has been processed, ignore it; otherwise, go to the next step.

Step3. Obtain the multicast sequence number in the message, and judge whether it is continuous with the most recently processed multicast sequence number. If it is not continuous, go to the next step; otherwise, go to Step 6.

Step4. Assemble the missing multicast sequence number into message 3 (namely, reissue application message), send it to the main controller using unicast, and go to the next step.

Step5. Save the currently received message, do not process it temporarily, go to Step1.

Step6. Process the received messages with consecutive multicast sequence numbers (including the previously saved but unprocessed messages) in order, and update their own management data.

Step7 (not shown in the figure). After the main controller receives the message of Step 4 of the above process, it should immediately obtain the corresponding data according to the sending record, and use the missing multicast sequence number to send the multicast message 1. This can ensure that ordinary nodes can synchronize the data of the main controller in time.

In the above process, if there are multiple packet loss phenomena in the network, the unprocessed messages in Step5 may not be updated in time. Therefore, the slave controller needs to restart the thread to continuously check whether there are saved but unprocessed messages in Step5. If it exists, it means that there is a missing multicast sequence number, and Step4 needs to be performed.

Finally, when the cluster is established or the main controller is switched, it is considered that all management data has changed, and the main controller first multicasts the "main controller switch" message (same as the main controller switch message above), and then multicast For all management data, the multicast sequence number starts from 0 again. After the ordinary node receives the "main controller switching" message, it clears its own management data and clears the message records and data related to the old main controller.

It can be seen that in this embodiment, the multicast technology is used to design incremental multicast sequence numbers, and the multicast messages are processed sequentially, which ensures that the slave controller and the master controller manage the management while reducing the synchronization workload of the master controller. Data consistency.

Embodiment four:

Corresponding to the above method embodiment, the embodiment of the present invention also provides a storage device. The storage device described below and the management data synchronization method described above can be referenced correspondingly.

As shown in Figure 4, the storage device includes:

Multiple controllers, each controller includes:

Memory, used to store computer programs;

The processor is used to implement the steps of the target method when the computer program is executed;

The target method executed by the slave controller D1 in the plurality of controllers is the method in the first embodiment;

The target method executed by the main controller D2 of the plurality of controllers is the same as the method in the second embodiment above.

Specifically, please refer to FIG. 5. FIG. 5 is a schematic diagram of a specific structure of a controller in a storage device provided by this embodiment. The controller may have relatively large differences due to different configurations or performance, and may include one or more A processor (central processing units, CPU) 322 (for example, one or more processors), a memory 332, and one or more storage media 330 (for example, one or more storage devices with a large amount of data) storing application programs 342 or data 344. Among them, the memory 332 and the storage medium 330 may be short-term storage or persistent storage. The program stored in the storage medium 330 may include one or more modules (not shown in the figure), and each module may include a series of instruction operations on the data processing device. Furthermore, the central processing unit 322 may be configured to communicate with the storage medium 330, and 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 and output interfaces 358, and/or one or more operating systems 341. For example, Windows ServerTM, Mac OS XTM, UnixTM, LinuxTM, FreeBSDTM, etc.

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

Embodiment five:

Corresponding to the first embodiment of the above method, the embodiment of the present invention also provides a management data synchronization device that can be applied to the slave controller. The management data synchronization device described below and the management data synchronization method described above may correspond to each other and refer to each other. .

Please refer to Figure 6, the device includes:

The management data synchronization message receiving module 101 is configured to receive and parse the management data synchronization message multicasted by the main controller after the management data changes, and obtain the multicast sequence number;

The message checking module 102 is configured to use the multicast sequence number to determine whether there is a target multicast sequence number that is missing and has no processing record;

The message missing processing module 103 is configured to send the target multicast sequence number to the main controller if there is a target multicast sequence number, and receive the target management data synchronization message corresponding to the target multicast sequence number reissued by the main controller;

The data synchronization module 104 is configured to, if there is no target multicast sequence number, process the management data synchronization messages without corresponding processing records in the order of the multicast sequence number to synchronize the management data.

The first management data synchronization device provided by the embodiment of the present invention is applied to the slave controller in the storage device, and the management data synchronization message received from the controller is automatically verified whether the message is missing or missing according to the multicast sequence number, and After determining that there is a target multicast sequence number that is missing or missing and has no processing record, it actively asks the main controller for the target management data synchronization message corresponding to the target multicast sequence number. Then, after determining that the multicast sequence numbers are continuous, the management data synchronization messages without corresponding processing records are processed in the order of the multicast sequence numbers to realize the synchronization of the management data with the main controller. In this process, the slave controller transfers the original management data synchronization verification operation from itself for processing, and the master controller only needs to multicast the management data synchronization message, and passively reissue the target management that was not received by the individual slave controllers. The data synchronization message is sufficient. That is, sharing the management data synchronization task of the master controller to each slave controller can avoid the problem of resource occupation of the master controller, guarantee the management quality of the storage array of the master controller, and further ensure the stability of the storage device.

In a specific embodiment of the present invention, it further includes:

The master-slave switching processing module is used to clear the management data that has been synchronized with the master controller after the master controller is switched, so as to synchronize the management data of the new master controller.

In a specific embodiment of the present invention, the master-slave switching processing module is specifically used to receive and parse the master controller switching message sent by the target controller to obtain the multicast sequence number and the master controller ID; in the master controller ID When it is inconsistent with the main controller, determine that the target controller is the new main controller.

In a specific embodiment of the present invention, the message checking module 102 is specifically used to determine whether the multicast sequence number is continuous; if not, it determines the missing multicast sequence number, and when there is no corresponding processing record for the missing multicast sequence number, Determine the missing multicast sequence number as the target multicast sequence number.

In a specific embodiment of the present invention, the data synchronization module 104 is specifically configured to use processing records to filter out management data synchronization messages without corresponding processing records; use multicast sequence numbers to sequence the selected management data synchronization messages Sorting: Analyze the management data synchronization messages in sequence according to the sort order to obtain the management data content.

In a specific implementation of the present invention, the message missing processing module 103 is specifically configured to send a reissue request message carrying the target multicast sequence number to the main controller.

In a specific embodiment of the present invention, the data synchronization module 104 is specifically configured to determine the management data type corresponding to the classified management data synchronization message when the management data synchronization message is a classified management data synchronization message; wherein, the management The data types include volumes, hosts, and fans; the management data content carried in the classified management data synchronization message is used to synchronize the management data corresponding to the management data type.

Embodiment 6:

Corresponding to the second embodiment of the method above, the embodiment of the present invention also provides a management data synchronization device applicable to the main controller. The management data synchronization device described below and the management data synchronization method described above can be referred to each other.

As shown in Figure 7, the device includes the following modules:

The management data synchronization message multicast module 201 is configured to multicast the management data synchronization message to each slave controller after the management data changes; the management data synchronization message includes the multicast sequence number;

The missing message determining module 202 is configured to receive the missing target multicast sequence number sent from the controller without processing records;

The message reissue module 203 is used 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 corresponding processing records in the order of the multicast sequence number, To synchronize management data.

The master controller in the storage device applies the second management data synchronization device provided by the embodiment of the present invention. After the management data changes, the master controller multicasts management data synchronization messages to each slave controller; then only Passively wait for the missing and unprocessed target multicast sequence numbers sent by individual slave controllers; then, re-send the target management data synchronization message corresponding to the target multicast sequence number to the slave controller. It can be seen that compared with the existing master controller that requires end-to-end communication between each slave controller and repeatedly confirms whether the management data is successfully synchronized, this device can greatly reduce the pressure of the master controller's management data synchronization. Reduce the calculation and storage performance of the main controller, save more resources to process storage array management tasks, and ensure the stability of the storage device.

In a specific implementation of the present invention, the missing message determining module 202 is configured to receive and analyze the reissue request message sent from the controller to obtain the target multicast sequence number.

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

In a specific embodiment of the present invention, the management data synchronization message multicast module 201 is specifically configured to determine the type of management data to be synchronized after the management data changes; wherein, the management data types include volume, host, Fan; Generate classification management data synchronization messages matching the management data type; multicast the classification management data synchronization messages to each slave controller, so that each slave controller synchronizes management data according to the management data type.

Embodiment Seven:

Corresponding to the above method embodiment, the embodiment of the present invention also provides a readable storage medium. The readable storage medium described below and the method for synchronizing management data described above can be referred to each other.

A readable storage medium in which a computer program is stored, and when the computer program is executed by a processor, the steps of the method for managing data synchronization in the foregoing method embodiment are implemented.

The readable storage medium may specifically be a U disk, a mobile hard disk, a read-only memory (Read-Only Memory, ROM), a random access memory (Random Access Memory, RAM), a magnetic disk, or an optical disk that can store program codes. Readable storage medium.

It should be noted that the terms "include", "include" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or equipment including a series of elements not only includes those elements, but also includes no Other elements clearly listed, or they also include elements inherent to the process, method, article, or equipment. Without more restrictions, the element defined by the sentence "including a..." does not exclude the existence of other identical elements in the process, method, article, or equipment that includes the element.

Professionals may further realize that the units and algorithm steps of the examples described in the embodiments disclosed in this article can be implemented by electronic hardware, computer software, or a combination of the two, in order to clearly illustrate the possibilities of hardware and software. Interchangeability, in the above description, the composition and steps of each example have been generally described in accordance with the function. Whether these functions are executed by hardware or software depends on the specific application and design constraint conditions of the technical solution. Professionals and technicians can use different methods for each specific application to implement the described functions, but such implementation should not be considered as going beyond the scope of the present invention.

Claims (15)

1. A method for managing data synchronization, which is characterized in that it includes:

   The slave controller receives and parses the management data synchronization message multicasted by the master controller after the management data changes, and obtains the multicast sequence number;

   Using the multicast sequence number to determine whether there is a target multicast sequence number that is missing and has no processing record;

   If yes, send the target multicast sequence number to the main controller, and receive a target management data synchronization message corresponding to the target multicast sequence number reissued by the main controller;

   If not, the management data synchronization messages without corresponding processing records are processed in the order of the multicast sequence number to synchronize the management data.
2. The management data synchronization method according to claim 1, further comprising:

   After it is determined that the main controller is switched, the management data that has been synchronized with the main controller is cleared, so as to synchronize the management data of the new main controller.
3. The management data synchronization method according to claim 2, wherein the determining the main controller to switch comprises:

   Receive and parse the master controller switching message sent by the target controller to obtain the multicast sequence number and master controller ID;

   When the main controller ID is inconsistent with the main controller, it is determined that the target controller is the new main controller.
4. The management data synchronization method according to claim 1, wherein determining whether there is a target multicast sequence number that is missing and has no processing record by using the multicast sequence number comprises:

   Judging whether the multicast sequence number is continuous;

   If not, the missing multicast sequence number is determined, and when there is no corresponding processing record for the missing multicast sequence number, it is determined that the missing multicast sequence number is the target multicast sequence number.
5. The management data synchronization method according to claim 1, wherein the processing of the management data synchronization messages without corresponding processing records in the order of the multicast sequence number to synchronize management data comprises:

   Use processing records to filter out management data synchronization messages without corresponding processing records;

   Order the filtered management data synchronization messages by using the multicast sequence number;

   The management data synchronization message is sequentially parsed according to the sequence to obtain the management data content.
6. The management data synchronization method according to claim 1, wherein sending the target multicast sequence number to the main controller comprises:

   Sending a reissuance request message carrying the target multicast sequence number to the main controller.
7. The management data synchronization method according to any one of claims 1 to 6, wherein the management data synchronization message is a classified management data synchronization message, and all data without corresponding processing records are processed in the order of the multicast sequence number. The management data synchronization message to synchronize management data includes:

   Determine the management data type corresponding to the classified management data synchronization message; wherein, the management data type includes volume, host, and fan;

   The management data corresponding to the management data type is synchronized by using the management data content carried in the classification management data synchronization message.
8. A method for managing data synchronization, which is characterized in that it includes:

   After the management data changes, the master controller multicasts a management data synchronization message to each slave controller; the management data synchronization message includes a multicast sequence number;

   Receive the missing and no-processed target multicast sequence number sent from the controller;

   Re-send 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 corresponding processing records in the order of the multicast sequence number To synchronize management data.
9. The management data synchronization method according to claim 8, wherein receiving the missing and no-processed target multicast sequence number sent from the controller comprises:

   Receiving and analyzing the reissuance request message sent by the slave controller to obtain the target multicast sequence number.
10. The management data synchronization method according to claim 8, wherein the re-sending the target management data synchronization message corresponding to the target multicast sequence number to the slave controller comprises:

    The target management data synchronization message is separately reissued to the slave controller.
11. The management data synchronization method according to any one of claims 8 to 10, wherein after the management data changes, multicasting a management data synchronization message to each slave controller includes:

    After the management data changes, determine the management data type to be synchronized; wherein, the management data type includes volume, host, and fan;

    Generating a classification management data synchronization message matching the management data type;

    The classification management data synchronization message is multicast to each of the slave controllers, so that each of the slave controllers synchronizes the management data according to the management data type.
12. A storage device, characterized in that it comprises:

    A plurality of controllers, each of the controllers includes:

    Memory, used to store computer programs;

    The processor is used to implement the steps of the target method when the computer program is executed;

    The target method executed by the slave controller in the plurality of controllers is the method according to any one of claims 1 to 7;

    The target method executed by the main controller among the plurality of controllers is the method according to any one of claims 8 to 11.
13. A management data synchronization device, which is characterized in that it is applied to a slave controller and includes:

    The management data synchronization message receiving module is used to receive and parse the management data synchronization message multicasted by the main controller after the management data changes, and obtain the multicast sequence number;

    A message checking module, configured to use the multicast sequence number to determine whether there is a target multicast sequence number that is missing and has no processing record;

    The message missing processing module is configured to send the target multicast sequence number to the main controller if the target multicast sequence number exists, and receive the corresponding target multicast sequence number reissued by the main controller Target management data synchronization message;

    The data synchronization module is configured to, if there is no target multicast sequence number, process the management data synchronization messages without corresponding processing records in the order of the multicast sequence numbers to synchronize the management data.
14. A management data synchronization device, which is characterized in that it is applied to a main controller and includes:

    The management data synchronization message multicast module is configured to multicast a management data synchronization message to each slave controller after the management data changes; the management data synchronization message includes a multicast sequence number;

    The missing message determination module is used to receive the missing target multicast sequence number sent from the controller without processing records;

    The message reissue module is used 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 non-corresponding processing records in the order of the multicast sequence number The management data synchronization message is used to synchronize the management data.
15. A readable storage medium, characterized in that a computer program is stored on the readable storage medium, and when the computer program is executed by a processor, the steps of the method for managing data synchronization according to any one of claims 1 to 11 are realized .

Images