50 likes | 146 Vues
An overview of archiving system deployed at Soleil Tango meeting with insights on system architecture, improvement goals, deployment challenges, and progress made since the last meeting. Includes advancements in code consolidation, error handling, and database communication for efficient data archiving and retrieval. Discusses future plans, Oracle database management, and scalability enhancements.
E N D
Archiving System Deployed at Soleil Tango Meeting (Hamburg, September 2007)
Tango Archiving Service • Since last meeting • Deployment • Next goals Tango Meeting (Hamburg, September 2007)
Since the last meeting – March 2007 • Code consolidation • Error treatment in the collectors • Thread pooling usage in the TdbArchivers • No more problem with the spectrum storage in the Oracle Database • Improvement of the communication between DB and the various Archivers • Connection pool in the SnapArchiver (Apache commons object-pooling + Jakarta Commons DBCP) • Deployment problems due to the high number of archived attributes • Oracle Database Backup / Restore • On going for the restoring part Tango Meeting (Hamburg, September 2007)
Machine Control – System Architecture • HDB : Since March • 2 600 archived Tango attributes near 5 000 attributes • Always 2 Linux servers • Knuth : 25 DServers * 5 devices, so 125 HdbArchivers • Jacquard : Oracle Database – 250 Go ↗ • TDB : Since March • 2 950 archived Tango attributes near 4 800 attributes • 2 Linux servers 3 Linux servers • Aho : 20 DServers * 5 devices, so 100 TdbArchivers • Foo : 20 DServers * 5 devices, so 100 TdbArchivers • Gernelle : Oracle Database – 90 Go for 3 days Tango Meeting (Hamburg, September 2007)
Archiving System Goals • Cohabitation between the events and the polling in the same code • Improvement of the HDB Oracle Database backup / restore procedure • Real Application Cluster from Oracle is studied to replace the current infrastructure • Deployment of the TDB archiving on the beam lines Tango Meeting (Hamburg, September 2007)