2004ApacheConHigh-speedObjectWebLogger.ppt

High-speed ObjectWeb Loggerfor J2EE? Application Servers michael.giroux@ Agenda History Requirements Implementation Status History Suggested during ApacheCon 2003 Project initiated one week after ApacheCon 2003 Mailing List created December 2003 howl@ Journal Prototype Jan 26, 2004 Hiram Chirino employs Doug Lea’s Concurrent Programming in Java? Mike Spille pyrasun.xa_log Mar 09, 2004 search for “XA Exposed” CVS commit core functionality Mar 30, 2004 Some Early Thoughts Use existing Logging API Lack of “force” notification API Complexity and use of String parameters Journaling is not Logging Transaction Journal is short-lived Disposable after XA 2PC is complete Machine readable Binary data for performance Event Logs are historical Reviewed after server failures for clues Human readable String data for convenience Tracing is not Logging either Software Mirror strategy Available via Hardware and/or OS Requirements for HOWL Journal Support JOTM Transaction Logging ObjectWeb’s Java Open Transaction Manager API tuned for transaction log Binary data – byte[] Application specified sync Replay logged records for recovery operations Performance and operational objectives 10,000 XA TX/Sec No more than 25% CPU Minimal impact on server restart time Detect incomplete journal data BSD License 2PC Transaction Lifecycle Agenda History Requirements Implementation Status Implementation Log is private to application Sharing the log is controlled by the application Multiple physical files (2 or more) Easier than circular reuse Restart effected by number of files Multiple records buffered into logical blocks java.nio.ByteBuffer Application data records HOWL control records Threads may block until IO is forced to disk Block Format Enough information to verify complete write Header Signature “HOWL” Block Sequence Number (used in record keys) Block size (bytes) Bytes used Hash Code (optional) Time Of Day Footer Signature “LWOH” Block Sequence Number Time of Day (same as header) Log C