SEARCH
0-9 A B C D E F G H I J K L M N O P Q R S T U V W X Y Z
Prev | Current Page 413 | Next

Robert Wrembel and Christian Koncilia

"Data Warehouses and Olap: Concepts, Architectures and Solutions"

However, all nodes that remain active
are needed to process a slice from the replica. In order to allow up to R nodes to
become unavailable, there must be R nonoverlapping replica slice sets.
If we desire y nodes to be able to be off-line simultaneously when a single replica
Figure 14. Schema in node X with replicated schema from node Y
224 Furtado
Copyright ?© 2007, Idea Group Inc. Copying or distributing in print or electronic forms without written permission of
Idea Group Inc. is prohibited.
is used, then the y nodes must not contain replica slices of each other. Partitioned
replicas (PRs).guarantee this by creating groups and placing replica slices from one
group in a different group. This way we can take a whole group off-line simultaneously
for maintenance or other functionality, because the complete set of replica
slices are elsewhere. This strategy is a hybrid between FPR and FR.
If replicas are partitioned into x slices, we denote it by PR(x). If x = N, we have a
fully partitioned replica. A very simple algorithm to generate less than N slices is:
Number nodes linearly;
The data for node i is partitioned into X slices starting at 1;
For slice set j = 0 to R
For (slice x from 1 to X) Place slice x in node (i+j+ x) MOD N
Figure 15 compares the response time (line) for query TPC-H Q9 and the
minimum number of replicas needed (bars) when 5 out of 20 nodes are off-line using
full replicas (FRs), fully partitioned replicas (FPRs), and partitioned replicas (PRs).


Pages:
401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425