WO2009117946A1 - Procédé de réalisation de serveurs de répartition principal - de secours et serveur de répartition - Google Patents

Procédé de réalisation de serveurs de répartition principal - de secours et serveur de répartition Download PDF

Info

Publication number
WO2009117946A1
WO2009117946A1 PCT/CN2009/070973 CN2009070973W WO2009117946A1 WO 2009117946 A1 WO2009117946 A1 WO 2009117946A1 CN 2009070973 W CN2009070973 W CN 2009070973W WO 2009117946 A1 WO2009117946 A1 WO 2009117946A1
Authority
WO
WIPO (PCT)
Prior art keywords
client
scheduling server
scheduling
new
topology relationship
Prior art date
Application number
PCT/CN2009/070973
Other languages
English (en)
Chinese (zh)
Inventor
兑继英
曹彦东
李耀辉
Original Assignee
华为技术有限公司
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 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2009117946A1 publication Critical patent/WO2009117946A1/fr

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

Definitions

  • the present invention relates to communication technologies, and in particular, to a master-slave implementation technology of a scheduling server and a scheduling service technology.
  • Each client receives data directly from the application server.
  • the application server needs to transfer a large amount of data to the client.
  • P2P peer-to-peer
  • the client can not only obtain data from the application server, but after other clients obtain the same data, the client can also obtain data from the other client, so that the client can alleviate the data.
  • P2P topology management can be divided into centralized topology management and distributed topology management.
  • the scheduling server specifies the data transmission relationship between the clients; for distributed topology management, the scheduling server provides a client with a set of candidate clients, and the client and the client Negotiate to establish a data transmission relationship.
  • the scheduling server needs to save the data transmission relationship between the clients. It can be said that the scheduling server plays an extremely important role in the centralized topology management technology. If the scheduling server fails, it will The client cannot join the P2P topology relationship. Clients that have joined the P2P topology relationship cannot adjust the topology relationship when needed. In order to avoid the negative consequences of the scheduling server due to failures, the scheduling server needs to use the redundant backup mechanism, that is, deploy two or more scheduling servers. When one of the scheduling servers fails, the other scheduling servers also You can continue to provide services to clients.
  • the traditional redundant backup mechanism includes the following three implementation methods: 1. Redundant backup of shared storage
  • the P2P topology relationship data is saved to a persistent storage device, and each scheduling server can obtain P2P topology relationship data from the persistent storage device when needed. For example, when the primary scheduling server fails, other scheduling servers can obtain P2P topology relationship data from the persistent storage device as the primary scheduling server, and continue to maintain the P2P topology relationship based on the original P2P topology relationship.
  • the primary scheduling server transmits the P2P topology relationship data to all the standby scheduling servers in real time.
  • the standby scheduling server bases on the original P2P topology relationship based on the data obtained by the real-time synchronization. Maintain P2P topology relationships.
  • the inventors have carefully analyzed and found that: Due to the large amount of data of the P2P topology relationship, the network transmission overhead is also large, to support 100,000 online clients, Each client uses 10 bytes as an example. In order to transmit P2P topology data, a transmission space of 1 Mbyte is required. In addition, in order to ensure the consistency of P2P topology data, in the synchronization process, the main scheduling server You cannot modify the topology. You must wait for the synchronization to complete before you can continue to provide scheduling functions for the client. This seriously affects the performance of the scheduling server.
  • the primary scheduling server sends only the modified part of the P2P topology relationship data to the standby scheduling server each time the P2P topology relationship is modified.
  • the inventors have carefully analyzed and found that: This method is very complicated to implement, and will increase the probability of software errors. Since the P2P topology data is interrelated, one If the local error occurs, the entire P2P topology relationship may be unavailable. Secondly, in some cases, the P2P topology relationship data needs to be completely synchronized. For example, in the case of a failure of the standby scheduling server, the primary scheduling server needs to be prepared. After the scheduling server is restored, the P2P topology relationship data is synchronized to the standby scheduling server at one time; sometimes, the primary scheduling server You can also save all the modified data.
  • the standby scheduling server After the standby server is restored, all the modified data is synchronized to the standby scheduling server. However, if the standby scheduling server recovers too long, the accumulated modified data may exceed the one-time. The amount of data being synchronized is even greater than the maximum space available to the primary dispatch server.
  • the technical problem to be solved by the embodiments of the present invention is to provide a master/slave implementation method of a scheduling server, a standby scheduling server, a scheduling server system, a method for providing a scheduling service, and a scheduling server, which are used to achieve the purpose of redundancy backup of the scheduling server. To solve the defects of the above several redundant backup mechanisms.
  • an embodiment of the present invention provides a method for implementing a master/slave of a scheduling server, including: the standby scheduling server determines whether the primary scheduling server can provide a scheduling service for the client; if the primary scheduling server cannot provide a scheduling service for the client The standby scheduling server provides the scheduling service for the client by using the new P2P topology relationship without obtaining the P2P topology relationship data maintained by the primary scheduling server.
  • the embodiment of the present invention further provides a scheduling server, including: a first detecting unit, configured to detect whether the primary scheduling server can provide a scheduling service for the client; and a scheduling service providing unit, configured to: if the first detecting unit determines the primary scheduling server If the scheduling service cannot be provided for the client, the scheduling service is provided to the client by using the new P2P topology relationship without obtaining the P2P topology relationship data maintained by the primary scheduling server.
  • a scheduling server including: a first detecting unit, configured to detect whether the primary scheduling server can provide a scheduling service for the client; and a scheduling service providing unit, configured to: if the first detecting unit determines the primary scheduling server If the scheduling service cannot be provided for the client, the scheduling service is provided to the client by using the new P2P topology relationship without obtaining the P2P topology relationship data maintained by the primary scheduling server.
  • the embodiment of the present invention further provides a scheduling server system, including: a primary scheduling server, configured to provide a scheduling service for a client; at least one standby scheduling server, when the primary scheduling server cannot provide a scheduling service for the client, where A standby scheduling server provides scheduling services for clients by using a new P2P topology relationship without obtaining P2P topology data maintained by the primary scheduling server.
  • the embodiment of the present invention further provides a method for a scheduling server to provide a scheduling service, including: when the scheduling server is re-working, determining whether the P2P topology relationship data originally maintained by the scheduling server can be obtained; if not, the scheduling server Provide scheduling services for clients using new P2P topology relationships.
  • the embodiment of the present invention further provides a scheduling server, including: a determining unit, configured to determine whether the originally maintained P2P topology relationship data can be obtained when the scheduling server is re-working; and a scheduling service providing unit, configured to After the determining unit determines that the originally maintained P2P topology relationship data cannot be obtained, the new P2P topology relationship is used to provide a scheduling service for the client.
  • the embodiment of the present invention further provides a method for a scheduling server to provide a scheduling service, including: the scheduling server performs message interaction with a client; if the client needs to join a P2P topology relationship currently maintained by the scheduling server, The dispatch server provides information for identifying the client to the client.
  • the embodiment of the present invention further provides a scheduling server, including: a message interaction unit, configured to perform message interaction with a client; and an information providing unit, configured to: if the client needs to join a P2P topology relationship currently maintained by the scheduling server And providing, by the scheduling server, information for identifying the client to the client.
  • a scheduling server including: a message interaction unit, configured to perform message interaction with a client; and an information providing unit, configured to: if the client needs to join a P2P topology relationship currently maintained by the scheduling server And providing, by the scheduling server, information for identifying the client to the client.
  • the standby calling server does not need to obtain the P2P topology relationship data maintained by the primary scheduling server.
  • the standby calling server does not need to store the primary scheduling server. Maintain P2P topology relationship data.
  • the standby server cannot maintain the P2P topology relationship maintained by the primary scheduling server, it can still ensure that the upper and lower nodes in the P2P topology relationship transmit data normally, and one of the nodes needs to join the P2P maintained by the standby calling server. In the topology relationship, you only need to add this node to the P2P topology relationship maintained by the standby server.
  • the embodiment of the present invention does not require the storage server to store the P2P topology relationship data, which saves the cost.
  • the embodiment of the present invention does not need the primary scheduling server to synchronize the P2P topology relationship data with the standby scheduling server, thereby improving the The reliability of point-to-point data transmission.
  • the scheduling server of the present invention provides the scheduling service
  • the scheduling service can be provided to the client by using the new P2P topology relationship. Therefore, the problem that the scheduling service cannot be provided once the scheduling server cannot obtain the originally maintained P2P topology relationship data is solved.
  • the scheduling server of the present invention provides a scheduling service
  • the information used by the scheduling server to identify the client is provided to the Client, this will ensure that the scheduling server provides scheduling for the client
  • the service it can be determined whether the client is already in the P2P topology relationship maintained by the client, thereby providing a corresponding scheduling service.
  • Figure 1 is a schematic diagram of an existing client/server architecture
  • FIG. 3 is a flowchart of a method for implementing active/standby of a scheduling server according to an embodiment of the present invention
  • FIG. 4 is a schematic structural diagram of a scheduling service system according to an embodiment of the present invention.
  • FIG. 5 is a flowchart of processing when a P2P terminal joins a P2P topology relationship according to an embodiment of the present invention. detailed description
  • the active/standby implementation method of the scheduling server in the embodiment of the present invention includes: Step S301: determining whether the primary scheduling server can provide a scheduling service for the client; Step S302: If the primary scheduling server cannot provide the scheduling service for the client, the primary scheduling server maintenance is not required.
  • the standby scheduling server uses the new P2P topology relationship to provide scheduling services for the client.
  • the new P2P topology relationship is relative to the P2P topology relationship maintained by the primary scheduling server.
  • the new P2P topology relationship used by the standby scheduling server can be used to refer to the P2P topology relationship maintained by the scheduling server.
  • the standby scheduling server starts working but has not yet communicated with any client, only the content server is maintained in the P2P topology relationship. As more clients join the P2P topology maintained by the standby scheduling server, The number of nodes in the P2P topology relationship increases.
  • the standby scheduling server determines whether the primary scheduling server can provide scheduling services for clients can be implemented in a variety of ways. For example, it can be detected whether the primary scheduling server is faulty or overloaded, and if so, it is determined that the primary scheduling server cannot provide scheduling services for the client. For another example, it may be determined whether a message that the primary scheduling server or other network entity issues a failure or overload of the primary scheduling server is received, and if so, it is determined that the primary scheduling server cannot provide a scheduling service for the client.
  • the standby scheduling server uses the new P2P topology relationship to provide scheduling services for clients, which can be implemented in a variety of ways. For example, if the client needs to join a new P2P topology relationship, the client is added to the new P2P topology relationship.
  • the new master scheduling server determines that the client needs to join the new P2P topology relationship.
  • the new primary scheduling server may first determine whether the client is in a new P2P topology relationship, and if not, determine whether the client needs to join a new P2P topology relationship. Determining whether the client is in a new P2P topology relationship can also be implemented in a variety of ways.
  • the new primary scheduling server determines whether the P2P topology version information reported by the client for identifying a new P2P topology relationship and/or the client information used to identify the client is related to the current P2P topology version information and / or the client information assigned to the client is consistent, and if so, the client is determined to be in a new P2P topology relationship, otherwise, the client is determined not to be in a new P2P topology relationship.
  • the new primary scheduling server provides P2P topology version information for identifying a new P2P topology relationship and/or client information for identifying the client to the client with which the message is exchanged, and is checked by the client.
  • the information reported by the client may include information that needs to be added to the P2P topology relationship, information that the upper node is abnormal, request information for replacing the superior node, or information about itself.
  • the self information is, for example, load information of itself, information on whether or not it is in the P2P topology relationship, or information in which P2P topology relationship itself.
  • the following is an example. Assume that the client in the P2P topology relationship maintained by the original primary scheduling server reports the information in the P2P topology relationship maintained by the original primary scheduling server but has a heavy load on its own, so the new primary scheduling server can report it according to its The information determines that the client should be added to the new P2P topology relationship to reduce the load of the client. Of course, since the new primary scheduling server does not obtain the P2P topology relationship maintained by the original primary scheduling server before, Data, so the new master dispatch server treats the client as a new client.
  • the information reported by the client may also include P2P topology version information for identifying a new P2P topology relationship and/or client information for identifying the client.
  • the P2P topology version information may be an identifier, which is called a P2P topology.
  • the version number, the client information can also be an identifier, called the client identifier.
  • the new primary scheduling server can identify the client using P2P topology version information and/or client information. In this case, if the client reports the P2P topology version information and/or the client information, the new primary scheduling server can be based on the P2P topology version information and/or the client. End information, determine whether the client is in a new P2P topology relationship, and if not, determine whether the client needs to join a new P2P topology relationship.
  • the new primary scheduling server determines that the client needs to join the new P2P topology relationship, it can specify the superior node for the client. In this way, the client can obtain P2P data from the superior node.
  • the P2P topology version information for identifying the P2P topology relationship maintained by the new primary scheduling server and/or the client information for identifying the client may also be provided to the client at the same time as or after the client is designated with the upper node. It should be noted that the P2P topology version information and the client information can be integrated into one type of information, that is, when the P2P topology version information and the client information are provided to the client, only one type of information can be provided. The information includes both the content of the P2P topology version information and the content of the client information.
  • the interactive message can carry P2P topology version information and/or client information each time it interacts with the client.
  • the client information can also be reported by the client without the need for a new primary dispatch server to provide client information. For example, if the client needs to join the new P2P topology relationship, it can record the client information generated and reported by the client to identify the client.
  • the client information can be recorded.
  • the information of the client here is not limited to the client information used to identify the client, but also refers to other types of client-related information.
  • Another implementation manner in which the standby scheduling server uses the new P2P topology relationship to provide the scheduling service for the client is that if the client in the P2P topology relationship maintained by the original primary scheduling server does not need to join the new P2P topology relationship, The client in the P2P topology relationship maintained by the original primary scheduling server still obtains P2P data in the P2P topology relationship maintained by the original primary scheduling server.
  • determining whether the client in the P2P topology relationship maintained by the original primary scheduling server does not need to join the new P2P topology relationship you need to determine whether the client in the P2P topology relationship maintained by the original primary scheduling server needs to join the new P2P topology relationship.
  • it can be implemented in a variety of ways.
  • One of the methods is: obtaining information reported by the client in the P2P topology relationship maintained by the original primary scheduling server; determining, according to the information, whether the client in the P2P topology relationship maintained by the original primary scheduling server needs to join a new one. P2P topology relationship.
  • Another implementation manner in which the standby scheduling server uses the new P2P topology relationship to provide the scheduling service for the client is that if the client that is originally in a P2P topology relationship needs to be added to the new P2P topology relationship, the indication may be indicated.
  • the client quits after the specified time arrives The original P2P topology relationship. For example, the client can be instructed to quit the original P2P topology relationship after 30 seconds. After 30 seconds, the client exits the original P2P topology relationship and joins the P2P topology relationship maintained by the new primary scheduling server.
  • the foregoing method may be implemented by multiple forms of devices, where the scheduling server includes: a first detecting unit, configured to detect whether the primary scheduling server can provide a scheduling service for the client; and a scheduling service providing unit, if the first The detecting unit determines that the primary scheduling server cannot provide the scheduling service for the client, and provides the scheduling service for the client by using the new P2P topology relationship without obtaining the P2P topology relationship data maintained by the primary scheduling server.
  • a first detecting unit configured to detect whether the primary scheduling server can provide a scheduling service for the client
  • a scheduling service providing unit if the first The detecting unit determines that the primary scheduling server cannot provide the scheduling service for the client, and provides the scheduling service for the client by using the new P2P topology relationship without obtaining the P2P topology relationship data maintained by the primary scheduling server.
  • the scheduling service providing unit includes: a second detecting unit, configured to detect whether the client needs to join a new P2P topology relationship; and a P2P topology relationship processing unit, configured to: if the second detecting unit detects that the client needs to join the new P2P In the topology relationship, the client is added to the new P2P topology relationship.
  • the second detecting unit may include: an information obtaining unit, configured to obtain information reported by the client; and a determining unit, configured to determine, according to the information, whether the client needs to join a new P2P topology relationship.
  • the scheduling server may further include: an information recording unit, configured to record the information of the client if the second detecting unit detects that the client needs to join the new P2P topology relationship.
  • the present invention further provides a scheduling server system, including: a primary scheduling server, configured to provide a scheduling service for a client; at least one standby scheduling server, when the primary scheduling server cannot be a client When the scheduling service is provided, one of the standby scheduling servers provides the scheduling service for the client by using the new P2P topology relationship without obtaining the P2P topology relationship data maintained by the primary scheduling server.
  • a primary scheduling server configured to provide a scheduling service for a client
  • at least one standby scheduling server when the primary scheduling server cannot be a client
  • one of the standby scheduling servers provides the scheduling service for the client by using the new P2P topology relationship without obtaining the P2P topology relationship data maintained by the primary scheduling server.
  • the scheduling server system may further include a message forwarding device, configured to forward a message between the client and a scheduling server capable of providing a scheduling service for the client, where the primary scheduling server cannot provide a scheduling service for the client, one of the When the standby scheduling server provides the scheduling service for the client, the message forwarding device forwards the message between the standby scheduling server and the client that provides the scheduling service for the client.
  • the message forwarding device may be a device such as a switch or a separate device independent of the switch.
  • the standby scheduling server mentioned above may refer not only to the standby scheduling server of the primary scheduling server, but also to the scheduling server that is maintaining other P2P topology relationships, or the scheduling relationship of the scheduling server. They are all relative.
  • the embodiment of the present invention further provides a method for the scheduling server to provide the scheduling service, including: determining whether the original maintained P2P topology relationship data can be obtained when re-working; if not, using the new P2P topology relationship as the client Provide scheduling services.
  • Re-work can mean that the scheduling server has already provided the scheduling service for the client, but the scheduling server has an abnormal phenomenon such as a crash or shutdown due to some or some reasons, so that the scheduling server can no longer provide the scheduling service, and the scheduling server restarts.
  • the scheduling service is restarted.
  • the scheduling server does not save the P2P topology relationship data until the scheduling server cannot continue to provide the scheduling service.
  • the original cannot be obtained.
  • Maintain P2P topology relationship data The new P2P topology relationship is relative to the P2P topology relationship originally maintained by the dispatch server.
  • Using the new P2P topology to provide scheduling services to clients can be implemented in a variety of ways. For example, if the client needs to join a new P2P topology relationship, the client can be added to the new P2P topology relationship.
  • Determining whether a client needs to join a new P2P topology relationship can also be implemented in a variety of ways. For example, obtaining information reported by the client; determining, according to the information, whether the client needs to join a new P2P topology relationship.
  • Determining whether the client is in a new P2P topology relationship can also be implemented in a variety of ways. For example, determining whether the P2P topology version information used to identify the new P2P topology relationship on the client and/or the client information used to identify the client is related to the current P2P topology version information and/or allocation. The client information to the client is consistent, and if so, the client is determined to be in a new P2P topology relationship, otherwise, the client is determined not to be in a new P2P topology relationship. For another example, a client that performs message interaction with the dispatch server provides a P2P extension for identifying a new primary dispatch server maintenance.
  • P2P topology version information of the Pu relationship and/or client information for identifying the client the client checking whether it is in a new P2P topology relationship; if obtaining the client reported by the client The information in the new P2P topology relationship is determined to be in the new P2P topology relationship; if the information reported by the client is not in the new P2P topology relationship, It is determined that the client is not in a new P2P topology relationship.
  • Another way to use the new P2P topology relationship to provide scheduling services for clients is to maintain the P2P topology if the clients in the original P2P topology relationship do not need to join the new P2P topology relationship. The client in the relationship still obtains P2P data in the originally maintained P2P topology relationship.
  • a method for determining whether a client in the P2P topology relationship that is to be maintained needs to be added to a new P2P topology relationship is obtained by obtaining information reported by the client in the originally maintained P2P topology relationship; Whether the client in the original maintained P2P topology needs to join the new P2P topology relationship.
  • the foregoing method embodiment may be implemented by multiple forms of devices, and one of the scheduling servers includes: a determining unit, configured to determine whether the originally maintained P2P topology relationship data can be obtained when re-working; the scheduling service providing unit, After the determining unit determines that the originally maintained P2P topology relationship data cannot be obtained, the new P2P topology relationship is used to provide a scheduling service for the client.
  • a determining unit configured to determine whether the originally maintained P2P topology relationship data can be obtained when re-working
  • the scheduling service providing unit After the determining unit determines that the originally maintained P2P topology relationship data cannot be obtained, the new P2P topology relationship is used to provide a scheduling service for the client.
  • the scheduling service providing unit may include: a detecting unit, configured to detect whether the client needs to join a new P2P topology relationship; and a P2P topology relationship processing unit, configured to: if the detecting unit detects that the client needs to join a new P2P extension In the Park relationship, the client is added to the new P2P topology relationship.
  • the detecting unit may include: an information obtaining unit, configured to obtain information reported by the client; and a determining unit, configured to determine, according to the information, whether the client needs to join a new P2P topology relationship.
  • the embodiment of the present invention further provides a method for a scheduling server to provide a scheduling service, including: performing message interaction with a client; if the client needs to join a P2P topology relationship currently maintained by the scheduling server, the scheduling is performed.
  • Information for the server to identify the client is provided to the client. After the information that the scheduling server uses to identify the client is provided to the client, all or part of the messages sent by the client may be carried by the scheduling server to identify the information of the client.
  • the scheduling server After the scheduling server is configured to identify that the information of the client is provided to the client, if the message interaction with the client is performed again, the scheduling server may be used again to identify the information provided by the client.
  • the client checks whether it is in a new P2P topology relationship; if the client reports the information in the new P2P topology relationship, The client is in the new P2P topology relationship; if the information reported by the client is not in the new P2P topology relationship, it is determined that the client is not in the new P2P topology relationship.
  • the scheduling server is configured to identify that the information of the client is provided to the client, if the message is exchanged with the client again, the scheduling server is used according to the message carried in the message reported by the client. Identifying the information of the client to determine whether the client is in a new P2P topology relationship.
  • the information for identifying the client includes P2P topology version information of the P2P topology relationship currently maintained by the scheduling server and/or client information for identifying the client is provided to the client.
  • one of the scheduling servers may include: a message interaction unit, configured to perform message interaction with the client; and an information providing unit, configured to perform current maintenance if the client needs to join the scheduling server In the P2P topology relationship, the information used by the scheduling server to identify the client is provided to the client.
  • the scheduling server 1, the scheduling server 2, and the message forwarding device form a scheduling server system, and interact with the P2P terminal (ie, the client mentioned above).
  • the P2P terminal ie, the client mentioned above.
  • the standby dispatching server needs to monitor whether the primary dispatching server is invalid. If the standby scheduling server finds that the primary scheduling server is invalid, the standby scheduling server needs to act as the primary scheduling server to interact with the P2P terminal. After the original primary scheduling server is restored, it can serve as the standby scheduling server.
  • the P2P terminal it interacts with the scheduling server device instead of the scheduling server 1 and the scheduling server 2.
  • Each scheduling server includes a terminal request processor, a service side terminal topology manager, a terminal topology unit, a terminal topology version number manager, and a monitoring unit.
  • the terminal request processor is responsible for receiving and processing the request of the P2P terminal
  • the service side terminal topology manager is responsible for querying and updating the topology of the P2P terminal
  • the terminal topology unit is responsible for saving the topology of the P2P terminal, and managing the terminal topology version number.
  • the device is responsible for maintaining the current topology version number of the P2P terminal (that is, the P2P topology version information mentioned above).
  • the monitoring unit is responsible for detecting whether the peer end is invalid, triggering the active/standby switchover, and performing data synchronization between the active and standby dispatch servers.
  • the synchronized data refers to a small amount of data such as configuration parameters, and does not include P2P topology data of a large amount of data.
  • the P2P terminal includes a terminal side topology manager, a terminal identification unit, and a terminal topology version number manager.
  • the terminal side topology manager is responsible for interacting with the scheduling server device to update the superior node information.
  • Each P2P terminal has a unique terminal identifier (i.e., the client information mentioned above for identifying the client), and the terminal identification unit is responsible for saving the terminal identifier.
  • the terminal topology version number unit is responsible for saving the terminal topology version number.
  • the terminal topology version number manager When each scheduling server is started, the terminal topology version number manager needs to update the terminal topology version number to identify the newly created P2P topology relationship after the startup. Each time a new topology version number is generated, it must be ensured that the new topology version number does not overlap with all the topology version numbers used by the active and standby scheduling servers for a period of time.
  • a simple implementation is that The time (which can be accurate to the second) is combined with the server's NIC address as the topology version number.
  • Step S501 The P2P terminal sends a request for joining the P2P topology relationship to the scheduling server device, where the request includes information of the P2P terminal, for example, information such as an IP address, a network card address, and an uplink and downlink bandwidth of the P2P terminal.
  • information of the P2P terminal for example, information such as an IP address, a network card address, and an uplink and downlink bandwidth of the P2P terminal.
  • Step S502 After receiving the request, the message forwarding device in the scheduling server device forwards the request to the main scheduling server.
  • Step S503 After receiving the request, the terminal of the primary scheduling server allocates a unique terminal identifier to the P2P terminal.
  • Step S504 The terminal requests the processor to invoke the service side terminal topology manager, and adds the P2P terminal to the P2P topology relationship.
  • Step S505 The service side terminal topology manager records the information of the P2P terminal, and specifies the upper node for the P2P terminal according to the topology management policy.
  • Step S506 The terminal requesting processor returns the topology information returned by the service side terminal topology manager and the topology version number assigned to the P2P terminal to the P2P terminal.
  • Step S507 After the P2P terminal receives the information returned by the scheduling server device, the terminal side topology manager parses the information, saves the terminal identifier in the information in the terminal identification unit, and saves the terminal topology version number in the information in the terminal.
  • the topology version number unit after which, follow the instructions in the message to connect to the superior node and obtain data from the superior node.
  • the topology update request may be sent to the scheduling server device. For details, refer to steps S508-S510 of FIG.
  • Step S508 The terminal side topology manager sends a topology update request to the scheduling server device.
  • Step S510 The service side terminal topology manager records the updated topology into the terminal topology component.
  • a P2P terminal After a P2P terminal joins a P2P topology relationship, it may need to interact with the scheduling server again for various reasons. For example, the P2P terminal finds that the upper node fails and needs to connect to the new upper node; the P2P terminal needs to provide its own load condition to the scheduling server, so that the scheduling server decides whether to use the P2P terminal as the upper node of the other P2P terminal.
  • the P2P terminal joins the P2P topology relationship, each time the message is sent to the scheduling server, the message can carry the terminal topology version number.
  • the standby scheduling server is started, and the new primary scheduling server provides scheduling services for the P2P terminal.
  • the new primary scheduling server is started, the new terminal topology version number is used as the current terminal topology version number.
  • the original P2P topology relationship can continue to exist, that is, the P2P topology relationship does not need to be completely adjusted, only when P2P is used.
  • the P2P terminal is added to the P2P topology relationship maintained by the new primary scheduling server.
  • the new primary scheduling server may use the current terminal topology version number and the terminal topology carried in the message sent by the P2P terminal. The version number is compared to determine whether the P2P topology relationship of the P2P terminal is the P2P topology relationship currently maintained by the new primary scheduling server. If yes, the P2P terminal is added to the P2P topology relationship maintained by the new primary scheduling server. Otherwise, According to the content of the request and other factors, the following different treatments can be performed:
  • the new primary scheduling server can ignore the request, and the P2P terminal can continue to rely on the original P2P topology relationship to obtain data.
  • the P2P terminal may have replaced the upper node by itself, and the new primary scheduling server may also ignore the request, so that the P2P terminal maintains the P2P extension itself. Park relationship;
  • the new primary scheduling server can ignore the request
  • the new primary scheduling server adds the P2P terminal to a P2P topology relationship maintained by the new primary scheduling server, and returns a new terminal topology version number to the P2P terminal.
  • the P2P terminal updates the saved terminal topology version number
  • the new primary scheduling server can return the terminal topology version number error message to the P2P terminal. After receiving the error message, the P2P terminal disconnects all the other terminals. Connect, re-request to join the new P2P topology relationship. Since the exit of one P2P terminal may cause its lower-level terminal to exit, and the exit of its lower-level terminal may cause more P2P terminal to exit, this chain-locking reaction may cause the new primary dispatching server to be overloaded for a period of time. run.
  • the P2P terminal can wait for a period of time before exiting the original P2P topology relationship, then exit the original P2P topology relationship, and then add a new P2P topology relationship, thus avoiding a large number of
  • the P2P terminal centrally sends a request to the new primary dispatch server in a short time, reducing the burden on the new primary dispatch server.
  • the terminal topology version number and the terminal identifier may not be mutually independent identifiers, but may be integrated into one identifier.
  • the terminal topology version number may be part of the terminal identifier, and the new master scheduling server is a P2P terminal.
  • the terminal identifier is assigned, the provided terminal identifier includes the terminal topology version number.
  • the terminal identifier may be specified by the scheduling server, or the P2P terminal may itself identify a terminal identifier that can uniquely identify itself, such as a network card address of the P2P terminal.
  • the new primary dispatch server only needs to discover the P2P terminal in any case.
  • the P2P topology relationship is not the P2P topology relationship maintained by the new primary scheduling server, and the P2P terminal may be required to rejoin the P2P topology relationship.
  • the new primary scheduling server may identify whether the P2P terminal is in the P2P topology relationship maintained by the new primary scheduling server; and the scheduling server actively sends the message carrying the current terminal topology version number to the P2P terminal. In this case, it is also possible for the P2P terminal to check whether it is in the P2P topology relationship maintained by the new primary dispatch server.
  • the message sent by the P2P terminal to the new primary scheduling server may not carry the terminal. Topology version number.
  • the standby scheduling server can refer to a scheduling server that does not maintain any P2P topology relationship, that is, a dedicated standby scheduling server that is the primary scheduling server, or that is maintaining other P2P extensions.
  • the scheduling server of the Park relationship that is, the dedicated scheduling server that is not the primary scheduling server, but the primary scheduling server that maintains other P2P topology relationships.
  • the scheduling server that maintains other P2P topology relationships is maintained. It is equivalent to the new primary scheduling server, which provides scheduling services for P2P terminals in the P2P topology relationship maintained by the original primary scheduling server.
  • embodiments of the scheduling server providing scheduling services can be applied to a wide variety of scenarios. For example, when the primary dispatch server fails and the standby dispatch server starts, the standby dispatch server can use this embodiment. For example, when a scheduling server needs to re-establish a P2P topology relationship due to the loss of the originally maintained P2P topology, etc., such an embodiment can also be used.
  • the storage medium may be a magnetic disk, an optical disk, a read-only memory (ROM), or a random access memory (RAM).

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer And Data Communications (AREA)

