Method and system for managing a distributed transaction process

• US 7,587,434 B2
• Filed: 08/29/2003
• Issued: 09/08/2009
• Est. Priority Date: 10/01/2002
• Status: Active Grant

• Current Assignee: Conduent Business Services, LLC (Conduent, Inc.)
• Original Assignee: ACS State & Local Solutions Incorporated (Conduent, Inc.)
• Inventors: Zhu, Zheng, Solitro, Pasquale, Wiles, Josh A., Zou, Kevin
• Primary Examiner(s): Breene; John E
• Assistant Examiner(s): Bullock; Joshua
• Application Number:
  US10/650,994
• Publication Number:
  US 20040088298A1
• Time in Patent Office: 2,202 Days
• Field of Search: 707/204, 707/200, 707/10
• US Class Current: 1/1
• CPC Class Codes: G06F 16/27 Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
• CPC Class Codes: Y10S 707/99955 Archiving or backup

Abstract

Systems and methods for managing a distributed transaction process include an active transaction manager that manages transactions with an active database, a latent transaction manager that manages transactions with a merge database, a transaction log that reflects the set of transactions in the active database that are not affiliated with the transactions in the merge database, and a merge manager that uses the transaction log to determine whether to transfer control of the merge database to the active transaction manager. Systems and methods may further instruct the active transaction manager to halt transactions with the active database while the merge database is updated to reflect a set of transactions affiliated with the set of transactions in the transaction log, and instruct the active transaction manager to subsequently manage transactions to the active database and the merge database.

Claims

1. A method for managing a distributed transaction system, comprising:

managing transactions with at least an active database by an active transaction manager, where the active database reflects an application of a set of active transactions;

managing transactions with a merge database, where the merge database reflects an application of a first subset of the set of active transactions;

generating discrepancy transaction log information that reflects a set of discrepancy transactions that is distinct from the first subset of active transactions, the discrepancy transactions consisting of active transactions not yet applied to the merge database;

determining whether to transfer control of the merge database to the active transaction manager; and

if a determination is made not to transfer control of the merge database to the active transaction manager,

instructing a latent transaction manager to apply the discrepancy transactions to the merge database to reflect the set of discrepancy transactions reflected in the discrepancy transaction log information, and

instructing the active transaction manager to continue to manage transactions with the active database; and

if a determination is made to transfer control of the merge database to the active transaction manager,

instructing the active transaction manager to halt transactions with the active database,

instructing the latent transaction manager to update the merge database to reflect the set of discrepancy transactions reflected in the discrepancy transaction log information, and

instructing the active transaction manager to manage transactions to the active database and the merge database.

2. The method of claim 1, wherein determining whether to transfer control of the merge database to the active transaction manager comprises:

determining a log number reflecting a total quantity of discrepancy transactions in the discrepancy transaction log information;

comparing the log number to a target value; and

transferring control of the merge database to the active transaction manager if the log number bears a predetermined relationship to the target value.

3. The method of claim 1, wherein determining whether to transfer control of the merge database to the active transaction manager comprises:

determining a log number reflecting a total quantity of discrepancy transactions in the discrepancy transaction log information;

comparing the log number to a target value; and

transferring control of the merge database to the active transaction manager if the log number is less than the target value.

4. The method of claim 1, wherein determining whether to transfer control of the merge database to the active transaction manager comprises:

calculating a characteristic distribution time associated with the active transaction manager;

calculating a time value for the merge database to reflect a set of discrepancy transactions reflected in the discrepancy transaction log information; and

transferring control of the merge database to the active transaction manager if the time value bears a predetermined relationship with the characteristic distribution time.

5. The method of claim 4 wherein calculating a characteristic distribution time comprises:

determining an amount of time per transaction for the active transaction manager to manage transactions with the active database; and

setting the characteristic distribution time equal or approximately equal to the amount of time per transaction.

6. The method of claim 1, wherein determining whether to transfer control of the merge database to the active transaction manager comprises:

calculating a characteristic distribution time associated with the active transaction manager;

calculating a time value for the merge database to reflect a set of discrepancy transactions reflected in the discrepancy transaction log information; and

