Method and system to maintain strong consistency of distributed replicated contents in a client/server system

• US 8,495,017 B2
• Filed: 08/04/2011
• Issued: 07/23/2013
• Est. Priority Date: 08/03/2011
• Status: Active Grant

• Current Assignee: Amadeus (Amadeus Global Travel Distribution S.A.)
• Original Assignee: Amadeus (Amadeus Global Travel Distribution S.A.)
• Inventors: Lafont, Caroline, Touffait, Guillaume, Collendavelloo, Yan, Defayet, Christophe, Amar, Virginie
• Primary Examiner(s): Cao, Phuong Thao
• Application Number:
  US13/136,576
• Publication Number:
  US 20130036092A1
• Time in Patent Office: 719 Days
• Field of Search: 707/634, 707/623, 707/638, 707/999.01, 707/999.201
• US Class Current: 707/634
• CPC Class Codes: G06F 16/172 Caching, prefetching or hoarding of files
• CPC Class Codes: G06F 16/178 Techniques for file synchronisation in file systems
• CPC Class Codes: G06F 16/184 implemented as replicated file system

Abstract

A method and a system for maintaining consistency of replicated files distributed over a plurality of independent processing slave nodes part of an application tier of a multi-tier client/server data processing system are described. The replicated files are distributed from a master node of a master tier. Upon reception of an update request to update a master database a new version of a replicated file is first generated and stored in a shared file system. A notification of availability of the new version is forwarded to a synchronizing slave node and broadcasted to all slave nodes. Each slave node preloads the new version of the replicated file from the shared file system and acknowledges successful completion. Upon reception of all acknowledgments in the synchronization slave node a notification of preloading achievement is forwarded to the master server which updates the master database.

Claims

1. A method of maintaining consistency between copies of a replicated file distributed over a plurality of nodes of a data processing system, the method comprising:

receiving an update request in a master server, the update request requesting that the replicated file be updated in a master database;

generating and storing a new version of the replicated file in a shared file system based on the update request;

providing a notification of availability of the new version of the replicated file to a plurality of slave nodes;

in response to receiving the notification of availability at each slave node, preloading a copy of the new version of the replicated file from the shared file system into a memory of each slave node, and upon completion of the preloading, acknowledging successful completion of the preloading; and

committing the data processing system to use the new version of the replicated file only if each slave node of the plurality of slave nodes acknowledges successful completion of the preloading to the master server.

2. The method of claim 1 wherein providing the notification of availability of the new version of the replicated file to the plurality of slave nodes comprises:

forwarding, from the master server, the notification of availability of the new version of the replicated file to a synchronizing slave node selected from the plurality of slave nodes; and

broadcasting from the synchronizing slave node the notification of availability to the other remaining slave nodes of the plurality of slave nodes.

3. The method of claim 2 wherein each slave node acknowledges successful completion of the preloading to a server process of the synchronizing slave node.

4. The method of claim 3 further comprising:

in response to all the other remaining slave nodes of the plurality of slave nodes acknowledging successful completion of the preloading to the server process of the synchronizing slave node, forwarding a notification of preloading achievement from the synchronizing slave node to the master server.

5. The method of claim 2 wherein committing the data processing system to use the new version of the replicated file comprises:

forwarding a commitment notification to the synchronizing slave node from the master server; and

in response to receiving the commitment notification, triggering with the synchronizing slave node the use of the new version of the replicated file in a slave database.

6. The method of claim 5 wherein triggering the use of the new version of the replicated file in the slave database comprises:

updating a version table in the slave database with a version number of the new version of the replicated file.

7. The method of claim 1 further comprising:

in response to a transaction initiated by a query for information from a user, interrogating a slave database at each slave node involved in the transaction; and

based upon the interrogation, instructing each slave node involved in the transaction whether to switch from a current version of the replicated file to the preloaded new version of the replicated file.

8. The method of claim 7 wherein the slave database only stores data related to a version of replicated files.

9. The method of claim 1 further comprising:

in response to a transaction initiated by a query for information from a user, reading in each slave node involved in said transaction a tag of a current version of the replicated file, the tag indicating if a new version of the replicated file is available;

in response to the tag indicating that a new version of the replicated file is available, interrogating a slave database of each slave node involved in the transaction; and

in response to being interrogated, instructing the interrogating slave node whether to switch from the current version of the replicated file to the new version of the replicated file.

10. The method of claim 9 wherein the tag is set at successful completion of preloading of the new version of the replicated file, and is reset at a first reading by the slave node.

11. The method of claim 1 wherein the received update request includes an update for the replicated file, generating and storing the new version of the replicated file in the shared file system is an incremental process in the master server comprising:

