Managing checkpoint queues in a multiple node system

• US 7,577,690 B2
• Filed: 04/17/2006
• Issued: 08/18/2009
• Est. Priority Date: 11/24/1998
• Status: Expired due to Term

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Chandrasekaran, Sashikanth, Chan, Wilson Wai Shun, Srihari, Vinay, Brower, David, Bridge, William H., Bamford, Roger J., MacNaughton, Neil
• Primary Examiner(s): Corrielus; Jean M
• Application Number:
  US11/405,805
• Publication Number:
  US 20060195648A1
• Time in Patent Office: 1,219 Days
• Field of Search: 707/205, 707/206, 707/202, 707/204, 711/118, 711/119, 711/130, 711/142, 711/143, 711/151, 711/158, 714/6, 714/20, 714/719
• US Class Current: 711/119
• CPC Class Codes: G06F 11/1469 Backup restoration techniques
• CPC Class Codes: G06F 11/1471 involving logging of persistent data for recovery
• CPC Class Codes: G06F 12/0804 with main memory updating G06F12/0806 takes precedence
• CPC Class Codes: G06F 12/0815 Cache consistency protocols
• CPC Class Codes: G06F 16/27 Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
• CPC Class Codes: Y10S 707/99952 Coherency, e.g. same view to multiple users
• CPC Class Codes: Y10S 707/99953 Recoverability
• CPC Class Codes: Y10S 707/99954 Version management
• CPC Class Codes: Y10S 707/99955 Archiving or backup

Abstract

Techniques are provided for managing caches in a system with multiple caches that may contain different copies of the same data item. Specifically, techniques are provided for coordinating the write-to-disk operations performed on such data items to ensure that older versions of the data item are not written over newer versions, and to reduce the amount of processing required to recover after a failure. Various approaches are provided in which a master is used to coordinate with the multiple caches to cause a data item to be written to persistent storage. Techniques are also provided for managing checkpoints associated with the caches, where the checkpoints are used to determine the position at which to begin processing recovery logs in the event of a failure.

Claims

1. A method for coordinating writing of data items to persistent storage, the method comprising the steps of:

maintaining within a first node a first queue for dirty data items that need to be written to persistent storage;

maintaining within the first node a second queue for dirty data items that need to be written to persistent storage;

moving entries from said first queue to said second queue when the dirty data items corresponding to the entries need to be transferred for use by a second node;

when selecting which data items to write to persistent storage, assigning priority to data items that correspond to entries in said second queue over data items that correspond to entries in said first queue; and

after selecting which data items to write to persistent storage, writing the selected items to persistent storage.

2. The method of claim 1 wherein the step of moving entries includes moving an entry from said first queue to said second queue in response to a message received by said first node, wherein said message indicates that another node has requested the data item that corresponds to said entry.

3. A method for coordinating writing of data items to persistent storage, the method comprising the steps of:

maintaining a forced-write count for each of said data items;

incrementing the forced-write count of a data item whenever the data item is written to persistent storage by one node for transfer of the data item to another node;

selecting which dirty data items to write to persistent storage based on the write counts associated with the data items;

after selecting which dirty data items to write to persistent storage, writing the selected items to persistent storage;

storing dirty data items that have forced-write counts at or above a certain threshold in a particular queue; and

when selecting dirty data items to write to persistent storage, giving priority to data items stored in said particular queue.

4. A computer-readable storage medium carrying instructions for coordinating writing of data items to persistent storage, the instructions when executed cause the comprising computer to perform the steps of:

maintaining within a first node a first queue for dirty data items that need to be written to persistent storage;

maintaining within the first node a second queue for dirty data items that need to be written to persistent storage;

moving entries from said first queue to said second queue when the dirty data items corresponding to the entries need to be transferred for use by a second node;

when selecting which data items to write to persistent storage, assigning priority to data items that correspond to entries in said second queue over data items that correspond to entries in said first queue; and

after selecting which data items to write to persistent storage, writing the selected items to persistent storage.

5. The computer-readable storage medium of claim 4 wherein the step of moving entries includes moving an entry from said first queue to said second queue in response to a message received by said first node, wherein said message indicates that another node has requested the data item that corresponds to said entry.

6. A computer-readable storage medium carrying instructions for coordinating writing of data items to persistent storage, the instructions when executed cause the computer to perform the steps of:

maintaining a forced-write count for each of said data items;

incrementing the forced-write count of a data item whenever the data item is written to persistent storage by one node for transfer of the data item to another node;

selecting which dirty data items to write to persistent storage based on the write counts associated with the data items;

after selecting which dirty data items to write to persistent storage, writing the selected items to persistent storage;

storing dirty data items that have forced-write counts at or above a certain threshold in a particular queue; and

when selecting dirty data items to write to persistent storage, giving priority to data items stored in said particular queue.