H2O: An

Autonomic,
Resource-Aware
Distributed
Database System

Angus Macdonald
Alan Dearle
Graham Kirby
 2

Motivation
 Resource Utilization

 Massive amount of resources in the enterprise are

unused
 10,000 machines at the University of St Andrews alone
 3

Motivation (ii)
 Resource Utilization
 Servers operating at 0% utilization still
consume 50% of power (relative to peak)*
100%
90%
Power Usage (relative to peak)

80%
70%
60%
50%
Power
40%
Energy Efficiency
30%
20%
10%
0%
0% 10% 20% 30% 40% 50% 60% 70% 80% 90% 100%
Utilization
*The Case for Energy-Proportional Computing (Google)
 4

Motivation (ii)
 Database systems could use these
unused resources
 Modern database systems can be difficult
to set up if you want data to be
 shareable
 highly available
 manageable
 5

Challenges
 The database system must be:
 Resource-aware
 Highly-available
 Autonomic
 6

Challenges (ii)
 Existing database systems
 Are not resource aware
 Rely on specially provisioned machines for
high-availability
 Make decisions autonomically, but with
more static configurations
 7

Implementation
 H2O is our research implementation
 Based on the H2 database system
 An H2O instance runs on every machine
 Containing a local database and a
resource monitor
A global schema is maintained
 8

Architecture: Relations
 Relations
are replicated over many
machines

TM(B)
TM(A) B
B
A
H2O

H2O

A H2O
 9

Architecture: Schema
A global schema is maintained by the
System Table

TM(B)
TM(A) B
B
A
H2O

H2O

ST A H2O
 10

Architecture: Meta-Data
 Meta-Datais also replicated to protect
against machine failure

TM(B)
TM(A) B ST
B
A
H2O

TM(B) H2O
TM(A)
ST A H2O
 11

Architecture: Placement

 Based on monitoring information

 Data placement
 Initial
Placement
 Movement
 Replication

 Query Planning
 12

Future Work
 Implementing the autonomic functionality
of H2O
 Carrying out evaluations of the system’s
performance
Questions?