-
Notifications
You must be signed in to change notification settings - Fork 3
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
Bulk delete filesets from 2024 Feb/Mar fixity failures #2571
Comments
Update -- the April fixity report had 12 out of 14 of these PIDs as failures. The two no longer appearing are |
I'm adding this to the Summer board as part of the ghost fileset investigation. If they resist deletion by standard means, no need to pursue further -- we'll update the ghost-tracking list to include them and close this ticket. |
@carakey Im gonna give this a go and will report back once I go through and try to delete the list of PIDs |
I went through and checked on these works. All the works are coming back as I did find them in Solr though. I was able to grab them using Im going to try to see if there are any services Hyrax has that interacts with Fedora on a deeper level, like the SolrService, but I wont spin my wheels on it. This is about how far I've been able to get in the past with the Ghost FileSets. |
@straleyb Thanks for taking a look and for the explanation. Good timing, too - the fixity check should run later this week, so we'll see if they pop up again there. |
@straleyb These filesets did not reappear on the June fixity report. Do we conclude that they were just leftover Solr apparitions, already removed from the database, and now also removed from the index? |
Sounds like a pretty accurate conclusion to me. All I did was delete them from Solr and if its resolved now, its gotta be that. Case closed! |
Descriptive summary
The February and March fixity check reports both had identical sets of 14 failed file IDs. I researched these and found that one ID (
kp78gg577
) is a member of the set of known ghost filesets from #2530. Based on evidence including comment history and duplicate filenames, the remaining 13 all appear to be older versions of files that were supposedly deleted during review prior to approval. This ticket pertains to deleting the problematic filesets -- they do not load on the site so cannot be deleted in the UI. There is a separate ticket for the underlying issue, #2572.The following filesets should be deleted if possible -- with some suspicion that they either are or will become zombies/ghosts.
Update: These two PIDs were on the list originally, but appear to have been deleted as of April 2024:
41687r1849p290h89nRelated work
#2572
#2530
The text was updated successfully, but these errors were encountered: