Flexible in-memory column store placement

• US 10,474,653 B2
• Filed: 09/30/2016
• Issued: 11/12/2019
• Est. Priority Date: 09/30/2016
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Mukherjee, Niloy, Kamp, Jesse, Lahiri, Tirthankar, Colgan, Maria, Raja, Vivekanandhan, Krishnaswamy, Vasudha, Gupta, Aditi, Kulkarni, Kartik
• Primary Examiner(s): Truong, Cam Y T
• Application Number:
  US15/281,718
• Publication Number:
  US 20180096010A1
• Time in Patent Office: 1,138 Days
• CPC Class Codes: G06F 16/221 Column-oriented storage; Management thereof
• CPC Class Codes: G06F 16/2282 Tablespace storage structures; Management thereof
• CPC Class Codes: G06F 16/24552 Database cache management
• 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: G06F 3/0604 Improving or facilitating administration, e.g. storage management
• CPC Class Codes: G06F 3/064 Management of blocks
• CPC Class Codes: G06F 3/067 Distributed or networked storage systems, e.g. storage area networks [SAN], network attached storage [NAS]

Abstract

Techniques are described herein for distributing distinct portions of a database object across volatile memories of selected nodes of a plurality of nodes in a clustered database system. The techniques involve storing a unit-to-service mapping that associates a unit (a database object or portion thereof) to one or more database services. The one or more database services are mapped to one or more nodes. The nodes to which a service is mapped may include nodes in disjoint database systems, so long as those database systems have access to a replica of the unit. The database object is treated as in-memory enabled by nodes that are associated with the service, and are treated as not in-memory enabled by nodes that are not associated with the service.

Claims

1. A computer-implemented method comprising:

storing, in a database that is accessible to a plurality of nodes, a unit-to-service mapping that maps a particular unit in the database to a particular database service, wherein the particular database service is a grouping of work executing in the database, wherein the particular unit includes one or more tables of the database;

storing, in the database, a service-to-node mapping that maps the particular database service to one or more nodes, wherein the one or more nodes are less than ail of the plurality of nodes;

based on both the unit-to-service mapping and the service-to-node mapping, the one or more nodes treating the particular unit as in-memory enabled and nodes, of the plurality of nodes, other than the one or more nodes treating the particular unit as not in-memory enabled, wherein chunks of tables that belong to in-memory enabled units are eligible for being pre-loaded into volatile memory to speed up query processing; and

wherein, each node of the one or more nodes treats the particular unit as in-memory enabled by loading at least a copy of a portion of the particular unit into local volatile memory in response to a load-triggering event and

as part of the loading at least the copy of the portion of the particular unit into the local volatile memory, converting the particular unit from a persistent-format to a mirror-format, wherein the method is performed by one or more computing devices.

2. The method of claim 1 wherein the particular unit is an entire database object.

3. The method of claim 1 wherein the particular unit is one or more chunks of a database object but less than all of the database object.

4. The method of claim 1 wherein:

the particular unit is a first object in the database;

the database includes a second object;

the second object is not mapped to any service; and

the method further comprising storing data that indicates that the second object is to be treated as memory-enabled by one of;

all of the plurality of nodes, or

none of the plurality of nodes.

5. The method of claim 1 wherein the one or more nodes includes a first node that has loaded a copy of the particular unit into volatile memory, the method further comprising:

detecting that the particular database service has stopped on the first node; and

responsive to detecting that the particular database service has stopped on the first node, deallocating the copy of the particular unit from local volatile memory of the first node.

6. The method of claim 1 wherein the one or more nodes includes a first node that has loaded a copy of the particular unit into volatile memory, the method further comprising:

receiving a request at the first node that requires the particular unit;

determining that the first node has loaded a copy of the particular unit into volatile memory; and

reading the copy of the particular unit.

7. The method of claim 1 wherein the one or more nodes includes a first node that has loaded a copy of the particular unit into volatile memory, the method further comprising:

receiving a request at a second node that requires the particular unit;

determining that the first node has loaded a copy of the particular unit into volatile memory; and

sending the request to the first node.

8. The method of claim 1 further comprising:

receiving a request that requires the particular unit;

determining that no node of the one or more nodes has loaded a copy of the particular unit into volatile memory; and

in response to determining that no node has loaded a copy of the particular unit into volatile memory, at least one node of the one or more nodes loading at least a portion of the particular unit into local volatile memory.

9. The method of claim 1 wherein the plurality of nodes belong to a first database system and the one or more nodes include at least one node that belongs to a second database system that is disjoint relative to the first database system.

10. The method of claim 9 wherein the one or more nodes include a node in the first database system and a node in the second database system.

11. The method of claim 9 wherein the one or more nodes include only nodes in the second database system.

12. The method of claim 9 wherein:

the particular unit is a first object in the database;

the database includes a second object that is a portion of the first object;

the second object is mapped to one or more nodes of the first database system; and