retrieving from the shared file system a current version of the replicated file;

converting the current version of the replicated file to an appropriate format to be updated;

applying the update to the current version of the replicated file to generate the new version of the replicated file; and

converting the new version of the replicated file for storage into the shared file system; and

storing the new version of the replicated file into the shared file system.

12. The method of claim 11 wherein the replicated file is compressed when stored in the shared file system, and converting the current version of the replicated file to the appropriate format comprises:

decompressing the current version of the replicated file stored in the shared file system with the master server; and

preloading the copy of the new version of the replicated file includes decompressing the new version of the replicated file with the each slave node.

13. The method of claim 1 further comprising:

in response to at least one of the slave nodes of the plurality of slave nodes failing to acknowledge successful completion of the preloading, sending an error notification from the master server to a sender of the update request.

14. The method of claim 1 wherein the shared file system comprises a network-attached storage (NAS).

15. The method of claim 1 wherein committing the data processing system to use the new version of the replicated file comprises:

updating the replicated file in the master database to the new version of the replicated file;

updating data in a slave database configured to keep track of replicated file versions used by the plurality of slave nodes, the data identifying a version of the replicated file to be used by the plurality of slave nodes; and

in response to updating the data identifying the version of the replicated file in the slave database, receiving in the master server a notification of commitment of each slave node of the plurality of slave nodes to use the new version of the replicated file.

16. The method of claim 15 further comprising:

in response to each slave node of the plurality of slave nodes acknowledging successful completion of the preloading, receiving a notification of preloading achievement in the master server, wherein updating the replicated file in the master database to the new version of the replicated file is in response to receiving the notification of preloading achievement.

17. A computer program product comprising:

a non-transitory computer-readable storage medium including program instructions that, when executed by one or more processors, cause the one or more processors to;

receive an update request in a master server, the update request requesting that a replicated file be updated in a master database;

generate and store a new version of the replicated file in a shared file system based on the update request;

provide a notification of availability of the new version of the replicated file to a plurality of slave nodes;

in response to receiving the notification of availability at each slave node, preload a copy of the new version of the replicated file from the shared file system into a memory of each slave node, and upon completion of the preloading, acknowledge successful completion of the preloading; and

commit the data processing system to use the new version of the replicated file only if all slave nodes of the plurality of slave nodes acknowledge successful completion of the preloading.

18. A method of maintaining consistency between copies of a replicated file containing business rules, the copies of the replicated file being distributed over a plurality of nodes of a data processing system, the method comprising:

receiving an update request in a master server to update business rules stored in a master database;

generating and storing a new version of the replicated file in a shared file system based on the update request;

providing a notification of availability of the new version of the replicated file to a plurality of slave nodes;

in response to receiving the notification of availability at each slave node, preloading a copy of the new version of the replicated file from the shared file system into a memory of each slave node, and upon completion of the preloading, acknowledging successful completion of the preloading; and

committing the data processing system to use the new version of the replicated file only if all slave nodes of the plurality of slave nodes acknowledge successful completion of the preloading.

19. The method of claim 18 wherein each business rule comprises a set of criteria and a content.

20. The method of claim 19 wherein each criterion of the set of criteria is associated to a weight.

21. The method of claim 19 wherein the set of criteria comprises a point of sale, a country, a group of countries, a country of origin of a flight, a destination of a flight, or a customer profile.

22. The method of claim 18 wherein an inventory of a travel provider comprises the data processing system.

23. The method of claim 18 wherein at least one of the slave nodes is connected to an inventory of an airline, a departure control system of an airline, a revenue management system of an airline, a revenue accounting system of an airline, or an electronic ticket server of an airline.

24. The method of claim 18 wherein committing the data processing system to use the new version of the replicated file comprises:

committing the use of the new version of the replicated file in a slave database configured to keep track of all replicated file versions;

forwarding a notification of commitment of all slave nodes to the master server; and

from the master server, acknowledging achievement of the update request in response to the received update request.

25. A distributed data processing system comprising:

a master tier including a master server and a shared file system; and

an application tier including a plurality of slave nodes, each slave node having a memory and being communicatively coupled to the master tier, wherein the master server is configured to provide a notification of availability of a new version of a replicated file in the shared file system to the plurality of slave nodes;

each slave node-of the plurality of slave nodes is configured to, in response to receiving the notification of availability, preload a copy of the new version of the replicated file from the shared file system, and upon completion of the preloading, acknowledge successful completion of the preloading; and

the master server is further configured to only commit the data processing system to use the new version of the replicated file in response to all slave nodes acknowledging-successful completion of the preloading.