1 / 18

Web application for detailed real-time database transaction monitoring for CMS condition data

Web application for detailed real-time 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.

tuyen
Télécharger la présentation

Web application for detailed real-time database transaction monitoring for CMS condition data

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Web application for detailed real-time 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, VincenzoInnocente, 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. Salvatore di Guida

  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 sub-system: • 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 sub-detectors, mainly evaluated offline: • Pedestal offsets, • Drift velocities, • Alignments, • Needed online for HLT, and offline for reconstructing properly physical quantities coming from collision events. Salvatore di Guida

  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) PopCon CMS Compact Muon Solenoid • ORCON • (Offline Reconstruction Condition DB • Online System) Salvatore di Guida

  5. PopCon UML Diagram Salvatore di Guida

  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 sub-detector, • Monitor any transactions towards them. Salvatore di Guida

  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 sub-detector’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. Salvatore di Guida

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

  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. Salvatore di Guida

  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). Salvatore di Guida

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

  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 sub-detector. Salvatore di Guida

  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 Salvatore di Guida

  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 111740 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 Salvatore di Guida

  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 Salvatore di Guida

  16. Architecture Salvatore di Guida

  17. Results • 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 % offailure Salvatore di Guida

  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/email alert system for end-user in case of transaction failures and DBA-developer in case of hardware/network problems. • Automatic error resolution in a heterogeneous software environment • See Antonio’s talk. Salvatore di Guida

More Related