pulibrary / dpul

Princeton's digital collections: Digital PUL
https://dpul.princeton.edu/
Apache License 2.0
15 stars 0 forks source link

Treasures of the East Asian Library Reindex issues #1488

Closed kelea99 closed 6 months ago

kelea99 commented 7 months ago

Summary

@tventimi reported not seeing new items appearing in this collection after making them complete in Figgy on the morning of Wednesday, Nov. 22. I was able to get them in by resaving/completing in figgy. as of today, the collection is still having rendex issues.

Impact

Please include hard deadlines, if the exhibit is part of an event, the issue is stopping work, etc. issue is stoppind dpul access to materials.

Priority recommendation

Sudden Priority Justification

Required if "asap" or "within the next 3 weeks" is checked. Add "Sudden Priority" and "Maintenance/Research labels this is stopping access to materials in DPUL. @tventimi - is there an immediate deadline? is this asap request?

Expected behaviour

Actual behaviour

Steps to reproduce behaviour

Screenshots

tventimi commented 7 months ago

Just an update on this issue: I have gradually been adding items to this collection, and some appear in DPUL right away, others not even after several days. As of today, I have marked reels 1-136 as complete in Figgy, and 20 of them are missing in DPUL: 100, 102-106, 108, 110-112, 117, 118, 120, 121, 124, 125, 128, 130, 132, and 134. To me, there is no obvious pattern to which reels appear in DPUL and which do not.

kelea99 commented 7 months ago

Making a new ticket to check out DPUL-Figgy sync auto-reindexing in general, @hackartisan . got another similar issue as above but for ephemera folders. I know he had a problem in the past, so ill look for that closed issue to refer to.

kelea99 commented 7 months ago

See:https://github.com/pulibrary/dpul/issues/1491

tventimi commented 6 months ago

I solved the issue for this particular series just by saving all of the missing reels again, though for some of them it look several tries.

hackartisan commented 6 months ago

Today I discovered that one of our DPUL machines was not able to connect to redis. That explains this error perfectly: Any time the workers on that box picked up the updates from Figgy, they tried to enque the index update but it got dropped because it couldn't enqueue the job. So sometimes it would have worked (when the worker that could connect picked up up) and sometimes it didn't (when the worker with connection issues picked it up). The redis connection is now fixed and that should resolve this issue.

Details of the fix are in https://github.com/pulibrary/dpul/issues/1491#issuecomment-1875942190