IMPLEMENTING FAILOVER PROCESSES BETWEEN STORAGE STAMPS
First Claim
1. A computer-implemented method in a distributed environment utilizing a processor and memory for invoking a clean failover of a storage account residing on storage stamps within the distributed computing environment, the method comprising:
- providing a primary storage stamp that includes one or more source partitions configured for accepting live traffic and for sending transactions to one or more destination partitions in order to advance replication to a secondary storage stamp;
providing the secondary storage stamp that includes the one or more destination partitions configured to replay the transactions;
performing a failover between the primary and the secondary storage stamp for a subset of the data on the primary stamp;
requesting that the one or more source partitions attempt to independently carry out a flush-send operation, wherein the flush-send operation involves distributing pending messages to the one or more destination partitions as a group; and
reconfiguring the one or more destination partitions to independently carry out a flush-replay operation, wherein the flush-replay operation involves aggressively replaying transactions currently pending at the one or more destination partitions.
2 Assignments
0 Petitions
Accused Products
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). Upon completing the flush-replay operations, designating the secondary storage stamp as a new primary storage stamp such that live traffic is directed to the new primary storage stamp.
-
Citations
20 Claims
-
1. A computer-implemented method in a distributed environment utilizing a processor and memory for invoking a clean failover of a storage account residing on storage stamps within the distributed computing environment, the method comprising:
-
providing a primary storage stamp that includes one or more source partitions configured for accepting live traffic and for sending transactions to one or more destination partitions in order to advance replication to a secondary storage stamp; providing the secondary storage stamp that includes the one or more destination partitions configured to replay the transactions; performing a failover between the primary and the secondary storage stamp for a subset of the data on the primary stamp; requesting that the one or more source partitions attempt to independently carry out a flush-send operation, wherein the flush-send operation involves distributing pending messages to the one or more destination partitions as a group; and reconfiguring the one or more destination partitions to independently carry out a flush-replay operation, wherein the flush-replay operation involves aggressively replaying transactions currently pending at the one or more destination partitions. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17)
-
-
18. One or more computer-storage media having computer-executable instructions embodied thereon, that when executed by a computing system having a processor and memory, cause the computing system to perform a method for implementing a abrupt failover of a client'"'"'s storage account from a primary storage stamp to a destination storage stamp, the method comprising:
-
experiencing a disaster at a first geo-location, wherein the primary storage stamp for the storage account exists within the first geo-location; and automatically triggering a failover from the primary storage stamp to the destination storage stamp in accordance with a predefined policy, wherein the destination storage stamp for the storage account exist in a second geo-location that is geographically remote from the first geo-location, and wherein the failover comprises; (a) disconnecting the primary storage stamp from taking client requests; (b) ensuring that an ongoing replication between the primary storage stamp and the destination storage stamp is severed such that the communication of transactions therebetween is interrupted; and (c) replaying the transactions held in a geo message log (GML) on the destination storage stamp that were delivered prior to experiencing the disaster. - View Dependent Claims (19)
-
-
20. A computer system within a distributed networking environment for conducting a clean failover for a storage account, the system comprising:
-
a primary storage stamp that includes one or more source partitions that represent a key range of initial data associated with a storage account, wherein the one or more source partitions are configured for accepting live traffic and for sending transactions to one or more destination partitions for carrying out replication thereto; a secondary storage stamp that includes the one or more destination partitions that represent a key range of replicated data associated with the storage account, wherein the one or more destination partitions are configured to replay the transactions such that the replicated data substantially mirrors content of the initial data; and a location service for invoking changes to the configuration of the one or more source partitions and for invoking changes to the configuration of the one or more destination partitions upon receiving an indication to failover from the primary storage stamp to the secondary storage stamp, wherein invoking changes to implement the failover comprises; (a) instructing the one or more source partitions to refrain from accepting live traffic; (b) instructing the one or more source partitions to independently perform a flush-send operation that attempts to flush the transactions remaining at the partitions to the secondary storage stamp; (c) instructing the one or more destination partitions to independently perform a flush-replay operation that replays pending transactions at the secondary storage stamp; (d) upon an individual destination partition, of the one or more destination partitions, substantially completing the flush-send operation, allowing the individual destination partition to commence accepting live traffic prior to others of the one or more destination partitions; and (e) upon each of the one or more destination partitions substantially completing the flush-send operation, designating the secondary storage stamp as a new primary storage stamp for the set of data failed over.
-
Specification