CN105208090A - Zookeeper-based Leader selection method - Google Patents
Zookeeper-based Leader selection method Download PDFInfo
- Publication number
- CN105208090A CN105208090A CN201510509299.8A CN201510509299A CN105208090A CN 105208090 A CN105208090 A CN 105208090A CN 201510509299 A CN201510509299 A CN 201510509299A CN 105208090 A CN105208090 A CN 105208090A
- Authority
- CN
- China
- Prior art keywords
- server
- leader
- zookeeper
- node
- cluster
- 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
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/104—Peer-to-peer [P2P] networks
- H04L67/1044—Group management mechanisms
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/104—Peer-to-peer [P2P] networks
- H04L67/1044—Group management mechanisms
- H04L67/1048—Departure or maintenance mechanisms
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/104—Peer-to-peer [P2P] networks
- H04L67/1044—Group management mechanisms
- H04L67/1051—Group master selection mechanisms
Landscapes
- Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- Computing Systems (AREA)
- Mathematical Physics (AREA)
- Theoretical Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The invention discloses a Zookeeper-based Leader selection method. The method comprises the following steps: 1, one EPHEMERAL directory node is created on each server, each server is numbered by the directory node, and a server with a current minimum number is selected as a Leader; and 2, when the server with the minimum number dies, because of the EPHEMERAL nodes, the node corresponding to the dead server is also deleted, another node with a minimum number reoccurs in a current node list, and the node is selected as a current Leader so that the problem of a single-point fault easily generated by a single Leader is prevented through dynamic selection of the Leader. According to the invention, process reengineering and optimization are carried out on a conventional platform; and the connection relation of system expansion is fully considered, and the employed technology and system structure can ensure future upgrading or seamless connection expansion of a service information system.
Description
Technical field
The present invention relates to a kind of method realizing Leader election based on Zookeeper, belong to technical field of electronic commerce.
Background technology
Along with the development of China's economic, the raising of people's living standard, people increase greatly for the demand of food, food security is more and more paid close attention to, simultaneously along with the quickening of society advancement, people are more and more busy, spend and compressed again and again in the time on food of buying, and spend in the time on healthy food of choosing just less, for how choosing " quality-assured vegetables ", " healthy dish " lacks experience especially.Therefore how to allow resident has bought health more easily, fresh, relieved agricultural product have just become the focus that numerous residents pay close attention to, also country paid close attention to simultaneously, in recent years, country is putting into effect a lot of policy for resident can buy in food convenient, safely, and visible government is quite pay attention to for food service industry.Under this overall situation, the investor of " agriculture and animal husbandry people " website has established this website, and in order to adapt to the needs of this platform development, in order to better for decision-making provides reference, more needs a set of perfect information system and business platform to support.
The website of e-commerce platform theory implanted by daily for resident required food by " agriculture and animal husbandry people " website the earliest as China, its decision-making level shows great foresight, take the lead in using information tool to manage its operation flow, roughly establish the codes and standards of routine work sequential work steps and automation.
But this website in use mainly contains the problem of the following aspects: 1, system flow different design closes the requirement of existing business flow process; 2, user operation is unfriendly, inconvenient; 3, original system and architecture design existing defects.Due to limitation and the defect of original system design, make system inevitably produce the problem of various instability, thus need the specification according to software standardization, optimization as much as possible is carried out to existing system, to improve the performance of system.
Summary of the invention
For the deficiency that prior art exists, the object of the invention is to provide a kind of method realizing Leader election based on Zookeeper, can optimization system, makes system more stable, thus improves the performance of system.
To achieve these goals, the present invention realizes by the following technical solutions:
A kind of method realizing Leader election based on Zookeeper of the present invention, comprises following step:
(1) on every station server, create an EPHEMERAL_SEQUENTIAL directory node, described EPHEMERAL_SEQUENTIAL directory node gives every station server numbering, and to select current be that the server of lowest number is as Leader;
(2) when the server of this lowest number is die, owing to being EPHEMERAL node, the node that the server of dying is corresponding is also deleted, so there is again the node of a lowest number in current node listing, just selecting this node to be current Leader, avoiding single Leader easily to occur Single Point of Faliure problem for realizing Dynamic Selection Leader.
The configuration item of Zookeeper cluster mode is as follows:
initLimit＝4
syncLimit＝3
server.1＝192.168.211.1:2888:3888
server.2＝192.168.211.2:2888:3888
InitLimit: this configuration item is used to configuration Zookeeper and accepts client, the longlyest how many heartbeat time interval numbers can be stood when initialization connects, Zookeeper server does not also receive the return information of client after more than the time span of 10 heartbeats, so show the failure of this client's side link, total time span be exactly 4*2000=8 second;
SyncLimit: this configuration item mark Leader and Follower between send message, request and response time length, the longest time span that can not exceed how many tickTime, total time span be exactly 3*2000=6 second;
Server.A=B:C:D: wherein A is a numeral, represents which number server this is; B is the ip address of this server; The port of the Leader server exchange information in what C represented is this server and cluster; What D represented is just in case the Leader server in cluster has been hung, and needs a port to re-start election, select a new Leader, and this port is just used to perform the port that when electing, server intercoms mutually; If the configuration mode of pseudo-cluster, because B is the same, so different Zookeeper instance communications port numbers can not be the same, different port numbers to be distributed to them.
The present invention is directed to the traffic-operating period that existing " agriculture and animal husbandry people " website is current, combing is carried out to existing operation flow, carries out business process reengineering (BPR), BPR and optimization are carried out to platform; The present invention is overall with the whole information platform project in " agriculture and animal husbandry people " website, enter and fully, systematically optimized, fully take into account the joining relation of system extension, the technology of employing and architecture, the upgrading in the future of guaranteed service information system or expansion connection.
Accompanying drawing explanation
Fig. 1 is ZooKeeper configuration management structure chart.
Embodiment
The technological means realized for making the present invention, creation characteristic, reaching object and effect is easy to understand, below in conjunction with embodiment, setting forth the present invention further.
ZooKeeper be one distributed, the distributed application program coordination service of open source code, being Chubby realization of increasing income of ***, is the significant components of Hadoop and Hbase.It is one provides the software of Consistency service for Distributed Application, and the function provided comprises: configuring maintenance, name Service, distributed synchronization, group service etc.
The target of ZooKeeper is exactly the key service that packaged complexity is easily made mistakes, and the system of the interface be simple and easy to and performance efficiency, function-stable is supplied to user.
Zookeeper principle is based on FastPaxos algorithm, there is the problem of livelock in paxos algorithm, namely when having that multiple proposer is staggered to be submitted to, likely the mutually exclusive neither one proposer that causes can submit to successfully, and FastPaxos has done some optimizations, by electing a leader, leader is only had to submit propose to, the visible FastPaxos of specific algorithm.
The basic running flow process of ZooKeeper is as follows:
1, Leader is elected;
2, synchrodata;
3, elect algorithm in Leader process to have a lot, but the election criterion that will reach is consistent;
4, Leader will have the highest zxid.
5, in cluster, most machine meets with a response and the Leader that selects of follow.
Zookeeper feature
In Zookeeper, znode is a node of following Unix file system path similar, can store or obtain data by this node in the past.If Flag is set to EPHEMERAL when creating znode, so after the node and Zookeeper that create this znode lose connection, this znode will no longer exist in Zookeeper, and Zookeeper uses Watcher to discover event information.When client receives event information, such as connect time-out, node data changes, child node changes, corresponding behavior can be called and carry out deal with data.How the Wiki page presentation of Zookeeper uses Zookeeper to process event notice, queue, Priority Queues, lock, shared lock, voidable shared lock, Two-phase commitment
So what Zookeeper can do, simple example: suppose that we have the server of 20 search engines (search mission of the part in each responsible general index) and a director server (being responsible for sending searching request and amalgamation result collection to the server of these 20 search engines), a director server for subsequent use (being responsible for the replacement director server when director server delays machine), the cgi (sending searching request to director server) of a web.15 servers in the server of search engine provide search service, and 5 servers are just at generating indexes.The server of these 20 search engines often will allow is providing the server of search service to stop providing service to start generating indexes, or the server of generating indexes derivation of having keeped vegetarian has become can search for provide and served.Use Zookeeper can ensure that director server automatic sensing has how many servers of search engine is provided and sends searching request to these servers, automatically enable director server for subsequent use when director server delays machine.
Zookeeper distributed service framework is a sub-project of ApacheHadoop, it is mainly with solving some the data management problems often run in Distributed Application, as: the management etc. of Uniform Name service, state synchronized service, cluster management, Distributed Application configuration item.
Zookeeper not only can provide service by unit, also supports that multimachine composition cluster provides service simultaneously.In fact Zookeeper also supports the mode of another pseudo-cluster, namely can run multiple Zookeeper example in a physical machine, will introduce installation and the configuration of cluster mode below.
Installation and the configuration of the cluster mode of Zookeeper neither be very complicated, and what do is exactly increase several configuration item.Cluster mode also will increase several configuration item below except the configuration item of three above:
initLimit＝5
syncLimit＝2
server.1＝192.168.211.1:2888:3888
server.2＝192.168.211.2:2888:3888
InitLimit: this configuration item is used to configuration Zookeeper and accepts the longlyest can stand how many heartbeat time interval numbers when client (client mentioned here is not the client that user connects Zookeeper server, but is connected to the Follower server of Leader in Zookeeper server cluster) initialization connects.Zookeeper server does not also receive the return information of client after more than time (namely tickTime) length of 10 heartbeats, so shows this client's side link failure.Be exactly total time span 5*2000=10 second
SyncLimit: this configuration item mark Leader and Follower between send message, request and response time length, the longest time span that can not exceed how many tickTime, total time span be exactly 2*2000=4 second
Server.A=B:C:D: wherein A is a numeral, represents which number server this is; B is the ip address of this server; The port of the Leader server exchange information in what C represented is this server and cluster; What D represented is just in case the Leader server in cluster has been hung, and needs a port to re-start election, select a new Leader, and this port is just used to perform the port that when electing, server intercoms mutually.If the configuration mode of pseudo-cluster, because B is the same, so different Zookeeper instance communications port numbers can not be the same, so will distribute different port numbers to them.
Except amendment zoo.cfg configuration file, a file myid also will be configured under cluster mode, this file is under dataDir catalogue, data are just had to be exactly the value of A inside this file, Zookeeper can read this file when starting, and the data inside taking compare with the configuration information inside zoo.cfg thus determine the end is that server.
Zookeeper is from Design Mode angle, it is a distributed service management framework based on Observer Pattern design, it is responsible for the data that store and management is all concerned about, then the registration of observer is accepted, once the state of these data changes, those observers that responsible notice has been registered on Zookeeper are just made corresponding reaction by Zookeeper, thus realizing similar Master/Slave management mode in cluster, the interior details such as detailed architecture about Zookeeper can read the source code of Zookeeper
The typical application scenarios of Zookeeper is as follows:
Uniform Name service (NameService)
In Distributed Application, usually the naming rule of complete set is needed, unique title can either be produced be convenient to again people's identification and remember, a desirable selection by tree-like name structure under normal circumstances, tree-like name structure is a stratified bibliographic structure, not only can not repeat people close friend.Mention here that you may contemplate JNDI, the function that NameService and the JNDI of quite right Zookeeper can complete is much the same, they are all be associated with in certain resource by stratified bibliographic structure, but the NameService of Zookeeper is the association in broad sense more, perhaps you do not need names associate in specific resources, you only may need one can not repeat title, just as the digital major key that generation one in database is unique.
NameService has been the built-in function of Zookeeper, as long as the API that you call Zookeeper just can realize.Just the node that creates a directory can be easy to as called create interface.
See Fig. 1, configuration management (ConfigurationManagement)
The management of configuration is very common in distributed application environment, such as same application system needs multiple pc Server to run, but some configuration item of the application system that they run is identical, if revise the configuration item that these are identical, so just must revise the PCServer that every platform runs this application system simultaneously, bother so very much and easily make mistakes.
Such a configuration information can be given Zookeeper to manage completely, configuration information is kept in certain directory node of Zookeeper, then by all states needing the applied for machines monitoring configuration information of amendment, once configuration information changes, every platform applied for machines will receive the notice of Zookeeper, then obtains new configuration information from Zookeeper and is applied to system.
Cluster management (GroupMembership)
Zookeeper can realize the function of cluster management easily, a service cluster is formed if any multiple stage Server, so one " house steward " service state of every platform machine in current cluster must be known, once there be machine not provide service, in cluster, other cluster must be known, thus adjusts and redistribute service strategy.Equally when increasing the service ability of cluster, one or more Server will be increased, " house steward " equally also must be allowed to know.
Zookeeper can not only help you to safeguard the service state of machine in current cluster, and you can be helped to select one " house steward ", allows this house steward carry out management cluster, another function LeaderElection of Here it is Zookeeper.
Their implementation is all the directory node creating an EPHEMERAL type on Zookeeper, then each Server they create directory node parent directory node on call getChildren (Stringpath, booleanwatch) method to arrange watch be true, owing to being EPHEMERAL directory node, when the Server creating it dies, this directory node is also thereupon deleted, so Children will change, at this moment the Watch on getChildren will be called, certain Server has been had to die so other Server just knows.Newly-increased Server is also same principle.
How Zookeeper realizes LeaderElection, namely selects a MasterServer.Equally every platform Server above creates an EPHEMERAL directory node, unlike it or a SEQUENTIAL directory node, so it is an EPHEMERAL_SEQUENTIAL directory node.Why it is EPHEMERAL_SEQUENTIAL directory node, because can number to every platform Server, can select current be the Server of lowest number is Master, if the Server of this lowest number dies, owing to being EPHEMERAL node, the node that the Server die is corresponding is also deleted, so there is again the node of a lowest number in current node listing, just selects this node to be current Master.So just achieve Dynamic Selection Master, avoid single Master in traditional sense and easily occur the problem of Single Point of Faliure.
More than show and describe general principle of the present invention and principal character and advantage of the present invention.The technical staff of the industry should understand; the present invention is not restricted to the described embodiments; what describe in above-described embodiment and specification just illustrates principle of the present invention; without departing from the spirit and scope of the present invention; the present invention also has various changes and modifications, and these changes and improvements all fall in the claimed scope of the invention.Application claims protection range is defined by appending claims and equivalent thereof.
Claims (2)
1. realize a method for Leader election based on Zookeeper, it is characterized in that, comprise following step:
(1) on every station server, create an EPHEMERAL_SEQUENTIAL directory node, described EPHEMERAL_SEQUENTIAL directory node gives every station server numbering, and to select current be that the server of lowest number is as Leader;
(2) when the server of this lowest number is die, owing to being EPHEMERAL node, the node that the server of dying is corresponding is also deleted, so there is again the node of a lowest number in current node listing, just selecting this node to be current Leader, avoiding single Leader easily to occur Single Point of Faliure problem for realizing Dynamic Selection Leader.
2. realize the method for Leader election according to claim 1 based on Zookeeper, it is characterized in that, the configuration item of Zookeeper cluster mode is as follows:
initLimit＝4
syncLimit＝3
server.1＝192.168.211.1:2888:3888
server.2＝192.168.211.2:2888:3888
InitLimit: this configuration item is used to configuration Zookeeper and accepts client, the longlyest how many heartbeat time interval numbers can be stood when initialization connects, Zookeeper server does not also receive the return information of client after more than the time span of 10 heartbeats, so show the failure of this client's side link, total time span be exactly 4*2000=8 second;
SyncLimit: this configuration item mark Leader and Follower between send message, request and response time length, the longest time span that can not exceed how many tickTime, total time span be exactly 3*2000=6 second;
Server.A=B:C:D: wherein A is a numeral, represents which number server this is; B is the ip address of this server; The port of the Leader server exchange information in what C represented is this server and cluster; What D represented is just in case the Leader server in cluster has been hung, and needs a port to re-start election, select a new Leader, and this port is just used to perform the port that when electing, server intercoms mutually; If the configuration mode of pseudo-cluster, because B is the same, so different Zookeeper instance communications port numbers can not be the same, different port numbers to be distributed to them.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510509299.8A CN105208090A (en) | 2015-08-19 | 2015-08-19 | Zookeeper-based Leader selection method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510509299.8A CN105208090A (en) | 2015-08-19 | 2015-08-19 | Zookeeper-based Leader selection method |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN105208090A true CN105208090A (en) | 2015-12-30 |
Family
ID=54955514
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201510509299.8A Pending CN105208090A (en) | 2015-08-19 | 2015-08-19 | Zookeeper-based Leader selection method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN105208090A (en) |
Cited By (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105871649A (en) * | 2016-06-21 | 2016-08-17 | 上海帝联信息科技股份有限公司 | Node server, service side and configuration file updating method thereof and updating control method |
| CN106559263A (en) * | 2016-11-17 | 2017-04-05 | 杭州沃趣科技股份有限公司 | A kind of improved distributed consensus algorithm |
| CN106685724A (en) * | 2017-01-10 | 2017-05-17 | 网宿科技股份有限公司 | Node-server management method and device based on election and system |
| CN107423188A (en) * | 2016-03-07 | 2017-12-01 | 阿里巴巴集团控股有限公司 | Log processing method and equipment |
| CN107845013A (en) * | 2017-09-25 | 2018-03-27 | 北京科东电力控制***有限责任公司 | A kind of electric power transaction platform distributed application services calling processing method |
| CN108268314A (en) * | 2016-12-31 | 2018-07-10 | 北京亿阳信通科技有限公司 | A kind of method of multithreading task concurrent processing |
| CN109615554A (en) * | 2018-12-06 | 2019-04-12 | 苏州市伽顿服饰有限公司 | Synchrodata system and its operating procedure, creation method based on intelligence manufacture |
| CN111431999A (en) * | 2020-03-23 | 2020-07-17 | 杭州趣维科技有限公司 | Cloud function distributed system based on Paxos algorithm |
| CN111866048A (en) * | 2019-04-30 | 2020-10-30 | 中移(苏州)软件技术有限公司 | Management method, agent equipment, management equipment, main server and system |
| CN113518116A (en) * | 2021-05-18 | 2021-10-19 | 广州泳泳信息科技有限公司 | Leader server election method and device based on Fast Paxos algorithm |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103152420A (en) * | 2013-03-11 | 2013-06-12 | 汉柏科技有限公司 | Method for avoiding single-point-of-failure of Ovirt virtual management platform |
| CN103188110A (en) * | 2013-03-29 | 2013-07-03 | 汉柏科技有限公司 | Zookeeper-based cloud platform service hot backup method |
| CN104202383A (en) * | 2014-08-26 | 2014-12-10 | 浪潮软件股份有限公司 | Centralized configuration distribution and management method in distributed cluster environment |
-
2015
- 2015-08-19 CN CN201510509299.8A patent/CN105208090A/en active Pending
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103152420A (en) * | 2013-03-11 | 2013-06-12 | 汉柏科技有限公司 | Method for avoiding single-point-of-failure of Ovirt virtual management platform |
| CN103188110A (en) * | 2013-03-29 | 2013-07-03 | 汉柏科技有限公司 | Zookeeper-based cloud platform service hot backup method |
| CN104202383A (en) * | 2014-08-26 | 2014-12-10 | 浪潮软件股份有限公司 | Centralized configuration distribution and management method in distributed cluster environment |
Non-Patent Citations (1)
| Title |
|---|
| DENNISIT: "《http://www.linuxidc.com/linux/2015-02/114230.htm 初始ZooKeeper与集群搭建实例_服务器应用_Linux公社-Linux***门户网站》", 28 February 2015 * |
Cited By (16)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107423188A (en) * | 2016-03-07 | 2017-12-01 | 阿里巴巴集团控股有限公司 | Log processing method and equipment |
| CN107423188B (en) * | 2016-03-07 | 2021-05-07 | 阿里巴巴集团控股有限公司 | Log processing method and device |
| CN105871649A (en) * | 2016-06-21 | 2016-08-17 | 上海帝联信息科技股份有限公司 | Node server, service side and configuration file updating method thereof and updating control method |
| CN106559263A (en) * | 2016-11-17 | 2017-04-05 | 杭州沃趣科技股份有限公司 | A kind of improved distributed consensus algorithm |
| CN108268314A (en) * | 2016-12-31 | 2018-07-10 | 北京亿阳信通科技有限公司 | A kind of method of multithreading task concurrent processing |
| CN106685724A (en) * | 2017-01-10 | 2017-05-17 | 网宿科技股份有限公司 | Node-server management method and device based on election and system |
| CN106685724B (en) * | 2017-01-10 | 2019-11-29 | 网宿科技股份有限公司 | Node server management method based on election, apparatus and system |
| CN107845013A (en) * | 2017-09-25 | 2018-03-27 | 北京科东电力控制***有限责任公司 | A kind of electric power transaction platform distributed application services calling processing method |
| CN109615554A (en) * | 2018-12-06 | 2019-04-12 | 苏州市伽顿服饰有限公司 | Synchrodata system and its operating procedure, creation method based on intelligence manufacture |
| CN109615554B (en) * | 2018-12-06 | 2022-08-02 | 苏州市伽顿服饰有限公司 | Synchronous data system based on intelligent manufacturing and operation method and synchronization method thereof |
| CN111866048B (en) * | 2019-04-30 | 2022-07-01 | 中移(苏州)软件技术有限公司 | Management method, agent equipment, management equipment, main server and system |
| CN111866048A (en) * | 2019-04-30 | 2020-10-30 | 中移(苏州)软件技术有限公司 | Management method, agent equipment, management equipment, main server and system |
| CN111431999A (en) * | 2020-03-23 | 2020-07-17 | 杭州趣维科技有限公司 | Cloud function distributed system based on Paxos algorithm |
| CN111431999B (en) * | 2020-03-23 | 2022-11-25 | 杭州小影创新科技股份有限公司 | Cloud function distributed system based on Paxos algorithm |
| CN113518116B (en) * | 2021-05-18 | 2022-04-01 | 广州泳泳信息科技有限公司 | Leader server election method and device based on Fast Paxos algorithm |
| CN113518116A (en) * | 2021-05-18 | 2021-10-19 | 广州泳泳信息科技有限公司 | Leader server election method and device based on Fast Paxos algorithm |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN105208090A (en) | Zookeeper-based Leader selection method | |
| US10148527B2 (en) | Dynamic network component placement | |
| JP2019200580A (en) | Decentralized ledger system, decentralized ledger subsystem, and decentralized ledger node | |
| CN104011701A (en) | Content delivery network | |
| TW201907324A (en) | Decentralized search and index update method, system, server and computer equipment | |
| CN104092770A (en) | Inner-enterprise address book management method and system based on cloud computing | |
| CN112995273B (en) | Network call-through scheme generation method and device, computer equipment and storage medium | |
| CN103607424A (en) | Server connection method and server system | |
| CN107203429A (en) | A kind of method and device that distributed task scheduling is loaded based on distributed lock | |
| CN103685535A (en) | Interface design of cloud database system for large-scale distributed heterogeneous data treatment | |
| CN102868550A (en) | Total network flow scheduler and method for querying domain name resolution record by using total network flow scheduler | |
| CN109525590A (en) | The transmission method and device of data packet | |
| CN106713353A (en) | Intelligent seamless aggregation method and system for geographic information service | |
| CN115086330A (en) | Cross-cluster load balancing system | |
| CN102929628B (en) | Service framework supporting multi-internet service center construction and operation | |
| CN111181915A (en) | Configuration method and device of sharing permission, storage medium and electronic device | |
| CN115803736A (en) | File generation method and device in Internet of things, computer equipment and storage medium | |
| CN104509028B (en) | The method and device of personal information is updated in a communications system | |
| CN102932185A (en) | Server user management system | |
| CN115017185A (en) | Data processing method, device and storage medium | |
| JP2015132972A (en) | Data relocation system | |
| CN114896006B (en) | Page menu creation method and device, storage medium and electronic device | |
| CN107888655A (en) | A kind of directory service data management method and system | |
| US11966770B2 (en) | Collaboration across isolated virtual environments | |
| CN115168366B (en) | Data processing method, data processing device, electronic equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20151230 |
|
| RJ01 | Rejection of invention patent application after publication |