CORAL Monitoring abstract for EGI CF 2012

Title

Monitoring in CORAL

Overview

The Large Hadron Collider (LHC), the world's largest and highest-energy particle accelerator, started its operations in September 2008 at CERN, Switzerland. Huge amounts of data are generated by the four experiments installed at different collision points along the LHC ring. The largest data volumes come from the ‘event data’ that record the signals left in the detectors by the particles generated in the LHC beam collisions and are generally stored on files. Relational database systems are commonly used instead to store the ‘conditions data’ that record the geometry, configuration and other working parameters of the detectors at the time the event data were collected. The CORAL software is widely used by the LHC experiments for storing and accessing conditions data using relational database technologies. It provides a C++ abstraction layer that supports data persistency for several backends and deployment models, including local access to SQLite files, direct client access to Oracle and MySQL servers, and read-only access to Oracle through the FroNTier/Squid and CoralServer/CoralServerProxy server/cache systems.

Description

Given the huge amount of operations executed by several CORAL clients at the same time on several database servers, it was crucial to develop a monitoring system with two main goals: first, to allow individual CORAL users to study and optimize the performance of the relational operations executed by their applications; second, to check whether the whole system is properly working and well configured. Client-level monitoring functionalities already existed in CORAL, but they have recently been reviewed and significantly improved, especially for the Oracle and Frontier plugins, and the same functionality are also being integrated into the CORAL server component (itself a CORAL-based application) and its client plugin. Work is in progress also on the monitoring of the CoralServerProxy components and on the aggregation of the monitoring information these proxies provide when deployed in a hierarchical structure, such as that used by the ATLAS High Level Trigger system. This presentation will report on the status of this work at the time of the 2012 EGI Community Forum, covering the design and implementation of these new features and the results from the first experience with their use.

Impact

CORAL had proven that it is a fundamental framework for database abstraction. It is used by various experiments and software components. It is appreciated for its reliability and performance.

Conclusion

The CORAL software is widely used by the LHC experiments for storing and accessing conditions data using relational database technologies. It provides a C++ abstraction layer that supports data persistency for several backends and deployment models. CORAL is appreciated for its reliability and performance.

Track classification

Operational services and infrastructure

Comments

None

-- RaffaelloTrentadue - 30-Nov-2011

Edit | Attach | Watch | Print version | History: r1 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r1 - 2011-11-30 - unknown
 
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    LCG All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback