CN106603588B - Server node processing method and device - Google Patents

Server node processing method and device Download PDF

Info

Publication number
CN106603588B
CN106603588B CN201510662199.9A CN201510662199A CN106603588B CN 106603588 B CN106603588 B CN 106603588B CN 201510662199 A CN201510662199 A CN 201510662199A CN 106603588 B CN106603588 B CN 106603588B
Authority
CN
China
Prior art keywords
address list
address
addresses
server
intranet
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.)
Active
Application number
CN201510662199.9A
Other languages
Chinese (zh)
Other versions
CN106603588A (en
Inventor
高阳
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Beijing Gridsum Technology Co Ltd
Original Assignee
Beijing Gridsum Technology Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Beijing Gridsum Technology Co Ltd filed Critical Beijing Gridsum Technology Co Ltd
Priority to CN201510662199.9A priority Critical patent/CN106603588B/en
Publication of CN106603588A publication Critical patent/CN106603588A/en
Application granted granted Critical
Publication of CN106603588B publication Critical patent/CN106603588B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

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/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
    • H04L67/1034—Reaction to server failures by a load balancer
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/45—Network directories; Name-to-address mapping
    • H04L61/4505—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols
    • H04L61/4511—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols using domain name system [DNS]
    • 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/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
    • H04L67/1031—Controlling of the operation of servers by a load balancer, e.g. adding or removing servers that serve requests

Abstract

The embodiment of the invention discloses a method and a device for processing a server node, wherein the method comprises the following steps: monitoring the resolution of an intranet DNS server to the SSO intranet domain name, extracting an IP address from a resolution result output by the intranet DNS server, and storing the IP address in a first IP address list; the first IP address list is used for recording IP addresses in an analysis result output by the intranet DNS server in a current monitoring period; responding to the end of the current monitoring period, if the first IP address list is different from the second IP address list, updating the second IP address list arranged in the LVS load balancing server according to the first IP address list; and the second IP address list records the IP addresses of all online servers in the SSO intranet server pool before the current monitoring period. The embodiment of the invention can simplify the online and offline process of the server node, improve the online and offline efficiency of the server node and reduce the operation and maintenance cost.

Description

Server node processing method and device
Technical Field
The present invention relates to communications technologies, and in particular, to a method and an apparatus for processing a server node.
Background
A Single Sign On (SSO) system is a technology in which a user can access all mutually trusted application systems by logging On only once in a plurality of application systems. The SSO includes a mechanism that can map the main login to the login of the same user in other applications, and provides a login verification function for all online products of an enterprise, which is one of the solutions for the currently popular business integration of the enterprise.
When a network user of a public network accesses an enterprise application system adopting the SSO technology, a Hyper Text Transfer Protocol (HTTP) request is sent to a public network Internet Protocol (IP) Address of a server where the application system is located, and the HTTP access request is sent to an SSO intranet server pool consisting of a plurality of intranet servers through a Linux Virtual Server (LVS) load balancing server by the LVS load balancing server according to the recorded IP Address.
In the process of implementing the invention, the inventor finds that, in the prior art, if a certain server (also called a server node or a node) in an SSO intranet server pool breaks down and needs to be offline, the node fault needs to be manually found, and the IP address of the broken node is removed from an LVS load balancing server in a manual mode, so that a network user in a public network cannot access the broken node; after the failed node is recovered, the IP address of the recovery node needs to be added to the LVS load balancing server manually, so that a network user in the public network can continue to access the node. Therefore, this prior art has at least the following problems: for operation and maintenance operation, the offline process of manually discovering node faults and removing the IP addresses of the fault nodes from the LVS load balancing server in a manual mode and the online process of manually adding the IP addresses of the recovery nodes to the LVS load balancing server are complex and lack of quick response; more human resources are occupied, and the operation and maintenance cost is higher.
Disclosure of Invention
The embodiment of the invention aims to solve the technical problem that: the server node processing method and device and the server are provided, so that the online and offline processes of the server node are simplified, the online and offline efficiency of the server node is improved, and the operation and maintenance cost is reduced.
In order to solve the above technical problem, according to an aspect of an embodiment of the present invention, a processing method for a server node is provided, including:
monitoring the analysis of the single sign-on SSO intranet domain name by an intranet domain name analysis DNS server, extracting an IP address from an analysis result output by the intranet DNS server, and storing the IP address in a first IP address list; the first IP address list is used for recording IP addresses in an analysis result output by the intranet DNS server in a current monitoring period;
responding to the end of the current monitoring period, if the first IP address list is different from the second IP address list, updating the second IP address list arranged in the Linux virtual server LVS load balancing server by using the first IP address list; and the second IP address list records the IP addresses of all online servers in the SSO intranet server pool before the current monitoring period.
In a processing method of a server node of another embodiment, the method further includes: in response to the end of the current monitoring period, comparing the IP addresses in the first IP address list with the IP addresses in the second IP address list;
and in response to that the IP address in the first IP address list is different from the IP address in the second IP address list, executing the operation of updating the second IP address list arranged in the LVS load balancing server by using the first IP address list.
In a processing method of a server node of another embodiment, the method further includes:
in response to the end of the current monitoring period, comparing the IP addresses in the first IP address list with the IP addresses in the third IP address list; the third IP address list records the IP addresses of all online servers in the SSO intranet server pool before the current monitoring period;
and responding to the fact that the IP address in the first IP address list is different from the IP address in the third IP address list, and sending the first IP address list so as to update a second IP address list arranged in the LVS load balancing server by using the first IP address list.
In a processing method of a server node of another embodiment, the method further includes:
in response to the fact that the IP address in the first IP address list is different from the IP address in the third IP address list, updating the IP address in the third IP address list to the IP address in the first IP address list;
and in response to the IP addresses in the first IP address list being identical to the IP addresses in the third IP address list, clearing all the IP addresses in the first IP address list.
In a processing method of a server node according to another embodiment, when the current monitoring period is a first monitoring period, the IP addresses recorded in the third IP address list specifically include: in the initial state, the IP addresses of all servers in the SSO intranet server pool.
In a processing method of a server node according to another embodiment, when the current monitoring period is a first monitoring period, the IP addresses recorded in the second IP address list specifically include: in the initial state, the IP addresses of all servers in the SSO intranet server pool.
According to another aspect of the embodiments of the present invention, there is provided a processing apparatus of a server node, including:
the monitoring unit is used for monitoring the analysis of the single sign-on SSO intranet domain name by the intranet domain name analysis DNS server, extracting an IP address from an analysis result output by the intranet DNS server and storing the IP address in a first IP address list; the first IP address list is used for recording IP addresses in an analysis result output by the intranet DNS server in a current monitoring period;
the first updating unit is used for responding to the end of the current monitoring period, and updating a second IP address list arranged in the LVS load balancing server of the Linux virtual server according to the first IP address list if the first IP address list is different from the second IP address list; and the second IP address list records the IP addresses of all online servers in the SSO intranet server pool before the current monitoring period.
In a processing apparatus of a server node according to another embodiment, the apparatus further includes:
the sending unit is used for responding to the end of the current monitoring period and sending the first IP address list to the receiving unit;
the receiving unit is used for receiving the first IP address list sent by the sending unit;
the first updating unit specifically includes:
the comparison module is used for comparing the IP address in the first IP address list received by the receiving unit with the IP address in the second IP address list;
and the updating module is used for responding to the fact that the IP address in the first IP address list is different from the IP address in the second IP address list according to the comparison result of the comparing module, and updating the IP address in the second IP address list into the IP address in the first IP address list.
In a processing apparatus of a server node according to another embodiment, the apparatus further includes:
the comparison unit is used for responding to the end of the current monitoring period and comparing the IP address in the first IP address list with the IP address in the third IP address list; the third IP address list records the IP addresses of all online servers in the SSO intranet server pool before the current monitoring period;
the sending unit is used for responding to the fact that the IP address in the first IP address list is different from the IP address in the third IP address list according to the comparison result of the comparison unit and sending the first IP address list to the receiving unit;
the receiving unit is used for receiving the first IP address list sent by the sending unit;
the first updating unit is specifically configured to update the IP address in the second IP address list to the IP address in the first IP address list received by the receiving unit.
In a processing apparatus of a server node according to another embodiment, the apparatus further includes:
the second updating unit is used for responding to the fact that the IP address in the first IP address list is different from the IP address in the third IP address list according to the comparison result of the comparing unit, and updating the IP address in the third IP address list into the IP address in the first IP address list; and in response to the IP addresses in the first IP address list being identical to the IP addresses in the third IP address list, clearing all the IP addresses in the first IP address list.
Based on the method and the device for processing the server node provided by the above embodiment of the present invention, the inner network DNS server is monitored to resolve the SSO inner network domain name, the IP address in the resolution result output by the inner network DNS server in the current monitoring period is recorded in the first IP address list, and when the current monitoring period ends, the second IP address list set in the LVS load balancing server is updated according to the first IP address list, wherein the second IP address list records the IP addresses of all online servers in the SSO inner network server pool before the current monitoring period. The embodiment of the invention can automatically update the IP address list in the LVS load balancing server according to the IP address analyzed by the internal network DNS, and can automatically finish the operation of removing and adding the server node in the LVS load balancing server without manual operation when the SSO system needs to go off-line or go on-line with a rear-end server node.
The technical solution of the present invention is further described in detail by the accompanying drawings and embodiments.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments of the invention and together with the description, serve to explain the principles of the invention.
The invention will be more clearly understood from the following detailed description, taken with reference to the accompanying drawings, in which:
fig. 1 is a flowchart of an embodiment of a processing method of a server node according to the present invention.
Fig. 2 is a flowchart of another embodiment of a processing method of a server node according to the present invention.
FIG. 3 is a flowchart of a processing method of a server node according to another embodiment of the present invention.
Fig. 4 is a schematic structural diagram of a processing device of a server node according to an embodiment of the present invention.
Fig. 5 is a schematic structural diagram of another embodiment of a processing device of a server node according to the present invention.
Fig. 6 is a schematic structural diagram of a processing device of a server node according to another embodiment of the present invention.
Fig. 7 is a schematic structural diagram of an embodiment of the DNS server of the present invention.
Fig. 8 is a schematic structural diagram of another embodiment of the DNS server of the present invention.
Fig. 9 is a schematic structural diagram of an LVS load balancing server according to an embodiment of the present invention.
Fig. 10 is a schematic structural diagram of another embodiment of the LVS load balancing server according to the present invention.
Detailed Description
Various exemplary embodiments of the present invention will now be described in detail with reference to the accompanying drawings. It should be noted that: the relative arrangement of the components and steps, the numerical expressions and numerical values set forth in these embodiments do not limit the scope of the present invention unless specifically stated otherwise.
Meanwhile, it should be understood that the sizes of the respective portions shown in the drawings are not drawn in an actual proportional relationship for the convenience of description.
The following description of at least one exemplary embodiment is merely illustrative in nature and is in no way intended to limit the invention, its application, or uses.
Techniques, methods, and apparatus known to those of ordinary skill in the relevant art may not be discussed in detail but are intended to be part of the specification where appropriate.
It should be noted that: like reference numbers and letters refer to like items in the following figures, and thus, once an item is defined in one figure, further discussion thereof is not required in subsequent figures.
The SSO system needs to receive requests for both: on one hand, when a network user of a public network accesses an application system of an enterprise, an HTTP request is sent to a public network IP address of a server where the application system is located, and the HTTP access request is sent to an SSO intranet server pool consisting of a plurality of intranet servers through an LVS load balancing server; on the other hand, when a product server in the intranet accesses an Application Programming Interface (API), the product server sends an HTTP access request to the SSO intranet server pool, and the intranet product server is addressed by querying a Domain Name System (DNS) server in the intranet to obtain IP addresses of a plurality of intranet servers. Therefore, in essence, both the network users of the public network and the product servers of the intranet send authentication requests to the intranet server pool of the SSO system, and the difference between the two is in the addressing mode: and the access request of the public network is distributed to the servers in the intranet server pool through the LVS load balancing server, and the access request of the intranet is inquired of IP addresses of all the servers in the intranet server pool through an intranet DNS and then is sent to the servers in the intranet server pool.
As described above, the present inventors found in the course of research that, because the addressing modes of the public network access request and the intranet access request are different, the following problems exist: if a certain server in the SSO intranet server pool breaks down and needs to be offline, two manual operations are needed to complete the offline action of the server node: 1, eliminating the IP address of the fault server node from an LVS load balancing server, so that a network user in a public network cannot access the fault node; and 2, eliminating mapping relation entries used for analyzing the IP address of the fault server node from the intranet DNS server, so that the intranet product server cannot analyze the fault server node. For operation and maintenance, the offline process is too complex and lacks quick response. Due to the architectural particularity, the prior art does not have an effective scheme for fast switching of fault nodes from an online state to an offline state.
Fig. 1 is a flowchart of an embodiment of a processing method of a server node according to the present invention. As shown in fig. 1, the processing method of the server node of the embodiment includes:
and 102, monitoring the resolution of the intranet DNS server to the SSO intranet domain name, extracting an IP address from a resolution result output by the intranet DNS server, and storing the IP address in a first IP address list.
The domain name of the SSO intranet is the domain name of the SSO intranet server pool, and the DNS server resolves the SSO intranet domain name to obtain the IP address of each online server in the SSO intranet server pool. The first IP address list is used for recording IP addresses in analysis results output by the intranet DNS server in the current monitoring period.
For example, in a specific application, a timing process may be started to monitor the resolution of the intranet DNS server on the SSO intranet domain name, and each time the intranet DNS server outputs a resolution result for one resolution request, the timing process may extract an IP address from the resolution result and store the IP address in the first IP address list. The internal network DNS server may store all the contents of each analysis result, for example, in a character string form, and the timer process may extract the IP address in the current monitoring period from the stored analysis result. For example, the character strings in the parsing result may be matched by a regular expression of the IP address, so as to identify the IP address therein.
And 104, responding to the end of the current monitoring period, and updating a second IP address list arranged in the LVS load balancing server according to the first IP address list if the first IP address list is different from the second IP address list.
And the second IP address list records the IP addresses of all online servers in the SSO intranet server pool before the current monitoring period.
Specifically, if the current monitoring period is the first monitoring period, the IP addresses recorded in the second IP address list are specifically: in the initial state, the IP addresses of all servers in the SSO intranet server pool.
In the embodiment of the present invention, in operation 102, the analysis of the SSO intranet domain name by the monitoring intranet DNS server is an operation executed in real time, and in response to that the operation executed after the current monitoring period is finished is an operation periodically executed based on the monitoring period, the operation is triggered to be executed when or after one monitoring period is finished.
Based on the processing method of the server node provided by the above embodiment of the present invention, the inner network DNS server is monitored to resolve the SSO inner network domain name, the IP address in the resolution result output by the inner network DNS server in the current monitoring period is recorded in the first IP address list, and when the current monitoring period ends, the second IP address list set in the LVS load balancing server is updated according to the first IP address list, where the second IP address list records the IP addresses of all online servers in the SSO inner network server pool before the current monitoring period.
The embodiment of the invention can automatically update the IP address list in the LVS load balancing server according to the IP address analyzed by the internal network DNS, and can automatically finish the operation of removing and adding the server node in the LVS load balancing server without manual operation when the SSO system needs to go off-line or go on-line with a rear-end server node, thereby simplifying the process of going on-line and going off-line of the server node, improving the efficiency of going on-line and going off-line of the server node and reducing the operation and maintenance cost.
Based on the embodiments of the invention, the linkage configuration of the LVS load balancing server and the intranet DNS server to the IP addresses of the servers in the SSO intranet server pool is realized, so that the access request distribution strategy configured by the LVS load balancing server and the intranet resolution IP address automatically keep linkage, and when an SSO system needs to go off-line or on-line for one server node, the operations of eliminating and adding the server node of the LVS load balancing server can be automatically completed only by operating the mapping relation entry on the intranet DNS.
In each embodiment of the invention, the duration of the monitoring period can be set according to practical conditions and experience, and the duration of the monitoring period is not easy to be too long, so that the related operations of sending the first IP address list and updating the second IP address list are avoided being carried out unnecessarily and frequently, and network resources and memory resources of the device are saved; the duration of the monitoring period is not too short, so that the intranet DNS server can resolve the IP addresses of all servers in the SSO intranet server pool in one monitoring period. In one specific example, the duration of the monitoring period may be set to 1-5 minutes, for example, and may be adjusted according to requirements.
Fig. 2 is a flowchart of another embodiment of a processing method of a server node according to the present invention. As shown in fig. 2, the processing method of the server node of the embodiment includes:
202, the resolution of the intranet DNS server to the SSO intranet domain name is monitored, and an IP address is extracted from a resolution result output by the intranet DNS server and stored in the first IP address list.
The first IP address list is used for recording IP addresses in analysis results output by the intranet DNS server in the current monitoring period.
204, in response to the end of the current monitoring period, the first list of IP addresses may be transmitted, for example, using a transmitting unit.
At the receiving end, the received IP addresses in the first IP address list and the second IP address list are compared to see if they are the same.
And the second IP address list records the IP addresses of all online servers in the SSO intranet server pool before the current monitoring period.
If the IP address in the first IP address list is different from the IP address in the second IP address list, the method comprises the following steps: there is a difference in the number of IP addresses and/or specific addresses between the two, which means that the resolution of the SSO intranet domain name on the intranet DNS is changed, and the operation of 208 is performed. Otherwise, if the IP address in the first IP address list is identical to the IP address in the second IP address list, the subsequent process of this embodiment is not executed.
And 208, updating the IP address in the second IP address list to the IP address in the first IP address list.
In the processing method of the server node in this embodiment, it may be first compared whether the IP address in the first IP address list is identical to the IP address in the second IP address list, and only when the IP address in the first IP address list is not identical to the IP address in the second IP address list, the IP address in the second IP address list is updated to the IP address in the first IP address list, and when the IP address in the first IP address list is identical to the IP address in the second IP address list, the second IP address list is not updated, thereby avoiding unnecessary operations on the second IP address list.
FIG. 3 is a flowchart of a processing method of a server node according to another embodiment of the present invention. As shown in fig. 3, the processing method of the server node of the embodiment includes:
and 302, monitoring the resolution of the intranet DNS server to the SSO intranet domain name, extracting an IP address from a resolution result output by the intranet DNS server, and storing the IP address in a first IP address list.
The first IP address list is used for recording IP addresses in analysis results output by the intranet DNS server in the current monitoring period.
In response to the end of the current monitoring period, the IP addresses in the first list of IP addresses are compared 304 with the IP addresses in the third list of IP addresses.
And the third IP address list records the IP addresses of all online servers in the SSO intranet server pool before the current monitoring period.
If the current monitoring period is the first monitoring period, the IP addresses recorded in the third IP address list are specifically: in the initial state, the IP addresses of all servers in the SSO intranet server pool.
If the IP address in the first IP address list is different from the IP address in the third IP address list, the method comprises the following steps: there is a difference in the number of IP addresses and/or specific addresses between the two, the operation of 306 is performed. Otherwise, if the IP address in the first IP address list is identical to the IP address in the third IP address list, the subsequent process of this embodiment is not executed.
A first list of IP addresses may be sent 306 using a sending unit.
At the receiving end, the IP addresses in the second IP address list are updated to the IP addresses in the received first IP address list 308.
And the second IP address list records the IP addresses of all online servers in the SSO intranet server pool before the current monitoring period.
In the processing method of the server node in this embodiment, a third IP address list may be set at the sending end, the IP addresses of all online servers in the SSO intranet server pool before the current monitoring period are recorded, when the current monitoring period is over, comparing whether the IP address in the first IP address list is identical to the IP address in the third IP address list, only when the IP address in the first IP address list is not identical to the IP address in the third IP address list, the first list of IP addresses is sent and the IP addresses in the second list of IP addresses are updated accordingly, when the IP address in the first IP address list is identical to the IP address in the third IP address list, the operations of sending the first IP address list and updating the second IP address list are not performed, thereby saving network resources required to transmit the first IP address list and performing unnecessary operations on the second IP address list.
In addition, in another embodiment based on the embodiment shown in fig. 3, according to the comparison result of operation 304, when the IP addresses in the first IP address list are not the same as the IP addresses in the third IP address list, the IP addresses in the third IP address list may be updated to the IP addresses in the first IP address list, so as to achieve timely update of the IP addresses of all online servers in the SSO intranet server pool; when the IP addresses in the first IP address list are identical to the IP addresses in the third IP address list, all the IP addresses in the first IP address list may be cleared, so that the IP addresses in the resolution result output by the intranet DNS server in the next monitoring period are recorded in the first IP address list.
In each embodiment of the present invention, the sending unit may specifically establish a socket (socket) connection with the receiving unit, and send the first IP address list to the receiving unit in a socket communication manner. Correspondingly, the receiving unit may specifically start a daemon process, monitor a socket connection sent from the sending unit, receive the first IP address list sent through the socket connection, call a management command line of the LVS load balancing server in a command line interpreter (shell), update an IP address of an online server node in the SSO intranet server pool recorded in the LVS load balancing server to an IP address in the first IP address list received through the socket connection, and thus, complete linkage between the SSO intranet IP address analyzed on the intranet DNS and the IP address of the server node in the LVS load balancing server.
Fig. 4 is a schematic structural diagram of a processing device of a server node according to an embodiment of the present invention. The processing apparatus of the server node in this embodiment may be used to implement the processing method embodiments of each server node described above in the present invention. As shown in fig. 4, the apparatus of this embodiment includes a monitoring unit 402 and a first updating unit 404. Wherein:
the monitoring unit 402 is configured to monitor resolution of the intranet domain name resolution DNS server on the single sign-on SSO intranet domain name, extract an IP address from a resolution result output by the intranet DNS server, and store the IP address in a first IP address list, where the first IP address list is used to record an IP address in a resolution result output by the intranet DNS server in a current monitoring period.
A first updating unit 404, configured to respond to that the current monitoring period ends, and if the first IP address list is different from the second IP address list, update the second IP address list set in the LVS load balancing server according to the first IP address list. And the second IP address list records the IP addresses of all online servers in the SSO intranet server pool before the current monitoring period.
For example, when the current monitoring period is the first monitoring period, the IP addresses recorded in the second IP address list may specifically be the IP addresses of all servers in the SSO intranet server pool in the initial state.
According to a specific example but not limiting of the embodiment of the present invention, in a specific application, the monitoring unit 402 may be disposed at a DNS server side; the first updating unit 404 may be disposed at the LVS load balancing server side.
Based on the processing device of the server node provided in the above embodiment of the present invention, the inner network DNS server is monitored to resolve the SSO inner network domain name, the IP address in the resolution result output by the inner network DNS server in the current monitoring period is recorded in the first IP address list, and when the current monitoring period ends, the second IP address list set in the LVS load balancing server is updated according to the first IP address list, where the second IP address list records the IP addresses of all online servers in the SSO inner network server pool before the current monitoring period. The embodiment of the invention can automatically update the IP address list in the LVS load balancing server according to the IP address analyzed by the internal network DNS server, and can automatically finish the operation of removing and adding the server node in the LVS load balancing server without manual operation when the SSO system needs to go off-line or go on-line of a rear-end server node, thereby simplifying the process of going on-line and going off-line of the server node, improving the efficiency of going on-line and going off-line of the server node and reducing the operation and maintenance cost.
Fig. 5 is a schematic structural diagram of another embodiment of a processing device of a server node according to the present invention. The processing device of the server node of this embodiment may be used to implement the processing method embodiment of the server node shown in fig. 2. As shown in fig. 5, compared with the embodiment shown in fig. 4, the processing means of the server node of this embodiment further includes a sending unit 406 and a receiving unit 408. Wherein:
a sending unit 406, configured to send the first IP address list to the receiving unit 408 in response to the end of the current monitoring period.
A receiving unit 408, configured to receive the first IP address list sent by the sending unit 406.
Accordingly, referring again to fig. 5, the first update sheet 404 specifically includes a comparison module 502 and an update module 504. The comparing module 502 is configured to compare the IP address in the first IP address list received by the receiving unit 408 with the IP address in the second IP address list. An updating module 504, configured to update the IP address in the second IP address list to the IP address in the first IP address list according to the comparison result of the comparing module 502 if the IP address in the first IP address list is different from the IP address in the second IP address list.
According to another specific example but not limiting of the above embodiment of the present invention, in a specific application, the sending unit 406 may be disposed at a DNS server side; the receiving unit 408 may be disposed at the LVS load balancing server side.
Fig. 6 is a schematic structural diagram of a processing device of a server node according to another embodiment of the present invention. The processing device of the server node of this embodiment may be used to implement the processing method embodiment of the server node shown in fig. 3. As shown in fig. 6, compared with the embodiment shown in fig. 4, the processing device of the server node of this embodiment further includes a sending unit 406, a receiving unit 408, and a comparing unit 410. Wherein:
a comparing unit 410, configured to compare the IP addresses in the first IP address list with the IP addresses in the third IP address list in response to the end of the current monitoring period. And the third IP address list records the IP addresses of all online servers in the SSO intranet server pool before the current monitoring period.
A sending unit 406, configured to send the first IP address list to the receiving unit 408 according to the comparison result of the comparing unit 410, in response to that the IP address in the first IP address list is different from the IP address in the third IP address list.
A receiving unit 408, configured to receive the first IP address list sent by the sending unit 406.
Accordingly, in this embodiment, the first updating unit 404 is specifically configured to update the IP address in the second IP address list to the IP address in the first IP address list received by the receiving unit 408.
Further, referring to fig. 6, in yet another embodiment of the processing apparatus of the server node of the present invention, a second updating unit 602 may further be included, configured to update the IP address in the third IP address list to the IP address in the first IP address list when the IP address in the first IP address list is not the same as the IP address in the third IP address list according to the comparison result of the comparing unit 410; and emptying all the IP addresses in the first IP address list when the IP addresses in the first IP address list are identical to the IP addresses in the third IP address list.
For example, when the current monitoring period is the first monitoring period, the IP addresses recorded in the third IP address list may specifically be the IP addresses of all servers in the SSO intranet server pool in the initial state.
According to another specific example but not limitation of the above embodiments of the present invention, in a specific application, the comparing unit 410, the sending unit 406, and the second updating unit 602 may be disposed on the DNS server side; the receiving unit 408 may be disposed at the LVS load balancing server side.
Fig. 7 is a schematic structural diagram of an embodiment of the DNS server of the present invention. As shown in fig. 7, the DNS server in this embodiment includes, in addition to the DNS unit 702 for performing domain name resolution, a monitoring unit 402, configured to monitor resolution of the single sign-on SSO intranet domain name by the DNS unit 702, extract an IP address from a resolution result output by the intranet DNS server, store the IP address in a first IP address list, so as to respond to the end of the current monitoring period, and update a second IP address list set in the LVS load balancing server according to the first IP address list when the first IP address list is different from the second IP address list. The first IP address list is used for recording IP addresses in an analysis result output by the intranet DNS server in the current monitoring period, and the second IP address list is used for recording IP addresses of all online servers in the SSO intranet server pool before the current monitoring period.
Based on the DNS server provided in the above-mentioned embodiment of the present invention, the resolution of the DNS unit to the SSO intranet domain name can be monitored, the first IP address list records the IP addresses in the resolution result output by the intranet DNS server in the current monitoring period, so that when the current monitoring period is ended, the second IP address list arranged in the LVS load balancing server is updated according to the first IP address list, so that the automatic update of the IP address list in the LVS load balancing server according to the IP address analyzed by the intranet DNS server is realized, when the SSO system needs to go off-line or come on-line a rear-end server node, the operations of eliminating and adding server nodes in the LVS load balancing server can be automatically completed, and manual operation is not needed, the online and offline processes of the server nodes are simplified, the online and offline efficiency of the server nodes is improved, and the operation and maintenance cost is reduced.
Fig. 8 is a schematic structural diagram of another embodiment of the DNS server of the present invention. As shown in fig. 8, compared with the embodiment shown in fig. 7, the DNS server of this embodiment further includes a comparing unit 410 and a sending unit 406. Wherein:
a comparing unit 410, configured to compare the IP addresses in the first IP address list with the IP addresses in the third IP address list in response to the end of the current monitoring period. And the third IP address list records the IP addresses of all online servers in the SSO intranet server pool before the current monitoring period.
A sending unit 406, configured to send the first IP address list to the receiving unit according to the comparison result of the comparing unit 410, when the IP address in the first IP address list is different from the IP address in the third IP address list, so that the receiving unit updates the second IP address list set in the LVS load balancing server according to the first IP address list. And the second IP address list records the IP addresses of all online servers in the SSO intranet server pool before the current monitoring period.
Further, referring to fig. 8 again, the DNS server of yet another embodiment further includes a second updating unit 602, configured to update the IP address in the third IP address list to the IP address in the first IP address list when the IP address in the first IP address list is not the same as the IP address in the third IP address list according to the comparison result of the comparing unit 410; and emptying all the IP addresses in the first IP address list when the IP addresses in the first IP address list are identical to the IP addresses in the third IP address list.
Fig. 9 is a schematic structural diagram of an LVS load balancing server according to an embodiment of the present invention. As shown in fig. 9, the LVS load balancing server in this embodiment further includes, in addition to the load balancing processing unit 902 for distributing the access request and the storage unit 904 for storing the second IP address list, a first updating unit 404 for, in response to the end of the current monitoring period, updating the second IP address list in the storage unit 904 according to the first IP address list when the first IP address list is different from the second IP address list. The second IP address list records the IP addresses of all online servers in the SSO intranet server pool before the current monitoring period; the first IP address list is used for recording IP addresses in analysis results output by the intranet DNS server in the current monitoring period.
Based on the LVS load balancing server provided in the above embodiment of the present invention, when the current monitoring period is finished, the second IP address list set in the LVS load balancing server may be updated according to the IP address in the resolution result output by the intranet DNS server in the current monitoring period recorded by the first IP address list, so as to implement automatic update of the IP address list in the LVS load balancing server according to the IP address resolved by the intranet DNS server.
Fig. 10 is a schematic structural diagram of another embodiment of the LVS load balancing server according to the present invention. As shown in fig. 10, compared with the embodiment shown in fig. 9, the load balancing server of this embodiment further includes a receiving unit 408 for receiving the first IP address list sent by the sending unit 406. Accordingly, in this embodiment, the first updating unit 404 is specifically configured to compare the IP address in the first IP address list received by the receiving unit 408 with the IP address in the second IP address list; and in response to the IP address in the first IP address list being different from the IP address in the second IP address list, updating the IP address in the second IP address list to the IP address in the first IP address list.
The embodiment of the invention provides the following technical scheme:
c1, a method for processing a server node, comprising:
monitoring the analysis of the single sign-on SSO intranet domain name by an intranet domain name analysis DNS server, extracting an IP address from an analysis result output by the intranet DNS server, and storing the IP address in a first IP address list; the first IP address list is used for recording IP addresses in an analysis result output by the intranet DNS server in a current monitoring period;
responding to the end of the current monitoring period, if the first IP address list is different from the second IP address list, updating the second IP address list arranged in the Linux virtual server LVS load balancing server by using the first IP address list; and the second IP address list records the IP addresses of all online servers in the SSO intranet server pool before the current monitoring period.
C2, the method of C1, further comprising:
in response to the end of the current monitoring period,
comparing the IP addresses in the first IP address list with the IP addresses in the second IP address list;
and in response to that the IP address in the first IP address list is different from the IP address in the second IP address list, executing the operation of updating the second IP address list arranged in the LVS load balancing server by using the first IP address list.
C3, the method of C1, further comprising:
in response to the end of the current monitoring period, comparing the IP addresses in the first IP address list with the IP addresses in the third IP address list; the third IP address list records the IP addresses of all online servers in the SSO intranet server pool before the current monitoring period;
and responding to the fact that the IP address in the first IP address list is different from the IP address in the third IP address list, and sending the first IP address list so as to update a second IP address list arranged in the LVS load balancing server by using the first IP address list.
C4, the method of C3, further comprising:
in response to the fact that the IP address in the first IP address list is different from the IP address in the third IP address list, updating the IP address in the third IP address list to the IP address in the first IP address list;
and in response to the IP addresses in the first IP address list being identical to the IP addresses in the third IP address list, clearing all the IP addresses in the first IP address list.
C5, according to the method described in C3 or C4, when the current monitoring period is the first monitoring period, the IP addresses recorded in the third IP address list are specifically: in the initial state, the IP addresses of all servers in the SSO intranet server pool.
C6, according to the method of any one of C1 to C5, when the current monitoring period is the first monitoring period, the IP addresses recorded in the second IP address list specifically are: in the initial state, the IP addresses of all servers in the SSO intranet server pool.
C7, a processing apparatus of a server node, comprising:
the monitoring unit is used for monitoring the analysis of the single sign-on SSO intranet domain name by the intranet domain name analysis DNS server, extracting an IP address from an analysis result output by the intranet DNS server and storing the IP address in a first IP address list; the first IP address list is used for recording IP addresses in an analysis result output by the intranet DNS server in a current monitoring period;
the first updating unit is used for responding to the end of the current monitoring period, and updating a second IP address list arranged in the LVS load balancing server of the Linux virtual server according to the first IP address list if the first IP address list is different from the second IP address list; and the second IP address list records the IP addresses of all online servers in the SSO intranet server pool before the current monitoring period.
C8, the apparatus of C7, further comprising:
the sending unit is used for responding to the end of the current monitoring period and sending the first IP address list to the receiving unit;
the receiving unit is used for receiving the first IP address list sent by the sending unit;
the first updating unit specifically includes:
the comparison module is used for comparing the IP address in the first IP address list received by the receiving unit with the IP address in the second IP address list;
and the updating module is used for responding to the fact that the IP address in the first IP address list is different from the IP address in the second IP address list according to the comparison result of the comparing module, and updating the IP address in the second IP address list into the IP address in the first IP address list.
C9, the apparatus of C7, further comprising:
the comparison unit is used for responding to the end of the current monitoring period and comparing the IP address in the first IP address list with the IP address in the third IP address list; the third IP address list records the IP addresses of all online servers in the SSO intranet server pool before the current monitoring period;
the sending unit is used for responding to the fact that the IP address in the first IP address list is different from the IP address in the third IP address list according to the comparison result of the comparison unit and sending the first IP address list to the receiving unit;
the receiving unit is used for receiving the first IP address list sent by the sending unit;
the first updating unit is specifically configured to update the IP address in the second IP address list to the IP address in the first IP address list received by the receiving unit.
C10, the apparatus of C9, further comprising:
the second updating unit is used for responding to the fact that the IP address in the first IP address list is different from the IP address in the third IP address list according to the comparison result of the comparing unit, and updating the IP address in the third IP address list into the IP address in the first IP address list; and in response to the IP addresses in the first IP address list being identical to the IP addresses in the third IP address list, clearing all the IP addresses in the first IP address list.
C11, according to the apparatus described in C9 or C10, when the current monitoring period is the first monitoring period, the IP addresses recorded in the third IP address list are specifically: in the initial state, the IP addresses of all servers in the SSO intranet server pool.
C12, in the apparatus according to any one of C6 to C11, when the current monitoring period is the first monitoring period, the IP addresses recorded in the second IP address list specifically are: in the initial state, the IP addresses of all servers in the SSO intranet server pool.
C13, the device according to any one of C6 to C12, the monitoring unit is arranged at the DNS server side; the first updating unit is arranged at the LVS load balancing server.
C14, the device according to C8, the sending unit is arranged at the DNS server side; the receiving unit is arranged at the LVS load balancing server side.
C15, the device of the domain name resolution server according to C10, the comparing unit, the sending unit and the second updating unit are arranged at the DNS server end; the receiving unit is arranged at the LVS load balancing server side.
C16, a domain name resolution server, including a domain name resolution DNS unit, also including a monitoring unit, used for monitoring the resolution of the DNS unit to the single sign-on SSO intranet domain name, and extracting the IP address from the resolution result output by the intranet DNS server and storing in the first IP address list, so as to respond to the end of the current monitoring period, when the first IP address list is different from the second IP address list, updating the second IP address list set in the LVS load balancing server of the Linux virtual server according to the first IP address list; the first IP address list is used for recording IP addresses in an analysis result output by the intranet DNS server in a current monitoring period; and the second IP address list records the IP addresses of all online servers in the SSO intranet server pool before the current monitoring period.
C17, the domain name resolution server according to C16, further comprising:
the comparison unit is used for responding to the end of the current monitoring period and comparing the IP address in the first IP address list with the IP address in the third IP address list; the third IP address list records the IP addresses of all online servers in the SSO intranet server pool before the current monitoring period;
the sending unit is used for responding to the fact that the IP address in the first IP address list is different from the IP address in the third IP address list according to the comparison result of the comparison unit, and sending the first IP address list to the receiving unit so that the receiving unit can update a second IP address list arranged in the LVS load balancing server of the Linux virtual server according to the first IP address list; and the second IP address list records the IP addresses of all online servers in the SSO intranet server pool before the current monitoring period.
C18, the domain name resolution server according to C16 or C17, further comprising:
the second updating unit is used for responding to the fact that the IP address in the first IP address list is different from the IP address in the third IP address list according to the comparison result of the comparing unit, and updating the IP address in the third IP address list into the IP address in the first IP address list; and in response to the IP addresses in the first IP address list being identical to the IP addresses in the third IP address list, clearing all the IP addresses in the first IP address list.
C19, a load balancing server, comprising a load balancing processing unit and a storage unit for storing a second IP address list, further comprising:
the first updating unit is used for responding to the end of the current monitoring period, and updating a second IP address list arranged in the load balancing server according to the first IP address list if the first IP address list is different from the second IP address list; the second IP address list records IP addresses of all online servers in an SSO intranet server pool before the current monitoring period; the first IP address list is used for recording IP addresses in analysis results output by the intranet DNS server in the current monitoring period.
C20, the load balancing server according to C19, further comprising a receiving unit, configured to receive the first IP address list sent by the sending unit;
the first updating unit is specifically configured to:
comparing the IP address in the first IP address list received by the receiving unit with the IP address in the second IP address list; and in response to the fact that the IP addresses in the first IP address list are different from the IP addresses in the second IP address list, updating the IP addresses in the second IP address list to the IP addresses in the first IP address list.
Those of ordinary skill in the art will understand that: all or part of the steps for implementing the method embodiments may be implemented by hardware related to program instructions, and the program may be stored in a computer readable storage medium, and when executed, the program performs the steps including the method embodiments; and the aforementioned storage medium includes: various media that can store program codes, such as ROM, RAM, magnetic or optical disks.
In the present specification, the embodiments are described in a progressive manner, each embodiment focuses on differences from other embodiments, and the same or similar parts in the embodiments are referred to each other. For the device and server embodiments, since they basically correspond to the method embodiments, the description is relatively simple, and for the relevant points, reference may be made to the partial description of the method embodiments.
The method, apparatus and server of the present invention may be implemented in a number of ways. For example, the method, apparatus and server of the present invention may be implemented by software, hardware, firmware or any combination of software, hardware and firmware. The above-described order for the steps of the method is for illustrative purposes only, and the steps of the method of the present invention are not limited to the order specifically described above unless specifically indicated otherwise. Furthermore, in some embodiments, the present invention may also be embodied as a program recorded in a recording medium, the program including machine-readable instructions for implementing a method according to the present invention. Thus, the present invention also covers a recording medium storing a program for executing the method according to the present invention.
The description of the present invention has been presented for purposes of illustration and description, and is not intended to be exhaustive or limited to the invention in the form disclosed. Many modifications and variations will be apparent to practitioners skilled in this art. The embodiment was chosen and described in order to best explain the principles of the invention and the practical application, and to enable others of ordinary skill in the art to understand the invention for various embodiments with various modifications as are suited to the particular use contemplated.

Claims (15)

1. A method for processing a server node, comprising:
monitoring the analysis of the single sign-on SSO intranet domain name by an intranet domain name analysis DNS server, extracting an IP address from an analysis result output by the intranet DNS server, and storing the IP address in a first IP address list; establishing socket connection between a sending end of an intranet DNS server and a receiving end of an LVS load balancing server, wherein the first IP address list is used for recording IP addresses in an analysis result output by the intranet DNS server in a current monitoring period;
responding to the end of the current monitoring period, sending a first IP address list to a receiving end in a socket communication mode, comparing whether the IP addresses in the first IP address list are the same as the IP addresses in a second IP address list or not at the receiving end, and updating the second IP address list arranged in the LVS load balancing server of the Linux virtual server by using the first IP address list if the first IP address list is different from the second IP address list; the second IP address list records IP addresses of all online servers in an SSO intranet server pool before the current monitoring period; the first IP address list is different from the second IP address list and includes: the number and/or specific addresses of the IP addresses in the first IP address list are different from those in the second IP address list;
in response to the end of the current monitoring period, comparing the IP addresses in the first IP address list with the IP addresses in the third IP address list; the third IP address list is arranged at the sending end, and the IP addresses of all online servers in the SSO intranet server pool before the current monitoring period are recorded in the third IP address list;
responding to the fact that the IP address in the first IP address list is different from the IP address in the third IP address list, and sending the first IP address list so as to update a second IP address list arranged in the LVS load balancing server by using the first IP address list; wherein, the IP address in the first IP address list is different from the IP address in the third IP address list, and the method comprises the following steps: the number and/or specific addresses of the IP addresses in the first IP address list are different from those in the third IP address list.
2. The method of claim 1, further comprising:
in response to the fact that the IP address in the first IP address list is different from the IP address in the third IP address list, updating the IP address in the third IP address list to the IP address in the first IP address list;
and in response to the IP addresses in the first IP address list being identical to the IP addresses in the third IP address list, clearing all the IP addresses in the first IP address list.
3. The method according to claim 1 or 2, wherein when the current monitoring period is a first monitoring period, the IP addresses recorded in the third IP address list are specifically: in the initial state, the IP addresses of all servers in the SSO intranet server pool.
4. The method according to any one of claims 1 to 2, wherein when the current monitoring period is a first monitoring period, the IP addresses recorded in the second IP address list are specifically: in the initial state, the IP addresses of all servers in the SSO intranet server pool.
5. A processing apparatus of a server node, comprising:
the monitoring unit is used for monitoring the analysis of the single sign-on SSO intranet domain name by the intranet domain name analysis DNS server, extracting an IP address from an analysis result output by the intranet DNS server and storing the IP address in a first IP address list; establishing socket connection between a sending end of an intranet DNS server and a receiving end of an LVS load balancing server, wherein the first IP address list is used for recording IP addresses in an analysis result output by the intranet DNS server in a current monitoring period;
the first updating unit is used for responding to the end of the current monitoring period, sending a first IP address list to a receiving end in a socket communication mode, comparing whether the IP addresses in the first IP address list are the same as the IP addresses in a second IP address list or not at the receiving end, and updating the second IP address list arranged in the LVS load balancing server of the Linux virtual server according to the first IP address list if the first IP address list is different from the second IP address list; the second IP address list records IP addresses of all online servers in an SSO intranet server pool before the current monitoring period; the first IP address list is different from the second IP address list and includes: the number and/or specific addresses of the IP addresses in the first IP address list are different from those in the second IP address list;
the comparison unit is used for responding to the end of the current monitoring period and comparing the IP address in the first IP address list with the IP address in the third IP address list; the third IP address list is arranged at the sending end, and the IP addresses of all online servers in the SSO intranet server pool before the current monitoring period are recorded in the third IP address list;
the sending unit is used for responding to the fact that the IP address in the first IP address list is different from the IP address in the third IP address list according to the comparison result of the comparison unit and sending the first IP address list to the receiving unit; wherein, the IP address in the first IP address list is different from the IP address in the third IP address list, and the method comprises the following steps: the number and/or specific addresses of the IP addresses in the first IP address list are different from those in the third IP address list;
the receiving unit is used for receiving the first IP address list sent by the sending unit;
the first updating unit is specifically configured to update the IP address in the second IP address list to the IP address in the first IP address list received by the receiving unit.
6. The apparatus of claim 5, further comprising:
the second updating unit is used for responding to the fact that the IP address in the first IP address list is different from the IP address in the third IP address list according to the comparison result of the comparing unit, and updating the IP address in the third IP address list into the IP address in the first IP address list; and in response to the IP addresses in the first IP address list being identical to the IP addresses in the third IP address list, clearing all the IP addresses in the first IP address list.
7. The apparatus according to claim 5 or 6, wherein when the current monitoring period is a first monitoring period, the IP addresses recorded in the third IP address list are specifically: in the initial state, the IP addresses of all servers in the SSO intranet server pool.
8. The apparatus according to any one of claims 5 to 6, wherein when the current monitoring period is a first monitoring period, the IP addresses recorded in the second IP address list are specifically: in the initial state, the IP addresses of all servers in the SSO intranet server pool.
9. The device according to any one of claims 5 to 6, wherein the monitoring unit is arranged at a DNS server side; the first updating unit is arranged at the LVS load balancing server.
10. The apparatus according to claim 5, wherein the sending unit is disposed at a DNS server side; the receiving unit is arranged at the LVS load balancing server side.
11. The apparatus according to claim 6, wherein the comparing unit, the sending unit and the second updating unit are disposed at a DNS server side; the receiving unit is arranged at the LVS load balancing server side.
12. A domain name resolution server comprises a domain name resolution DNS unit and is characterized by further comprising a monitoring unit, wherein the monitoring unit is used for monitoring the resolution of the DNS unit on a single sign-on SSO intranet domain name, and recording an IP address in a resolution result output by the intranet DNS server in a current monitoring period through a first IP address list so as to respond to the end of the current monitoring period and update a second IP address list arranged in a Linux virtual server LVS load balancing server according to the first IP address list;
the comparison unit is used for responding to the end of the current monitoring period and comparing the IP address in the first IP address list with the IP address in the third IP address list; the third IP address list is arranged at the sending end, and the IP addresses of all online servers in the SSO intranet server pool before the current monitoring period are recorded in the third IP address list;
the sending unit is used for responding to the fact that the IP address in the first IP address list is not identical to the IP address in the third IP address list according to the comparison result of the comparison unit, and sending the first IP address list to the receiving unit so that the receiving unit can update a second IP address list arranged in the LVS load balancing server of the Linux virtual server according to the first IP address list; wherein, the second IP address list records the IP addresses of all online servers in the SSO intranet server pool before the current monitoring period, and the IP addresses in the first IP address list and the IP addresses in the third IP address list are not identical, including: the number and/or specific addresses of the IP addresses in the first IP address list are not identical to those in the third IP address list.
13. The domain name resolution server according to claim 12, further comprising:
a second updating unit, configured to update the IP address in the third IP address list to the IP address in the first IP address list in response to that the IP address in the first IP address list is not identical to the IP address in the third IP address list according to the comparison result of the comparing unit; and in response to the IP addresses in the first IP address list being identical to the IP addresses in the third IP address list, clearing all the IP addresses in the first IP address list.
14. A load balancing server, comprising a load balancing processing unit and a storage unit for storing a second IP address list, further comprising:
the first updating unit is used for responding to the end of the current monitoring period and updating a second IP address list arranged in the load balancing server according to the first IP address list; the second IP address list records IP addresses of all online servers in an SSO intranet server pool before the current monitoring period; and the first IP address list records the IP addresses in the analysis result output by the intranet DNS server in the current monitoring period.
15. The load balancing server according to claim 14, further comprising a receiving unit, configured to receive the first IP address list sent by the sending unit;
the first updating unit is specifically configured to:
comparing the IP address in the first IP address list received by the receiving unit with the IP address in the second IP address list; and in response to the IP addresses in the first IP address list and the second IP address list not being identical, updating the IP addresses in the second IP address list to the IP addresses in the first IP address list.
CN201510662199.9A 2015-10-14 2015-10-14 Server node processing method and device Active CN106603588B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201510662199.9A CN106603588B (en) 2015-10-14 2015-10-14 Server node processing method and device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201510662199.9A CN106603588B (en) 2015-10-14 2015-10-14 Server node processing method and device

Publications (2)

Publication Number Publication Date
CN106603588A CN106603588A (en) 2017-04-26
CN106603588B true CN106603588B (en) 2020-05-15

Family

ID=58553024

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201510662199.9A Active CN106603588B (en) 2015-10-14 2015-10-14 Server node processing method and device

Country Status (1)

Country Link
CN (1) CN106603588B (en)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109889511B (en) * 2019-01-31 2021-10-01 中国人民解放军61660部队 Process DNS activity monitoring method, equipment and medium
CN109905397A (en) * 2019-03-12 2019-06-18 深圳市网心科技有限公司 A kind of method and intranet server for establishing data connection
CN110933145A (en) * 2019-11-14 2020-03-27 光通天下网络科技股份有限公司 Remote scheduling method, device, equipment and medium

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2001144812A (en) * 1999-11-17 2001-05-25 Sharp Corp Authentication processing system for wireless ip terminal
CN103595825A (en) * 2013-10-25 2014-02-19 北京奇虎科技有限公司 Domain name resolution detection method, domain name resolution detection device and server
CN103944907A (en) * 2014-04-25 2014-07-23 天地融科技股份有限公司 Data updating method and system
CN104346410A (en) * 2013-08-09 2015-02-11 腾讯科技（深圳）有限公司 Method and equipment for monitoring terminal equipment
CN104796445A (en) * 2014-01-21 2015-07-22 航天信息股份有限公司 Resource synchronization method and device by server nodes

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN100499695C (en) * 2004-12-21 2009-06-10 华为技术有限公司 Signal detection device and method, and number detection device and method
CN101291194B (en) * 2008-05-20 2010-08-25 成都市华为赛门铁克科技有限公司 Method and system for keeping sequence of report
GB0904559D0 (en) * 2009-03-17 2009-04-29 British Telecomm Web application access
CN102104483B (en) * 2009-12-18 2013-10-02 杭州华三通信技术有限公司 Single sign-on method, system and load balancing equipment based on load balance
US10176335B2 (en) * 2012-03-20 2019-01-08 Microsoft Technology Licensing, Llc Identity services for organizations transparently hosted in the cloud

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2001144812A (en) * 1999-11-17 2001-05-25 Sharp Corp Authentication processing system for wireless ip terminal
CN104346410A (en) * 2013-08-09 2015-02-11 腾讯科技（深圳）有限公司 Method and equipment for monitoring terminal equipment
CN103595825A (en) * 2013-10-25 2014-02-19 北京奇虎科技有限公司 Domain name resolution detection method, domain name resolution detection device and server
CN104796445A (en) * 2014-01-21 2015-07-22 航天信息股份有限公司 Resource synchronization method and device by server nodes
CN103944907A (en) * 2014-04-25 2014-07-23 天地融科技股份有限公司 Data updating method and system

Also Published As

Publication number Publication date
CN106603588A (en) 2017-04-26

Similar Documents

Publication Publication Date Title
US9893931B2 (en) Connection recovery method, apparatus, and system
US8892768B2 (en) Load balancing apparatus and load balancing method
CN103780679B (en) Long delay remote invocation method based on http protocol
CN101453495B (en) Method, system and equipment for preventing authentication address resolution protocol information loss
CN103002069A (en) Domain name resolution method, device and system
CN102708173A (en) Method and system for processing user requests of accessing to web pages
JP4163697B2 (en) Load distribution system, real server, and load distribution method
CN106603588B (en) Server node processing method and device
CN103905572A (en) Domain name resolution request processing method and device
CN110995656A (en) Load balancing method, device, equipment and storage medium
CN105338128A (en) Domain name resolution method and device
US8903998B2 (en) Apparatus and method for monitoring web application telecommunication data by user
US20150156349A1 (en) Information processing apparatus, system, and control method for information processing apparatus
CN111147598A (en) HTTP message processing method and device
JP5245837B2 (en) Terminal device, relay device, and program
CN103795584A (en) Client side identity detection method and gateway
CN111193778B (en) Method and device for balancing WEB service load
CN109495602B (en) Method and device for processing network access abnormity
JP6605149B2 (en) Method and apparatus for detecting shared terminal
TW201644249A (en) Devices and methods for performing TCP handshakes
CN105721231A (en) Service quality sensing detection method and service quality sensing detection device
KR101670699B1 (en) Method and system for communicating between web pages
US20140047014A1 (en) Network access system
CN104580178A (en) Method and equipment for Portal authentication
CN110809064B (en) IP address switching method, device and system

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
CB02 Change of applicant information
CB02 Change of applicant information

Address after: 100083 No. 401, 4th Floor, Haitai Building, 229 North Fourth Ring Road, Haidian District, Beijing

Applicant after: Beijing Guoshuang Technology Co.,Ltd.

Address before: 100086 Cuigong Hotel, 76 Zhichun Road, Shuangyushu District, Haidian District, Beijing

Applicant before: Beijing Guoshuang Technology Co.,Ltd.

GR01 Patent grant
GR01 Patent grant