Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Do not log an error when data object or collection deletion fails. #30

Open
JustinKyleJames opened this issue Jul 23, 2019 · 0 comments

Comments

@JustinKyleJames
Copy link
Collaborator

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant