The ALICE DAQ infoLogger

ALICE (A Large Ion Collider Experiment) is a heavy-ion experiment studying the physics of strongly interacting matter and the quark-gluon plasma at the CERN LHC (Large Hadron Collider). The ALICE DAQ (Data Acquisition System) is based on a large farm of commodity hardware consisting of more than 600...

Full description

Saved in:
Bibliographic Details
Published in:Journal of physics. Conference series 2014-01, Vol.513 (1), p.12005-7
Main Authors: Chapeland, S, Carena, F, Carena, W, Barroso, V Chibante, Costa, F, Dénes, E, Divià, R, Fuchs, U, Grigore, A, Ionita, C, Delort, C, Simonetti, G, Soós, C, Telesca, A, Vyvre, P Vande, Haller, B Von
Format: Article
Language:English
Subjects:
Accumulators
Architecture
Gluons
Heavy ions
Indexing
Large Hadron Collider
Messages
Physics
Programming
Quark-gluon plasma
Switches
Tables (data)
Citations: Items that this one cites
Items that cite this one
Online Access:Get full text
Tags: Add Tag
No Tags, Be the first to tag this record!
Description
Summary:ALICE (A Large Ion Collider Experiment) is a heavy-ion experiment studying the physics of strongly interacting matter and the quark-gluon plasma at the CERN LHC (Large Hadron Collider). The ALICE DAQ (Data Acquisition System) is based on a large farm of commodity hardware consisting of more than 600 devices (Linux PCs, storage, network switches). The DAQ reads the data transferred from the detectors through 500 dedicated optical links at an aggregated and sustained rate of up to 10 Gigabytes per second and stores at up to 2.5 Gigabytes per second. The infoLogger is the log system which collects centrally the messages issued by the thousands of processes running on the DAQ machines. It allows to report errors on the fly, and to keep a trace of runtime execution for later investigation. More than 500000 messages are stored every day in a MySQL database, in a structured table keeping track for each message of 16 indexing fields (e.g. time, host, user, ...). The total amount of logs for 2012 exceeds 75GB of data and 150 million rows. We present in this paper the architecture and implementation of this distributed logging system, consisting of a client programming API, local data collector processes, a central server, and interactive human interfaces. We review the operational experience during the 2012 run, in particular the actions taken to ensure shifters receive manageable and relevant content from the main log stream. Finally, we present the performance of this log system, and future evolutions.
ISSN:1742-6588
1742-6596
DOI:10.1088/1742-6596/513/1/012005