Web application for detailed realtime database transaction monitoring

Transcription

1 Web application for detailed realtime database transaction monitoring for CMS condition data ICCMSE 2009 The 7th International Conference of Computational Methods for Science and Engineering Friday October 2 Salvatore Di Guida, Michele de Gruttola, Vincenzo Innocente, Antonio Pierro

2 Outline What are CMS condition data? How are CMS condition data handled by PopCon? What is PopCon monitoring? Why PopCon monitoring? GUI: PopCon from different users perspectives; Example of different users perspectives and different reports (table, error, chart). Architecture. Results. Upgrades and improvements. ICCMSE 2009 Salvatore di Guida 2

3 What are condition data? Configuration data: needed to bring CMS in running mode: Voltage settings of power supplies, Parameters for front-end electronics; Condition data: describing the state of any detector subsystem: High-low voltages, Magnet currents, Needed online for post mortem analysis of detector errors and for HLT, while offline for data quality monitoring and proper event reconstruction. Calibration data: describing the calibration of different subdetectors, mainly evaluated offline: Pedestal offsets, Drift velocities, Alignments, Needed online for HLT, and offline for reconstructing properly physical quantities coming from collision events. ICCMSE 2009 Salvatore di Guida 3

4 What is PopCon? PopCon (Populator of Condition Objects tool): is an application package fully integrated in the overall CMS framework intended to transfer, store, and retrieve condition data in the Offline Databases; Assigns metadata information (tag and IOV). CMS relies on three ORACLE databases for the condition data. PopCon OMDS (Online Master Database System) ORCOFF (Offline Reconstruction Condition Database Offline System) ORCON CMS (Offline Reconstruction Condition Compact Muon PopCon DB Solenoid Online System) ICCMSE 2009 Salvatore di Guida 4

5 PopCon UML Diagram ICCMSE 2009 Salvatore di Guida 5

6 Central Population of Condition Databases Centralized procedure using an account and a dedicated machine in the online network, where a set of automatic jobs was deployed: üpopulate ORCON accounts for each subdetector, ümonitor any transactions towards them. ICCMSE 2009 Salvatore di Guida 6

7 Central Population of Condition Databases Two possibilities for each sub-detector: Run automatically the so-called O2O application that reads from any online source, assigns tag and IOV and uploads data in the dedicated ORCON account (condition data); Dropbox (calibration data): users copy data in SQLite format into a dedicated folder, then these data are automatically exported to the subdetector s ORCON account. PopCon transfers data into the DB accounts: Creates log information stored in a DB account. Watchdog to monitor automatic jobs status: Monitoring information stored in the DB. ICCMSE 2009 Salvatore di Guida 7

8 Offline Dropbox Infrastructure that, using Web applications inside Virtual Machine technology, allows the exportation of calibration data to offline databases The calibration data are exported to ORCON using ssh tunneling, then streamed offline to ORCOFF The user uploads sqlite files containing calibration data and fills in metadata information Automatic HTTP request for obtaining the next Run to be processed at PromptReco level ICCMSE 2009 Salvatore di Guida 8

9 What is PopCon monitoring? Open source web based service for heterogeneous DB server performing large data transfers, providing HW and SW monitoring: DB status and history of all DB transactions: Aborted, committed, pending; Error monitoring reports: Identify any mistakes made by users, application failures, unexpected networks shutdowns, etc.; Reports from different users perspectives: Personal views for: Oracle database administrator, CMS detector manager, CMS sub-detector manager, End user. ICCMSE 2009 Salvatore di Guida 9

10 Why PopCon Monitoring? We might use the existing web monitoring tool for our purpose, but we need to fulfill the challenge requirements of CMS experiment: Usage of CMSSW standards: Generic CMSSW component to feel comfortable developers and end-users in building and using new package in CMSSW; Monitoring the heterogeneous software environment: Oracle DBs, CMSSW framework and other open source packages; Open source product; CERN Participation in Oracle Technology Beta Programs: We need a flexible architecture to handle unexpected error; Maximize the performance: Stress test of CMSSW infrastructure and HW components, Avoiding bottlenecks due to Huge Data Access (history and current data). ICCMSE 2009 Salvatore di Guida 10

11 PopCon from different users perspectives Personal reports, and the trend of self-monitoring to check the status of his own jobs Overview and full report of subdetector to check all transaction done in a dedicated account TheCMS sub-detector manager End -users The ORACLE DB Administrator and PopCon Developer The central CMS detector manager Overview and full report for all detectors subsystems Log Inspection for deep scan, security checks, performance issues ICCMSE 2009 Salvatore di Guida 11

12 GUI (I) Table Reporting Recent activity recorded from sub-detector RPC (Resistive Plate Chambers) Manager point of view: General view of last transactions towards a DB account, useful to keep track of all the new data transfers for a specific subdetector. ICCMSE 2009 Salvatore di Guida 12

13 GUI (II) Error reporting The Central CMS Detector Administrator Error Reporting view: General view of DB transaction status, useful to identify the different running jobs and spot quickly problems in DB transactions. Data transaction at 11:00 is missing ICCMSE 2009 Salvatore di Guida 13

14 GUI (III) Error reporting The ORACLE DB Administrator Error Reporting view: Log report to display information about primary key violation and inconsistencies in mapping between data members of C++ objects and schema objects. destdb: oracle://cms_orcon_prod/cms_cond_31x_pixel, inputtag: GainCalib_TEST_hlt, tag: SiPixelGainCalibrationHLT_2009runs_hlt, from to, user comment: craft09gains2 logdb: oracle://cms_orcon_prod/cms_cond_31x_popconlog CORAL/RelationalPlugins/oracle Error ORA-00001: unique constraint (CMS_COND_31X_PIXEL.METADATA_PK) violated (Executing the statement) error ---- Conditions BEGIN addmapping: metadata entry "SiPixelGainCalibrationHLT_2009runs_hlt" already exists ---- Conditions END ICCMSE 2009 Salvatore di Guida 14

15 GUI (IV) Chart reporting PopCon activity history: A multiple line chart view of transaction DB, useful to have a general view of the status of DBs usage for the central CMS detector manager and The ORACLE DB Administrator. Number of DB transactions Date ICCMSE 2009 Salvatore di Guida 15

16 Architecture ICCMSE 2009 Salvatore di Guida 16

17 Results % offailure Since the transaction status web monitoring was introduced: The percentage of transaction failure decreased From 28.9% to 15.2%; Peak in January due to the introduction of the new tool: Many users not yet familiar with it. Introduction of transaction status monitoring aug sep oct nov dec jan feb mar apr may jun jul aug ICCMSE 2009 Salvatore di Guida 17

18 Upgrades and improvements Storing and monitoring logs of quota information for the online account: DB backend set up, web interface ready to be deployed. SMS/ alert system for end-user in case of transaction failures and DBAdeveloper in case of hardware/network problems. Automatic error resolution in a heterogeneous software environment See Antonio s talk. ICCMSE 2009 Salvatore di Guida 18