Commitment control for less than an entire record in an in-memory database in a parallel computer system
First Claim
1. A parallel computer system comprising:
- a plurality of nodes coupled together, each node including at least one processor and memory;
an in-memory database residing in the plurality of nodes, the in-memory database defining a record that includes at least one mandatory portion that must be present for a change to the record to commit and at least one secondary portion that need not be present for a change to the record to commit;
a database manager residing in a memory, the database manager comprising;
a mandatory commit mechanism that commits changes to the at least one mandatory portion of the record when all mandatory portions of the record are available during a transaction and when at least one secondary portion is not available.
1 Assignment
0 Petitions
Accused Products
Abstract
In a networked computer system that includes multiple interconnected nodes, a commitment control mechanism allows designating certain portions of a record in an in-memory database as mandatory and other portions of the record as secondary, and performs mandatory commitment control once all the mandatory portions are available even if one or more secondary portions are not yet available. The secondary portions may be under separate commitment control that is asynchronous to the commitment control for the mandatory portions, or may be under no commitment control at all. The result is a commitment control mechanism that performs commitment control for portions of a record that are marked mandatory even when one or more of the portions marked secondary are not available.
-
Citations
19 Claims
-
1. A parallel computer system comprising:
-
a plurality of nodes coupled together, each node including at least one processor and memory; an in-memory database residing in the plurality of nodes, the in-memory database defining a record that includes at least one mandatory portion that must be present for a change to the record to commit and at least one secondary portion that need not be present for a change to the record to commit; a database manager residing in a memory, the database manager comprising; a mandatory commit mechanism that commits changes to the at least one mandatory portion of the record when all mandatory portions of the record are available during a transaction and when at least one secondary portion is not available. - View Dependent Claims (2, 3, 4, 5)
-
-
6. A computer-implemented method for commitment control for an in-memory database in a parallel computer system, the method comprising the steps of:
-
(A) defining at least one portion of a record in the in-memory database as mandatory that must be present for a change to the record to commit; (B) defining at least one portion of the record as secondary that need not be present for a change to the record to commit; (C) allocating portions of the record to a plurality of nodes in the parallel computer system; (D) monitoring mandatory portions of the record during a transaction; and (E) when all mandatory portions of the record are available during the transaction and at least one secondary portion is not available, committing changes to all mandatory portions of the record. - View Dependent Claims (7, 8, 9, 10, 11)
-
-
12. A computer-implemented method for commitment control for an in-memory database in a parallel computer system, the method comprising the steps of:
-
(A) marking at least one portion of a record in the in-memory database as mandatory that must be present for a change to the record to commit; (B) marking at least one portion of the record as secondary that need not be present for a change to the record to commit; (C) allocating portions of the record to a plurality of nodes in the parallel computer system; (D) starting a transaction to the record in the in-memory database; (E) monitoring all mandatory portions of the record during the transaction; (F) when all mandatory portions of the record are available during the transaction and at least one secondary portion is not available and the transaction has not timed out, committing changes to the mandatory portions of the record; (G) after performing step (F), committing changes to all secondary portions of the record when all secondary portions of the record are available during the transaction and the transaction has not timed out, wherein the committing changes to all secondary portions of the record is done in a commit cycle that is separate and asynchronous to the commit cycle for the mandatory portions of the record in step (F). - View Dependent Claims (13, 14)
-
-
15. A computer-readable article of manufacture comprising:
-
a database manager comprising a mandatory commit mechanism that monitors during a transaction a record that includes at least one mandatory portion that must be present for a change to the record to commit and at least one secondary portion that need not be present for a change to the record to commit, the database manager committing changes to at least one mandatory portion of the record when all mandatory portions of the record are available during the transaction and when at least one secondary portion is not available; and recordable media bearing the database manager. - View Dependent Claims (16, 17, 18, 19)
-
Specification