Oracle International Corporation

Sun Microsystems, Inc.

Oracle America, Inc.

Mahesh Kannan

Darpan Dinker

Pramod Gopinath

Rajiv Mordani

Rajendra Inamdar

Sanjeeb Kumar Sahoo

Sandeep Shrivastava

Michael Cico

Anthony Vlatas

Suveen R Nadipalli

Abhijit Kumar

Kshitiz Saxena

Shreedhar Ganapathy

Carla Mott

Described herein are systems and methods that can support bridging VCNs in a manner which addresses customer needs with respect to access mechanisms, connectivity, regional availability, service complexity, and customer isolation/security. The system and methods that can support bridging VCNs as described herein have particular utility with respect to providing etcd-as-a-Service. In particular embodiments virtual network interface (VNIC) features are used to implement a bridge between a subnet of an etcd VCN and a subnet of a customer VCN in order to bridge the subnets.

Virtual interface system and method for multi-tenant cloud networking

In accordance with an embodiment, described herein is a system and method for supporting a reactive response using a dependency injection (DI) framework. The DI framework can determine the dependencies of a response object, and invoke a plurality of services for retrieving dependency objects from backend systems to satisfy those dependencies. Each service can return a reactive object, which the DI framework can match to a dependency object, thereby enabling the DI framework to orchestrate asynchronous concurrent calls to the services on behalf of an application. Each reactive object can be used to retrieve a corresponding dependency object at a later time. The DI framework can use the dependency object to compose the response object and inject the response object to an application at the server environment.

Systems and method for supporting reactive responses using a dependency injection framework

In accordance with an embodiment, described herein is a system and method rule-based elasticity support in an application server environment. The method can begin with providing, at one or more computers, including an application server environment executing thereon, a plurality of deployable resources which can be used within the application server environment, one or more partitions, an administration server, the administration server comprising a diagnostic framework, a rules framework, and an elastic service manager, and a dynamic cluster for use by the one or more partitions. The method can continue with monitoring, by the diagnostic framework, metrics associated with the one or more partition and the dynamic cluster. The method can then trigger, by the rules framework, the action based upon a comparison between one of the one or more rules and the monitored metrics associated with the one or more partitions and the dynamic cluster.

System and method for rule-based elasticity in a multitenant application server environment

In accordance with an embodiment, described herein is a system and method for supporting interceptors in an application server environment. The method can provide, at one or more computers, including an application server environment executing thereon, a plurality of deployable resources which can be used within the application server environment, one or more partitions, wherein each partition provides an administrative and runtime subdivision of a domain, and an interceptor framework, the interceptor framework comprising a plurality of interceptors. The method can further select and trigger, on a call for a method invocation, an interceptor chosen from the plurality of interceptors. The method can interrupt, by the triggered interceptor, the call for the method invocation, wherein the interceptor is selected based at least upon the call for a method invocation.

System and method for interceptors in a multitenant application server environment

A system and method for elasticity management of services for use with a cloud computing environment. In accordance with an embodiment, a cloud platform enables provisioning of enterprise software applications within a cloud environment, including packaging enterprise applications as service definition packages (SDP), and instantiating the services using service management engines (SME). In an embodiment, an elasticity manager can be used to determine the health of the services, and to take appropriate actions, including detecting events, issuing alerts and/or notifying the orchestration engine to manage the service lifecycle, e.g., to respond to an increased demand for particular services.

System and method for elasticity management of services with a cloud computing environment

A method, system, and medium are disclosed for performing failover data replication with colocation of session state data. In servicing a client request, a first session is created on a primary server. A first portion of session data comprises a state of the first session and is stored on the primary server. An identifier of the first session is stored on the primary server. One or more backup servers are selected for backup of the first portion of session data. A second session is created on the primary server. A second portion of session data comprises a state of the second session and is stored on the primary server. The same backup server(s) are selected for backup of the second portion based on the stored identifier of the first session. The primary server replicates the first and second portions of session data into memory space of the backup servers.

Failover data replication with colocation of session state data

A method, system, and medium are disclosed for performing transparent failover in a cluster server system. The cluster includes a plurality of servers. In servicing a client request, a primary server replicates session data for the client into memory space of one or more backup servers. The primary server sends a response to the client, wherein the response includes an indication of the one or more backup servers. When the client sends a subsequent request, it includes an indication of the backup servers. If the primary server is unavailable, the cluster determines a recovery server from among the backup servers indicated by the request. The chosen recovery server would then service the request.

Failover data replication to a preferred list of instances

Entities within a cluster are uniquely identified with a node ID and an engine ID. The node ID uniquely identifies a node within a cluster of nodes and the engine ID uniquely identifies one of several engines included in the node. Entities may be further identified with a cluster ID, an engine type ID, and/or a virtual server ID. At least some of these IDs may be included in communications received from clients and used to route the communications to the cluster entity identified by the included IDs.

System and method for uniquely identifying processes and entities in clusters

A system may include a client and a distributed data manager coupled to the client. The distributed data manager may include a data store storing a data object that includes several sub-elements. The client is configured to update a portion of the data object by sending a message to the distributed data manager. The message specifies one of the sub-elements of the data object to be updated and includes a new value of that sub-element but does not include a new value of the entire data object. The distributed data manager is configured to perform updates to the data object in the data store dependent on which of the sub-elements of the data object are specified by the client.

Distributed data system with incremental data updates

A cluster topology self-healing process is performed in order to replicate a data set stored on a failed node from a first node storing another copy of the data set to a second non-failed node. The self-healing process is performed by: locking one of several domains included in the data set, where locking that domain does not lock any of the other domains in the data set; storing data sent from the first node to the second node in the domain; and releasing the domain. This process of locking, storing, and releasing is repeated for each other domain in the data set. Each domain may be locked for significantly less time than it takes to copy the entire data set. Accordingly, client access requests targeting a locked domain will be delayed for less time than if the entire data set is locked during the self-healing process.

Item and method for performing a cluster topology self-healing process in a distributed data system cluster

Data stored within a cluster may be distributed among nodes each storing a portion of the data. The data may be replicated wherein different nodes store copies of the same portion of the data. In response to detecting the failure of a node, the cluster may initiate a timeout period. If the node remains failed throughout the timeout period, the cluster may copy the portion of the data stored on the failed node onto one or more other nodes of the cluster. If the node returns to the cluster during the timeout period, the cluster may maintain the copy of the data on the previously failed node without copying the portion of the data stored on the failed node onto any other nodes. By delaying self-healing of the cluster for the timeout period, an unbalanced data distribution may be avoided in cases where a failed node quickly rejoins the cluster.

System and method for reforming a distributed data system cluster after temporary node failures or restarts

A distributed system provides for separate management of dynamic cluster membership and distributed data. Nodes of the distributed system may include a state manager and a topology manager. A state manager handles data access from the cluster. A topology manager handles changes to the dynamic cluster topology. The topology manager enables operation of the state manager by handling topology changes, such as new nodes to join the cluster and node members to exit the cluster. A topology manager may follow a static topology description when handling cluster topology changes. Data replication and recovery functions may be implemented, for example to provide high availability.

Growing community of inventors

San Jose, CA, United States of America

Mahesh Kannan