METHOD AND MECHANISM FOR EFFICIENT RE-DISTRIBUTION OF IN-MEMORY COLUMNAR UNITS IN A CLUSTERED RDBMS ON TOPOLOGY CHANGE
First Claim
1. A method comprising:
- for each map-storing node of a plurality of map-storing nodes in a database system, maintaining a respective mapping that indicates;
a plurality of chunks of data;
for each chunk of the plurality of chunks of data;
one or more host nodes assigned to the chunk, andfor each host node of the one or more host nodes assigned to the chunk, a registration timestamp corresponding to a time when the map-storing node established that the host node was a host of the chunk;
in response to a re-distribution event, determining a first set of one or more chunks, of the plurality of chunks, affected by the re-distribution event;
for each chunk of the first set of chunks;
determining at least one additional host node for the chunk;
each map-storing node, of the plurality of map-storing nodes, updating the respective mapping to indicate the at least one additional host node and an additional registration timestamp for the chunk for the at least one additional host node;
wherein the method is performed by one or more computing devices.
0 Assignments
0 Petitions
Accused Products
Abstract
Techniques are described herein for executing queries on distinct portions of a database object that has been separate into chunks and distributed across the volatile memories of a plurality of nodes in a clustered database system. The techniques involve redistributing the in-memory database object portions on changes to the clustered database system. Each node may maintain a mapping indicating which nodes in the clustered database system store which chunks, and timestamps indicating when each mapping entry was created or updated. A query coordinator may use the timestamps to select a database server instance with local in memory access to data required by a portion of a query to process that portion of the query.
-
Citations
22 Claims
-
1. A method comprising:
-
for each map-storing node of a plurality of map-storing nodes in a database system, maintaining a respective mapping that indicates; a plurality of chunks of data; for each chunk of the plurality of chunks of data; one or more host nodes assigned to the chunk, and for each host node of the one or more host nodes assigned to the chunk, a registration timestamp corresponding to a time when the map-storing node established that the host node was a host of the chunk; in response to a re-distribution event, determining a first set of one or more chunks, of the plurality of chunks, affected by the re-distribution event; for each chunk of the first set of chunks; determining at least one additional host node for the chunk; each map-storing node, of the plurality of map-storing nodes, updating the respective mapping to indicate the at least one additional host node and an additional registration timestamp for the chunk for the at least one additional host node; wherein the method is performed by one or more computing devices. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11)
-
-
12. One or more non-transitory computer-readable media storing instructions, which when executed by one or more hardware processors, cause:
-
for each map-storing node of a plurality of map-storing nodes in a database system, maintaining a respective mapping that indicates; a plurality of chunks of data; for each chunk of the plurality of chunks of data; one or more host nodes assigned to the chunk, and for each host node of the one or more host nodes assigned to the chunk, a registration timestamp corresponding to a time when the map-storing node established that the host node was a host of the chunk; in response to a re-distribution event, determining a first set of one or more chunks of the plurality of chunks affected by the re-distribution event; for each chunk of the first set of chunks; determining at least one additional host node for the chunk; each map-storing node, of the plurality of map-storing nodes, updating the respective mapping to indicate the at least one additional host node and an additional registration timestamp for the chunk for the at least one additional host node. - View Dependent Claims (13, 14, 15, 16, 17, 18, 19, 20, 21, 22)
-
Specification