Microsoft Technology Licensing, LLC

Chittur Padmanabhan Subbaraman

Abolade Gbadegesin

Vishal Vikram Ghotge

Megan Galbraith Donahue

Yasser Elsayed Shaaban

Sunita Shrivastava

Peter J Torr

Darin Miller

Jorge I Raastroem

Timothy Daniel Noonan

Rachel Jiang

Adrian Dragomir

Marc David McClure

Jianping Yin

Gregory Arthur De Souza

Pavan Rajamohan Hullumane

Joseph M Joy

Christopher L Darling

Marc David Mcclure

Peter John Torr

The subject disclosure is directed towards a background transfer service that provides platform-level support for third party applications to queue data transfers to run in the background, including when the application is not running in the foreground. Applications may thus perform downloading and uploading tasks in the background; however the background transfer service manages the data transfer requests so as to limit each background application's ability to interfere with foreground application operations, that is, by controlling resource usage according to one or more policies.

Background transfer service for applications on mobile devices

A dependency filter object for use in a server cluster is described. In an implementation, a method includes bringing online one or more resource objects included in a dependency tree. Each of the resource objects corresponds to a resource available in a server cluster. The dependency tree includes a dependency filter object that specifies a dependency of a first one of the resource objects on a second one of the resource objects. The bringing online of the first resource object is managed according to the specified dependency on the second resource object.

Dependency filter object

In a first exemplary media implementation, one or more processor-accessible media include processor-executable instructions that, when executed, direct a system to perform actions that include: accumulating host status information at multiple hosts; and sending the accumulated host status information from the multiple hosts. In a second exemplary media implementation, one or more processor-accessible media include processor-executable instructions that, when executed, direct a system to perform actions that include: receiving host status information from multiple hosts; and making load balancing decisions responsive to the received host status information. In a third exemplary media implementation, one or more processor-accessible media include processor-executable instructions that, when executed, direct a system to perform actions that include: determining health and load information on a per application basis; and selecting an application from among multiple applications responsive to the health and load information.

Network load balancing with host status information

A failover scope comprises a node collection in a computer cluster. A resource group (e.g., application program) is associated with one or more failover scopes. If a node fails, its hosted resource groups only failover to nodes identified in each resource group's associated failover scope(s), beginning with a first associated failover scope, in order, thereby defining an island of nodes within which a resource group can failover. If unable to failover to a node of a resource group's first failover scope, failover is attempted to a node represented in any next associated failover scope, which may require manual intervention. Failover scopes may represent geographic sites, whereby each resource group attempts to failover to nodes within its site before failing over to another site. Failover scopes may be managed by the cluster runtime automatically, e.g., an added node is detectable as belonging to a site represented by a failover scope.

Failover scopes for nodes of a computer cluster

In a server cluster, a system and method is provided for mitigating redundant resource failure notifications and other problems resulting from late handling of messages. Traditional resource management can result in the generation of redundant resource failure notifications that trigger unnecessary recovery actions, or cause other cluster problems such as performing an action that has previously been handled as part of failure recovery. The present invention tracks resource failures and eliminates recovery actions for redundant resource failure notifications. An incarnation number is passed to a resource each time it is called, and is incremented whenever a resource failure notification is delivered. Failure notifications having an incarnation number lower than the current incarnation number are discarded. Message processing similarly uses an incarnation number to distinguish between queued messages that correspond to those from a currently healthy node and those from a previous incarnation of the node, which no longer have meaning.

Use of incarnation number for resource state cycling

Growing community of inventors

Carnation, WA, United States of America

Chittur Padmanabhan Subbaraman