Kraken: Online and Elastic Resource Reservations for Cloud Datacenters

Carlo Fuerst, Stefan Schmid, Lalith Suresh, Paolo Costa

Research output: Contribution to journalJournal articleResearchpeer-review

13 Citations (Scopus)
157 Downloads (Pure)

Abstract

In cloud environments, the absence of strict network performance guarantees leads to unpredictable job execution times. To address this issue, recently, there have been several proposals on how to provide guaranteed network performance. These proposals, however, rely on computing resource reservation schedules a priori. Unfortunately, this is not practical in today's cloud environments, where application demands are inherently unpredictable, e.g., due to differences in the input data sets or phenomena, such as failures and stragglers. To overcome these limitations, we designed KRAKEN, a system that allows to dynamically update minimum guarantees for both network bandwidth and compute resources at runtime. Unlike previous work, KRAKEN does not require prior knowledge about the resource needs of the applications but allows to modify reservations at runtime. KRAKEN achieves this through an online resource reservation scheme, which comes with provable optimality guarantees. In this paper, we motivate the need for dynamic resource reservation schemes, present how this is provided by KRAKEN, and evaluate KRAKEN via extensive simulations and a preliminary Hadoop prototype.

Original languageEnglish
JournalIEEE/ACM Transactions on Networking
Volume26
Issue number1
Pages (from-to)422-435
Number of pages14
ISSN1063-6692
DOIs
Publication statusPublished - Feb 2018

Keywords

  • algorithms
  • Bandwidth
  • Cloud computing
  • embedding
  • IEEE transactions
  • Network topology
  • Network virtualization
  • predictable performance
  • Runtime
  • Virtual machining
  • Predictable performance
  • Embedding
  • Algorithms

Fingerprint

Dive into the research topics of 'Kraken: Online and Elastic Resource Reservations for Cloud Datacenters'. Together they form a unique fingerprint.

Cite this