StoRM Backend v. 1.11.8

Released on 13.03.2015 with StoRM v. 1.11.8.

Description

This release fixes a critical issue that prevented the proper cleanup of PtP requests state after an srmRm was called on a SURL. As a consequence, a SURL could remain stuck and it would be impossible to perform other PtPs on that SURL without cleaning the database state by hand. All sites should upgrade to 1.11.8 at their earliest convenience to avoid being affected by this issue.

This release also introduces peformance improvements in the handling of SRM releaseFiles and statusPrepareToGet requests.

Bug fixes

• [STOR-779] - rm command does not properly abort ongoing PtP requests
• [STOR-776] - Inefficient SQL query for surl status checks
• [STOR-777] - Inefficient query used to update SURL status when a releaseFiles is called
• [STOR-778] - Improve efficiency on status PtGs

Installation and configuration

This release requires a YAIM reconfiguration of the backend service, in order to apply changes to the StoRM database schema.

IMPORTANT In order to avoid issues with locked SURLs as consequeunce of this issue, a database cleanup is recommended. To drop the storm database:

• log into the StoRM MySQL database as root
• drop the storm_db and storm_be_ISAM databases
• run YAIM to recreate the databases from scratch

If you cannot afford to drop the database (e.g., you cannot stop the service), see this GIST for scripts and advice on how stuck surls can be unlocked. You will need to run YAIM anyway after upgrading the packages to apply the schema changes introduced by this release.

You can find information about upgrade, clean installation and configuration of StoRM services in the System Administration Guide.