| Daniels, D., Haskin, R., Reinke, J., Sawdon, W. "Shared Logging Services for Fault-Tolerant Distributed Computing," Position Paper for Fourth ACM SIGOPS European Workshop, Bologna, Italy, Sept. 1990. |
....reclamation. As a microkernel, Quicksilver typically implemented system services in user level servers. The log manager server was used primarily by the transaction manager, but was theoretically available to other subsystems. Later work explored sharing the log service across multiple resources [3]. The WAFS used by PFS is also a service for shared logging, built into a monolithic kernel architecture. Other work has explored sharing the WAFS service between the kernel and user applications [20] 4 PFS Architecture Overview 4.1 Block Modification and Writes When buffered file system ....
Daniels, D., Haskin, R., Reinke, J., Sawdon, W. "Shared Logging Services for Fault-Tolerant Distributed Computing," Position Paper for Fourth ACM SIGOPS European Workshop, Bologna, Italy, Sept. 1990.
....Logs are the greatest common divisor of most reliability mechanisms: well known algorithms for fault tolerance, such as two step commitment [1] recovery protocols [2] and concurrency control [3] need reliable logs. Thus, a logging service is a basic tool for reliability in distributed systems [4, 5]. Moreover, an increasing number of applications implement logs customized to their specific needs. As examples, Camelot [6] QuickSilver [7] and Isis [8] use logs for transactions management and failure recovery. Emacs uses an in memory log to undo and redo file modifications. Instant Replay [9] ....
....logs are multiplexed and replicated over multiple physical logs, i.e. storage media, also presenting the same semantics. For clients 1 , a logical log is represented by an unique log identifier (Lid) The pair (Lid, Rid) is similar to the Log Sequence Numbers of Camelot [6] or Quicksilver [4]. A client may use multiple logs. A physical or logical log may be shared between processes. Records from different logical logs can be multiplexed on a physical log. 3 Requirements The logs of different existing applications present several different features. The differences may be quantitative, ....
D. Daniels, R. Haskin, J. Reinke, and W. Sawdon, "Shared logging services for fault tolerant distributed computing," in Proc. of the 4th ACM SIGOPS European Workshop, (Bologna, (Italy)), pp. 3--5, Sept. 1990.
....condition is unknown or unrepeatable. Likewise, live monitoring plays an important part in service management. Loss of service is easily detectable when presented visually and appropriate steps can be taken to alleviate the problem. Logging services are provided for many reasons. Daniels et al. [2] describe a logging service for the provision of fault tolerance in distributed computing. When a fault occurs, a replay of the log can ensure that the correct state is regained. Others use logging services to improve performance in parallel and distributed systems [6, 7] detecting bottlenecks in ....
Dean Daniels, Roger Haskin, Jon Reinke, and Wayne Sawdon. Shared logging services for fault-tolerant distributed computing. ACM SIGOPS Operating Systems Review, 25(1):65--68, January 1991. Position Paper for Fourth ACM SIGOPS European Workshop.
....during restart by scanning the log only once and only forward. 1. Introduction Logs are an important facility for fault tolerant distributed systems since they allow to reliably store information that is needed to provide a global consistent system state also in the presence of failures [1][2][7] A log is a piece of stable storage that survives the complete crash of a node in a distributed system and can tolerate media faults. Logically, the log represents an append only sequence of unstructured records needed to redo past actions or to correct the loss of consistency due to effective ....
....by checkpointing the log table, i.e. transferring the contents of the log table to a separate log partition as described in Fig. 3. new log partition log record non volatile memory buffer volatile memory log table old log partition Fig. 3 : log compression Compared to existing Log Services [1][2][7] our approach to realize the compression phase turns out to be very efficient because of the following two aspects : Elsewhere, a Log Service is not able to distinguish between obsolete and relevant log records, since it does not get the knowledge to interpret the semantics of the log records. ....
D. Daniels, R. Haskin, J. Reinke, W. Sawdon : "Shared Logging Service for Fault Tolerant Distributed Computing", 4th ACM SIGOPS European Workshop, Bologna, 1990
....de journalisation a travers une e tude de quatre syste mes de journalisation existants : Clio, Camelot DLF, K I T L O G et Sprite LFS. Il vise a fournir une vue claire des proble mes et des solutions actuelles. Introduction An increasing number of applications uselogging for multiple purposes [Daniels 1990, Satyanarayanan et al. 1992a, Satyanarayanan et al. 1992b, Ruffin 1994] Surprisingly, very few logging facilities exist. Moreover, most of them are dedicated to a particular use. Since little research has been done in this domain, logging techniques are not very well known. Logging techniques are ....
....(see 5. 4) ffl Finally, the different algorithms for quick data lookup all present a tradeoff between space overhead and efficiency of read access (see x6) Research in general purpose logging systems is important because the need for logging is increasing in number and variety every day [Daniels 1990, Satyanarayanan et al. 1992a, Satyanarayanan et al. 1992b, Ruffin 1994] Generalpurpose systems present new challenges; for instance, a general purpose system must be customisable to its different client needs [Ruffin 1993] The lack of semantics knowledge, partially solved by logical logs, is ....
DANIELS, D., HASKIN, R., REINKE, J., SAWDON, W. 1990. Shared Logging Services for Fault Tolerant Distributed Computing. Proc. of the fourth ACM SIGOPS Eur. Work., Bologna (Italy). 3--5 Sep. 1990. Oper. Syst. Review, Vol. 25, N ffi 1, pp. 65-68. Jan.
No context found.
Daniels, D., Haskin, R., Reinke, J., Sawdon, W. "Shared Logging Services for Fault-Tolerant Distributed Computing," Position Paper for Fourth ACM SIGOPS European Workshop, Bologna, Italy, Sept. 1990.
No context found.
D. Daniels, R. Haskin, J. Reinke and W. Sawdon. Shared Logging Service for Fault Tolerant Distributed Computing. 4th ACM SIGOPS European Workshop, Bologna, 1990
Online articles have much greater impact More about CiteSeer.IST Add search form to your site Submit documents Feedback
CiteSeer.IST - Copyright Penn State and NEC