the particular unit is mapped to one or more nodes of the second database system.

13. The method of claim 1 wherein the particular unit comprises a plurality of chunks and each node of the one or more nodes hosts one or more chunks of the plurality of chunks.

14. One or more non-transitory computer-readable media storing instructions, wherein the instructions include:

instructions which, when executed by one or more hardware processors, cause storing, in a database that is accessible to a plurality of nodes, a unit-to-service mapping that maps a particular unit in the database to a particular database service, wherein the particular database service is a grouping of work executing in the database, wherein the particular unit includes one or more tables of the database;

instructions which, when executed by one or more hardware processors, cause storing, in the database, a service-to-node mapping that maps the particular database service to one or more nodes, wherein the one or more nodes are less than all of the plurality of nodes;

instructions which, when executed by one or more hardware processors, cause based on both the unit-to-service mapping and the service-to-node mapping, the one or more nodes treating the particular unit as in-memory enabled and nodes, of the plurality of nodes, other than the one or more nodes treating the particular unit as not in-memory enabled, wherein chunks of tables that belong to in-memory enabled units are eligible for being pre-loaded into volatile memory to speed up query processing; and

wherein, each node of the one or more nodes treats the particular unit as in-memory enabled by loading at least a copy of a portion of the particular unit into local volatile memory in response to a load-triggering event; and

instructions which, when executed by one or more hardware processors, cause as part of the loading at least the copy of the portion of the particular unit into the local volatile memory, converting the particular unit from a persistent-format to a mirror-format.

15. The one or more non-transitory computer-readable media of claim 14, wherein the particular unit is an entire database object.

16. The one or more non-transitory computer-readable media of claim 14, wherein the particular unit is one or more chunks of a database object but less than all of the database object.

17. The one or more non-transitory computer-readable media of claim 14 wherein:

the particular unit is a first object in the database;

the database includes a second object;

the second object is not mapped to any service; and

the instructions further including instructions which, when executed by one or more hardware processors, cause storing data that indicates that the second object is to be treated as memory-enabled by one of;

all of the plurality of nodes, or

none of the plurality of nodes.

18. The one or more non-transitory computer-readable media of claim 14 wherein the one or more nodes includes a first node that has loaded a copy of the particular unit into volatile memory, the instructions further comprising:

instructions which, when executed by one or more hardware processors, cause detecting that the particular database service has stopped on the first node; and

instructions which, when executed by one or more hardware processors, cause responsive to detecting that the particular database service has stopped on the first node, deallocating the copy of the particular unit from local volatile memory of the first node.

19. The one or more non-transitory computer-readable media of claim 14 wherein the one or more nodes includes a first node that has loaded a copy of the particular unit into volatile memory, the instructions further comprising:

instructions which, when executed by one or more hardware processors, cause receiving a request at the first node that requires the particular unit;

instructions which, when executed by one or more hardware processors, cause determining that the first node has loaded a copy of the particular unit into volatile memory; and

instructions which, when executed by one or more hardware processors, cause reading the copy of the particular unit.

20. The one or more non-transitory computer-readable media of claim 14 wherein the one or more nodes includes a first node that has loaded a copy of the particular unit into volatile memory, the instructions further comprising:

instructions which, when executed by one or more hardware processors, cause receiving a request at a second node that requires the particular unit;

instructions which, when executed by one or more hardware processors, cause determining that the first node has loaded a copy of the particular unit into volatile memory; and

instructions which, when executed by one or more hardware processors, cause sending the request to the first node.

21. The one or more non-transitory computer-readable media of claim 14, the instructions further comprising:

instructions which, when executed by one or more hardware processors, cause receiving a request that requires the particular unit;

instructions which, when executed by one or more hardware processors, cause determining that no node of the one or more nodes has loaded a copy of the particular unit into volatile memory; and

instructions which, when executed by one or more hardware processors, cause in response to determining that no node has loaded a copy of the particular unit into volatile memory, at least one node of the one or more nodes loading at least a portion of the particular unit into local volatile memory.

22. The one or more non-transitory computer-readable media of claim 14 wherein the plurality of nodes belong to a first database system and the one or more nodes include at least one node that belongs to a second database system that is disjoint relative to the first database system.

23. The one or more non-transitory computer-readable media of claim 22 wherein the one or more nodes include a node in the first database system and a node in the second database system.

24. The one or more non-transitory computer-readable media of claim 22 wherein the one or more nodes include only nodes in the second database system.

25. The one or more non-transitory computer-readable media of claim 22 wherein:

the particular unit is a first object in the database;

the database includes a second object that is a portion of the first object;

the second object is mapped to one or more nodes of the first database system; and

the particular unit is mapped to one or more nodes of the second database system.

26. The one or more non-transitory computer-readable media of claim 22 wherein the particular unit comprises a plurality of chunks and each node of the one or more nodes hosts one or more chunks of the plurality of chunks.