注册 登录  
 加关注
   显示下一条  |  关闭
温馨提示!由于新浪微博认证机制调整,您的新浪微博帐号绑定已过期,请重新绑定!立即重新绑定新浪微博》  |  关闭

中吴南顾惟一笑

成功法则就是那19个字

 
 
 

日志

 
 

ARIES: A Transaction Recovery Method Supporting Fine-Granularity Locking and Partial Rollbacks Using Write-Ahead Logging  

2010-06-11 16:24:22|  分类: dbms |  标签: |举报 |字号 订阅

  下载LOFTER 我的照片书  |
http://www.eecs.berkeley.edu/~fox/summaries/database/aries.html
C. Mohan, Don Haderle, Bruce Lindsay, Hamid Pirahesh, and Peter Schwarz
Summary by: Steve Gribble and Armando Fox

One-line summary: Extraordinarily intricate and delicate logic necessary for fully general, robust, and fine-grained recovery and rollback of transactions.

Overview/Main Points

  • This paper is far too detailed to provide a succint summary. The highest-level points are:
    • ARIES records in a log the progress of the transaction, and any actions (including UNDO/REDO) which cause changes to recoverable data objects.
    • ARIES uses write-ahead logging (WAL) - an updated page is written back to the same location from where it was read (in-place updating), and WAL guarantees that log records representing changes to the data must already be on stable storage before the in-place updating of DB data can occur.
    • Some terms and concepts which are important:
      • forward-processing: updates performed when system is in normal processing mode (SQL calls)
      • partial rollback: ability to set up savepoints during transaction, and request roll back of changes performed by transaction to savepoint
      • total rollback: all updates of transaction are undone
      • normal undo: total or partial rollback when system is in normal operation
      • restart undo: transaction rollback during restart recovery after system failure
      • compensation log records (CLRs) are logs of updates performed during rollback - in ARIES, CLRs are viewed as redo-only log records.
      • page-oriented redo occurs if log record whose update is being redone describes the page of the database that was modified. logical redo is higher-level; performing a redo may require accessing several pages.
  • ARIES "features":
    1. simplicity (!!!!!)
    2. operation logging (and value logging)
    3. flexible storage management
    4. partial rollbacks
    5. flexible buffer management (make least number of assumptions about buffer management policies in ARIES)
    6. recovery independence - the recovery of one object should not force the concurrent recovery of another object.
    7. logical undo - the ability, during undo, to affect a page that is different from the one modified during forward processing (allows higher level of concurrency)
    8. parallelism and fast recovery - exploit parallelism during the different stages of restart recovery and during media recovery (multiprocessors are your friends)
    9. minimal overhead - good performance during normal and recovery processing

Relevance

The canonical paper on transaction recovery. Shows in gory, gory detail what is required for industrial strength transaction recovery techniques.
  评论这张
 
阅读(130)| 评论(0)
推荐 转载

历史上的今天

在LOFTER的更多文章

评论

<#--最新日志,群博日志--> <#--推荐日志--> <#--引用记录--> <#--博主推荐--> <#--随机阅读--> <#--首页推荐--> <#--历史上的今天--> <#--被推荐日志--> <#--上一篇,下一篇--> <#-- 热度 --> <#-- 网易新闻广告 --> <#--右边模块结构--> <#--评论模块结构--> <#--引用模块结构--> <#--博主发起的投票-->
 
 
 
 
 
 
 
 
 
 
 
 
 
 

页脚

网易公司版权所有 ©1997-2017