1 / 9

Persistency Framework News for ATLAS

Persistency Framework News for ATLAS. Andrea Valassi (IT-ES) For the Persistency Framework team ATLAS Database Meeting, 15 th July 2010. Outline. Recent developments and releases POOL, CORAL, COOL Oracle client Work in progress. LCG 56g for ATLAS (May 2010).

lyn
Télécharger la présentation

Persistency Framework News for ATLAS

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. Persistency Framework Newsfor ATLAS Andrea Valassi (IT-ES) For the Persistency Framework team ATLAS Database Meeting, 15th July 2010

  2. Outline • Recent developments and releases • POOL, CORAL, COOL • Oracle client • Work in progress

  3. LCG 56g for ATLAS (May 2010) • Main motivation: fix inconsistency in expat library • Wrong version of expat was linked to frontier_client (bug #65398) • Caused issues with ROOT (bug #65114) and GFAL (bug #65722) • POOL 2.9.8a • Rebuild of previous POOL 2.9.8 (for ATLAS in LCG 56f) • CORAL 2.3.9a • Do not link FrontierAccess against libexpat (bug #65936) • COOL 2.8.6b • Rebuild of previous COOL 2.8.6 (for ATLAS in LCG 56f) • For full details see the release notes on TWiki • Also: port to osx10.6/32bit

  4. LCG 59 for ATLAS (July 2010) • Main motivation: external upgrades, POOL/CORAL patches • ROOT 5.26, python 2.6, oracle 11.2, Xerces 3.1, Qt 4.6… • POOL 2.9.9a • ATLAS-specific support for fast file merge • Improved handling of RelationalCollection metadata • CORAL 2.3.10a • First (incomplete?) fix for transaction bug #65597 in reconnecting • ATLAS-specific optimizations in FrontierAccess (bug #66638) • Fix to write CLOBs larger than 64kb in ATLAS_DD (bug #47663) • Fix segfault with synonyms in ATLAS PVSS (bug #68313) • COOL 2.8.6d • Rebuild of previous COOL 2.8.6b (for ATLAS in LCG 56g) • For full details see the release notes on TWiki • Also: drop osx10.5 (keep only osx10.6)

  5. New 11.2.0.1.0p2 Oracle client • All bugs relevant to CORAL are fixed in 11.2.0.1.0p2 • Crash on AMD Opteron quadcore (bug #62194) • I tested this in Ljubljana – thanks to many site admins for their help! • SELinux issues on SLC5 (bug #45238) • Now fixed for all four combinations 32/64bit OCI/OCCI • ATLAS upgrading again from 10g to 11g in LCG 59 • Had downgraded back to 10g in LCG 56e (April 2010) because of the crash on AMD Opteron quadcore (bug #62194) at many sites • No showstopper from 10g, but 11g is better for the future • Several bugs (SELinux and others) are only fixed in 11g client • Light instant client (smaller memory) available on both 10g/11g • Oracle 11g server for development will soon be deployed

  6. Frontier and CORAL / COOL • Smooth integration of Frontier into ATLAS software in 2009 • Frontier was already supported in CORAL (production use in CMS) • Frontier was already supported in COOL (…just in case…!) • A few ATLAS-specific s/w optimizations were needed • E.g., avoid duplicated queries in FrontierAccess (bug #66638) • Also, minor functional fixes in FrontierAccess (e.g. bug #60053) • Further optimizations have been suggested • E.g. additional table caches in COOL – pending (bug #66639) • Is anything else needed on the software side? • Monitoring of Frontier servers and Squid caches • Very active community of users and site admins in ATLAS and IT (focusing on service-level monitoring of load and availability) • Some query-level monitoring in frontier_client (used by CORAL) • Work ongoing in CORAL team for query-level monitoring (e.g. for CORAL server monitoring in ATLAS online) • Is anything needed for Frontier monitoring on the software side?

  7. Work in progress and open issues • CORAL • Improve CORAL robustness in database reconnections • “A transaction is not active” in CORAL server(bug #65597) • ORA-24327 “need explicit attach” in ATLAS and CMS (bug #24327) • New functionalities (e.g. sequences, constraints…) • API extensions break binary compatibility of ATLAS online/offline • CORAL server extensions (monitoring, security, R/W access…) • COOL • Many payload per IOV: replace ATLAS CoraCool (task #10335) • API extensions break binary compatibility of ATLAS online/offline • PVSS2COOL review… • POOL • Very active development on collections (ATLAS only) • Simplified POOL-ORA is being cloned (moved?) into CMSSW • ROOT area quiet after adding ATLAS fast merge – more needed?

  8. Reserve slides

  9. Oracle client – Apr 2010 summary • ATLAS downgraded back from 11g to 10g in 56e (Feb 2010) • 11g client bug #62194 on AMD Opteron quadcore at many sites • ATLAS is presently using 10.2.0.4p1 with light instant client • See also the minutes of the February 11 T1SCM • 10g client is OK for now, but 11g is desirable eventually • Light instant client (smaller memory) available on both 10g/11g • SELinux bug #45238 is ~ fixed in 11g, workaround for 10g • OCIEnvCreatebug #31554 fixed in 11g, backport in 10.2.0.4p1 • LOB MT hang bug #47435 fixed in 11g, workaround in CORAL • LOB MT crash bug #49662 solved only by workaround in CORAL • OCIStmtReleasebug #61090 only in 11g, workaround in CORAL • Apr 2010: installed 11.2.0.1.0p1 with three new patches • Fix for AMD Opteron: seems OK, waiting for ATLAS validation • SELinux fixes for OCI 64bit (and OCCI 32bit)

More Related