DIRECTORY YggEnvironment, YggLog, YggLogRep; YggLogControl: CEDAR DEFINITIONS = BEGIN FileStore: TYPE = YggEnvironment.FileStore; TransID: TYPE = YggEnvironment.TransID; PageCount: TYPE = YggEnvironment.PageCount; RecordID: TYPE = YggLog.RecordID; RecordType: TYPE = YggLog.RecordType; Format: PROC []; Recover: PROC []; DiscoverWhereToStartAnalysisPass: PROC [errorOnBadCheckpoint: BOOL] RETURNS [ ok: BOOL, checkpointWord: YggEnvironment.WordNumber, checkpointRecord, startAnalysisRecord: RecordID]; AnalysisProc: TYPE = PROC [record: RecordID, type: RecordType, trans: TransID]; RegisterAnalysisProc: PROC [recordType: RecordType, analysisProc: AnalysisProc]; ForkCheckpointProcess: PROC [wakeupPeriodInSeconds: NAT]; CheckpointProc: TYPE = PROC [] RETURNS [keepRecord, startAnalysisRecord: RecordID]; RegisterCheckpointProc: PROC [checkpointProc: CheckpointProc]; WordsUsableByClient: PROC [] RETURNS [words: INT]; RecordIDOfNextWrite: PROC [] RETURNS [RecordID]; WriteNoopRecords: PROC [nPages: PageCount] RETURNS [followingRecord: RecordID]; PeekCurrentType: PROC [thisRecord: RecordID] RETURNS [recordType: RecordType]; PeekCurrentTransactionHeader: PROC [thisRecord: RecordID] RETURNS [transHdr: YggLogRep.TransactionHeader]; END. YggLogControl.mesa Copyright Ó 1985, 1987, 1988, 1989 by Xerox Corporation. All rights reserved. Last edited by MBrown on April 3, 1983 10:54 am Hauser, March 8, 1985 10:49:19 am PST Bob Hagmann June 15, 1989 8:41:43 am PDT This interface contains procedures for initialization of the log subsystem. One aspect of initialization is registering procedures to take part in the analysis pass of recovery and in periodic log checkpoints. The transaction and backup subsystems are expected to register procedures for this purpose. All calls to RegisterAnalysisProc and RegisterCheckpointProc must complete before the analysis pass of recovery begins. To ensure this, a client can be called by InitProcs.CalledBeforeAnalysisPass, or can call from a PROGRAM proc (called by STARTing the module). This call formats the given files to a well-defined initial state that is acceptable to recovery. This should not be called while the server is running. Call Format, then call Recover, in order to cold-start a server. CAUTION: The previous contents of logFile and restartFile are lost! This call performs a warm-start of the log subsystem using the given log. As a side effect, many procedures registered through the YggLog and YggLogControl interfaces are called, as well as the procedures defined in InitProcs. Where to begin? Called from Recover during analysis pass over log. This proc can read record using YggLog.ReadForRecovery (to skip over transaction portion of log), or LogBasic.GetCurrent (to read entire log record). Forks a process that performs periodic log checkpoints. Should not be called until Recover has returned. This process is an infinite loop that sleeps for wakeupPeriodInSeconds seconds, then does the following: 1) calls each subsystem that writes log records. At present the three subsystems that write log records are the worker, coordinator, and backup. Each subsystem declares how much log it depends upon, and how much log it must examine at restart. If a subsystem notices that it is using too much log, it takes action (probably in another process) to reduce its use. The worker subsystem forces all dirty FilePageMgr pages to disk and writes workerComplete log records for transactions whose effects are fully done (or undone). 2) writes a checkpointComplete log record if some value in this record is different than in the previous checkpointComplete record. 3) initiates an incremental garbage collection in order to keep zones compact. (it makes sense to do this in the checkpoint process since step 1 often frees storage). nextRecord is the RecordID of the next log record to be written. This parm should be used by the CheckpointProc to control its use of the finite log resource (keeping the log from filling up and keeping the cost of restart down to a reasonable value). keepRecord is oldest record in online log required by this component. startAnalysisRecord is oldest record in online log that must be examined during the analysis pass of restart. Making keepRecord and startAnalysisRecord distinct allows the backup system to require much more online log than other subsystems, yet allow restart to be fast. Client should not allow its use of log (RecordID of next AlpineLog.Write - keepRecord) to exceed this bound. RecordID that AlpineLog.Write would have returned as thisRecord, had it been called. There is no way to guarantee that calling AlpineLog.Write after calling this proc will generate this RecordID, however. For use by a test program that wishes to generate a load on the log. Peek at the next record type. Peek at the next record type. ÊZ˜šœ™IcodešœN™N—šœ™Jšœ ™ K™%K™(—J˜šÏk ˜ Jšœ˜Jšœ˜Jšœ ˜ J˜—šœœ˜"Jš˜Jšœœ˜+Jšœ œ˜'Jšœœ˜+Jšœ œ˜!Jšœœ˜%J˜JšœK™KJ˜JšœS™SJšœM™MJšœ@™@J˜JšœQ™QJšœP™PJšœN™NJšœ™J˜J˜šÏnœœ˜JšœI™IJšœO™OJšœ@™@JšœC™CJ˜—šžœœ˜JšœI™IJšœQ™QJšœF™FJ˜J˜—šž œœœœ˜MJšœœ^˜fJ™J˜J˜—J˜šžœœœ6˜OJšœ2™2JšœP™PJšœD™DJ˜—Jšžœœ6˜PJ˜J˜šžœœœ˜9JšœM™MJšœ™JšœO™OJšœ™JšœQ™QJšœO™OJšœJ™JJšœO™OJšœQ™QJšœI™IJšœ6™6JšœS™SJšœ/™/JšœN™NJšœW™WJ˜—šžœœœ˜Jšœ-˜4JšœK™KJšœI™IJšœN™NJšœ™JšœE™EJšœO™OJšœ™JšœN™NJšœQ™QJ˜—Jšžœœ"˜>J˜šžœœœ œ˜2JšœV™VJšœ™J˜—šžœœœ˜0JšœT™TJšœV™VJšœ ™ J˜—šžœœœ˜OJšœD™DJ˜—šžœœœ˜NJšœ™J˜—šžœœœ)˜jJšœ™J˜—Jšœ˜J˜J˜—J˜—…—ôb