Abstract

L'invention porte sur un procédé de réalisation de serveurs de répartition principal – de secours, sur un serveur de répartition, sur un système de serveur de répartition et sur un procédé pour fournir un service de répartition par un serveur de répartition, le procédé de réalisation de serveurs de répartition principal – de secours comprenant les étapes suivantes : un serveur de répartition de secours détermine si un serveur de répartition principal peut fournir ou non le service de répartition pour un client, si le serveur de répartition principal ne peut pas fournir le service de répartition pour le client, le serveur de répartition de secours fournit le service de répartition pour le client à l'aide d'une nouvelle relation topologique poste à poste (P2P) sous la condition ne nécessitant pas d'obtenir les données de relation topologique P2P conservées par le serveur de répartition principal.
PCT/CN2009/070973 2008-03-28 2009-03-24 Procédé de réalisation de serveurs de répartition principal - de secours et serveur de répartition WO2009117946A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN200810088808.4 2008-03-28
CN 200810088808 CN101262369B (zh) 2008-03-28 2008-03-28 调度服务器的主备实现方法及调度服务器

Publications (1)

Publication Number Publication Date
WO2009117946A1 true WO2009117946A1 (fr) 2009-10-01

Family

ID=39962594

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2009/070973 WO2009117946A1 (fr) 2008-03-28 2009-03-24 Procédé de réalisation de serveurs de répartition principal - de secours et serveur de répartition

