Search

EP-4736024-A1 - SYSTEM AND METHOD TO OVERCOME DATA RACE CONDITIONS IN A DATABASE

EP4736024A1EP 4736024 A1EP4736024 A1EP 4736024A1EP-4736024-A1

Abstract

The present disclosure relates to a method for mitigating data race conditions in a database (218). The method comprising requesting, by two or more data sources, one or more changes to be performed on a data stored in the database (218). The method comprising capturing the requested one or more changes in a streaming job to generate one or more alarms related to the one or more changes. The method comprising generating one or more logs related to the captured one or more changes. The method comprising determining a type of operation to be performed on the stored data based on the one or more generated logs and the one or more generated alarms. The method comprising responsive to determining, performing the type of operation on the data stored in the database (218).

Inventors

  • BHATNAGAR, AAYUSH
  • BHATNAGAR, PRADEEP KUMAR
  • VENKATRAMAN, Rajeshwari
  • PATEL, HIMANSHU
  • Tiwari, Shubham
  • Bhardwaj, Avinash

Assignees

  • Jio Platforms Limited

Dates

Publication Date
20260506
Application Date
20240530

Claims (20)

  1. 1. A method (700) for mitigating data race conditions in a database (218), the method (700) comprising: requesting (702), by two or more data sources, one or more changes to be performed on a data stored in the database (218); capturing (704) the requested one or more changes in a streaming job to generate one or more alarms related to the one or more changes; generating (706) one or more logs related to the captured one or more changes; determining (708) a type of operation to be performed on the stored data based on the one or more generated logs and the one or more generated alarms; and responsive to determining, performing (710) the type of operation on the data stored in the database (218).
  2. 2. The method as claimed in claim 1, wherein the one or more changes are related to performing data manipulation operations on the data in the database (218).
  3. 3. The method as claimed in claim 2, wherein the data manipulation operations include at least one of an insert operation, an update operation, or a delete operation.
  4. 4. The method as claimed in claim 1, wherein the one or more alarms include messages indicating the one or more changes to be performed on the data in the database (218).
  5. 5. The method as claimed in claim 4, wherein the messages are stored in a distributed event streaming platform.
  6. 6. The method as claimed in claim 1, wherein the one or more alarms include at least one of a new alarm or a clear alarm.
  7. 7. The method as claimed in claim 6, wherein the new alarm indicates performing the insert operation on the data in the database (218).
  8. 8. The method as claimed in claim 7, wherein an insert query is created when the new alarm is generated.
  9. 9. The method as claimed in claim 6, wherein the clear alarm indicates performing the update operation on the data in the database (218).
  10. 10. The method as claimed in claim 6, wherein the update operation includes updating the data with a clear time as indicated in the clear alarm.
  11. 11. The method as claimed in claim 10, further comprising storing the updated data with the clear time to a history table of a distributed computing framework.
  12. 12. A system (100) for mitigating data race conditions in a database (218), the system (100) comprising: a receiving unit (202) configured for: receiving a request, from two or more data sources, for performing one or more changes on a data stored in the database (218); and capturing the requested one or more changes in a streaming job to generate one or more alarms related to the one or more changes; a processing unit (208) configured for: generating one or more logs related to the captured one or more changes; determining a type of operation to be performed on the stored data based on the one or more generated logs and the one or more generated alarms; and responsive to determining, performing the type of operation on the data stored in the database (218).
  13. 13. The system (100) as claimed in claim 12, wherein the one or more changes are related to performing data manipulation operations on the data in the database (218).
  14. 14. The system (100) as claimed in claim 13, wherein the data manipulation operations include at least one of an insert operation, an update operation, or a delete operation.
  15. 15. The system (100) as claimed in claim 12, wherein the one or more alarms include messages indicating the one or more changes to be performed on the data in the database (218).
  16. 16. The system (100) as claimed in claim 15, wherein the messages are stored in a distributed event streaming platform.
  17. 17. The system (100) as claimed in claim 12, wherein the one or more alarms include at least one of a new alarm or a clear alarm.
  18. 18. The system (100) as claimed in claim 17, wherein the new alarm indicates performing the insert operation on the data in the database (218).
  19. 19. The system (100) as claimed in claim 18, wherein an insert query is created when the new alarm is generated.
  20. 20. The system (100) as claimed in claim 17, wherein the clear alarm indicates performing the update operation on the data in the database (218).

