Providing Durability of In-Memory Columnar Datastores Using Multile Logs

• US 20150019516A1
• Filed: 07/09/2013
• Published: 01/15/2015
• Est. Priority Date: 07/09/2013
• Status: Abandoned Application

• Current Assignee: Sybase Incorporated (SAP SE)
• Original Assignee: Anil Goel, David Wein
• Inventors: FLORENDO, Colin, WEIN, David, GOEL, Anil
• Application Number:
  US13/937,769
• Publication Number:
  US 20150019516A1
• Time in Patent Office: Days
• US Class Current: 707/703
• CPC Class Codes: G06F 16/215 Improving data quality; Data cleansing, e.g. de-duplication, removing invalid entries or correcting typographical errors
• CPC Class Codes: G06F 16/221 Column-oriented storage; Management thereof

Abstract

Embodiments described herein generally relate to providing durability of in memory columnar datastores using multiple logs. A computer-implemented method is described. The method includes receiving a request to perform a transaction involving multiple tables in a column-oriented database system. The method further includes performing the transaction on each of the two or more database tables. Performance of the transaction generates two or more commit fragments corresponding to each of the two or more database tables. The method further includes writing each commit fragment to a transaction log for each of the two or more database tables. The method also includes writing a commit record for the transaction to a commit log after all commit fragments have been written.

Claims

1. A computer-implemented method in a database system, comprising:

receiving, from a client, a request to perform a transaction, the transaction requiring two or more database tables in an in-memory column-oriented data store;

performing the transaction on each of the two or more database tables, wherein performance of the transaction generates two or more commit fragments corresponding to each of the two or more database tables; and

updating a transaction log and a commit log according to the generated two or more commit fragments.

2. The method of claim 1, wherein updating a transaction log further comprises storing each commit fragment in a transaction log for each of the two or more database tables.

3. The method of claim 2, further comprising acknowledging completion of the transaction to the client after storing all commit fragments.

4. The method of claim 2, wherein updating a commit log further comprises storing a commit record for the transaction in a commit log after all commit fragments have been stored.

5. The method of claim 1, further comprising:

receiving a request to perform recovery of the in-memory data store;

scanning the commit log to identify a first list of transactions that were committed before a system crash, wherein the scan is performed from beginning to end of the commit log;

scanning the transaction togs to identify a second list of transactions were committed before the system crash, wherein the scan is performed from end to beginning of the transaction logs;

terminating the scanning of the transaction logs when the scanning of the transaction logs identifies a transaction present the first list of transactions that must be redone; and

appending each transaction on the second list of transactions to the first list of transactions to create a list of transactions that must be redone.

6. The method of claim 5, wherein each transaction on the second list of transactions is identified based on a complete set of commit fragments for the transaction.

7. The method of claim 5, further comprising redoing each transaction on the list of transactions that must be redone.

8. A system, comprising:

one or more processors; and

a memory, the memory storing instructions that, when executed by the one or more processors, cause the one or more processors to;

receive, from a client, a request to perform a transaction, the transaction requiring two or more database tables in an in-memory column-oriented data store;

perform the transaction on each of the two or more database tables, wherein performance of the transaction generates two or more commit fragments corresponding to each of the two or more database tables; and

update a transaction log and a commit log according to the generated two or more commit fragments.

9. The system of claim 8, further comprising one or more disk based storage devices, and wherein the memory farther stores instructions that cause the one or more processors to store each commit fragment in a transaction log for each of the two or more database tables on the one or more disk based storage devices.

10. The system of claim 9, wherein the memory further stores instructions that cause the one or more processors to acknowledge completion of the transaction to the client after storing all commit fragments.

11. The system of claim 9, wherein the memory farther stores instructions that cause the one or more processors to store the commit log on the one or more disk based storage devices.

12. The system of claim 8, wherein the memory further stores instructions that cause the one or more processors to:

receive a request to perform recovery of the in-memory data store;

scan the commit log to identify a first list of transactions that were committed before a system crash, wherein the scan is performed from beginning to end of the commit log;

scan the transaction logs to identify a second list of transactions were committed before the system crash, wherein the scan is performed from end to beginning of the transaction logs;

terminate the scanning of the transaction logs when the scanning of the transaction logs identifies a transaction present the first list of transactions that must be redone; and

append each transaction on the second list of transactions to the first list of transactions to create a list of transactions that must be redone.

13. The system of claim 12, wherein each transaction on the second list of transactions is identified based on a complete set of commit fragments for the transaction.

14. The system of claim 12, wherein the memory further stores instructions that cause the one or more processors to redo each transaction on the list of transactions that must be redone.

15. A computer-readable medium haying instructions stored thereon, the instructions when executed causing at least one computing device to perform operations, the operations comprising:

receiving, from a client, a request to perform a transaction, the transaction requiring two or more database tables in an in-memory column-oriented data store;

performing the transaction on each of the two or more database tables, wherein performance of the transaction generates two or more commit fragments corresponding to each of the two or more database tables; and

updating a transaction log and a commit log according to the generated two or more commit fragments.

16. The computer-readable medium of claim 15, wherein updating a transaction log further comprises storing each commit fragment in a transaction log for each of the two or more database tables.

17. The computer-readable medium of claim 16, the operations further comprising acknowledging completion of the transaction to the client after storing all commit fragments.

18. The computer-readable medium of claim 16, wherein updating a commit log further comprises storing a commit record for the transaction in a commit log after all commit fragments have been stored.

19. The computer-readable medium of claim 15, the operations further comprising:

receiving a request to perform recovery of the in-memory data store;

scanning the commit log to identify a first list of transactions that were committed before a system crash, wherein the scan is performed from beginning to end of the commit log;

scanning the transaction logs to identify a second list of transactions were committed before the system crash, wherein the scan is performed from end to beginning of the transaction logs;

terminating the scanning of the transaction logs when the scanning of the transaction logs identifies a transaction present the first list of transactions that must be redone; and

appending each transaction on the second list of transactions to the first list of transactions to create a list of transactions that must be redone.

20. The computer-readable medium of claim 15, wherein each transaction on the second list of transactions is identified based on a complete set of commit fragments for the transaction.