|
# Welcome to the B2SAFE wiki!
|
|
B2SAFE wiki
|
|
|
|
===========
|
|
|
|
The B2SAFE service is a software developed within the [EUDAT project](http://www.eudat.eu).
|
|
|
|
|
|
* From iRODS 3.3.x to irods 4.1.6 in one go |
|
The Service offers functionality for the long term data preservation. The main feature is the function to replicate data sets across different data centres in a safe and efficient way while maintaining all information required to easily find and query information about the replica locations. The information about the replica locations and other important information is stored in a PID ([Persistent IDentifier](https://www.eudat.eu/services/userdoc/pids-in-eudat)) registry. The B2SAFE Service is implemented as a package on top of [iRODS](http://www.irods.org), providing a set of iRODS rules and scripts.
|
|
|
|
|
|
|
|
---------------
|
|
|
|
Deployment
|
|
|
|
---------------
|
|
|
|
|
|
|
|
See install.txt .
|
|
|
|
|
|
|
|
---------------
|
|
|
|
Documentation
|
|
|
|
---------------
|
|
|
|
|
|
|
|
http://eudat.eu/services/userdoc
|
|
|
|
|
|
|
|
---------------
|
|
|
|
Known issues
|
|
|
|
---------------
|
|
|
|
### Memory Leak
|
|
|
|
|
|
|
|
- Issue:
|
|
|
|
|
|
|
|
the iRODS server forks an irods agent for each client request: each irods agent handling a PID creation request allocates about 1 GB of memory/10^4 object registered, due to a memory leak.
|
|
|
|
Therefore in order to manage concurrent requests coming from, for example, 30 users, involving the registration of collections of 10^4 objects, the B2SAFE administrator should plan to provide at least 32 GB of memory dedicated to the B2SAFE instance (https://github.com/irods/irods/issues/2929).
|
|
|
|
|
|
|
|
- Fix:
|
|
|
|
|
|
|
|
An iRODS [development package](https://github.com/irods/contrib/tree/master/microservices/administration/msifree_microservice_out) is needed. The installation instructions are here: https://github.com/irods/contrib/issues/7#issuecomment-172605195. Once installed, it is possible to use the microservice msifree_microservice_out to avoid the memory leak issue, setting to "true" the parameter _msiFreeEnabled_ in the function _getConfParameters_ in the rule set file _local.re_ . |