transferring control of the merge database to the active transaction manager if the time value is less than the characteristic distribution time.

7. The method of claim 6 wherein calculating a characteristic distribution time comprises:

determining an amount of time per transaction for the active transaction manager to manage transactions with the active database; and

setting the characteristic distribution time equal or approximately equal to the amount of time per transaction.

8. The method of claim 1, wherein managing transactions with at least an active database comprises:

generating unique identifiers for active transactions.

9. The method of claim 1, wherein managing transactions with at least an active database comprises:

managing transactions in association with a Java Virtual Machine.

10. The method of claim 1, wherein managing transactions with at least an active database comprises:

managing transactions with said active database stored in RAM.

11. The method of claim 1, wherein managing transactions with a merge database comprises:

managing transactions with said merge database stored in RAM.

12. The method of claim 1, wherein managing transactions with at least an active database comprises:

managing a persistence log.

13. A system, including at least one processor and memory, for managing a distributed transaction process comprising:

an active transaction manager that manages transactions with at least an active database, where the active database reflects an application of a set of active transactions;

a latent transaction manager that manages transactions with a merge database, where the merge database reflects an application of a first subset of the set of active transactions;

a discrepancy transaction log that reflects a set of discrepancy transactions that is distinct from the first subset of active transactions;

the discrepancy transactions consisting of active transactions not yet applied to the merge database;

a merge manager that uses the transaction log to determine whether to transfer control of the merge database to the active transaction manager;

where, if the merge manager does not transfer control of the merge database to the active transaction manager,

the latent transaction manager is configured to apply the discrepancy transactions to the merge database to reflect the set of discrepancy transactions reflected in the discrepancy transaction log; and

where, if the merge manager transfers control of the merge database to the active transaction manager,

the latent transaction manager is configured to update the merge database to reflect the set of discrepancy transactions reflected in the discrepancy transaction log, and

the active transaction manager is configured to halt transactions with the active database while the latent transaction manager updates the merge database to reflect the set of discrepancy transactions reflected in the discrepancy transaction log, and

the active transaction manager is further configured to subsequently manage transactions to the active database and the merge database.

14. The system of claim 13, wherein the merge manager comprises:

a counter configured to generate a log number reflecting a total quantity of discrepancy transactions in the discrepancy transaction log; and

a controller configured to transfer control of the merge database to the active transaction manager if the log number is approximately equal to a target value.

15. The system of claim 13, wherein the merge manager comprises:

a counter configured to generate a log number reflecting a total quantity of discrepancy transactions in the discrepancy transaction log; and

a controller configured to transfer control of the merge database to the active transaction manager if the log number is less than a target value.

16. The system of claim 13, wherein the merge manager comprises:

a time calculator configured to calculate a characteristic distribution time associated with the active transaction manager;

a merge time calculator configured to calculate a merge time value for the merge database to reflect a set of discrepancy transactions reflected in the discrepancy transaction log; and

a controller configured to transfer control of the merge database to the active transaction manager if the merge time value is approximately equal to the characteristic distribution time.

17. The system of claim 16, wherein the time calculator comprises:

an active time calculator configured to calculate an amount of time per transaction for the active transaction manager to manage transactions with the active database; and

a results processor configured to set the characteristic distribution time equal or approximately equal to the amount of time per transaction.

18. The system of claim 13, wherein the merge manager comprises:

a time calculator configured to calculate a characteristic distribution time associated with the active transaction manager;

a merge time calculator configured to calculate a merge time value for the merge database to reflect a set of discrepancy transactions reflected in the discrepancy transaction log; and

a controller configured to transfer control of the merge database to the active transaction manager if the merge time value is less than the characteristic distribution time.

19. The system of claim 18, wherein the time calculator comprises:

an active time calculator configured to calculate an amount of time per transaction for the active transaction manager to manage transactions with the active database; and

a results processor configured to set the characteristic distribution time equal or approximately equal to the amount of time per transaction.

20. The system of claim 13, wherein the active transaction manager comprises:

an identifier generator configured to generate unique identifiers for active transactions.

21. The system of claim 13, where the active transaction manager is implemented in association with a Java Virtual Machine.

