Open tedgin opened 1 year ago
I think this might be completely solved/prevented by the logical locking introduced in 4.2.9.
We will test this again when we upgrade the Data Store to 4.2.11.
It looks like the issue is related to database transactions. The issue disappeared when I close the database transactions after file deletion and creation.
Ah, very good - a workaround until upgrade.
Bug Report
iRODS Version, OS and Version
iRODS 4.2.8, CentOS 7
What did you try to do?
I'm going to defer to @iychoi to explain how this happened, since he understands the steps better than I do. In brief, I think he did the following in rapid succession.
Our rule logic asynchronously replicates newly created data objects. I suspect that occasionally the replication of the data object created in step 1 would be in progress when he deleted the data object in step 2.
Expected behavior
I expect that when a data object is deleted while it is being replicated that it would cause the replication to be interrupted and the data object is entirely removed from the catalog.
Observed behavior (including steps to reproduce, if applicable)
We occasionally end up with two data objects in the catalog with the same logical path but different Ids. One data object has a replica in the replication resource, and the other has a replica in the ingest resource.
Here's an example.