Country Status (2)

Country Link
CN (1) CN101262369B (fr)
WO (1) WO2009117946A1 (fr)

Families Citing this family (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101262369B (zh) * 2008-03-28 2011-05-11 华为技术有限公司 调度服务器的主备实现方法及调度服务器
CN103124278A (zh) * 2011-11-21 2013-05-29 苏州达联信息科技有限公司 一种视频分发网络全局服务器主备同步消息的实现方法及处理装置
CN102427412A (zh) * 2011-12-31 2012-04-25 网宿科技股份有限公司 基于内容分发网络的零延时主备源灾备切换方法和系统
CN103209136A (zh) * 2012-01-11 2013-07-17 中兴通讯股份有限公司 一种网络负荷控制方法及登记服务器
CN104731702B (zh) * 2013-12-23 2017-12-26 展讯通信（上海）有限公司 测试系统及其服务端
CN104734902B (zh) * 2013-12-23 2018-03-23 展讯通信（上海）有限公司 测试系统及其服务端
CN103702226A (zh) * 2013-12-31 2014-04-02 广州华多网络科技有限公司 直播类客户端频道信息的展示方法与装置
CN110703985B (zh) 2016-10-25 2021-05-18 华为技术有限公司 一种数据同步方法及带外管理设备
CN107197036A (zh) * 2017-06-22 2017-09-22 广东网金控股股份有限公司 一种基于区块链的信息一致处理方法及终端
CN112448990B (zh) * 2019-09-05 2023-12-05 北京京东尚科信息技术有限公司 一种保障服务可用性的方法、装置、系统和存储介质

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1604569A (zh) * 2004-10-29 2005-04-06 清华大学 一种鲁棒的基于点对点的流调度方法
US20050283529A1 (en) * 2004-06-22 2005-12-22 Wan-Yen Hsu Method and apparatus for providing redundant connection services
US20070220305A1 (en) * 2006-03-20 2007-09-20 Nec Corporation Multiplex server system and server multiplexing method
CN101060391A (zh) * 2007-05-16 2007-10-24 华为技术有限公司 主备服务器切换方法及系统及主用服务器、备用服务器
CN101068186A (zh) * 2007-06-05 2007-11-07 华为技术有限公司 一种客户端节点网络拓扑构造方法及流媒体分发系统
CN101262369A (zh) * 2008-03-28 2008-09-10 华为技术有限公司 调度服务器的主备实现方法及调度服务器

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20050283529A1 (en) * 2004-06-22 2005-12-22 Wan-Yen Hsu Method and apparatus for providing redundant connection services
CN1604569A (zh) * 2004-10-29 2005-04-06 清华大学 一种鲁棒的基于点对点的流调度方法
US20070220305A1 (en) * 2006-03-20 2007-09-20 Nec Corporation Multiplex server system and server multiplexing method
CN101060391A (zh) * 2007-05-16 2007-10-24 华为技术有限公司 主备服务器切换方法及系统及主用服务器、备用服务器
CN101068186A (zh) * 2007-06-05 2007-11-07 华为技术有限公司 一种客户端节点网络拓扑构造方法及流媒体分发系统
CN101262369A (zh) * 2008-03-28 2008-09-10 华为技术有限公司 调度服务器的主备实现方法及调度服务器

Also Published As

Publication number Publication date
CN101262369B (zh) 2011-05-11
CN101262369A (zh) 2008-09-10

Similar Documents

Publication Publication Date Title
WO2009117946A1 (fr) Procédé de réalisation de serveurs de répartition principal - de secours et serveur de répartition
US11172023B2 (en) Data synchronization method and system
CN111565229B (zh) 一种基于Redis的通信系统分布式方法
CN111615066B (zh) 一种基于广播的分布式微服务注册及调用方法
JP5863942B2 (ja) ウィットネスサービスの提供
KR100812374B1 (ko) 클러스터 시스템에서 프로토콜 네트워크 장애 관리 시스템및 방법
WO2012174893A1 (fr) Procédé et dispositif de commutation sur la base d'une reprise sur sinistre de deux centres dans un système iptv
JP2004280738A (ja) 代理応答装置
WO2012037787A1 (fr) Procédé et système d'accès et de gestion de terminaux en informatique en nuage
CN112333015B (zh) 媒体数据存储方法、装置、系统、电子设备及存储介质
WO2020024991A1 (fr) Procédé et dispositif d'accès de passerelle de l'internet des objets, et support de stockage
CN111371625A (zh) 一种双机热备的实现方法
WO2019174454A1 (fr) Procédé et dispositif de récupération de liaison, système, support de stockage et dispositif électronique
WO2020057445A1 (fr) Système, procédé et dispositif de communication
CN112671554A (zh) 一种节点故障处理方法及相关装置
US20100082822A1 (en) Technique for realizing high reliability in inter-application communication
US8161147B2 (en) Method of organising servers
KR20140001499A (ko) 고가용성 관리 방법 및 시스템
KR20200072941A (ko) 실시간 오류 감지를 통한 vrrp 기반의 네트워크 장애 대응 방법 및 장치
US10536875B2 (en) System and method for seamless TCP connection handoff
WO2012167710A1 (fr) Procédé et système de sauvegarde de services dans un réseau à nœuds hétérogènes
CN111858193A (zh) 一种实现服务器池服务的方法和系统
KR101401006B1 (ko) 고가용성 시스템에서 소프트웨어 업데이트를 수행하기 위한 방법 및 장치
TWI397296B (zh) 伺服器系統與使用者註冊方法
WO2022037654A1 (fr) Procédé, appareil et système de traitement d'échec de synchronisation temporelle et support de stockage

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 09723723

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 09723723

Country of ref document: EP

Kind code of ref document: A1