22. The system of claim 13, where said active database is stored in RAM.

23. The system of claim 13, where said merge database is stored in RAM.

24. The system of claim 13, where the active transaction manager manages a persistence log.

25. A tangible computer-readable storage medium embodying computer-readable code for instructing a system that manages a distributed transaction process, the computer-readable code comprising:

an active transaction manager, where the active transaction manager manages transactions with at least an active database and where the active database reflects an application of a set of active transactions;

a latent transaction manager, where the latent transaction manager manages transactions with a merge database, where the merge database reflects an application of a first subset of the set of active transactions;

a discrepancy transaction log that reflects a set of discrepancy transactions that is distinct from the first subset of active transactions, the discrepancy transactions consisting of active transactions not yet applied to the merge database; and

a merge manager that uses the transaction log to determine whether to transfer control of the merge database to the active transaction manager;

where, if the merge manager does not transfer control of the merge database to the active transaction manager,

the latent transaction manager is configured to apply the discrepancy transactions to the merge database to reflect the set of discrepancy transactions reflected in the discrepancy transaction log; and

where, if the merge manager transfers control of the merge database to the active transaction manager,

the latent transaction manager is configured to apply the discrepancy transactions to the merge database to reflect the set of discrepancy transactions reflected in the discrepancy transaction log; and

the active transaction manager is configured to halt transactions with the active database while the latent transaction manager updates the merge database to reflect the set of discrepancy transactions reflected in the discrepancy transaction log, and

the active transaction manager is further configured to subsequently manage transactions to the active database and the merge database.

26. The tangible computer-readable storage medium of claim 25, wherein the merge manager comprises:

a counter configured to generate a log number reflecting a total quantity of discrepancy transactions in the discrepancy transaction log; and

a controller configured to transfer control of the merge database to the active transaction manager if the log number is approximately equal to a target value.

27. The tangible computer-readable storage medium of claim 25, wherein the merge manager comprises:

a counter configured to generate a log number reflecting a total quantity of discrepancy transactions in the discrepancy transaction log; and

a controller configured to transfer control of the merge database to the active transaction manager if the log number is less than a target value.

28. The tangible computer-readable storage medium of claim 25, wherein the merge manager comprises:

a time calculator configured to calculate a characteristic distribution time associated with the active transaction manager;

a merge time calculator configured to calculate a merge time value for the merge database to reflect a set of discrepancy transactions reflected in the discrepancy transaction log information; and

a controller configured to transfer control of the merge database to the active transaction manager if the merge time value is approximately equal to the characteristic distribution time.

29. The tangible computer-readable storage medium of claim 28, wherein the time calculator comprises:

an active time calculator configured to calculate an amount of time per transaction for the active transaction manager to manage transactions with the active database; and

a result calculator configured to set the characteristic distribution time equal or approximately equal to the amount of time per transaction.

30. The tangible computer-readable storage medium of claim 25, wherein the merge manager comprises:

a time calculator configured to calculate a characteristic distribution time associated with the active transaction manager;

a merge time calculator configured to calculate a merge time value for the merge database to reflect a set of discrepancy transactions reflected in the discrepancy transaction log; and

a controller configured to transfer control of the merge database to the active transaction manager if the merge time value is less than the characteristic distribution time.

31. The tangible computer-readable storage medium of claim 30, wherein the time calculator comprises:

an active time calculator configured to calculate an amount of time per transaction for the active transaction manager to manage transactions with the active database; and

a results processor configured to set the characteristic distribution time equal or approximately equal to the amount of time per transaction.

32. The tangible computer-readable storage medium of claim 25, wherein the active transaction manager comprises:

an identifier generator configured to generate unique identifiers for active transactions.

33. The tangible computer-readable storage medium of claim 25, wherein the active transaction manager is implemented in association with a Java Virtual Machine.

34. The tangible computer-readable storage medium of claim 25, wherein said active database is stored in RAM.

35. The tangible computer-readable storage medium of claim 25, wherein said merge database is stored in RAM.

36. The tangible computer-readable storage medium of claim 25, wherein the active transaction manager manages a persistence log.