Abstract: Embodiments of the present invention relate to invoking and managing a failover of a storage account between partitions within a distributed computing environment, where each partition represents a key range of data for the storage account. The partitions affected by the failover include source partitions hosted on a primary storage stamp and destination partitions hosted on a secondary storage stamp, where the storage account's data is being actively replicated from the primary to the secondary storage stamp. Upon receiving a manual or automatic indication to perform the failover, configuring the source partitions to independently perform flush-send operations (e.g., distributing pending messages as a group) and then configuring the destination partitions to independently perform flush-replay operations (e.g., aggressively replaying currently pending transactions).

Abstract: Embodiments of the present invention relate to invoking and managing a failover of a storage account between partitions within a distributed computing environment, where each partition represents a key range of data for the storage account. The partitions affected by the failover include source partitions hosted on a primary storage stamp and destination partitions hosted on a secondary storage stamp, where the storage account's data is being actively replicated from the primary to the secondary storage stamp. Upon receiving a manual or automatic indication to perform the failover, configuring the source partitions to independently perform flush-send operations (e.g., distributing pending messages as a group) and then configuring the destination partitions to independently perform flush-replay operations (e.g., aggressively replaying currently pending transactions).

Abstract: Embodiments of the present invention relate to invoking and managing a failover of a storage account between partitions within a distributed computing environment, where each partition represents a key range of data for the storage account. The partitions affected by the failover include source partitions hosted on a primary storage stamp and destination partitions hosted on a secondary storage stamp, where the storage account's data is being actively replicated from the primary to the secondary storage stamp. Upon receiving a manual or automatic indication to perform the failover, configuring the source partitions to independently perform flush-send operations (e.g., distributing pending messages as a group) and then configuring the destination partitions to independently perform flush-replay operations (e.g., aggressively replaying currently pending transactions).

Abstract: Embodiments of the present invention relate to invoking and managing a failover of a storage account between partitions within a distributed computing environment, where each partition represents a key range of data for the storage account. The partitions affected by the failover include source partitions hosted on a primary storage stamp and destination partitions hosted on a secondary storage stamp, where the storage account's data is being actively replicated from the primary to the secondary storage stamp. Upon receiving a manual or automatic indication to perform the failover, configuring the source partitions to independently perform flush-send operations (e.g., distributing pending messages as a group) and then configuring the destination partitions to independently perform flush-replay operations (e.g., aggressively replaying currently pending transactions).

Abstract: The claimed subject matter provides a system and/or a method facilitates energy-aware connection distribution among a plurality of servers in a cluster. A set of busy servers in the cluster can be provided that each handle a high number of connections. In addition, a set of tail servers in the cluster can be managed that each maintain a low number of connections. A load skewing component gives priority to at least a subset of the set of busy servers when dispatching new connection requests from a plurality of users. In addition, the load skewing component controls the number of tail servers to maintain a sufficient number for energy-aware operation.

Abstract: The claimed subject matter provides a system and/or a method that facilitates managing a number of active servers in a cluster. A forecast component can predict at least one of login rate or number of connections in the cluster at a future time. A dynamic load analysis component can evaluate dynamic behaviors in login rate and number of connections in the cluster as a result of load dispatching. Moreover, a provisioning component can determine a number of servers in the cluster needed based at least in part on the prediction and dynamic behavior analysis. In addition, the provisioning component can include an additional margin in the number of servers needed in accordance with multiplicative factors.

Abstract: The claimed subject matter provides a system and/or a method that facilitates managing a number of active servers in a cluster. A forecast component can predict at least one of login rate or number of connections in the cluster at a future time. A dynamic load analysis component can evaluate dynamic behaviors in login rate and number of connections in the cluster as a result of load dispatching. Moreover, a provisioning component can determine a number of servers in the cluster needed based at least in part on the prediction and dynamic behavior analysis. In addition, the provisioning component can include an additional margin in the number of servers needed in accordance with multiplicative factors.

Abstract: The claimed subject matter provides a system and/or a method facilitates energy-aware connection distribution among a plurality of servers in a cluster. A set of busy servers in the cluster can be provided that each handle a high number of connections. In addition, a set of tail servers in the cluster can be managed that each maintain a low number of connections. A load skewing component gives priority to at least a subset of the set of busy servers when dispatching new connection requests from a plurality of users. In addition, the load skewing component controls the number of tail servers to maintain a sufficient number for energy-aware operation.

Abstract: Systems and methods are described for shielding a vulnerability in an application through disablement of one or more features. In an implementation, a method includes identifying a vulnerability in at least one of a plurality of features for an application module. A communication is formed for receipt by a plurality of clients to shield execution of the application module from the identified vulnerability. The communication describes that the at least one feature is to be disabled from execution in conjunction with the application module.