CN103580918A - Method and device for processing configuration data - Google Patents

Method and device for processing configuration data Download PDF

Info

Publication number
CN103580918A
CN103580918A CN201310528909.XA CN201310528909A CN103580918A CN 103580918 A CN103580918 A CN 103580918A CN 201310528909 A CN201310528909 A CN 201310528909A CN 103580918 A CN103580918 A CN 103580918A
Authority
CN
China
Prior art keywords
type file
configuration type
node
slave node
version number
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Granted
Application number
CN201310528909.XA
Other languages
Chinese (zh)
Other versions
CN103580918B (en
Inventor
孟杰
梁明旭
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Priority to CN201310528909.XA priority Critical patent/CN103580918B/en
Publication of CN103580918A publication Critical patent/CN103580918A/en
Application granted granted Critical
Publication of CN103580918B publication Critical patent/CN103580918B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Landscapes

  • Information Transfer Between Computers (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

The embodiment of the invention provides a method and device for processing configuration data. According to the method and device for processing the configuration data, due to the fact that main nodes receive and store configuration type files of standby nodes and the version numbers of the configuration type files of the standby nodes are different from the version numbers of the configuration type files stored in the main nodes, during system upgrading, part of the standby nodes can be firstly upgraded, the other part of the standby nodes which are not upgraded are used for service operation, then the upgraded standby nodes are used for service operation continuously and the remaining standby nodes are upgraded, and due to the fact that the version numbers of the configuration type files of the upgraded standby nodes are changed after upgrading, configuration type files of the upgraded standby nodes are stored in the main nodes, so that service operation can be conducted by both the standby nodes which are not upgraded and the standby nodes which are upgraded in the main nodes at the same time. The method and device for processing the configuration data have the advantage that services can be provided for users when a trunking system is upgraded.

Description

A kind of configuration data processing method and device
Technical field
The present invention relates to cluster device data configuration field, relate in particular to a kind of configuration data processing method and device.
Background technology
In group system, generally include host node and slave node, host node and slave node coordinate operation business, for user provides service.
Because when the version of the configuration data of host node and slave node is identical, when both can coordinate operation business, so, existing group system is when upgrading, need whole nodes to restart simultaneously, and when whole nodes are restarted, any business of must reruning.
Visible, existing group system, when upgrading, cannot provide service for user.
Summary of the invention
The embodiment of the present invention provides a kind of configuration data processing method, and object is to solve existing group system when upgrading, and the problem of service cannot be provided for user.
To achieve these goals, the embodiment of the present invention provides following technical scheme:
The first aspect of the embodiment of the present invention provides a kind of configuration data processing method, comprising:
Host node receives the Configuration Type file of slave node, the version number of the Configuration Type file of described slave node is different from the version number of the Configuration Type file of storing in described host node, described Configuration Type file comprises configuration data, and described version number is corresponding one by one with described Configuration Type file;
Described host node is preserved the Configuration Type file of described slave node.
In the first implementation of the first aspect of the embodiment of the present invention, receive the Configuration Type file of described slave node at described host node before, also comprise:
When meeting when pre-conditioned, described host node sends the version number of the Configuration Type file of described host node to described slave node.
In the second implementation of the first aspect of the embodiment of the present invention, receive the Configuration Type file of slave node at described host node before, also comprise:
After described host node determines that the version number of Configuration Type file of described host node is different with the version number of the Configuration Type file of described slave node, described host node sends Configuration Type file request message to described slave node.
In the third implementation of the first aspect of the embodiment of the present invention, described host node determines that the version number of Configuration Type file of the described host node detailed process different with the version number of the Configuration Type file of described slave node comprises:
When meeting when pre-conditioned, described host node obtains the version number of the Configuration Type file of described slave node;
Described host node, by relatively, determines that the version number of Configuration Type file of described slave node is different with the version number of the Configuration Type file of described host node.
In the 4th kind of implementation of the first aspect of the embodiment of the present invention, described pre-conditioned at least comprising with the next item down:
Described slave node is connected with described host node;
Described host node changes to the second management node by the first management node.
In the 5th kind of implementation of the first aspect of the embodiment of the present invention, after described host node is preserved the Configuration Type file of described slave node, also comprise:
Described host node receives described slave node configuration data that send, that have the first title and second value, and the value of described configuration data configuration data in the Configuration Type file of described slave node, that have the first title is sent out while being modified to described second value by the first numerical value;
Described host node is kept at described the first title and described second value correspondence in presetting database.
In the 6th kind of implementation of the first aspect of the embodiment of the present invention, in described host node is kept at presetting database by described the first title and described second value correspondence after, also comprise:
Described host node receives the configuration data value of described slave node transmission and obtains message, described configuration data is configuration data in the Configuration Type file of described slave node, that have the second title, and described configuration data value is obtained the version number of the Configuration Type file that carries described slave node in message;
Described host node inquires about whether there is described the second title from described presetting database;
If so, described host node sends to described slave node by numerical value corresponding to described the second title;
If not, described host node is query aim Configuration Type file, and the version number of described target configuration type file is identical with the version number of the Configuration Type file of described slave node;
By in described target configuration type file, numerical value corresponding to described the second title sends to described slave node.
The second aspect of the embodiment of the present invention provides a kind of configuration data processing method, comprising:
Slave node sends the Configuration Type file of described slave node to host node, so that described host node is preserved the Configuration Type file of described slave node, the version number of the Configuration Type file of described slave node is different from the version number of the Configuration Type file of storing in host node, described Configuration Type file comprises configuration data, and described version number is corresponding one by one with described Configuration Type file.
In the first implementation of the second aspect of the embodiment of the present invention, the Configuration Type file that described slave node sends described slave node to host node comprises:
After described slave node determines that the version number of Configuration Type file of described host node is different with the version number of the Configuration Type file of described slave node, described slave node sends the Configuration Type file of described slave node to host node.
In the second implementation of the second aspect of the embodiment of the present invention, determine that the version number of Configuration Type file of the described host node detailed process different with the version number of the Configuration Type file of described slave node comprises:
Described slave node receives the version number of the Configuration Type file of described host node;
Described slave node, by the version number of Configuration Type file of more described slave node and the version number of the Configuration Type file of described host node, determines that both are different.
In the third implementation of the second aspect of the embodiment of the present invention, the Configuration Type file that described slave node sends described slave node to host node comprises:
Described slave node is according to the Configuration Type file request message receiving, to described host node, send the Configuration Type file of described slave node, described configuration file request message is determined the version number of Configuration Type file of described host node and the different rear transmissions of version number of the Configuration Type file of described slave node by described host node.
In the 4th kind of implementation of the second aspect of the embodiment of the present invention, send the Configuration Type file of described slave node to host node at slave node after, also comprise:
When the value of configuration data in the Configuration Type file of described slave node, that have the first title is modified to described second value by the first numerical value, described slave node sends described the first title and described second value to described host node.
The third aspect of the embodiment of the present invention provides a kind of host node, comprising:
The first receiver module, for receiving the Configuration Type file of slave node, the version number of the Configuration Type file of described slave node is different from the version number of the Configuration Type file of storing in described host node, described Configuration Type file comprises configuration data, and described version number is corresponding one by one with described Configuration Type file;
The first memory module, for preserving the Configuration Type file of described slave node.
In the first implementation of the third aspect of the embodiment of the present invention, also comprise:
The first sending module, before receiving the Configuration Type file of described slave node at described the first receiver module, when meeting when pre-conditioned, sends the version number of the Configuration Type file of described host node to described slave node.
In the second implementation of the third aspect of the embodiment of the present invention, also comprise:
The first determination module, for when meeting when pre-conditioned, obtains the version number of the Configuration Type file of described slave node, and by relatively, determines that the version number of Configuration Type file of described slave node is different with the version number of the Configuration Type file of described host node;
The second sending module, after determining that when described the first determination module the version number of Configuration Type file of described host node is different with the version number of the Configuration Type file of described slave node, sends Configuration Type file request message to described slave node.
In the third implementation of the third aspect of the embodiment of the present invention, also comprise:
The second receiver module, for receiving described slave node configuration data that send, that have the first title and second value, the value of described configuration data configuration data in the Configuration Type file of described slave node, that have the first title is sent out while being modified to described second value by the first numerical value;
The second memory module, for being kept at presetting database by described the first title and described second value correspondence.
In the 4th kind of implementation of the third aspect of the embodiment of the present invention, also comprise:
The 3rd receiver module, for receiving the configuration data value of described slave node transmission, obtain message, described configuration data is configuration data in the Configuration Type file of described slave node, that have the second title, and described configuration data value is obtained the version number of the Configuration Type file that carries described slave node in message;
Enquiry module, for whether there is described the second title from described presetting database inquiry, if, numerical value corresponding to described the second title is sent to described slave node, if not, query aim Configuration Type file, the version number of described target configuration type file is identical with the version number of the Configuration Type file of described slave node, by described target configuration type file, numerical value corresponding to described the second title sends to described slave node.
The fourth aspect of the embodiment of the present invention provides a kind of slave node, comprising:
The 4th sending module, for send the Configuration Type file of described slave node to host node, so that described host node is preserved the Configuration Type file of described slave node, the version number of the Configuration Type file of described slave node is different from the version number of the Configuration Type file of storing in host node, described Configuration Type file comprises configuration data, and described version number is corresponding one by one with described Configuration Type file.
In the first implementation of the fourth aspect of the embodiment of the present invention, aspect the described Configuration Type file that sends described slave node to host node, described the 4th sending module specifically for:
After definite version number of Configuration Type file of described host node is different with the version number of the Configuration Type file of described slave node, to host node, send the Configuration Type file of described slave node.
In the second implementation of the fourth aspect of the embodiment of the present invention, also comprise:
The second determination module, for receiving the version number of the Configuration Type file of described host node, and by relatively, determines that the version number of Configuration Type file of described slave node is different with the version number of the Configuration Type file of described host node.
In the third implementation of the fourth aspect of the embodiment of the present invention, aspect the described Configuration Type file that sends described slave node to host node, described the 4th sending module specifically for:
According to the Configuration Type file request message receiving, to described host node, send the Configuration Type file of described slave node, described configuration file request message is determined the version number of Configuration Type file of described host node and the different rear transmissions of version number of the Configuration Type file of described slave node by described host node.
In the 4th kind of implementation of the fourth aspect of the embodiment of the present invention, also comprise:
The 5th sending module, while being modified to described second value for the value of the configuration data Configuration Type file when described slave node, that have the first title by the first numerical value, sends described the first title and described second value to described host node.
The configuration data processing method that the embodiment of the present invention provides and device, because host node receives and preserves the Configuration Type file of slave node, and the version number of the Configuration Type file of described slave node is different from the version number of the Configuration Type file of storing in host node, therefore, Configuration Type file that can compatible different editions in host node, because can change before the version number of the Configuration Type file of the slave node after upgrading upgrades, so, the Configuration Type file of the slave node after upgrading can be saved in host node, therefore, in host node, both comprised the not Configuration Type file of the slave node of upgrading, the Configuration Type file that comprises again the slave node after upgrading, thereby the slave node before can simultaneously supporting upgrading and after upgrading carries out the operation of business, so, when system is upgraded, a part of slave node of can first upgrading, and the slave node of being upgraded by another part operation business, then by the slave node after upgrading, continue operation business, the remaining slave node of upgrading again, visible, method described in the present embodiment and device, when upgrading, group system also can continue to provide service for user.
Accompanying drawing explanation
In order to be illustrated more clearly in the embodiment of the present invention or technical scheme of the prior art, to the accompanying drawing of required use in embodiment or description of the Prior Art be briefly described below, apparently, accompanying drawing in the following describes is only some embodiments of the present invention, for those of ordinary skills, do not paying under the prerequisite of creative work, can also obtain according to these accompanying drawings other accompanying drawing.
Fig. 1 is the schematic diagram of the application scenarios of the disclosed embodiment of the embodiment of the present invention;
Fig. 2 is the flow chart of the disclosed a kind of configuration data processing method of the embodiment of the present invention;
Fig. 3 is the flow chart of disclosed another configuration data processing method of the embodiment of the present invention;
Fig. 4 is the flow chart of disclosed another configuration data processing method of the embodiment of the present invention;
Fig. 5 is the flow chart of disclosed another configuration data processing method of the embodiment of the present invention;
Fig. 6 is the structural representation of the disclosed a kind of host node of the embodiment of the present invention;
Fig. 7 is the structural representation of disclosed another host node of the embodiment of the present invention;
Fig. 8 is the structural representation of the disclosed a kind of slave node of the embodiment of the present invention;
Fig. 9 is the structural representation of disclosed another host node of the embodiment of the present invention;
Figure 10 is the structural representation of disclosed another slave node of the embodiment of the present invention.
Embodiment
The embodiment of the present invention can be applied to group system, as shown in Figure 1, described group system can comprise management node and ordinary node, the quantity of management node can be one, also can be two or more, a host node as group system in described management node, other management node is slave node, ordinary node is all as the slave node of group system.
Below in conjunction with the accompanying drawing in the embodiment of the present invention, the technical scheme in the embodiment of the present invention is clearly and completely described, obviously, described embodiment is only the present invention's part embodiment, rather than whole embodiment.Embodiment based in the present invention, those of ordinary skills, not making the every other embodiment obtaining under creative work prerequisite, belong to the scope of protection of the invention.
The disclosed a kind of configuration data processing method of the embodiment of the present invention, as shown in Figure 2, comprising:
S201: slave node sends the Configuration Type file of described slave node to host node;
In the present embodiment, slave node can initiatively send Configuration Type file to host node, sends Configuration Type file after also can receiving the request of host node to host node.
Wherein, the version number of the Configuration Type file of described slave node is different from the version number of the Configuration Type file of storing in host node, and described Configuration Type file comprises configuration data, and described version number is corresponding one by one with described Configuration Type file.
S202: described host node is preserved the Configuration Type file of described slave node.
Conventionally, in each node of group system, store configuration data, each configuration data is generally comprised of title and numerical value.In the present embodiment, the configuration data of node is included in Configuration Type file, Configuration Type file has and its version number one to one, because configuration data is comprised of title and numerical value, so the title of the configuration data comprising when two Configuration Type files is incomplete same, or, the numerical value of the configuration data of same title is different, or when the numerical value of the configuration data of the incomplete same and same title of the title of configuration data is also different, the version number of Configuration Type file is all different.For example, Configuration Type file A comprises that name is called a and name is called two fields of b, the value of a field is 1, the value of b field is 2, the version number of Configuration Type file A is V1, Configuration Type file B comprises that name is called a and name is called two fields of b, the value of a field is 1, the value of b field is 3, the version number of Configuration Type file B is V2, Configuration Type file C comprises that name is called a, name is called b and name is called three fields of c, and the version number of Configuration Type file C is V3, and V1, V2 and V3 are mutually different version number.
In prior art, in host node, only store the configuration data of a version, therefore, in order to meet main-standby nodes, coordinate the demand of carrying out business, the version of the configuration data in host node and slave node must be identical, so, when cluster is upgraded, whole nodes in cluster must be restarted simultaneously, to complete the loading of identical version configuration data.Thereby, when group system is upgraded, must suspend and provide service for user.
And configuration data processing method described in the present embodiment, make when carrying out group system upgrading, a part of node of can first upgrading, by another part node operation business, after a part of node has been upgraded, this part node being completed by upgrading again continues operation business, and remaining node is upgraded, after slave node upgrading, although wherein the version number of configuration data is different from before upgrading, but also can be saved in host node, therefore, the node that completes upgrading still can be mutual with host node, with operation business, therefore, method described in the present embodiment, can avoid suspending the defect that service is provided for user when system is upgraded.
For example, as shown in Figure 1, before upgrading, the version number of the configuration data of system is V1.0, and when upgrading, the first slave node is first upgraded, the second slave node operation business, and after the first slave node has been upgraded, the version number of its Configuration Type file is V2.0.
On the basis of existing technology, because host node is not upgraded, configuration data is still V1.0 version, so the slave node that completes upgrading cannot move business, therefore, the interruption that still can not avoid user to serve.And method described in the present embodiment, the Configuration Type file that version number is V2.0 can be saved in host node, and therefore, the slave node that completes upgrading can be taken over the slave node operation business of not upgrading, thereby continue as user, provides service.
Disclosed another configuration data processing method of the embodiment of the present invention, as shown in Figure 3, comprising:
S301: when described slave node is connected with described host node, described host node sends the version number of the Configuration Type file of described host node to described slave node;
Host node can initiatively send the version number of the Configuration Type file of self to slave node, the version number that also can respond slave node transmission obtains request, sends the version number of the Configuration Type file of self to slave node.
S302: described slave node determines that by the version number of the version number of the Configuration Type file of more described slave node and the Configuration Type file of described host node both are different;
S303: described slave node sends the Configuration Type file of described slave node to described host node;
S304: host node is preserved the Configuration Type file of described slave node.
In embodiment shown in Fig. 3, different with the version number of the Configuration Type file of slave node by relatively more definite version number of Configuration Type file of host node by slave node, in addition, this process can also be carried out by host node, as shown in Figure 4, disclosed another configuration data processing method of the embodiment of the present invention, comprising:
S401: when described host node changes to the second management node by the first management node, described host node obtains the version number of the Configuration Type file of described slave node;
Particularly, host node can initiatively obtain the version number of the Configuration Type file of slave node to slave node, also can receive the version number of the Configuration Type file of the slave node that slave node sends.
S402: the version number of the version number of the Configuration Type file of the more described slave node of described host node and the Configuration Type file of described host node, determines that both are different;
S403: described host node sends Configuration Type file request message to described slave node;
S404: according to described Configuration Type file request message, send the Configuration Type file of described slave node to described host node;
S405: described host node is preserved the Configuration Type file of described slave node.
Method shown in Fig. 4 or Fig. 5, after different with the version number of the Configuration Type file of described host node by relatively more definite version number of Configuration Type file of described slave node, the Configuration Type file of slave node is saved in host node, therefore make the Configuration Type file of compatible different editions in host node number, thereby can support to move business with the slave node of not upgrading after upgrading, so, when upgrading, also can provide service for user.
The disclosed a kind of configuration data processing method of the embodiment of the present invention, as shown in Figure 5, comprising:
S501: slave node sends the Configuration Type file of described slave node to host node;
S502: described host node is preserved the Configuration Type file of described slave node;
S503: when the value of configuration data in the Configuration Type file of described slave node, that have the first title is modified to described second value by the first numerical value, described slave node sends described the first title and described second value to described host node;
S504: described host node is kept at described the first title and described second value correspondence in presetting database.
In the present embodiment, in the database of host node, only preserve the amended numerical value of configuration parameter, but not whole configuration datas of slave node, so, the memory space of host node can be saved.
Alternatively, in the present embodiment, can also comprise the following steps:
S505: described host node receives the configuration data value of described slave node transmission and obtains message, described configuration data is configuration data in the Configuration Type file of described slave node, that have the second title, and described configuration data value is obtained the version number of the Configuration Type file that carries described slave node in message;
S506: described host node inquires about whether there is described the second title from described presetting database;
S507: if described host node sends to described slave node by numerical value corresponding to described the second title;
Wherein, the first title can be identical with the second title, also can be different.
S508: if not, described host node is query aim Configuration Type file, the version number of described target configuration type file is identical with the version number of the Configuration Type file of described slave node;
S509: by described target configuration type file, numerical value corresponding to described the second title sends to described slave node.
In the present embodiment, because therefore the numerical value of the configuration data for modification of storing in the presetting database in host node, first inquire about presetting database, can improve the efficiency of feedback.
It should be noted that, in the above-described embodiments, alternatively, version number can be carried in Configuration Type file and send to opposite end, also can directly version number be sent to opposite end, does not limit here.
The disclosed a kind of configuration data processing method of the embodiment of the present invention, comprising:
A: host node receives the Configuration Type file of slave node, the version number of the Configuration Type file of described slave node is different from the version number of the Configuration Type file of storing in described host node, described Configuration Type file comprises configuration data, and described version number is corresponding one by one with described Configuration Type file;
B: described host node is preserved the Configuration Type file of described slave node.
Optionally, at A: host node also comprises before receiving the Configuration Type file of slave node:
A1: when meeting when pre-conditioned, described host node sends the version number of the Configuration Type file of described host node to described slave node;
Alternatively, pre-conditioned can at least comprising with the next item down: described slave node is connected with described host node; Or described host node changes to the second management node by the first management node.
Or, at A: host node also comprises before receiving the Configuration Type file of slave node:
A2: after described host node determines that the version number of Configuration Type file of described host node is different with the version number of the Configuration Type file of described slave node, described host node sends Configuration Type file request message to described slave node.
Alternatively, in the embodiment shown in fig. 1, can also comprise the following steps:
A3: described host node receives described slave node configuration data that send, that have the first title and second value, and the value of described configuration data configuration data in the Configuration Type file of described slave node, that have the first title is sent out while being modified to described second value by the first numerical value;
B3: described host node is kept at described the first title and described second value correspondence in presetting database
C3: described host node receives the configuration data value of described slave node transmission and obtains message, configuration data in the Configuration Type file that described configuration data is described slave node, that have the second title;
D3: described host node inquires about whether there is described the second title from described presetting database;
E3: if described host node sends to described slave node by numerical value corresponding to described the second title;
F3: if not, described host node is query aim Configuration Type file, the version number of described target configuration type file is identical with the version number of the Configuration Type file of described slave node;
G3: by described target configuration type file, numerical value corresponding to described the second title sends to described slave node.
The embodiment of the invention also discloses a kind of configuration data processing method, be applied to the slave node in group system, comprising:
Slave node sends the Configuration Type file of described slave node to host node, so that described host node is preserved the Configuration Type file of described slave node.Wherein, the version number of the Configuration Type file of described slave node is different from the version number of the Configuration Type file of storing in host node, and described Configuration Type file comprises configuration data, and described version number is corresponding one by one with described Configuration Type file.
Alternatively, in the present embodiment, a kind of specific implementation that slave node sends the Configuration Type file of described slave node to host node is: after described slave node determines that the version number of Configuration Type file of described host node is different with the version number of the Configuration Type file of described slave node, described slave node sends the Configuration Type file of described slave node to host node.
The another kind of specific implementation that slave node sends the Configuration Type file of described slave node to host node is: receive the Configuration Type file request message that described host node sends, described configuration file request message is determined the version number of Configuration Type file of described host node and the different rear transmissions of version number of the Configuration Type file of described slave node by described host node, and according to described Configuration Type file request message, to described host node, send the Configuration Type file of described slave node.
Alternatively, in the present embodiment, can also comprise: when the value of configuration data in the Configuration Type file of described slave node, that have the first title is modified to described second value by the first numerical value, described slave node sends described the first title and described second value to described host node.
The embodiment of the invention also discloses a kind of host node, as shown in Figure 6, comprising:
The first receiver module 601, for receiving the Configuration Type file of slave node, the version number of the Configuration Type file of described slave node is different from the version number of the Configuration Type file of storing in described host node, described Configuration Type file comprises configuration data, and described version number is corresponding one by one with described Configuration Type file;
The first memory module 602, for preserving the Configuration Type file of described slave node.
The Configuration Type file that can receive slave node of the host node described in the present embodiment, and the Configuration Type file of node is preserved, because the version number of the Configuration Type file of slave node is different from the version number of the Configuration Type file of storing in described host node, so Configuration Type file that can compatible different editions in the host node described in the present embodiment, thereby support to have the operation of slave node of the configuration data of different editions, thereby make the group system can be incessantly for user provides service in escalation process.
Alternatively, host node described in the present embodiment, as shown in Figure 6, can also comprise: the first sending module 603, for before described the first receiver module receives the Configuration Type file of described slave node, when meeting when pre-conditioned, to described slave node, send the version number of the Configuration Type file of described host node.
Or alternatively, the host node described in the present embodiment, as shown in Figure 7, except the first receiver module 701 and the first memory module 702, can also comprise:
The first determination module 703, for when meeting when pre-conditioned, obtain the version number of the Configuration Type file of described slave node, and by relatively, determine that the version number of Configuration Type file of described slave node is different with the version number of the Configuration Type file of described host node.
The second sending module 704, after determining that when described the first determination module the version number of Configuration Type file of described host node is different with the version number of the Configuration Type file of described slave node, sends Configuration Type file request message to described slave node.
Alternatively, the host node described in the present embodiment, can also comprise:
The second receiver module 705, for receiving described slave node configuration data that send, that have the first title and second value, the value of described configuration data configuration data in the Configuration Type file of described slave node, that have the first title is sent out while being modified to described second value by the first numerical value;
The second memory module 706, is kept at presetting database for described host node by described the first title and described second value correspondence;
The 3rd receiver module 707, for receiving the configuration data value of described slave node transmission, obtain message, described configuration data is configuration data in the Configuration Type file of described slave node, that have the second title, and described configuration data value is obtained the version number of the Configuration Type file that carries described slave node in message;
Enquiry module 708, for whether there is described the second title from described presetting database inquiry, if, numerical value corresponding to described the second title is sent to described slave node, if not, query aim Configuration Type file, the version number of described target configuration type file is identical with the version number of the Configuration Type file of described slave node, by described target configuration type file, numerical value corresponding to described the second title sends to described slave node.
The embodiment of the invention also discloses a kind of slave node, comprising:
The 4th sending module, for send the Configuration Type file of described slave node to host node, so that described host node is preserved the Configuration Type file of described slave node, the version number of the Configuration Type file of described slave node is different from the version number of the Configuration Type file of storing in host node, described Configuration Type file comprises configuration data, and described version number is corresponding one by one with described Configuration Type file.
Alternatively, aspect the described Configuration Type file that sends described slave node to host node, described the 4th sending module specifically for:
According to the Configuration Type file request message receiving, to described host node, send the Configuration Type file of described slave node, described configuration file request message is determined the version number of Configuration Type file of described host node and the different rear transmissions of version number of the Configuration Type file of described slave node by described host node.
Alternatively, be illustrated in figure 8 a kind of specific implementation of the slave node described in the present embodiment:
The second determination module 801, for receiving the version number of the Configuration Type file of described host node, and by relatively, determines that the version number of Configuration Type file of described slave node is different with the version number of the Configuration Type file of described host node.
The 4th sending module 802, for after definite version number of Configuration Type file of described host node is different with the version number of the Configuration Type file of described slave node, described slave node sends the Configuration Type file of described slave node to host node.
The 5th sending module 803, while being modified to described second value for the value of the configuration data Configuration Type file when described slave node, that have the first title by the first numerical value, sends described the first title and described second value to described host node.
The embodiment of the invention also discloses a kind of host node, as shown in Figure 9, comprising:
The first receiver 901, for receiving the Configuration Type file of slave node, the version number of the Configuration Type file of described slave node is different from the version number of the Configuration Type file of storing in described host node, described Configuration Type file comprises configuration data, and described version number is corresponding one by one with described Configuration Type file;
First processor 902, for the Configuration Type file of preserving described slave node to storage medium 803;
Described the first storage medium 903 can also be for storing the program of first processor, and the data that produce in first processor running;
Described the first receiver, first processor and the first storage medium all can communicate by the first data/address bus 904.
Alternatively, host node in the present embodiment can also comprise: the first transmitter, for before described host node receives the Configuration Type file of described slave node, when meeting when pre-conditioned, to described slave node, send the version number of the Configuration Type file of described host node, or, after described host node determines that the version number of Configuration Type file of described host node is different with the version number of the Configuration Type file of described slave node, to described slave node, send Configuration Type file request message.
Alternatively, first processor in the present embodiment can also be for: when meeting when pre-conditioned, obtain the version number of the Configuration Type file of described slave node, and by relatively, determine that the version number of Configuration Type file of described slave node is different with the version number of the Configuration Type file of described host node.
Alternatively, the first receiver in the present embodiment can also be for: receive described slave node configuration data that send, that have the first title and second value, the value of described configuration data configuration data in the Configuration Type file of described slave node, that have the first title is sent out while being modified to described second value by the first numerical value; Described first processor can also be for: described the first title and described second value correspondence are kept to presetting database.
Alternatively, the first receiver in the present embodiment can also be for: receive the configuration data value that described slave node sends and obtain message, described configuration data is configuration data in the Configuration Type file of described slave node, that have the second title, and described configuration data value is obtained the version number of the Configuration Type file that carries described slave node in message; Described first processor can also be for: from described presetting database inquiry, whether have described the second title, if, numerical value corresponding to described the second title is sent to described slave node, if not, query aim Configuration Type file, the version number of described target configuration type file is identical with the version number of the Configuration Type file of described slave node, by described target configuration type file, numerical value corresponding to described the second title sends to described slave node.
The embodiment of the invention also discloses a kind of slave node, as shown in figure 10, comprising:
The second transmitter 1001, for send the Configuration Type file of described slave node to host node, so that described host node is preserved the Configuration Type file of described slave node, the version number of the Configuration Type file of described slave node is different from the version number of the Configuration Type file of storing in host node, described Configuration Type file comprises configuration data, and described version number is corresponding one by one with described Configuration Type file;
The second storage medium 1002, described the second transmitter is connected by the second data/address bus 1003 with the second storage medium.
Alternatively, to host node, sending aspect the Configuration Type file of described slave node, described the second transmitter can be specifically for: according to the Configuration Type file request message receiving, to described host node, send the Configuration Type file of described slave node, described configuration file request message is determined the version number of Configuration Type file of described host node and the different rear transmissions of version number of the Configuration Type file of described slave node by described host node.
Alternatively, described the second transmitter can also be for: when the value of configuration data Configuration Type file, that have the first title of described slave node is modified to described second value by the first numerical value, to described host node, send described the first title and described second value.
Alternatively, can also comprise:
The second processor, for receiving the version number of the Configuration Type file of described host node, and by relatively, determines that the version number of Configuration Type file of described slave node is different with the version number of the Configuration Type file of described host node.
To host node, sending aspect the Configuration Type file of described slave node, described the second transmitter can be specifically for: after definite version number of Configuration Type file of described host node is different with the version number of the Configuration Type file of described slave node, send the Configuration Type file of described slave node to host node.
The second transmitter described in the present embodiment, the second storage medium and the second processor can be connected by the second data/address bus.
If the function described in the present embodiment method usings that the form of SFU software functional unit realizes and during as production marketing independently or use, can be stored in a computing equipment read/write memory medium.Understanding based on such, the part that the embodiment of the present invention contributes to prior art or the part of this technical scheme can embody with the form of software product, this software product is stored in a storage medium, comprise that some instructions are with so that a computing equipment (can be personal computer, server, mobile computing device or the network equipment etc.) carry out all or part of step of method described in each embodiment of the present invention.And aforesaid storage medium comprises: various media that can be program code stored such as USB flash disk, portable hard drive, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), magnetic disc or CDs.
In this specification, each embodiment adopts the mode of going forward one by one to describe, and each embodiment stresses is the difference with other embodiment, between each embodiment same or similar part mutually referring to.
Above-mentioned explanation to the disclosed embodiments, makes professional and technical personnel in the field can realize or use the present invention.To the multiple modification of these embodiment, will be apparent for those skilled in the art, General Principle as defined herein can, in the situation that not departing from the spirit or scope of the present invention, realize in other embodiments.Therefore, the present invention will can not be restricted to these embodiment shown in this article, but will meet the widest scope consistent with principle disclosed herein and features of novelty.

Claims (22)

1. a configuration data processing method, is characterized in that, comprising:
Host node receives the Configuration Type file of slave node, the version number of the Configuration Type file of described slave node is different from the version number of the Configuration Type file of storing in described host node, described Configuration Type file comprises configuration data, and described version number is corresponding one by one with described Configuration Type file;
Described host node is preserved the Configuration Type file of described slave node.
2. method according to claim 1, is characterized in that, before receiving the Configuration Type file of described slave node, also comprises at described host node:
When meeting when pre-conditioned, described host node sends the version number of the Configuration Type file of described host node to described slave node.
3. method according to claim 1, is characterized in that, before receiving the Configuration Type file of slave node, also comprises at described host node:
After described host node determines that the version number of Configuration Type file of described host node is different with the version number of the Configuration Type file of described slave node, described host node sends Configuration Type file request message to described slave node.
4. method according to claim 3, is characterized in that, described host node determines that the version number of Configuration Type file of the described host node detailed process different with the version number of the Configuration Type file of described slave node comprises:
When meeting when pre-conditioned, described host node obtains the version number of the Configuration Type file of described slave node;
Described host node, by relatively, determines that the version number of Configuration Type file of described slave node is different with the version number of the Configuration Type file of described host node.
5. according to the method described in claim 2 or 4, it is characterized in that described pre-conditioned at least comprising with the next item down:
Described slave node is connected with described host node;
Described host node changes to the second management node by the first management node.
6. according to the method described in claim 1 to 4 any one, it is characterized in that, after described host node is preserved the Configuration Type file of described slave node, also comprise:
Described host node receives described slave node configuration data that send, that have the first title and second value, and the value of described configuration data configuration data in the Configuration Type file of described slave node, that have the first title is sent out while being modified to described second value by the first numerical value;
Described host node is kept at described the first title and described second value correspondence in presetting database.
7. method according to claim 6, is characterized in that, in described host node is kept at presetting database by described the first title and described second value correspondence after, also comprise:
Described host node receives the configuration data value of described slave node transmission and obtains message, described configuration data is configuration data in the Configuration Type file of described slave node, that have the second title, and described configuration data value is obtained the version number of the Configuration Type file that carries described slave node in message;
Described host node inquires about whether there is described the second title from described presetting database;
If so, described host node sends to described slave node by numerical value corresponding to described the second title;
If not, described host node is query aim Configuration Type file, and the version number of described target configuration type file is identical with the version number of the Configuration Type file of described slave node;
By in described target configuration type file, numerical value corresponding to described the second title sends to described slave node.
8. a configuration data processing method, is characterized in that, comprising:
Slave node sends the Configuration Type file of described slave node to host node, so that described host node is preserved the Configuration Type file of described slave node, the version number of the Configuration Type file of described slave node is different from the version number of the Configuration Type file of storing in host node, described Configuration Type file comprises configuration data, and described version number is corresponding one by one with described Configuration Type file.
9. method according to claim 8, is characterized in that, the Configuration Type file that described slave node sends described slave node to host node comprises:
After described slave node determines that the version number of Configuration Type file of described host node is different with the version number of the Configuration Type file of described slave node, described slave node sends the Configuration Type file of described slave node to host node.
10. method according to claim 9, is characterized in that, determines that the version number of Configuration Type file of the described host node detailed process different with the version number of the Configuration Type file of described slave node comprises:
Described slave node receives the version number of the Configuration Type file of described host node;
Described slave node, by the version number of Configuration Type file of more described slave node and the version number of the Configuration Type file of described host node, determines that both are different.
11. methods according to claim 8, is characterized in that, the Configuration Type file that described slave node sends described slave node to host node comprises:
Described slave node is according to the Configuration Type file request message receiving, to described host node, send the Configuration Type file of described slave node, described configuration file request message is determined the version number of Configuration Type file of described host node and the different rear transmissions of version number of the Configuration Type file of described slave node by described host node.
Method described in 12. according to Claim 8 to 10 any one, is characterized in that, after sending the Configuration Type file of described slave node, also comprises at slave node to host node:
When the value of configuration data in the Configuration Type file of described slave node, that have the first title is modified to described second value by the first numerical value, described slave node sends described the first title and described second value to described host node.
13. 1 kinds of host nodes, is characterized in that, comprising:
The first receiver module, for receiving the Configuration Type file of slave node, the version number of the Configuration Type file of described slave node is different from the version number of the Configuration Type file of storing in described host node, described Configuration Type file comprises configuration data, and described version number is corresponding one by one with described Configuration Type file;
The first memory module, for preserving the Configuration Type file of described slave node.
14. host nodes according to claim 13, is characterized in that, also comprise:
The first sending module, before receiving the Configuration Type file of described slave node at described the first receiver module, when meeting when pre-conditioned, sends the version number of the Configuration Type file of described host node to described slave node.
15. host nodes according to claim 13, is characterized in that, also comprise:
The first determination module, for when meeting when pre-conditioned, obtains the version number of the Configuration Type file of described slave node, and by relatively, determines that the version number of Configuration Type file of described slave node is different with the version number of the Configuration Type file of described host node;
The second sending module, after determining that when described the first determination module the version number of Configuration Type file of described host node is different with the version number of the Configuration Type file of described slave node, sends Configuration Type file request message to described slave node.
16. according to claim 13 to the host node described in 15 any one, it is characterized in that, also comprises:
The second receiver module, for receiving described slave node configuration data that send, that have the first title and second value, the value of described configuration data configuration data in the Configuration Type file of described slave node, that have the first title is sent out while being modified to described second value by the first numerical value;
The second memory module, for being kept at presetting database by described the first title and described second value correspondence.
17. according to the host node described in 16, it is characterized in that, also comprises:
The 3rd receiver module, for receiving the configuration data value of described slave node transmission, obtain message, described configuration data is configuration data in the Configuration Type file of described slave node, that have the second title, and described configuration data value is obtained the version number of the Configuration Type file that carries described slave node in message;
Enquiry module, for whether there is described the second title from described presetting database inquiry, if, numerical value corresponding to described the second title is sent to described slave node, if not, query aim Configuration Type file, the version number of described target configuration type file is identical with the version number of the Configuration Type file of described slave node, by described target configuration type file, numerical value corresponding to described the second title sends to described slave node.
18. 1 kinds of slave nodes, is characterized in that, comprising:
The 4th sending module, for send the Configuration Type file of described slave node to host node, so that described host node is preserved the Configuration Type file of described slave node, the version number of the Configuration Type file of described slave node is different from the version number of the Configuration Type file of storing in host node, described Configuration Type file comprises configuration data, and described version number is corresponding one by one with described Configuration Type file.
19. slave nodes according to claim 18, is characterized in that, aspect the described Configuration Type file that sends described slave node to host node, described the 4th sending module specifically for:
After definite version number of Configuration Type file of described host node is different with the version number of the Configuration Type file of described slave node, to host node, send the Configuration Type file of described slave node.
20. slave nodes according to claim 19, is characterized in that, also comprise:
The second determination module, for receiving the version number of the Configuration Type file of described host node, and by relatively, determines that the version number of Configuration Type file of described slave node is different with the version number of the Configuration Type file of described host node.
21. slave nodes according to claim 18, is characterized in that, aspect the described Configuration Type file that sends described slave node to host node, described the 4th sending module specifically for:
According to the Configuration Type file request message receiving, to described host node, send the Configuration Type file of described slave node, described configuration file request message is determined the version number of Configuration Type file of described host node and the different rear transmissions of version number of the Configuration Type file of described slave node by described host node.
22. according to claim 18 to the slave node described in 21 any one, it is characterized in that, also comprises:
The 5th sending module, while being modified to described second value for the value of the configuration data Configuration Type file when described slave node, that have the first title by the first numerical value, sends described the first title and described second value to described host node.
CN201310528909.XA 2013-10-30 2013-10-30 A kind of configuration data processing method and device Active CN103580918B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201310528909.XA CN103580918B (en) 2013-10-30 2013-10-30 A kind of configuration data processing method and device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201310528909.XA CN103580918B (en) 2013-10-30 2013-10-30 A kind of configuration data processing method and device

Publications (2)

Publication Number Publication Date
CN103580918A true CN103580918A (en) 2014-02-12
CN103580918B CN103580918B (en) 2017-12-15

Family

ID=50051899

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201310528909.XA Active CN103580918B (en) 2013-10-30 2013-10-30 A kind of configuration data processing method and device

Country Status (1)

Country Link
CN (1) CN103580918B (en)

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104320466A (en) * 2014-10-29 2015-01-28 侯荣涛 Office data storage structure and office data updating method for subsystems of communication system
CN105005487A (en) * 2015-06-29 2015-10-28 清华大学 Continuous-service high-performance cluster operating system online upgrading method
CN105791337A (en) * 2014-12-19 2016-07-20 华为数字技术(苏州)有限公司 Upgrading method, device and cluster system
CN106803790A (en) * 2016-12-06 2017-06-06 浙江大华技术股份有限公司 The upgrade control method and device of a kind of group system
CN108345462A (en) * 2018-01-11 2018-07-31 华为技术有限公司 The method and apparatus of component upgrade
CN111752488A (en) * 2020-06-30 2020-10-09 重庆紫光华山智安科技有限公司 Management method and device of storage cluster, management node and storage medium

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030023898A1 (en) * 2001-07-16 2003-01-30 Jacobs Dean Bernard Layered architecture for data replication
CN101795392A (en) * 2009-12-25 2010-08-04 深圳市同洲电子股份有限公司 Application data-downloading method, digital television receiving terminal and system
CN101888407A (en) * 2010-06-11 2010-11-17 广东宝莱特医用科技股份有限公司 Method for configuration interactive synchronization between independently used module and module integrating device

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030023898A1 (en) * 2001-07-16 2003-01-30 Jacobs Dean Bernard Layered architecture for data replication
CN101795392A (en) * 2009-12-25 2010-08-04 深圳市同洲电子股份有限公司 Application data-downloading method, digital television receiving terminal and system
CN101888407A (en) * 2010-06-11 2010-11-17 广东宝莱特医用科技股份有限公司 Method for configuration interactive synchronization between independently used module and module integrating device

Cited By (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104320466A (en) * 2014-10-29 2015-01-28 侯荣涛 Office data storage structure and office data updating method for subsystems of communication system
CN105791337A (en) * 2014-12-19 2016-07-20 华为数字技术(苏州)有限公司 Upgrading method, device and cluster system
CN105791337B (en) * 2014-12-19 2019-11-12 华为数字技术(苏州)有限公司 A kind of upgrade method, equipment and group system
CN105005487A (en) * 2015-06-29 2015-10-28 清华大学 Continuous-service high-performance cluster operating system online upgrading method
CN105005487B (en) * 2015-06-29 2018-06-22 清华大学 A kind of High-Performance Computing Cluster operating system online upgrading method of continuous service
CN106803790A (en) * 2016-12-06 2017-06-06 浙江大华技术股份有限公司 The upgrade control method and device of a kind of group system
CN106803790B (en) * 2016-12-06 2019-09-17 浙江大华技术股份有限公司 A kind of upgrade control method and device of group system
CN108345462A (en) * 2018-01-11 2018-07-31 华为技术有限公司 The method and apparatus of component upgrade
CN111752488A (en) * 2020-06-30 2020-10-09 重庆紫光华山智安科技有限公司 Management method and device of storage cluster, management node and storage medium
CN111752488B (en) * 2020-06-30 2022-11-01 重庆紫光华山智安科技有限公司 Management method and device of storage cluster, management node and storage medium

Also Published As

Publication number Publication date
CN103580918B (en) 2017-12-15

Similar Documents

Publication Publication Date Title
CN103580918A (en) Method and device for processing configuration data
US8880838B2 (en) Storage network data allocation
CN103544077A (en) Data processing method and device and shared memory device
CN104301233A (en) Route access method, route access system and user terminal
CN109213699A (en) A kind of metadata management method, system, equipment and computer readable storage medium
CN101944124A (en) Distributed file system management method, device and corresponding file system
CN103812849A (en) Local cache updating method and system, client and server
US8959504B2 (en) Update scanning
CN103491152A (en) Metadata obtaining method, device and system in distributed file system
CN103324533A (en) distributed data processing method, device and system
CN104516794A (en) Database document backup method, device and system
CN103678143A (en) File storage method and device and electronic equipment
CN105468300A (en) IP hard disc management method and device
CN102821111A (en) Real-time synchronizing method for file cloud storage
JP6975153B2 (en) Data storage service processing method and equipment
US11455117B2 (en) Data reading method, apparatus, and system, avoiding version rollback issues in distributed system
CN102419753B (en) Information processing equipment, information processing method and information processing system
CN105279020A (en) Task scheduling method and system
CN104808953B (en) Control the method, device and mobile terminal of data storage
CN103412860A (en) Method and device for extending database and database system
CN109829678B (en) Rollback processing method and device and electronic equipment
CN105144073A (en) Removable storage device identity and configuration information
CN104572638A (en) Data reading and writing method and device
US8725966B2 (en) Generation and update of storage groups constructed from storage devices distributed in storage subsystems
CN113806076B (en) Method, device, equipment and readable medium for distributing four-control environment memory

Legal Events

Date Code Title Description
C06 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant