Method and system combining state replication and operational-replay synchronization

• US 7,543,000 B2
• Filed: 01/23/2006
• Issued: 06/02/2009
• Est. Priority Date: 01/23/2006
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: International Business Machines Corporation
• Inventors: Castro, Paul C., Rayfield, James T., Leff, Avraham, Yeh, Danny L., Konuru, Ravindranath
• Primary Examiner(s): Vital; Pierre M
• Assistant Examiner(s): LIAO, JASON G
• Application Number:
  US11/337,393
• Publication Number:
  US 20070185920A1
• Time in Patent Office: 1,226 Days
• Field of Search: None
• US Class Current: 1/1
• CPC Class Codes: G06F 16/273 Asynchronous replication or reconciliation
• CPC Class Codes: Y10S 707/99952 Coherency, e.g. same view to multiple users

Abstract

A system, method and computer program product for synchronizing replicas of shared data structures associated with one or more computer systems. The method comprises: evaluating a metric for performing a replica synchronization operation on a first computer system according to a first synchronization method; evaluating the metric for performing a replica synchronization operation on the first computer system according to a second synchronization method; and, selecting, at synchronization time, based on the evaluated metric, whether to use the first or second synchronization methods, and communicating a command to a second computer system to replicate a shared data structure based on the selected synchronization method.

Claims

1. A method for synchronizing replicas of shared data structures of a transactional application performing eager commit after work, associated with one or more computer systems requiring consistency guarantees, at least one said one or more computer system intermittently-connected to other computer systems via a network and executing operations associated with a shared data structure of the transactional application while in a disconnected state, said method comprising:

at a first computer system, while in a disconnected state, logging information related to said executed operations of said shared data structure in both an Operational Log and a State Log; and

,

when said disconnected first computer system reconnects, dynamically at said time of reconnecting, evaluating a metric for performing a replica synchronization operation on said first computer system according to a first synchronization method using information logged in said Operational Log;

evaluating the metric for performing a replica synchronization operation on said first computer system according to a second synchronization method using information logged in said State Log; and

,

dynamically selecting, at synchronization time, based on the evaluated metric, whether to use said first or second synchronization methods, and communicating a command to a second computer system to replicate said shared data structure based on said selected synchronization method,

said evaluated metric including a cost metric based on an amount of a CPU time required to do a replica synchronization where for said first synchronization method, a first CPU time is estimated from an execution time information relating to said executed operation as logged in the Operational Log when in said disconnected state weighted by the ratio of a CPU speed of said first computer system versus a CPU sped of said second computer system; and

, for said second synchronization method, a second CPU time is estimated from a number of entries in the State Log multiplied by an estimated processing time per state change of said second computer; and

forwarding one of said Operational Log recorded at said first computer system or said State Log to said second computer system for replica synchronization thereat in accordance with said evaluated cost metric, thereby ensuring consistency across the shared data structures of the transactional application at said one or more computer systems.

2. The method for synchronizing as claimed in claim 1, wherein said first synchronization method comprises a state-based synchronization method.

3. The method for synchronizing as claimed in claim 2, further comprising:

enabling an application executing on a first computer system to access and execute operations on one or more replicas; and

, in response to said accessing and executing,

generating a State Log to record usage of stored data.

4. The method for synchronizing as claimed in claim 1, wherein said second synchronization method comprises an operational-replay synchronization method.

5. The method for synchronizing as claimed in claim 4, further comprising:

enabling an application executing on a first computer system to access and execute operations on one or more replicas, wherein in response to said accessing said executing, a further step of generating an Operational Log to record usage of stored data.

6. The method for synchronizing as claimed in claim 1, further comprising:

evaluating said metric based on one or more characteristics of a communications network over which said one or more computer systems communicate.

7. The method for synchronizing as claimed in claim 1, further comprising:

evaluating said metric based on relative CPU speeds of said one or more computers.

8. The method for synchronizing as claimed in claim 5, further comprising:

evaluating said metric based on one of;

a size of said State Log or said Operational Log.

9. The method for synchronizing as claimed in claim 1, wherein said metric is evaluated based on power consumed by a computer system when performing said replicating.

10. The method for synchronizing as claimed in claim 6, wherein said metric is evaluated based on an amount of network bandwidth available.

11. The method for synchronizing as claimed in claim 1, wherein said selecting of said replica synchronization operation is evaluated on a transaction basis.

12. The method for synchronizing as claimed in claim 1, wherein said selecting of said replica synchronization operation is evaluated for an entire synchronization session.

13. The method for synchronizing as claimed in claim 1, further comprising:

performing a sub-optimal replica synchronization operation to retry the replica synchronization if an optimal algorithm replica synchronization operation fails.

14. The method for synchronizing as claimed in claim 1, further comprising:

selecting, at synchronization time, whether to use said first or second synchronization methods based on a policy.

15. The method for synchronizing as claimed in claim 1, further comprising:

wherein said replica synchronization operation preserves transaction semantics.

16. A system for synchronizing replicas of shared data structures of a transactional application performing eager commit after work for one or more computer devices requiring consistency guarantees, at least one said one or more computer devices intermittently-connected to other computer devices via a network and executing operations associated with a shared data structure of the transactional application while in a disconnected state, said method comprising:

means for logging information related to said executed operations of said shared data structure in both an Operational Log and a State Log at a first computer device while in a disconnected state; and

,

means for executing at said first computer device at said time of reconnecting to said network, for evaluating a metric associated with performing a replica synchronization operation on that reconnected computer device according to first and second synchronization methods using information logged in both said Operational Log and said State Log, respectively;

means for dynamically selecting, at synchronization time, based on the evaluated metric, whether to use said first or second synchronization methods; and

means for communicating a command to a second computer device to replicate said shared data structure based on said selected synchronization method, said means forwarding one of said Operational Log or said State Log recorded at said first computer device to said second computer device for replica synchronization in accordance with said evaluated cost metric.

said evaluated metric including a cost metric based on an amount of a CPU time required to do a replica synchronization where for said first synchronization method, a first CPU time is estimated from an execution time information relating to said executed operation as logged in the Operational Log when in said disconnected state weighted by the ratio of a CPU speed of said first computer device versus a CPU speed of said second computer device; and

, for said second synchronization method, a second CPU time is estimated from a number of entries in the State Log multiplied by an estimated processing time per state change of said second computer; and

forwarding one of said Operational Log recorded at said first computer system or said State Log to said second computer system for replica synchronization thereat in accordance with said evaluated cost metric, thereby ensuring consistency across the shared data structures of the transactional application at said one or more computer systems.

17. The system for synchronizing as claimed in claim 16, wherein said first synchronization method comprises a state-based synchronization method, said metric being evaluated based on parameters provided in a State Log that reflect usage of stored data.

18. The system for synchronizing as claimed in claim 16, wherein said second synchronization method comprises an operational-replay synchronization method, said metric being evaluated based on parameters provided in an Operational Log that reflect usage of stored data.

19. The system for synchronizing as claimed in claim 16, wherein said one or more computer devices intermittently connect to said communications network.

20. The system for synchronizing as claimed in claim 16, wherein said one or more computer devices are adapted for communicating over a communications network defining a distributed client/server environment.

21. The system for synchronizing as claimed in claim 16, wherein said one or more computer devices are adapted for communicating over a communications network defining a peer-to-peer environment.

22. A program storage device readable by a machine, tangibly embodying a program of instructions executable by the machine to perform method steps for synchronizing replicas of shared data structures of a transactional application performing eager commit after work, associated with one or more computer systems requiring consistency guarantees, at least one said one or more computer system intermittently-connected to other computer systems via a network and executing operations associated with a shared data structure of the transactional application while in a disconnected state, said program storage device executing instructions for performing method steps of:

;

at a first computer system, while in a disconnected state, logging information related to said executed operations of said shared data structure in both an Operational Log and a State Log; and

,

when said disconnected first computer system reconnects, dynamically at said time of reconnecting, evaluating a metric for performing a replica synchronization operation on said first computer system according to a first synchronization method using information logged in said Operational Log;

evaluating the metric for performing a replica synchronization operation on said first computer system according to a second synchronization method using information logged in said State Log; and

,

dynamically selecting, at synchronization time, based on the evaluated metric, whether to use said first or second synchronization methods, and communicating a command to a second computer system to replicate said shared data structure based on said selected synchronization method,

said evaluated metric including a cost metric based on an amount of a CPU time required to do a replica synchronization where for said first synchronization method, a first CPU time is estimated from an execution time information relating to said executed operation as logged in the Operational Log when in said disconnected state weighted by the ratio of a CPU speed of said first computer system versus a CPU speed of said second computer system; and

, for said second synchronization method, a second CPU time is estimated from a number of entries in the State Log multiplied by an estimated processing time per state change of said second computer; and

forwarding one of said Operational Log recorded at said first computer system or said State Log to said second computer system for replica synchronization thereat in accordance with said evaluated cost metric, thereby ensuring consistency across the shared data structures of the transactional application at said one or more computer systems.