Hi all, I’ve run into a problem that appears to be related to our recent upgrade to Hyrax 3.6. It’s taking a really long time to add or remove participants in an Administrative Set. It looks like Hyrax is doing something with each record in the Admin Set when we do these task (it didn’t in 2.x), and the time it takes to complete the action is proportional to the # of records in the Admin Set. For our largest Admin Set, it just eventually times out, so I’m currently unable to make changes to that Admin Set.
- Slack
UPDATE: Rob said this is likely due to Sipity being added to all member works of the admin set. We should check if this has been fixed in Hyrax (it may not have)
bkiahstroud
commented
6 months ago
Story
Notes
Initially, this was thought to be due to nested indexing. However, the current working theory is that the participant is being added to all works within the admin set.
UPDATE: Rob said this is likely due to Sipity being added to all member works of the admin set. We should check if this has been fixed in Hyrax (it may not have)