CORAL Server Meeting

Tuesday 9 Sept 2008, 17:00 → 18:00 Europe/Zurich

31/2-029 (CERN)

Design and development issues of the CORAL server project, and integration with the ATLAS dbproxy project. Phone conference details: Dial-in: +1-510-665-5437 Passcode Tuesday : 8083 Passcode Wednesday : 8082 Agenda: - Experiences with the latest CORAL server (CORALSERVER-0-1-4) - Andy, Zsolt (15') - Development status: server, access plugin, proxy - Andy, Alexander, Zsolt (10') - Results of the CoralServer profiling - Zsolt (10') - Plan until November - the functionalities required in the first release (10') - Plans for the next week - All (5') - AOB - All (5')

Participants: Andrea, Andy, Alexander, Dirk, Rainer, Zsolt

Experiences with the latest CORAL server (CORALSERVER-0-1-4)

According to Andy's report, the server hangs at the Connect or StartTransaction request when using the full farm (~40 clients).
The server was configured to use a lot of threads. CERN side tests run well, but we have smaller parallel coverage, better tests are supposed to produce the hanging behaviour. 
The error is actually not a blocking issue, as in the presence of the proxy, the hang does not occur.

Development status: server, access plugin, proxy

Schema caching operation is added to CoralAccess, TCP IP optimization is added to CoralMessaging. Table and view list cacheing is ongoing. 
Monitoring tool: waiting for the daemon mode log operation on the server side (writing the server logs to the control channel).

Results of the CoralServer profiling

The already implemented optimizations boosted the COOL test execution time from 6-7 minutes to 70-80 seconds (reminder: server-less test execution time was ~50s).

Plan until November - the functionalities required in the first release

CORAL 2.1.0 will be the first CORAL release including offically the server. ATLAS online will use only the read-only functionalities, the security and update requirements will come from ATLAS offline later. It means that CORAL 2.1.0 will include a stable and well-performing server with readonly capabilities only, and on demand, we will add the other functionalities later.

AOB

There will be an AF presentation about the CORAL server progress on 24 September. There may also be a DM Group Meeting presentation about the topic. We need to think about the presentation for the November conference.

Plans for the next week

• CORALSERVER-0-1-5 release: schema and TCP/IP optimizations, logs to debug channel - Zsolt
• CORALSERVER-0-1-6 release: table and view list caching, possible resolution of the hang problem - Zsolt
• Stress test with many clients and requests - Zsolt, Alexander
• Monitoring tool: Alexander
• Thesis work: Alexander
• (optional) server design doc: Zsolt