US20150127801A1 - Name service object clustering - Google Patents
Name service object clustering Download PDFInfo
- Publication number
- US20150127801A1 US20150127801A1 US14/589,441 US201514589441A US2015127801A1 US 20150127801 A1 US20150127801 A1 US 20150127801A1 US 201514589441 A US201514589441 A US 201514589441A US 2015127801 A1 US2015127801 A1 US 2015127801A1
- Authority
- US
- United States
- Prior art keywords
- cluster
- server
- client
- bind
- load balancing
- 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.)
- Abandoned
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
- G06F9/5083—Techniques for rebalancing the load in a distributed system
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/10—Flow control; Congestion control
- H04L47/12—Avoiding congestion; Recovering from congestion
- H04L47/125—Avoiding congestion; Recovering from congestion by balancing the load, e.g. traffic engineering
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/14—Error detection or correction of the data by redundancy in operation
- G06F11/1479—Generic software techniques for error detection or fault masking
- G06F11/1482—Generic software techniques for error detection or fault masking by means of middleware or OS functionality
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/54—Interprogram communication
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/54—Interprogram communication
- G06F9/541—Interprogram communication via adapters, e.g. between incompatible applications
-
- 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/1004—Server selection for load balancing
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/16—Error detection or correction of the data by redundancy in hardware
- G06F11/20—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements
- G06F11/202—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements where processing functionality is redundant
- G06F11/2023—Failover techniques
- G06F11/2028—Failover techniques eliminating a faulty processor or activating a spare
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/16—Error detection or correction of the data by redundancy in hardware
- G06F11/20—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements
- G06F11/202—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements where processing functionality is redundant
- G06F11/2035—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements where processing functionality is redundant without idle spare hardware
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/54—Interprogram communication
- G06F9/546—Message passing systems or structures, e.g. queues
Definitions
- the present invention generally relates to the field of distributed object oriented computing and, more particularly, to a method for fault tolerance, load balance and “failover” of CORBA object servers via name service clustering.
- CORBA Common Object Request Broker Architecture
- RMI Remote Method Invocation
- CORBA/IIOP Common Object Request Broker Architecture/Internet Inter Orb Protocol
- a large number of requests to a CORBA object server can cause information bottlenecks at the server (i.e., a decrease in server capacity or a reduction in processing speed).
- a single CORBA object server can become the single-point of failure in a network.
- clients maybe long lived, unavailability of services from a server is unacceptable.
- Another solution to the prior problems involves redesigning and replicating the CORBA server, and statically configuring the replica servers such that each server object contains one profile for each replica server object.
- client requests “failover” to a replica server.
- this configuration is not scalable, i.e., it is not applicable to different servers located in a large network.
- a further solution to the above mentioned problems comprises redesigning the client such that it captures failures and redirects requests to another server.
- this approach not only requires client code changes, but also requires that the client possess prior knowledge related to the existence of all the servers in the network. It is therefore apparent there is a need for a method for reducing failures associated with selecting a server located in a distributed object oriented computing environment.
- the present invention is directed to a method for fault tolerance, load balance and “failover” of CORBA object servers via name service clustering.
- Name service clustering such as implemented in “Visibroker Naming Service” (Trademark, Borland Software Corp, Scotts Valley, Calif.), permits naming service load balancing over a set of object references contained within the same cluster such that loads are equitably distributed among servers.
- Each cluster contains its own unique object binding table which contains object references that each typically represent a single server.
- Load balancing is performed using a load balance algorithm (e.g., Round Robin). The specific algorithm which is used to perform load balancing is specified upon creation of each naming service cluster.
- a load balance is performed to return an object reference which was previously bound to the cluster.
- the client machine may then communicate with the server associated with the object reference which was selected. Failover is provided by dynamically adding cluster components to resolved object references upon resolving each cluster.
- a method for fault tolerance, load balance and failover of CORBA object servers comprises the steps of: invoking a cluster contained in a context; performing a load balance to select an object server located in the invoked cluster; appending a cluster component to the invoked cluster to provide failover upon failure of the object server; forwarding a selected object reference to a client upon completion of the load balance; and communicating with a server associated with the selected object reference which was forwarded to the client.
- a method for fault tolerance, load balance and failover of CORBA object servers comprises the steps of: setting a flag in a file to activate implicit clustering; invoking a cluster contained in a context having clusters; performing a load balance to select an object server located in the clusters; forwarding a selected object reference to a client upon completion of the load balance; and communicating with the server associated with the selected object reference which was forwarded to the client.
- FIG. 1 is an illustration of a network arrangement of hardware components for implementing a method in accordance with a preferred embodiment of the invention
- FIG. 2 is an exemplary illustration of a naming graph comprising an object management group in a distributed computing system
- FIG. 3 is an illustration of a server replication operation in accordance with the preferred embodiment of the invention.
- FIG. 4 is an illustration of a dynamic bind and unbind operation of cluster objects in accordance with the preferred embodiment of the invention.
- FIG. 5 is a flow chart of a method for load balancing in accordance with the preferred embodiment of the invention.
- FIG. 6 is a flow chart of a method for dynamic object clustering in accordance with the preferred embodiment of the invention.
- the Visibroker Naming ServiceTM permits the activation and deactivation of an implicit clustering feature and associates multiple object references with a single name. Activation of the implicit clustering feature may be accomplished using a flag located in a file, such as a configuration file, or the like.
- the clustering of object references in this manner becomes highly scalable because the object references may be dynamically added or removed from a cluster through cluster bind or unbind operations.
- the naming service load balances over the set of object references associated with the name and distributes the load accordingly. As a result, the need to recreate clusters is eliminated because the load balancing is performed among a common predetermined group of object reference binders.
- FIG. 1 shows a network arrangement by which the preferred embodiment can be implemented.
- the network 100 includes host servers 110 , 110 a . . . 110 n which provide content over the Internet 120 to a plurality of distributed users that access the host server through client machines 130 , 130 a . . . 130 n.
- the content provided by the host server 110 , 110 a . . . 110 n can be viewed by users through a web browser or other functionally equivalent software running at their respective client machines 130 (hereinafter, “browser”).
- the client machines or “client” 130 can assume a variety of forms, including a home computer, a personal digital assistant (PDA), a pager, an Internet compliant telephone, or other Internet compliant device.
- the client machines 130 and the host server 110 communicate with one another in a conventional manner over a communication link through a distributed computer network such as the Internet 120 .
- a distributed computer network such as the Internet 120 .
- communications can be through an Intranet or Extranet or between a host computer and a kiosk located nearby, as understood by those of skill in the art.
- FIG. 2 is an exemplary illustration of a naming graph comprising an object management group in a distributed computing system.
- the starting point for the construction of such a graph is the “Root Context” of the object management group.
- the Root context contains object name bindings.
- Such a repository of object name bindings is called a CosNaming Service, and permits a client to locate an object using a logical name which is bound within the repository.
- Visibroker Naming ServiceTM is an implementation of OMG CosNaming Service.
- Visibroker Naming ServiceTM includes a feature called clustering which groups objects within a cluster to provide scalability and high availability to applications via load balancing and alternative server selection, i.e., “failover”, upon server failures.
- a Visibroker Naming ServiceTM cluster is a placeholder for a set of functionally exchangeable objects.
- a naming service cluster differs from the CosNaming context in that the CosNaming context is a directory that may contain sub-contexts, object references, and service clusters, while a service cluster may contain only object references.
- Each object reference shown in FIG. 2 will contain the server's Host Name, IP Address, Port No., and the like.
- FIG. 3 is an illustration of a server replication operation in accordance with the preferred embodiment of the invention.
- Visibroker Naming ServiceTM clustering permits naming service load balancing over a set of object references contained within the same cluster such that loads are equitably distributed among servers.
- Each cluster contains its own unique object binding table which contains object references which each typically represent a single server.
- Load balancing is performed using a load balance algorithm (e.g., Round Robin).
- the specific algorithm which is used to perform load balancing in a given implementation is not critical to the invention, but is specified upon creation of each naming service cluster.
- a load balance (2) is performed to return an object reference (3) which was previously bound to the cluster.
- the client may then communicate with the server associated with the object reference which was selected.
- failover is provided by dynamically adding cluster components to resolved object references upon resolving each cluster (4).
- a cluster component which is a part of an object reference of an object is created.
- Each cluster component provides to a client object resource broker (ORB) information which permits the client ORB to access the cluster object located in the name service to which this object is bound.
- ORB client object resource broker
- this information permits the client ORB to contact the cluster object to obtain another object in the same cluster to which the client ORB can then failover to. If an object reference fails during processing, the particular object reference binding associated with the specific object reference in the cluster becomes stale.
- binding When a client invokes an invocation to a specific server, the connection to the server is accomplished using a process called binding. In order for the client to communicate with the server, it must bind with the server using the IP Address and Port No. contained in a specific object reference.
- a binding is performed by using an object reference and performing the necessary steps to derive a concrete connection to a specific process that implements the functionality represented by that object reference.
- User participation in the binding process is accomplished via a “binding interceptor” which is a Java class that the user may implement as desired. Each class comprises methods of differing relevancies which are used to indicate the binding status (i.e., Bind, Bind_Succeeded, Bind_Failed, and Exception_Occurred).
- a “Bind” is performed by using an object reference and performing the steps necessary to derive a concrete connection to a specific process which implements the functionality represented by that object reference.
- a Bind_Succeeded is an indication that a connection was achieved
- a Bind_Failed is an indication that a connection was not established
- an Exception_Occurred represents an indeterminate state between Bind_Succeeded and Bind_Failed.
- a bind method is called.
- the user will be provided with a class containing the most relevant methods, preferably the three most relevant methods.
- the most relevant methods are Bind, Bind_Succeeded and Bind_Failed.
- the user then writes (specifies) the class such that the class subsequently contains the most relevant methods.
- the user code is called (i.e., a bind interceptor is used).
- the bind interceptor provides a user with an option to select an alternative server in the instance where the system was operating adequately and then fails. For example, if a returned bind interceptor contains a Bind_Failed method, the user is presented with an opportunity to choose to connect to another server.
- the client associated with the stale object reference When an attempt to send a request to the stale server is made, the client associated with the stale object reference will transparently intercept the cluster component using the binding interceptor. The interceptor will then invoke the cluster's select operation (i.e., its load balancing algorithm) to select and return to the client another object reference in the same cluster. Communication is then established between the client and the server of the newly returned object reference. As a result, the failover to one of the object references in the same cluster is transparently achieved. The failed object reference is thereafter marked as “suspect.” In an embodiment, the stale object reference is automatically removed from the cluster based on a user established preference.
- the Visibroker Naming ServiceTM permits the activation and deactivation of an implicit clustering feature and associates multiple object references with a single name.
- Activation of the implicit clustering feature may be accomplished using a flag located in a file, such as a configuration file, or the like.
- the clustering of object references in this manner becomes highly scalable because the object references may be dynamically added or removed from a cluster through cluster bind or unbind operations.
- FIG. 4 is an illustration of a dynamic bind and unbind operation of cluster objects in accordance with the preferred embodiment of the invention.
- implicit clustering When implicit clustering is activated, object reference bindings using the same name are clustered together in the same cluster.
- a default load balance algorithm such as Smart Round Robin, is used for implicit clustering. This algorithm may be changed at the discretion of the user.
- FIG. 5 is a flow chart of a method for load balancing in accordance with the preferred embodiment of the invention.
- the method is implemented when a client invokes a cluster located under a particular context or specific directory, as indicated in step 500 .
- a load balance is performed to return an object reference which is bound to the cluster, as indicated in step 510 .
- Load balancing is performed using a load balance algorithm (e.g., Round Robin).
- the specific algorithm which is used to perform load balancing is specified upon creation of each naming service cluster.
- An object reference is forwarded to the cluster, as indicated in step 520 .
- cluster components are dynamically added to resolved object references subsequent to load balancing each cluster to provide failover, as indicated in step 530 . Failover is provided in the manner discussed previously.
- the client communicates with the server associated with the object reference which was selected and forwarded to the client, as indicated in step 540 .
- FIG. 6 is a flow chart illustrating dynamic bind and unbind operations of cluster objects in accordance with the preferred embodiment of the invention.
- the method is implemented when implicit clustering is activated, as indicated in step 600 .
- a cluster containing the clustered object reference bindings using the same name is invoked, as indicated in step 610 .
- Load balancing is performed on the clustered object references using a default load balance algorithm, as indicated in step 620 . This algorithm may be changed at the discretion of the user, e.g., from a Round Robin algorithm to a different algorithm.
- a selected object reference based on the load balance is returned upon completion of load balancing, as indicated in step 630 .
- the client communicates with the server associated with the object reference which was selected and forward to the client, as indicated in step 640 .
- Methods in accordance with the invention permit transparent load balancing among multiple object references in the same cluster to be achieved.
- transparent failover among object references in the same cluster is provided.
- Method according to the invention also provide a dynamic addition of new object references into a cluster via binding, along with the dynamic removal of old object references from a cluster via unbinding.
- automatic detection of stale object references in a cluster and clean up based on the preference of a client is achieved.
- Such methods provide a consistent application of the load balancing algorithms per cluster. New load balancing algorithms may be up-loaded to the system as required. The method eliminates the need to change the client code or server code such that manual configurations are not required.
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Software Systems (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Quality & Reliability (AREA)
- Computer And Data Communications (AREA)
- Hardware Redundancy (AREA)
Abstract
Method and System for load balance of Common Object Request Broker Architecture (CORBA) object servers, comprising: invoking a name service cluster, indicating to a user whether bind interceptors are in use, and providing the user with a class having relevant methods if bind interceptors are in use.
Description
- This application is a continuation of U.S. patent application Ser. No. 14/031,382, filed Sep. 19, 2013, which is a continuation of U.S. patent application No. 10/017,495, filed Dec. 14, 2001, which claims priority of U.S. Provisional Patent Application No. 60/255,651, filed Dec. 14, 2000. All of the foregoing are incorporated herein by reference in their entireties.
- 1. Field of the Invention
- The present invention generally relates to the field of distributed object oriented computing and, more particularly, to a method for fault tolerance, load balance and “failover” of CORBA object servers via name service clustering.
- 2. Description of the Related Art
- Recently, Common Object Request Broker Architecture (CORBA) has emerged as the de facto standard architecture for distributed object computing. This distributed object infrastructure enables organizations to build and deploy robust distributed object applications across the Internet and enterprise intranets.
- Emerging application servers and Enterprise Java Bean (EJB) technology are being built on top of the pre-existing CORBA infrastructure. Remote Method Invocation (RMI) technology takes advantage of the capabilities of the Common Object Request Broker Architecture/Internet Inter Orb Protocol (CORBA/IIOP) infrastructure. As a result, fault tolerance, high availability and the load balancing capability of CORBA object servers become critically important due to the increased system capacity.
- For example, a large number of requests to a CORBA object server can cause information bottlenecks at the server (i.e., a decrease in server capacity or a reduction in processing speed). As a result, a single CORBA object server can become the single-point of failure in a network. Moreover, since clients maybe long lived, unavailability of services from a server is unacceptable.
- In the past, these problems have been solved by replicating the CORBA servers and performing a load balance by using a predefined algorithm among the replicas to select a specific object server. Load balancing across the servers can be performed with a variety of techniques, such as via a Round Robin directory and a naming service or a special CORBA object server which dispatches requests from clients to servers. However, substantial coding, redesign and reconfiguration of the server, which results in increased costs, is unavoidable.
- Another solution to the prior problems involves redesigning and replicating the CORBA server, and statically configuring the replica servers such that each server object contains one profile for each replica server object. Upon failure of a server, client requests “failover” to a replica server. However, this configuration is not scalable, i.e., it is not applicable to different servers located in a large network. Once the redesign, replication, and configuration of the server is completed and implemented, it cannot be changed.
- A further solution to the above mentioned problems comprises redesigning the client such that it captures failures and redirects requests to another server. However, this approach not only requires client code changes, but also requires that the client possess prior knowledge related to the existence of all the servers in the network. It is therefore apparent there is a need for a method for reducing failures associated with selecting a server located in a distributed object oriented computing environment.
- The present invention is directed to a method for fault tolerance, load balance and “failover” of CORBA object servers via name service clustering. Name service clustering, such as implemented in “Visibroker Naming Service” (Trademark, Borland Software Corp, Scotts Valley, Calif.), permits naming service load balancing over a set of object references contained within the same cluster such that loads are equitably distributed among servers. Each cluster contains its own unique object binding table which contains object references that each typically represent a single server. Load balancing is performed using a load balance algorithm (e.g., Round Robin). The specific algorithm which is used to perform load balancing is specified upon creation of each naming service cluster.
- When a client machine invokes a cluster located under a particular context or specific directory, i.e., “resolves,” a load balance is performed to return an object reference which was previously bound to the cluster. The client machine may then communicate with the server associated with the object reference which was selected. Failover is provided by dynamically adding cluster components to resolved object references upon resolving each cluster.
- In accordance with the invention, a method for fault tolerance, load balance and failover of CORBA object servers comprises the steps of: invoking a cluster contained in a context; performing a load balance to select an object server located in the invoked cluster; appending a cluster component to the invoked cluster to provide failover upon failure of the object server; forwarding a selected object reference to a client upon completion of the load balance; and communicating with a server associated with the selected object reference which was forwarded to the client.
- In another embodiment of the invention a method for fault tolerance, load balance and failover of CORBA object servers comprises the steps of: setting a flag in a file to activate implicit clustering; invoking a cluster contained in a context having clusters; performing a load balance to select an object server located in the clusters; forwarding a selected object reference to a client upon completion of the load balance; and communicating with the server associated with the selected object reference which was forwarded to the client.
- The present invention may be more readily understood by one skilled in the art with reference being had to the following detailed description of the preferred embodiments thereof, taken in conjunction with the accompanying drawings wherein like elements are designated by identical reference numerals throughout the several views, and in which:
-
FIG. 1 is an illustration of a network arrangement of hardware components for implementing a method in accordance with a preferred embodiment of the invention; -
FIG. 2 is an exemplary illustration of a naming graph comprising an object management group in a distributed computing system; -
FIG. 3 is an illustration of a server replication operation in accordance with the preferred embodiment of the invention; -
FIG. 4 is an illustration of a dynamic bind and unbind operation of cluster objects in accordance with the preferred embodiment of the invention; -
FIG. 5 is a flow chart of a method for load balancing in accordance with the preferred embodiment of the invention; and -
FIG. 6 is a flow chart of a method for dynamic object clustering in accordance with the preferred embodiment of the invention. - By way of overview and introduction, the invention is described in connection with a preferred embodiment, depicted in
FIG. 3 , in which load balancing is performed amongservers 110 connected to the Internet 120, or other distributed computer network. - Generally, the Visibroker Naming Service™ permits the activation and deactivation of an implicit clustering feature and associates multiple object references with a single name. Activation of the implicit clustering feature may be accomplished using a flag located in a file, such as a configuration file, or the like. The clustering of object references in this manner becomes highly scalable because the object references may be dynamically added or removed from a cluster through cluster bind or unbind operations.
- When implicit clustering is activated, object reference bindings using the same name are clustered together in the same cluster. A default load balance algorithm, such as Smart Round Robin, is used for implicit clustering. This algorithm may be changed at the discretion of the user.
- If a call to a name within the clustered object references is invoked, the naming service load balances over the set of object references associated with the name and distributes the load accordingly. As a result, the need to recreate clusters is eliminated because the load balancing is performed among a common predetermined group of object reference binders.
-
FIG. 1 shows a network arrangement by which the preferred embodiment can be implemented. Thenetwork 100 includeshost servers client machines host server - The client machines or “client” 130 can assume a variety of forms, including a home computer, a personal digital assistant (PDA), a pager, an Internet compliant telephone, or other Internet compliant device. The
client machines 130 and thehost server 110 communicate with one another in a conventional manner over a communication link through a distributed computer network such as the Internet 120. In lieu of the Internet, communications can be through an Intranet or Extranet or between a host computer and a kiosk located nearby, as understood by those of skill in the art. -
FIG. 2 is an exemplary illustration of a naming graph comprising an object management group in a distributed computing system. The starting point for the construction of such a graph is the “Root Context” of the object management group. The Root context contains object name bindings. Such a repository of object name bindings is called a CosNaming Service, and permits a client to locate an object using a logical name which is bound within the repository. - Visibroker Naming Service™ is an implementation of OMG CosNaming Service. In addition, Visibroker Naming Service™ includes a feature called clustering which groups objects within a cluster to provide scalability and high availability to applications via load balancing and alternative server selection, i.e., “failover”, upon server failures.
- A Visibroker Naming Service™ cluster is a placeholder for a set of functionally exchangeable objects. A naming service cluster differs from the CosNaming context in that the CosNaming context is a directory that may contain sub-contexts, object references, and service clusters, while a service cluster may contain only object references. Each object reference shown in
FIG. 2 will contain the server's Host Name, IP Address, Port No., and the like. -
FIG. 3 is an illustration of a server replication operation in accordance with the preferred embodiment of the invention. Visibroker Naming Service™ clustering permits naming service load balancing over a set of object references contained within the same cluster such that loads are equitably distributed among servers. Each cluster contains its own unique object binding table which contains object references which each typically represent a single server. Load balancing is performed using a load balance algorithm (e.g., Round Robin). The specific algorithm which is used to perform load balancing in a given implementation is not critical to the invention, but is specified upon creation of each naming service cluster. - When a client invokes a cluster located under a particular context or specific directory (1), i.e., “resolves,” a load balance (2) is performed to return an object reference (3) which was previously bound to the cluster. The client may then communicate with the server associated with the object reference which was selected.
- As shown in
FIG. 3 , failover is provided by dynamically adding cluster components to resolved object references upon resolving each cluster (4). In other words, upon resolving each cluster, a cluster component which is a part of an object reference of an object is created. Each cluster component provides to a client object resource broker (ORB) information which permits the client ORB to access the cluster object located in the name service to which this object is bound. Upon the occurrence of a failure, this information permits the client ORB to contact the cluster object to obtain another object in the same cluster to which the client ORB can then failover to. If an object reference fails during processing, the particular object reference binding associated with the specific object reference in the cluster becomes stale. - When a client invokes an invocation to a specific server, the connection to the server is accomplished using a process called binding. In order for the client to communicate with the server, it must bind with the server using the IP Address and Port No. contained in a specific object reference. Here, a binding is performed by using an object reference and performing the necessary steps to derive a concrete connection to a specific process that implements the functionality represented by that object reference. User participation in the binding process is accomplished via a “binding interceptor” which is a Java class that the user may implement as desired. Each class comprises methods of differing relevancies which are used to indicate the binding status (i.e., Bind, Bind_Succeeded, Bind_Failed, and Exception_Occurred). A “Bind” is performed by using an object reference and performing the steps necessary to derive a concrete connection to a specific process which implements the functionality represented by that object reference. Here, a Bind_Succeeded is an indication that a connection was achieved, a Bind_Failed is an indication that a connection was not established and an Exception_Occurred represents an indeterminate state between Bind_Succeeded and Bind_Failed.
- Each time a client attempts to establish a connection with a server object, a bind method is called. In accordance with the invention, if a user is provided with the knowledge that bind interceptors may be used, the user will be provided with a class containing the most relevant methods, preferably the three most relevant methods. In the preferred embodiment, the most relevant methods are Bind, Bind_Succeeded and Bind_Failed. The user then writes (specifies) the class such that the class subsequently contains the most relevant methods. When the connection to the server is being established, the user code is called (i.e., a bind interceptor is used). The bind interceptor provides a user with an option to select an alternative server in the instance where the system was operating adequately and then fails. For example, if a returned bind interceptor contains a Bind_Failed method, the user is presented with an opportunity to choose to connect to another server.
- When an attempt to send a request to the stale server is made, the client associated with the stale object reference will transparently intercept the cluster component using the binding interceptor. The interceptor will then invoke the cluster's select operation (i.e., its load balancing algorithm) to select and return to the client another object reference in the same cluster. Communication is then established between the client and the server of the newly returned object reference. As a result, the failover to one of the object references in the same cluster is transparently achieved. The failed object reference is thereafter marked as “suspect.” In an embodiment, the stale object reference is automatically removed from the cluster based on a user established preference.
- In an aspect of the invention, the Visibroker Naming Service™ permits the activation and deactivation of an implicit clustering feature and associates multiple object references with a single name. Activation of the implicit clustering feature may be accomplished using a flag located in a file, such as a configuration file, or the like. The clustering of object references in this manner becomes highly scalable because the object references may be dynamically added or removed from a cluster through cluster bind or unbind operations.
-
FIG. 4 is an illustration of a dynamic bind and unbind operation of cluster objects in accordance with the preferred embodiment of the invention. When implicit clustering is activated, object reference bindings using the same name are clustered together in the same cluster. A default load balance algorithm, such as Smart Round Robin, is used for implicit clustering. This algorithm may be changed at the discretion of the user. - When a call to a name within the clustered object references is invoked (1), the naming service load balances (2) over the set of object references associated with the name and distributes the load accordingly (4). As a result, the need to recreate clusters is eliminated because the load balancing is performed among a common group of object reference binders.
-
FIG. 5 is a flow chart of a method for load balancing in accordance with the preferred embodiment of the invention. In accordance with the preferred embodiment, the method is implemented when a client invokes a cluster located under a particular context or specific directory, as indicated instep 500. A load balance is performed to return an object reference which is bound to the cluster, as indicated instep 510. Load balancing is performed using a load balance algorithm (e.g., Round Robin). The specific algorithm which is used to perform load balancing is specified upon creation of each naming service cluster. An object reference is forwarded to the cluster, as indicated instep 520. Next, cluster components are dynamically added to resolved object references subsequent to load balancing each cluster to provide failover, as indicated instep 530. Failover is provided in the manner discussed previously. Next, the client communicates with the server associated with the object reference which was selected and forwarded to the client, as indicated instep 540. -
FIG. 6 is a flow chart illustrating dynamic bind and unbind operations of cluster objects in accordance with the preferred embodiment of the invention. In accordance with this embodiment, the method is implemented when implicit clustering is activated, as indicated instep 600. Next, a cluster containing the clustered object reference bindings using the same name is invoked, as indicated instep 610. Load balancing is performed on the clustered object references using a default load balance algorithm, as indicated instep 620. This algorithm may be changed at the discretion of the user, e.g., from a Round Robin algorithm to a different algorithm. A selected object reference based on the load balance is returned upon completion of load balancing, as indicated instep 630. Next, the client communicates with the server associated with the object reference which was selected and forward to the client, as indicated instep 640. - Methods in accordance with the invention permit transparent load balancing among multiple object references in the same cluster to be achieved. In addition, transparent failover among object references in the same cluster is provided. Method according to the invention also provide a dynamic addition of new object references into a cluster via binding, along with the dynamic removal of old object references from a cluster via unbinding. Moreover, automatic detection of stale object references in a cluster and clean up based on the preference of a client is achieved. Further, such methods provide a consistent application of the load balancing algorithms per cluster. New load balancing algorithms may be up-loaded to the system as required. The method eliminates the need to change the client code or server code such that manual configurations are not required.
- While the invention has been particularly shown and described with reference to a preferred embodiment thereof, it will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the spirit and scope of the invention.
Claims (1)
1. A method for load balance of Common Object Request Broker Architecture (CORBA) object servers, comprising:
invoking a name service cluster;
indicating to a user whether bind interceptors are in use; and
providing the user with a class having relevant methods if bind interceptors are in use.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US14/589,441 US20150127801A1 (en) | 2000-12-14 | 2015-01-05 | Name service object clustering |
Applications Claiming Priority (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US25565100P | 2000-12-14 | 2000-12-14 | |
US10/017,495 US8566849B2 (en) | 2000-12-14 | 2001-12-14 | Name service object clustering |
US14/031,382 US8966497B2 (en) | 2000-12-14 | 2013-09-19 | Name service object clustering |
US14/589,441 US20150127801A1 (en) | 2000-12-14 | 2015-01-05 | Name service object clustering |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US14/031,382 Continuation US8966497B2 (en) | 2000-12-14 | 2013-09-19 | Name service object clustering |
Publications (1)
Publication Number | Publication Date |
---|---|
US20150127801A1 true US20150127801A1 (en) | 2015-05-07 |
Family
ID=26689952
Family Applications (3)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/017,495 Expired - Fee Related US8566849B2 (en) | 2000-12-14 | 2001-12-14 | Name service object clustering |
US14/031,382 Expired - Fee Related US8966497B2 (en) | 2000-12-14 | 2013-09-19 | Name service object clustering |
US14/589,441 Abandoned US20150127801A1 (en) | 2000-12-14 | 2015-01-05 | Name service object clustering |
Family Applications Before (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/017,495 Expired - Fee Related US8566849B2 (en) | 2000-12-14 | 2001-12-14 | Name service object clustering |
US14/031,382 Expired - Fee Related US8966497B2 (en) | 2000-12-14 | 2013-09-19 | Name service object clustering |
Country Status (1)
Country | Link |
---|---|
US (3) | US8566849B2 (en) |
Families Citing this family (20)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6751646B1 (en) * | 2000-06-01 | 2004-06-15 | Sprint Communications Company L.P. | Method and apparatus for implementing CORBA compliant name services incorporating load balancing features |
US6904602B1 (en) | 2000-11-30 | 2005-06-07 | Sprint Communications Company L.P. | Method and apparatus for implementing persistence in trader services associated with a computer system |
US7043731B2 (en) * | 2001-07-12 | 2006-05-09 | Qwest Communications International, Inc. | Method and system for distributing access to group of objects based on round robin algorithm and only when the object is available |
US7036039B2 (en) * | 2002-03-29 | 2006-04-25 | Panasas, Inc. | Distributing manager failure-induced workload through the use of a manager-naming scheme |
US8103748B2 (en) * | 2002-05-20 | 2012-01-24 | International Business Machines Corporation | Rule-based method and system for managing heterogenous computer clusters |
JP4019817B2 (en) * | 2002-06-28 | 2007-12-12 | 株式会社日立製作所 | Distributed object control method and its implementation system |
EP1406171A1 (en) * | 2002-10-04 | 2004-04-07 | Hewlett-Packard Company | Data processing system and method |
US7424721B2 (en) | 2003-05-19 | 2008-09-09 | Sun Microsystems, Inc. | Inter-object communication interface bridge |
US7269603B1 (en) | 2003-12-17 | 2007-09-11 | Sprint Communications Company L.P. | Enterprise naming service system and method |
US7444536B1 (en) * | 2004-04-16 | 2008-10-28 | Sun Microsystems, Inc. | RMI-IIOP request failover mechanism |
US7779116B2 (en) * | 2006-02-09 | 2010-08-17 | International Business Machines Corporation | Selecting servers based on load-balancing metric instances |
US8799918B2 (en) * | 2006-09-11 | 2014-08-05 | Microsoft Corporation | Dynamic network load balancing using roundtrip heuristic |
US20100121906A1 (en) * | 2008-11-11 | 2010-05-13 | Electronics And Telecommunications Research Institute | Device management apparatus and method for home network system |
CN104980510B (en) * | 2015-06-17 | 2018-03-27 | 中国人民解放军国防科学技术大学 | A kind of method of the transparent clustering of CORBA Distributed Applications |
US10237339B2 (en) | 2016-08-19 | 2019-03-19 | Microsoft Technology Licensing, Llc | Statistical resource balancing of constrained microservices in cloud PAAS environments |
US10671245B2 (en) | 2017-03-29 | 2020-06-02 | Microsoft Technology Licensing, Llc | Collection and control of user activity set data and activity set user interface |
US10732796B2 (en) | 2017-03-29 | 2020-08-04 | Microsoft Technology Licensing, Llc | Control of displayed activity information using navigational mnemonics |
US10853220B2 (en) | 2017-04-12 | 2020-12-01 | Microsoft Technology Licensing, Llc | Determining user engagement with software applications |
US10693748B2 (en) | 2017-04-12 | 2020-06-23 | Microsoft Technology Licensing, Llc | Activity feed service |
US11580088B2 (en) | 2017-08-11 | 2023-02-14 | Microsoft Technology Licensing, Llc | Creation, management, and transfer of interaction representation sets |
Citations (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5437025A (en) * | 1993-01-26 | 1995-07-25 | International Business Machines Corporation | System and method for run time configuration of objects in an object oriented computing environment |
US5864866A (en) * | 1997-03-26 | 1999-01-26 | International Business Machines Corporation | Apparatus and method for providing externalization in an object-oriented environment |
US5941950A (en) * | 1996-11-07 | 1999-08-24 | Samsung Electronics, Co., Ltd. | Socket binding method in communication system using socket function |
US6209018B1 (en) * | 1997-11-13 | 2001-03-27 | Sun Microsystems, Inc. | Service framework for a distributed object network system |
US6606643B1 (en) * | 2000-01-04 | 2003-08-12 | International Business Machines Corporation | Method of automatically selecting a mirror server for web-based client-host interaction |
US6633923B1 (en) * | 1999-01-29 | 2003-10-14 | Iona Technologies Inc. | Method and system for dynamic configuration of interceptors in a client-server environment |
US7082553B1 (en) * | 1997-08-25 | 2006-07-25 | At&T Corp. | Method and system for providing reliability and availability in a distributed component object model (DCOM) object oriented system |
Family Cites Families (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5452447A (en) * | 1992-12-21 | 1995-09-19 | Sun Microsystems, Inc. | Method and apparatus for a caching file server |
JP3212007B2 (en) * | 1993-04-26 | 2001-09-25 | インターナショナル・ビジネス・マシーンズ・コーポレーション | Operating system environment boot method and system |
US5742759A (en) * | 1995-08-18 | 1998-04-21 | Sun Microsystems, Inc. | Method and system for facilitating access control to system resources in a distributed computer system |
US7043731B2 (en) * | 2001-07-12 | 2006-05-09 | Qwest Communications International, Inc. | Method and system for distributing access to group of objects based on round robin algorithm and only when the object is available |
-
2001
- 2001-12-14 US US10/017,495 patent/US8566849B2/en not_active Expired - Fee Related
-
2013
- 2013-09-19 US US14/031,382 patent/US8966497B2/en not_active Expired - Fee Related
-
2015
- 2015-01-05 US US14/589,441 patent/US20150127801A1/en not_active Abandoned
Patent Citations (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5437025A (en) * | 1993-01-26 | 1995-07-25 | International Business Machines Corporation | System and method for run time configuration of objects in an object oriented computing environment |
US5941950A (en) * | 1996-11-07 | 1999-08-24 | Samsung Electronics, Co., Ltd. | Socket binding method in communication system using socket function |
US5864866A (en) * | 1997-03-26 | 1999-01-26 | International Business Machines Corporation | Apparatus and method for providing externalization in an object-oriented environment |
US7082553B1 (en) * | 1997-08-25 | 2006-07-25 | At&T Corp. | Method and system for providing reliability and availability in a distributed component object model (DCOM) object oriented system |
US6209018B1 (en) * | 1997-11-13 | 2001-03-27 | Sun Microsystems, Inc. | Service framework for a distributed object network system |
US6633923B1 (en) * | 1999-01-29 | 2003-10-14 | Iona Technologies Inc. | Method and system for dynamic configuration of interceptors in a client-server environment |
US6606643B1 (en) * | 2000-01-04 | 2003-08-12 | International Business Machines Corporation | Method of automatically selecting a mirror server for web-based client-host interaction |
Non-Patent Citations (1)
Title |
---|
Carla, Load Balacing for eNetwork Communications Server, 04/1999. * |
Also Published As
Publication number | Publication date |
---|---|
US20020099970A1 (en) | 2002-07-25 |
US20140089512A1 (en) | 2014-03-27 |
US8966497B2 (en) | 2015-02-24 |
US8566849B2 (en) | 2013-10-22 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US8966497B2 (en) | Name service object clustering | |
US7406692B2 (en) | System and method for server load balancing and server affinity | |
KR100330936B1 (en) | Workload management amongst server objects in a client/server network with distributed objects | |
KR100614265B1 (en) | A duplicated naming service in a distributed processing system | |
US6571274B1 (en) | Clustered enterprise Java™ in a secure distributed processing system | |
US6581088B1 (en) | Smart stub or enterprise javaTM bean in a distributed processing system | |
US6385643B1 (en) | Clustered enterprise Java™ having a message passing kernel in a distributed processing system | |
US6360256B1 (en) | Name service for a redundant array of internet servers | |
EP2843565A1 (en) | Distributed Application Server | |
GB2325999A (en) | Workload management in a client/server computer network with distributed objects | |
US20020174259A1 (en) | Distributable multi-daemon configuration for multi-system management | |
JP2001216174A (en) | Application substituting method and storage medium in which application substitution program is stored | |
JP4123440B2 (en) | Object-oriented network distributed computing system, load balancing apparatus and server thereof | |
CN112911009A (en) | Access load balancing system and method | |
Carr et al. | IIOP and SOAP Failover in Static Clusters | |
JP2005258757A (en) | Application service management system, method, and program |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: BORLAND SOFTWARE CORPORATION, CALIFORNIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:ZHAO, CUIE;KASARAVALLI, VISHWANATH;NATARAJAN, VIJAYKUMAR;SIGNING DATES FROM 20020206 TO 20020225;REEL/FRAME:034635/0560 |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |