Access the full text.
Sign up today, get DeepDyve free for 14 days.
[As shown in Fig. 8.3 in the previous chapter, the size of a RAMCloud Cluster can be changed without an interruption of the query processing executed by AnalyticsDB. However, the dynamic resizing in Fig. 8.3b is done via a purposeful revocation of a node which gives RAMCloud the time to redistribute the data from the to-be-removed node before its actual revocation. This kind of awareness cannot be expected in the event of a hardware failure. For the scenario of an unexpected hardware failure, RAMCloud features a fast crash recovery mechanism [ORS+\documentclass[12pt]{minimal} \usepackage{amsmath} \usepackage{wasysym} \usepackage{amsfonts} \usepackage{amssymb} \usepackage{amsbsy} \usepackage{mathrsfs} \usepackage{upgreek} \setlength{\oddsidemargin}{-69pt} \begin{document}$${^+}$$\end{document}11] as explained in Sect. 3.3.]
Published: Jul 8, 2015
Keywords: RAMCloud; Dynamic Resizing; Revocation Action; Hardware Failure; Previous Chapter
Read and print from thousands of top scholarly journals.
Already have an account? Log in
Bookmark this article. You can see your Bookmarks on your DeepDyve Library.
To save an article, log in first, or sign up for a DeepDyve account if you don’t already have one.
Copy and paste the desired citation format or use the link below to download a file formatted for EndNote
Access the full text.
Sign up today, get DeepDyve free for 14 days.
All DeepDyve websites use cookies to improve your online experience. They were placed on your computer when you launched this website. You can change your cookie settings through your browser.