Resource replication service protocol

• US 20070026373A1
• Filed: 11/02/2005
• Published: 02/01/2007
• Est. Priority Date: 07/26/2005
• Status: Abandoned Application

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Robeal, Rafik, Suriyanarayanan, Guhan, Teodosiu, Dan, Cong, Shi, Robert, Christophe, Liu, Huisheng, Bjorner, Nikolaj, Golds, David, Balakrishnan, Shobana, Porkka, Joseph
• Application Number:
  US11/266,515
• Publication Number:
  US 20070026373A1
• Time in Patent Office: Days
• US Class Current: 434/322
• CPC Class Codes: G06F 8/00 Arrangements for software engineering testing or debugging G06F11/36; administrative, planning or organisation aspects of software project management G06Q10/06

Abstract

Aspects of the subject matter described herein relate to replicating resources across machines participating in a replica set. In aspects, a downstream machine requests that an upstream machine notify the downstream machine when updates to resources of the replica set occur. When such updates occur, the upstream machine notifies the downstream machine. In response thereto, the downstream machine requests resource meta-data and may include a limit as to how much resource meta-data may be sent. The upstream machine responds with the requested resource meta-data. Thereafter, the downstream machine determines which data associated with the updated resources to request and requests such data.

Claims

1. A computer-readable medium having computer-executable instructions, comprising:

requesting notification of updates to a replica set that occur on an upstream machine;

receiving notification that updates to the replica set have occurred on the upstream machine;

requesting meta-data regarding the updates, wherein the meta-data includes attributes for synchronizing local resources with resources residing on the upstream machine; and

requesting data associated with at least one of the resources based at least in part on the meta-data and local resources.

2. The computer-readable medium of claim 1, further comprising requesting a version vector from the upstream machine, wherein the version vector represents knowledge of the upstream machine regarding latest versions of resources in the replica set.

3. The computer-readable medium of claim 1, wherein requesting meta-data regarding the updates comprises sending a parameter that indicates a maximum number of records of the meta-data to return.

4. The computer-readable medium of claim 3, further comprising receiving a second number of records of the meta-data together with a value that represents an offset into the meta-data, wherein the offset indicates a last record the upstream machine reached in sending the meta-data.

5. The computer-readable medium of claim 4, further comprising sending the offset in another request to obtain additional records of the meta-data.

6. The computer-readable medium of claim 1, wherein a single connection is used for a synchronization between the upstream machine and local resources for a plurality of replica sets including the replica set.

7. The computer-readable medium of claim 1, wherein requesting notification of updates to a replica set that occur on an upstream machine comprises requesting that a version vector associated with the upstream machine is sent when updates have occurred on the upstream machine, and wherein receiving notification that updates to the replica set have occurred on the upstream machine comprises receiving the version vector.

8. A method implemented at least in part by a machine, comprising:

receiving a first request for notification of updates that occur to a first data store;

providing the notification after an update occurs to the first data store;

receiving a second request for meta-data regarding the update, wherein the meta-data includes attributes for use in determining whether data associated with a resource of the first data store needs to be sent to a second data store to synchronize the second data store with the first data store; and

in response to the second request, providing at least some of the meta-data.

9. The method of claim 8, further comprising:

receiving a third request for a version vector, wherein the version vector represents knowledge regarding latest versions of resources in the replica set that reside on the first data store; and

in response to the third request, providing the version vector.

10. The method of claim 9, further comprising refraining from sending the version vector until after the third request is received.

11. The method of claim 8, wherein the second request includes a parameter that indicates an amount of meta-data to provide in response to the second request.

12. The method of claim 11, further comprising providing an offset that indicates a position in the meta-data that was reached in providing at least some of the meta-data.

13. The method of claim 12, further comprising:

receiving a third request that includes the offset; and

in response to the third request, providing more of the meta-data starting at the offset.

14. The method of claim 11, further comprising indicating that all of the meta-data has been provided.

15. The method of claim 8, wherein the method defines at least part of a communication protocol between at least two machines.

16. At least one computer-readable medium containing instructions which when executed by a computer, perform actions, comprising:

at an interface, receiving an instruction to provide meta-data associated with updates to resources involved in a replica set, wherein the meta-data includes attributes for synchronizing resources in at least two data stores, and wherein the instruction is associated with a value that indicates a maximum amount of the meta-data to provide; and

in response thereto, attempting to locate at least some of the meta-data up to the maximum amount and providing the at least some of the meta-data if located.

17. The at least one computer-readable medium of claim 16, wherein the instruction includes a delta version vector that indicates which resources have been updated.

18. The at least one computer-readable medium of claim 16, further comprising providing an offset that indicates a position in the meta-data that was reached in providing at least some of the meta-data.

19. The at least one computer-readable medium of claim 18, further comprising:

at the interface, receiving the offset with another instruction to provide the meta-data; and

in response thereto, locating more of the meta-data up to the maximum amount based at least in part on the offset.

20. The at least one computer-readable medium of claim 16, wherein the value that indicates a maximum amount of the meta-data to provide is received at the interface together with the instruction.