CN109600263A - EOS node realizes the method that node is automatically accessed and produced by access ETCD cluster - Google Patents
EOS node realizes the method that node is automatically accessed and produced by access ETCD cluster Download PDFInfo
- Publication number
- CN109600263A CN109600263A CN201811554623.8A CN201811554623A CN109600263A CN 109600263 A CN109600263 A CN 109600263A CN 201811554623 A CN201811554623 A CN 201811554623A CN 109600263 A CN109600263 A CN 109600263A
- Authority
- CN
- China
- Prior art keywords
- node
- etcd
- eos
- configuration
- registration center
- 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.)
- Pending
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0803—Configuration setting
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
- H04L41/0654—Management of faults, events, alarms or notifications using network fault recovery
- H04L41/0659—Management of faults, events, alarms or notifications using network fault recovery by isolating or reconfiguring faulty entities
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0803—Configuration setting
- H04L41/0823—Configuration setting characterised by the purposes of a change of settings, e.g. optimising configuration for enhancing reliability
- H04L41/0833—Configuration setting characterised by the purposes of a change of settings, e.g. optimising configuration for enhancing reliability for reduction of network energy consumption
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0876—Aspects of the degree of configuration automation
- H04L41/0886—Fully automatic configuration
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0893—Assignment of logical groups to network elements
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Automation & Control Theory (AREA)
- Computer And Data Communications (AREA)
Abstract
The invention discloses the method that EOS node is automatically accessed and produced by access ETCD cluster realization node, this method includes introducing registration center ETCD to be registered；EOS node is started by configuring sharing mode, when the starting of each node, requires to be registered in registration center ETCD, keeps long connection by EOS node and registration center ETCD service, and the state of node is monitored by registration center ETCD；When new node accesses, automatic acquisition configuration is started, and realizes synchronous configuration, while the configuration of all nodes is monitored by registration center ETCD；After certain node failure of starting, ETCD services automatic rejection malfunctioning node information, realizes the automatic rejection of EOS node；When making configuration change after having new node to enter or reject certain malfunctioning node, program automatically updates configured list, and all online EOS nodes is notified to obtain latest configuration automatically.Through the above scheme, invention achieves the purposes for automatically accessing and producing of node, have very high practical value and promotional value.
Description
Technical field
The invention belongs to block chain technical fields, and in particular to EOS node realizes that node is automatic by access ETCD cluster
The method for accessing and producing.
Background technique
In block chain EOS node deployment, when the starting of EOS node, load configuration information is required, when there is new node
When access, need to restart server load configuration, after some node breaks down, the information of the node still remains EOS section
In point, so there are following four disadvantages in terms of EOS load is configured with automatic management node: (1) needing to add when service starting
Configuration information is carried, each service of these configuration informations is similar, wants if carrying out configuration by reading configuration file and can exist
More parts of configuration files are write, are resulted in waste of resources；(2) when configuration file is changed, the configuration file of each node will be changed, and
Change can just come into force after needing to restart service with postponing, and make configuration extremely not flexible, increase deployment difficulty；(3) new node accesses
When, it needs to write configuration file from newly, causes deploying step cumbersome；(4) when there is node failure, malfunctioning node is not picked
It removes, causes useless connection, increase network consumption.Therefore solving the above problems is those skilled in the art's urgent need to resolve.
Summary of the invention
The purpose of the present invention is to provide the sides that EOS node is automatically accessed and produced by access ETCD cluster realization node
Method mainly solves complex steps when EOS node existing in the prior art accesses again, while cannot be certainly after EOS node failure
Turn goes out the problem of increasing network consumption.
To achieve the goals above, The technical solution adopted by the invention is as follows:
EOS node realizes the method that node is automatically accessed and produced by access ETCD cluster, includes the following steps:
1) registration center ETCD is introduced to be registered；
2) EOS node is started by configuring sharing mode acquisition configured list, when the starting of each node, Suo Youpei
It sets and requires to be registered in registration center ETCD, long connection is kept by EOS node and registration center ETCD service, and pass through
Registration center ETCD is monitored the state of node, while all configurations of other nodes to be started are all from registration center ETCD
It is obtained；
3) when new node accesses, automatic acquisition configuration is started, and configuration synchronous with the realization of other nodes, is owned simultaneously
The configuration of node is monitored by registration center ETCD；
4) after certain node failure of starting, ETCD services automatic rejection malfunctioning node information, realizes the automatic of EOS node
It rejects；
5) when making configuration change after having new node to enter or reject certain malfunctioning node, program automatically updates configuration column
Table, while all online EOS nodes being notified to obtain latest configuration automatically.
Further, it included three stages that the configuration in the step 2 is shared, was respectively as follows:
When a:EOS starts, all configuration informations dynamically are registered to registration center ETCD；
B: when EOS does P2P connection, all ip and port are read from registration center ETCD；
When c:EOS node has change, need to reacquire latest configuration table data from registration center ETCD.
Further, new node access included three stages in the step 3, was respectively as follows:
A: when there is new node access, the configuration of this node is registered first, then directly obtains and configures from registration center ETCD
New list；
B: other nodes monitor that catalogue changes, and online EOS node is notified to have new node to need to connect；
Latest configuration table data is obtained from registration center ETCD when other nodes of c:EOS do P2P connection.
Specifically, in the step 4 when certain node failure, processing includes four-stage, is respectively as follows:
A: all EOS nodes and registration center ETCD service keep long connection, the key by each node with expired time
Refresh key value in value and timer fixed time period and keeps long connection；
B: all nodes of the monitoring in addition to this node start monitoring event to the key value of each node；
C: after some node failure, this node would not persistently refresh key value, will trigger monitoring event, event touching
After hair, the configuration of malfunctioning node in registration center ETCD service is deleted, and the ip and port of malfunctioning node are notified to save to other
Point；
Other nodes of d:EOS are notified, reacquire latest configuration table data.
Compared with prior art, the invention has the following advantages:
(1) present invention can obtain automatically configuration when there is new EOS node access and be started, while all nodes
Configuration is monitored by registration center ETCD, is avoided and is needed to reconfigure file as the prior art, to cause portion
The case where affixing one's name to complex steps occurs, and present invention step in the access of EOS new node is simple compared with the existing technology.
(2) in the present invention when there is node failure, access and the section of EOS node with automatic rejection malfunctioning node, can be realized
The automatic management of point, while when there is configuration change, program automatically updates configured list, while notifying all online EOS
Node obtains latest configuration automatically, so that network consumption and load capacity are alleviated, so that whole network operation is more unobstructed.
Detailed description of the invention
Fig. 1 is flow diagram of the invention.
Specific embodiment
Present invention will be further explained below with reference to the attached drawings and examples, and embodiments of the present invention include but is not limited to
The following example.
Embodiment
As shown in Figure 1, EOS node realizes the method that node is automatically accessed and produced by access ETCD cluster, including such as
Lower step:
Registration center ETCD is introduced to be registered；EOS node is started by configuring sharing mode acquisition configured list,
Wherein configuration is shared when being included in EOS starting, dynamically registers all configuration informations to registration center ETCD, does P2P connection in EOS
When, all ip and port are read from registration center ETCD, other nodes of EOS are obtained when doing P2P connection from registration center ETCD
Latest configuration table data is taken, when the starting of each node, all configurations require to be registered in registration center ETCD, pass through
EOS node and registration center ETCD service keep long connection, and the state of node is monitored by registration center ETCD, simultaneously
All configurations of other nodes to be started are all obtained from registration center ETCD.
When there is new node access, the configuration of this node is registered first, and it is new then directly to obtain configuration from registration center ETCD
List, other nodes monitor that catalogue changes, notify online EOS node to have new node to need to connect, other nodes of EOS
Obtain latest configuration table data from registration center ETCD when doing P2P connection, it is automatic to obtain configuration and is started, and with other sections
Point realizes synchronous configuration, while the configuration of all nodes is monitored by registration center ETCD；In all EOS nodes and registration
Heart ETCD service keeps long connection, by refreshing key in key value and timer fixed time period of each node with expired time
It is worth and keeps long connection, all nodes in addition to this node starts monitoring event, the event of some node to the key value of each node
After barrier, this node would not persistently refresh key value, will trigger monitoring event, and delete going out in registration center's ETCD service
The configuration of the node of failure, and the ip and port of malfunctioning node are notified to give other nodes, other nodes of EOS are notified, weight
It is new to obtain latest configuration table data.
When making configuration change after having new node to enter or reject certain malfunctioning node, program automatically updates configured list,
All online EOS nodes are notified to obtain latest configuration automatically simultaneously.By the above method, the present invention realizes oneself of new node
The function that the node of dynamic access and failure is automatically deleted not will cause deployment step to effectively improve the flexibility of configuration
Rapid is cumbersome, while deleting the node of failure, avoids the useless connection of other nodes, while alleviating the consumption of network.
Above-described embodiment is merely a preferred embodiment of the present invention, and it is not intended to limit the protection scope of the present invention, as long as using
Design principle of the invention, and the non-creative variation worked and made is carried out on this basis, it should belong to of the invention
Within protection scope.
Claims (4)
1.EOS node realizes the method that node is automatically accessed and produced by access ETCD cluster, which is characterized in that including as follows
Step:
1) registration center ETCD is introduced to be registered；
2) EOS node is started by configuring sharing mode acquisition configured list, and when the starting of each node, all configurations are all
It needs to be registered in registration center ETCD, long connection is kept by EOS node and registration center ETCD service, and pass through registration
Center ETCD is monitored the state of node, while all configurations of other nodes to be started are all carried out from registration center ETCD
It obtains；
3) when new node accesses, automatic acquisition configuration is started, and configuration synchronous with the realization of other nodes, while all nodes
Configuration be monitored by registration center ETCD；
4) after certain node failure of starting, ETCD services automatic rejection malfunctioning node information, realizes picking automatically for EOS node
It removes；
5) when making configuration change after having new node to enter or reject certain malfunctioning node, program automatically updates configured list, together
All online EOS nodes of Shi Tongzhi obtain latest configuration automatically.
2. EOS node according to claim 1 realizes the method that node is automatically accessed and produced by access ETCD cluster,
It is characterized in that, the configuration in the step 2 is shared including three stages, it is respectively as follows:
When a:EOS starts, all configuration informations dynamically are registered to registration center ETCD；
B: when EOS does P2P connection, all ip and port are read from registration center ETCD；
When c:EOS node has change, need to reacquire latest configuration table data from registration center ETCD.
3. EOS node according to claim 2 realizes the method that node is automatically accessed and produced by access ETCD cluster,
It is characterized in that, new node access included three stages in the step 3, it is respectively as follows:
A: when there is new node access, registering the configuration of this node first, then directly obtains the new column of configuration from registration center ETCD
Table；
B: other nodes monitor that catalogue changes, and online EOS node is notified to have new node to need to connect；
Latest configuration table data is obtained from registration center ETCD when other nodes of c:EOS do P2P connection.
4. EOS node according to claim 3 realizes the method that node is automatically accessed and produced by access ETCD cluster,
It is characterized in that, processing includes four-stage in the step 4 when certain node failure, it is respectively as follows:
A: all EOS nodes and registration center ETCD service keep long connection, key value by each node with expired time and
Refresh key value in timer fixed time period and keeps long connection；
B: all nodes of the monitoring in addition to this node start monitoring event to the key value of each node；
C: after some node failure, this node would not persistently refresh key value, will trigger monitoring event, after event triggering,
The configuration of malfunctioning node in registration center ETCD service is deleted, and the ip and port of malfunctioning node are notified to give other nodes；
Other nodes of d:EOS are notified, reacquire latest configuration table data.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811554623.8A CN109600263A (en) | 2018-12-18 | 2018-12-18 | EOS node realizes the method that node is automatically accessed and produced by access ETCD cluster |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811554623.8A CN109600263A (en) | 2018-12-18 | 2018-12-18 | EOS node realizes the method that node is automatically accessed and produced by access ETCD cluster |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN109600263A true CN109600263A (en) | 2019-04-09 |
Family
ID=65963988
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201811554623.8A Pending CN109600263A (en) | 2018-12-18 | 2018-12-18 | EOS node realizes the method that node is automatically accessed and produced by access ETCD cluster |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN109600263A (en) |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20130083691A1 (en) * | 2011-10-04 | 2013-04-04 | Juniper Networks, Inc. | Methods and apparatus for a self-organized layer-2 enterprise network architecture |
| CN105099761A (en) * | 2015-06-26 | 2015-11-25 | 广东欧珀移动通信有限公司 | Method and system for concentratedly managing configuration information of client |
| CN107734035A (en) * | 2017-10-17 | 2018-02-23 | 华南理工大学 | A kind of Virtual Cluster automatic telescopic method under cloud computing environment |
-
2018
- 2018-12-18 CN CN201811554623.8A patent/CN109600263A/en active Pending
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20130083691A1 (en) * | 2011-10-04 | 2013-04-04 | Juniper Networks, Inc. | Methods and apparatus for a self-organized layer-2 enterprise network architecture |
| CN105099761A (en) * | 2015-06-26 | 2015-11-25 | 广东欧珀移动通信有限公司 | Method and system for concentratedly managing configuration information of client |
| CN107734035A (en) * | 2017-10-17 | 2018-02-23 | 华南理工大学 | A kind of Virtual Cluster automatic telescopic method under cloud computing environment |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US8386536B2 (en) | Gateway server, file management system, and file management method and program | |
| US8307085B2 (en) | Storing state of distributed architecture in external store | |
| Namiot et al. | On software standards for smart cities: API or DPI | |
| CN103338243B (en) | The data cached update method and system of Web node | |
| KR101871383B1 (en) | Method and system for using a recursive event listener on a node in hierarchical data structure | |
| US9479603B2 (en) | Integration of active interest information with an address book | |
| CN110765165B (en) | Method, device and system for synchronously processing cross-system data | |
| CN107103011B (en) | Method and device for realizing terminal data search | |
| US20190050945A1 (en) | Auto-suggestion for group activities based on combined user data sets | |
| CN107104824A (en) | A kind of network topology determines method and apparatus | |
| US8751711B2 (en) | Storage topology manager | |
| CN104657435A (en) | Storage management method for application data and network management system | |
| CN109600263A (en) | EOS node realizes the method that node is automatically accessed and produced by access ETCD cluster | |
| CN114157671A (en) | Method for distributing information carried by blockchain network to a plurality of client nodes | |
| CN101789963A (en) | Data synchronization system | |
| CN113938842A (en) | Method, network equipment and system for self-organizing network root node election | |
| CN110674080B (en) | Method and system for collecting large-data-volume unstructured file based on NiFi | |
| CN111367996A (en) | KV index-based thermal data increment synchronization method and device | |
| CN116594834A (en) | Operation and maintenance data processing method and device for multi-protocol server | |
| CN110609812A (en) | Design method of tagged file system | |
| CN113505111B (en) | Shared directory mounting method and distributed network additional storage system | |
| TWI481227B (en) | System and method for forwarding object | |
| CN105389368A (en) | Method for managing metadata of database cluster of MPP architecture | |
| CN116126521B (en) | Load balancing method, device, storage medium and equipment for service memory information | |
| CN108092790B (en) | Management method and device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20190409 |