Dell Products Inc.

Emc IP Holding Company LLC

Johnson Controls Technology Company

Mukesh Sharma

George Mathew

Murthy Mamidi

Neelkanth S Gupte

Vijayasimha Reddy Naga

Tejas Mahendra

Shefali Gautam

Akshay S Baljekar

A method for managing network traffic includes: identifying, by a source pod, a port of a first service; in response to the identifying the port of the first service, connecting, by the source pod, to the port of the first service; receiving, by the source pod, a first notification from the first service, after the first notification: identifying, by the source pod, a port of a second service; in response to the identifying the port of the second service, connecting, by the source pod, to the port of the second service; receiving, by the source pod, a second notification from the second service; and upon receiving the second notification, sending, by the source pod, network traffic to the second service.

Method and system for optimizing internal network traffic in Kubernetes

Embodiments for performing load balancing in a filesystem of a distributed network comprising worker nodes accessing shared resources that are controlled by distributed locks to grant and prevent access from clients, by assigning a range of directory entries to each worker node, and providing feedback from each worker node to a load balancer to expose an internal state of acquired resources and other parameters of each worker node. In response to periodic updates of the directory ranges to be collocated, the system maintains directory ranges in each worker so that complete subtrees of the directory tree fit in a single range assigned to a worker. Upon receipt of a client request to access a data asset, the load balancer selects the most optimum worker to satisfy the request based on the worker internal states and other parameters.

Intelligent load balancing in a distributed system

A system for continuous manageability of Kubernetes clusters is described. A system identifies a node, in a cluster of nodes, which failed to communicate with the cluster of nodes. The system identifies an application, which executed on the identified node, and which enabled continuous availability of cluster management for nodes in the cluster until when the identified node failed. The system identifies another node, which is already in the cluster of nodes, and which satisfies a prerequisite for executing the identified application, as a replacement node for the identified node that failed. The system installs the identified application on the replacement node in the cluster. The system enables, by the replacement node executing the identified application, continuous availability of cluster management for multiple nodes in the cluster.

Continuous manageability of Kubernetes clusters

Upon completing replicating a file set from a source to destination, a snapshot taken of the file set is maintained at the source. The file set includes a namespace file having metadata and other files having content data. Verification is started on the file set replicated to the destination. While the verification is in-progress, a next replication cycle is started. Upon detecting corruption in the namespace file, the next replication cycle is paused and any changes to the file set are rolled back. The snapshot being maintained at the source is fetched. The namespace file having the corruption is replaced with the namespace file from the snapshot being maintained at the source. Other files in the file set having the content data are not replaced.

Fast recovery for replication corruptions

Embodiments for simulating timing-related error conditions in a distributed system, by allowing a user to define a fault map specifying one or more faults to be committed by components in the distributed system. These generated fault events are to be executed in different components of the distributed system in a serialized distributed order. An event injection process delivers the fault map messages to the nodes in the distributed system, and the nodes then execute an operation sequence containing the fault events in the proper order as coordinated by the event injection process. The faults are then committed by the associated components in the nodes. Execution of these fault events occurs before, after or during a regular component procedure or action to simulate the desired timing-related error.

Fault definition and injection process to simulate timing based errors in a distributed system

Embodiments of the present disclosure are directed to a heating and cooling system includes a heat exchanger configured to place an airflow and a refrigerant in thermal communication with one another, where the heat exchanger has a coil and a plurality of fans coupled to the coil, and where the plurality of fans is arranged in an array adjacent to the coil.

Growing community of inventors

Pune, India

Mukesh Sharma