Description

SYSTEM AND METHOD TO OVERCOME DATA RACE CONDITIONS IN A DATABASE RESERVATION OF RIGHTS [0001] A portion of the disclosure of this patent document contains material, which is subject to intellectual property rights such as but are not limited to, copyright, design, trademark, integrated circuit (IC) layout design, and/or trade dress protection, belonging to Jio Platforms Limited (JPL) or its affiliates (hereinafter referred as owner). The owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office patent files or records, but otherwise reserves all rights whatsoever. All rights to such intellectual property are fully reserved by the owner. TECHNICAL FIELD [0002] The present disclosure relates to the field of Database Management Systems (DBMS) and data integration. More precisely, it relates to a system for an automated Change Data Capture (CDC) mechanism to overcome a data race conditions in a database. BACKGROUND [0003] Background description includes information that may be useful in understanding the present invention. It is not an admission that any of the information provided herein is prior art or relevant to the presently claimed invention, or that any publication specifically or implicitly referenced is prior art. [0004] The organizations may at times need to move data between different database environments. For example, to create a backup of the data, or to enable sharing of the data between different database applications. The data replication systems help address this need, for example by detecting and replicating changes to the data in a database table, as a result of row operations, rather than copying the entire table and the data therein. The data replication systems can be used to synchronize the data in a target database with the data in a source database. [0005] However, in the environments that support very large data sets, for example big data environments, present challenges related to availability, scalability, and fault-tolerance. The traditional databases or data replication systems may not scale sufficiently to handle such larger amounts of data. [0006] Data race conditions happens whenever two processes update the database simultaneously. They occur when multiple threads or processes access shared data concurrently without proper synchronization, leading to unpredictable and erroneous behavior. Data race conditions can result in incorrect data insertion and sometimes leads to data corruptions. Data race conditions arise when at least two threads or processes perform simultaneous read and write operations on the same shared data, and at least one of the operations is a write . The exact interleaving and timing of these operations become unpredictable, potentially leading to inconsistent or unexpected results. Further, the data race conditions may lead to improper updating of the data. [0007] However, the current techniques are inefficient in handling the race conditions in a database. Thus, there is a need for improved techniques that can overcome the race conditions in an effective manner. OBJECTS OF INVENTION [0008] Some of the objects of the present disclosure, that at least one embodiment herein satisfy are as listed herein below. [0009] It is an object of the present disclosure to overcome the above limitations and drawbacks of the existing methods for using CDC to overcome data race conditions. [0010] It is an object of the present disclosure to address data race conditions is to ensure data consistency in a concurrent environment. [0011] It is an object of the present disclosure to enables synchronization of data changes across multiple systems or components. [0012] It is an object of the present disclosure to help detect conflicts that arise when multiple threads or processes attempt to modify shared data concurrently. [0013] It is an object of the present disclosure to capture and propagate data changes in near real-time and minimize the time window for potential race conditions to occur and swiftly propagate changes to ensure consistent and up-to- date data across systems. [0014] It is an object of the present disclosure to enhance the scalability and performance of systems by reducing contention and improving parallel processing capabilities. [0015] It is an object of the present disclosure to contribute to system reliability by providing fault-tolerant mechanisms for capturing and processing data changes. [0016] It is an object of the present disclosure to simplify the development and maintenance of concurrent systems by providing a structured and standardized approach to handle data races. [0017] It is an object of the present disclosure to align the objectives of using CDC with the specific requirements and challenges of addressing data race conditions to achieve improved data consistency, concurrency control, and overall reliability in the face of concurrent access