Network partition tolerance in a high available centralized VCS implementation

• US 10,467,198 B2
• Filed: 02/16/2017
• Issued: 11/05/2019
• Est. Priority Date: 09/15/2016
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Lopez, Jonathan Lopez, Vimberg, Juan Ignacio
• Primary Examiner(s): Uddin, Mohammed R
• Application Number:
  US15/434,513
• Publication Number:
  US 20180075057A1
• Time in Patent Office: 992 Days
• Field of Search: 707611, 707638, 707690, 707695, 707999203
• CPC Class Codes: G06F 16/148 File search processing
• CPC Class Codes: G06F 16/1774 Locking methods, e.g. locking methods for file systems allowing shared and concurrent access to files
• CPC Class Codes: G06F 16/178 Techniques for file synchronisation in file systems
• CPC Class Codes: G06F 16/2343 Locking methods, e.g. distributed locking or locking implementation details
• CPC Class Codes: G06F 16/2379 Updates performed during online database operations; commit processing
• CPC Class Codes: G06F 16/275 Synchronous replication
• CPC Class Codes: G06F 16/278 Data partitioning, e.g. horizontal or vertical partitioning

Abstract

Implementations provide a database lock mechanism used to prevent concurrent writes to service on network partition scenarios associated with a version control system. The database lock mechanism may be provided on per repository basis to ensure both nodes are working and maintaining data consistency, even when they are not connected when interruptions in network communication disrupts the intercommunication between nodes. In other implementations, the disclosed locking mechanism is configured to ensure and perform write and synchronization operations on isolated nodes, regardless of miss-communication between the nodes.

Claims

1. A non-transitory computer readable medium including one or more instructions executable by one or more processors for:

receiving at a first node of a system containing a plurality of nodes, an action providing requested changes to a file that is common to at least a second node and stored in a database locked from allowing changes to the file by a database lock, wherein the first node and the second node are isolated by a network partition;

analyzing attributes of the action to determine whether the action received is required to update the file;

analyzing the requested changes to the file to determine substantive changes to the file and changes to the file that do not change substantive content of the file;

receiving a variable level of the requested changes specifying one or more substantive changes to the file and one or more changes to the file that do not change substantive content of the file, to be accepted or rejected;

rejecting and accepting the substantive changes to the tile and the changes to the file that do not change substantive content of the tile according to the variable level;

synchronizing substantive changes to the file and rejecting changes to the file that are informational;

in response to determining that the action is required to update the file, determining from a data repository whether a database update action is set as unlocked;

if the database update action is set as unlocked then querying the data repository associated with the first node to determine revision information pertaining to the file;

determining from the revision information whether the file is a latest revision associated with required changes to the file;

if the file is the latest revision, then unlocking the data repository;

committing the changes to the data repository;

in response to committing the changes to the data repository, updating the revision of the file in the data repository based on the changes; and

in response to committing the changes to the data repository and updating the revision of the data repository, releasing the database lock and updating the file with the changes.

2. The computer readable medium of claim 1, wherein the data repository is a SVN repository.

3. The computer readable medium of claim 1, wherein the data repository comprises a local repository associated with the first node.

4. The computer readable medium of claim 1, wherein determining from a synchronization attribute stored in the data repository a data synchronization type used to update the database.

5. The computer readable medium of claim 4, further comprising determining from data synchronization type whether changes to the first node and changes to the second node are synchronously updated in the database.

6. The computer readable medium of claim 4, further comprising determining from the data synchronization type whether changes to the first node and changes to the second node are asynchronously updated in the database.

7. The computer readable medium of claim 1, wherein attributes of the action comprise other attributes indicating the action received is not required to update the file.

8. The computer readable medium of claim 1, wherein attributes of the action comprise other attributes indicating the action received is related to changes to file information.

9. The computer readable medium of claim 1, wherein analyzing attributes of the action further comprises determining whether the requested changes to the file would result in no change to file contents.

10. The computer readable medium of claim 1, wherein determining from the revision information whether the file is the latest revision further comprises analyzing a plurality of data stored in the data repository.

11. A computer implemented method comprising:

receiving at a first node of a system containing a plurality of nodes, an action providing requested changes to a file that is common to at least a second node and stored in a database locked from allowing changes to the file by a database lock, wherein the first node and the second node are isolated by a network partition;

analyzing attributes of the action to determine whether the action received is required to update the file;

analyzing the requested changes to the file to determine substantive changes to the file and changes to the file that do not change substantive content of the file;

receiving a variable level of the requested changes specifying one or more substantive changes to the file and one or more changes to the file that do not change substantive content of the file, to be accepted or rejected;

rejecting and accepting the substantive changes to the file and the changes to the file that do not change substantive content of the file according to the variable level;

synchronizing substantive changes to the file and rejecting changes to the file that are informational;

in response to determining that the action is required to update the file, determining from a data repository whether a database update action is set as unlocked;

if the database update action is set as unlocked then querying the data repository associated with the first node to determine revision information pertaining to the file;

determining from the revision information whether the file is a latest revision associated with required changes to the file;

if the file is the latest revision, then unlocking the data repository;

committing the changes to the data repository;

in response to committing the changes to the data repository, updating the revision of the file in the data repository based on the changes; and

in response to committing the changes to the data repository and updating the revision of the data repository, releasing the database lock and updating the file with the changes.

12. The method of claim 11, wherein the data repository is a SVN repository.

13. The method of claim 11, wherein the data repository comprises a local repository associated with the first node.

14. The method of claim 11, wherein determining from a synchronization attribute stored in the data repository a data synchronization type used to update the database.

15. The method of claim 14, further comprising determining from data synchronization type whether changes to the first node and changes to the second node are synchronously updated in the database.

16. The method of claim 14, further comprising determining from the data synchronization type whether changes to the first node and changes to the second node are asynchronously updated in the database.

17. The method of claim 11, wherein attributes of the action comprise other attributes indicating the action received is not required to update the file.

18. The method of claim 11, wherein attributes of the action comprise other attributes indicating the action received is related to changes to file information.

19. The method of claim 11, wherein analyzing attributes of the action further comprises determining whether changes to the file would result in no change to file contents.

20. An apparatus for managing database data updates in a computing environment between partitioned systems, the computing environment comprising a data system having one or more computing devices in communication with a software application that executes software configured to provide information accessible to the one or more computing devices, a computing device of the one or more computing devices executing the software to:

receive at a first node of a system containing a plurality of nodes, an action providing requested changes to a file that is common to at least a second node and stored in a database locked from allowing changes to the file by a database lock, wherein the first node and the second node are isolated by a network partition;

analyze attributes of the action to determine whether the action received is required to update the file;

analyze the requested changes to the file to determine substantive changes to the file and changes to the file that do not change substantive content of the file;

receive a variable level of the requested changes specifying one or more substantive changes to the file and one or more changes to the file that do not change substantive content of the file, to be accepted or rejected;

reject and accept the substantive changes to the file and the changes to the tile that do not change substantive content of the file according to the variable level;

synchronize substantive changes to the file and rejecting changes to the file that are informational;

in response to determining that the action is required to update the file, determine from a data repository whether a database update action is set as unlocked;

if the database update action is set as unlocked then querying the data repository associated with the first node to determine revision information pertaining to the file;

determine from the revision information whether the file is a latest revision associated with required changes to the file;

if the file is the latest revision, then unlock the data repository;

commit the changes to the data repository;

in response to committing the changes to the data repository, update the revision of the file in the data repository based on the changes; and

in response to commit the changes to the data repository and update the revision of the data repository, release the database lock and update the file with the changes.