You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When an object is deleted in Lustre, we can't determine the object path. We only get the fidstr and can't look up the path from the fidstr since the object no longer exists.
In the case where the path is not in the register map, the data object or collect would have never been created. However, on the connector side we do not know that the object wasn't created and we don't know the the deletion is outside the register map. Therefore, the deletions are blindly sent to iRODS.
Currently we are logging an error message when we are in policy mode and the object does not exist. Since this is a common occurrence change the log message to debug rather than error.
The text was updated successfully, but these errors were encountered:
When an object is deleted in Lustre, we can't determine the object path. We only get the fidstr and can't look up the path from the fidstr since the object no longer exists.
In the case where the path is not in the register map, the data object or collect would have never been created. However, on the connector side we do not know that the object wasn't created and we don't know the the deletion is outside the register map. Therefore, the deletions are blindly sent to iRODS.
Currently we are logging an error message when we are in policy mode and the object does not exist. Since this is a common occurrence change the log message to debug rather than error.
The text was updated successfully, but these errors were encountered: