|
|
## 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_ . |
|
|
\ No newline at end of file |
|
|
No known issue. |
|
|
\ No newline at end of file |