Recovery protocols for shared memory database systems

Significant performance advantages can be gained by implementing a database system on a cache-coherent shared memory multiprocessor. However, problems arise when failures occur. A single node (where a node refers to a processor/memory pair) crash may require a reboot of the entire shared memory syst...

Ausführliche Beschreibung

Gespeichert in:
Bibliographische Detailangaben
Veröffentlicht in:SIGMOD 95: International Conference on Management of Data 1995-05, Vol.24 (2), p.11-22
Hauptverfasser: Molesky, Lory D., Ramamritham, Krithi
Format: Artikel
Sprache:eng
Online-Zugang:Volltext
Tags: Tag hinzufügen
Keine Tags, Fügen Sie den ersten Tag hinzu!
container_end_page 22
container_issue 2
container_start_page 11
container_title SIGMOD 95: International Conference on Management of Data
container_volume 24
creator Molesky, Lory D.
Ramamritham, Krithi
description Significant performance advantages can be gained by implementing a database system on a cache-coherent shared memory multiprocessor. However, problems arise when failures occur. A single node (where a node refers to a processor/memory pair) crash may require a reboot of the entire shared memory system. Fortunately, shared memory multiprocessors that isolate individual node failures are currently being developed. Even with these, because of the side effects of the cache coherency protocol, a transaction executing strictly on a single node may become dependent on the validity of the memory of many nodes thereby inducing unnecessary transaction aborts. This happens when database objects, such as records, and database support structures, such as index structures and shared lock tables, are stored in shared memory.In this paper, we propose crash recovery protocols for shared memory database systems which avoid the unnecessary transaction aborts induced by the effects of using shared physical memory. Our recovery protocols guarantee that if one or more nodes crash, all the effects of active transactions running on the crashed nodes will be undone, and no effects of transactions running on nodes which did not crash will be undone. In order to show the practicality of our protocols, we discuss how existing features of cache-coherent multiprocessors can be utilized to implement these recovery protocols. Specifically, we demonstrate that (1) for many types of database objects and support structures, volatile (in-memory) logging is sufficient to avoid unnecessary transaction aborts, and (2) a very low overhead implementation of this strategy can be achieved with existing multiprocessor features.
doi_str_mv 10.1145/568271.223786
format Article
fullrecord <record><control><sourceid>proquest_cross</sourceid><recordid>TN_cdi_crossref_primary_10_1145_568271_223786</recordid><sourceformat>XML</sourceformat><sourcesystem>PC</sourcesystem><sourcerecordid>29439389</sourcerecordid><originalsourceid>FETCH-LOGICAL-c139t-f79a1e1cb3cd9c57738fcae4f49a834fd7ae4c88041a574cd276182195a51f373</originalsourceid><addsrcrecordid>eNotkM1LAzEUxAMq2FaP3vfkbWtePjbJUYpaoSCInkOafcHKrql5W2H_e1fW0zDMMAw_xm6ArwGUvtONFQbWQkhjmzO25NYZB0ZCc84WHBpZa8vtJVsSfXIOFhq-YPoVY_7BMlbHkoccc0dVyqWij1CwrXrs85S1YQj7QFjRSAP2dMUuUugIr_91xd4fH94223r38vS8ud_VEaQb6mRcAIS4l7F1URsjbYoBVVIuWKlSayYTreUKgjYqtsI0YAU4HTQkaeSK3c6707nvE9Lg-wNF7LrwhflEXjglnbRuKtZzMZZMVDD5Yzn0oYweuP-j42c6fqYjfwFA0Fbn</addsrcrecordid><sourcetype>Aggregation Database</sourcetype><iscdi>true</iscdi><recordtype>article</recordtype><pqid>29439389</pqid></control><display><type>article</type><title>Recovery protocols for shared memory database systems</title><source>ACM Digital Library</source><creator>Molesky, Lory D. ; Ramamritham, Krithi</creator><creatorcontrib>Molesky, Lory D. ; Ramamritham, Krithi</creatorcontrib><description>Significant performance advantages can be gained by implementing a database system on a cache-coherent shared memory multiprocessor. However, problems arise when failures occur. A single node (where a node refers to a processor/memory pair) crash may require a reboot of the entire shared memory system. Fortunately, shared memory multiprocessors that isolate individual node failures are currently being developed. Even with these, because of the side effects of the cache coherency protocol, a transaction executing strictly on a single node may become dependent on the validity of the memory of many nodes thereby inducing unnecessary transaction aborts. This happens when database objects, such as records, and database support structures, such as index structures and shared lock tables, are stored in shared memory.In this paper, we propose crash recovery protocols for shared memory database systems which avoid the unnecessary transaction aborts induced by the effects of using shared physical memory. Our recovery protocols guarantee that if one or more nodes crash, all the effects of active transactions running on the crashed nodes will be undone, and no effects of transactions running on nodes which did not crash will be undone. In order to show the practicality of our protocols, we discuss how existing features of cache-coherent multiprocessors can be utilized to implement these recovery protocols. Specifically, we demonstrate that (1) for many types of database objects and support structures, volatile (in-memory) logging is sufficient to avoid unnecessary transaction aborts, and (2) a very low overhead implementation of this strategy can be achieved with existing multiprocessor features.</description><identifier>ISSN: 0163-5808</identifier><identifier>ISBN: 0897917316</identifier><identifier>ISBN: 9780897917315</identifier><identifier>DOI: 10.1145/568271.223786</identifier><language>eng</language><ispartof>SIGMOD 95: International Conference on Management of Data, 1995-05, Vol.24 (2), p.11-22</ispartof><woscitedreferencessubscribed>false</woscitedreferencessubscribed><cites>FETCH-LOGICAL-c139t-f79a1e1cb3cd9c57738fcae4f49a834fd7ae4c88041a574cd276182195a51f373</cites></display><links><openurl>$$Topenurl_article</openurl><openurlfulltext>$$Topenurlfull_article</openurlfulltext><thumbnail>$$Tsyndetics_thumb_exl</thumbnail><link.rule.ids>314,780,784,27924,27925</link.rule.ids></links><search><creatorcontrib>Molesky, Lory D.</creatorcontrib><creatorcontrib>Ramamritham, Krithi</creatorcontrib><title>Recovery protocols for shared memory database systems</title><title>SIGMOD 95: International Conference on Management of Data</title><description>Significant performance advantages can be gained by implementing a database system on a cache-coherent shared memory multiprocessor. However, problems arise when failures occur. A single node (where a node refers to a processor/memory pair) crash may require a reboot of the entire shared memory system. Fortunately, shared memory multiprocessors that isolate individual node failures are currently being developed. Even with these, because of the side effects of the cache coherency protocol, a transaction executing strictly on a single node may become dependent on the validity of the memory of many nodes thereby inducing unnecessary transaction aborts. This happens when database objects, such as records, and database support structures, such as index structures and shared lock tables, are stored in shared memory.In this paper, we propose crash recovery protocols for shared memory database systems which avoid the unnecessary transaction aborts induced by the effects of using shared physical memory. Our recovery protocols guarantee that if one or more nodes crash, all the effects of active transactions running on the crashed nodes will be undone, and no effects of transactions running on nodes which did not crash will be undone. In order to show the practicality of our protocols, we discuss how existing features of cache-coherent multiprocessors can be utilized to implement these recovery protocols. Specifically, we demonstrate that (1) for many types of database objects and support structures, volatile (in-memory) logging is sufficient to avoid unnecessary transaction aborts, and (2) a very low overhead implementation of this strategy can be achieved with existing multiprocessor features.</description><issn>0163-5808</issn><isbn>0897917316</isbn><isbn>9780897917315</isbn><fulltext>true</fulltext><rsrctype>article</rsrctype><creationdate>1995</creationdate><recordtype>article</recordtype><recordid>eNotkM1LAzEUxAMq2FaP3vfkbWtePjbJUYpaoSCInkOafcHKrql5W2H_e1fW0zDMMAw_xm6ArwGUvtONFQbWQkhjmzO25NYZB0ZCc84WHBpZa8vtJVsSfXIOFhq-YPoVY_7BMlbHkoccc0dVyqWij1CwrXrs85S1YQj7QFjRSAP2dMUuUugIr_91xd4fH94223r38vS8ud_VEaQb6mRcAIS4l7F1URsjbYoBVVIuWKlSayYTreUKgjYqtsI0YAU4HTQkaeSK3c6707nvE9Lg-wNF7LrwhflEXjglnbRuKtZzMZZMVDD5Yzn0oYweuP-j42c6fqYjfwFA0Fbn</recordid><startdate>19950522</startdate><enddate>19950522</enddate><creator>Molesky, Lory D.</creator><creator>Ramamritham, Krithi</creator><scope>AAYXX</scope><scope>CITATION</scope><scope>7SC</scope><scope>8FD</scope><scope>JQ2</scope><scope>L7M</scope><scope>L~C</scope><scope>L~D</scope></search><sort><creationdate>19950522</creationdate><title>Recovery protocols for shared memory database systems</title><author>Molesky, Lory D. ; Ramamritham, Krithi</author></sort><facets><frbrtype>5</frbrtype><frbrgroupid>cdi_FETCH-LOGICAL-c139t-f79a1e1cb3cd9c57738fcae4f49a834fd7ae4c88041a574cd276182195a51f373</frbrgroupid><rsrctype>articles</rsrctype><prefilter>articles</prefilter><language>eng</language><creationdate>1995</creationdate><toplevel>online_resources</toplevel><creatorcontrib>Molesky, Lory D.</creatorcontrib><creatorcontrib>Ramamritham, Krithi</creatorcontrib><collection>CrossRef</collection><collection>Computer and Information Systems Abstracts</collection><collection>Technology Research Database</collection><collection>ProQuest Computer Science Collection</collection><collection>Advanced Technologies Database with Aerospace</collection><collection>Computer and Information Systems Abstracts – Academic</collection><collection>Computer and Information Systems Abstracts Professional</collection><jtitle>SIGMOD 95: International Conference on Management of Data</jtitle></facets><delivery><delcategory>Remote Search Resource</delcategory><fulltext>fulltext</fulltext></delivery><addata><au>Molesky, Lory D.</au><au>Ramamritham, Krithi</au><format>journal</format><genre>article</genre><ristype>JOUR</ristype><atitle>Recovery protocols for shared memory database systems</atitle><jtitle>SIGMOD 95: International Conference on Management of Data</jtitle><date>1995-05-22</date><risdate>1995</risdate><volume>24</volume><issue>2</issue><spage>11</spage><epage>22</epage><pages>11-22</pages><issn>0163-5808</issn><isbn>0897917316</isbn><isbn>9780897917315</isbn><abstract>Significant performance advantages can be gained by implementing a database system on a cache-coherent shared memory multiprocessor. However, problems arise when failures occur. A single node (where a node refers to a processor/memory pair) crash may require a reboot of the entire shared memory system. Fortunately, shared memory multiprocessors that isolate individual node failures are currently being developed. Even with these, because of the side effects of the cache coherency protocol, a transaction executing strictly on a single node may become dependent on the validity of the memory of many nodes thereby inducing unnecessary transaction aborts. This happens when database objects, such as records, and database support structures, such as index structures and shared lock tables, are stored in shared memory.In this paper, we propose crash recovery protocols for shared memory database systems which avoid the unnecessary transaction aborts induced by the effects of using shared physical memory. Our recovery protocols guarantee that if one or more nodes crash, all the effects of active transactions running on the crashed nodes will be undone, and no effects of transactions running on nodes which did not crash will be undone. In order to show the practicality of our protocols, we discuss how existing features of cache-coherent multiprocessors can be utilized to implement these recovery protocols. Specifically, we demonstrate that (1) for many types of database objects and support structures, volatile (in-memory) logging is sufficient to avoid unnecessary transaction aborts, and (2) a very low overhead implementation of this strategy can be achieved with existing multiprocessor features.</abstract><doi>10.1145/568271.223786</doi><tpages>12</tpages></addata></record>
fulltext fulltext
identifier ISSN: 0163-5808
ispartof SIGMOD 95: International Conference on Management of Data, 1995-05, Vol.24 (2), p.11-22
issn 0163-5808
language eng
recordid cdi_crossref_primary_10_1145_568271_223786
source ACM Digital Library
title Recovery protocols for shared memory database systems
url https://sfx.bib-bvb.de/sfx_tum?ctx_ver=Z39.88-2004&ctx_enc=info:ofi/enc:UTF-8&ctx_tim=2025-01-08T02%3A17%3A38IST&url_ver=Z39.88-2004&url_ctx_fmt=infofi/fmt:kev:mtx:ctx&rfr_id=info:sid/primo.exlibrisgroup.com:primo3-Article-proquest_cross&rft_val_fmt=info:ofi/fmt:kev:mtx:journal&rft.genre=article&rft.atitle=Recovery%20protocols%20for%20shared%20memory%20database%20systems&rft.jtitle=SIGMOD%2095:%20International%20Conference%20on%20Management%20of%20Data&rft.au=Molesky,%20Lory%20D.&rft.date=1995-05-22&rft.volume=24&rft.issue=2&rft.spage=11&rft.epage=22&rft.pages=11-22&rft.issn=0163-5808&rft.isbn=0897917316&rft.isbn_list=9780897917315&rft_id=info:doi/10.1145/568271.223786&rft_dat=%3Cproquest_cross%3E29439389%3C/proquest_cross%3E%3Curl%3E%3C/url%3E&disable_directlink=true&sfx.directlink=off&sfx.report_link=0&rft_id=info:oai/&rft_pqid=29439389&rft_id=info:pmid/&rfr_iscdi=true