Alerts for when indexing stops
Currently there are no alerts when indexing stops working. We would like to see some put in place.
We recently had our keyword indexing stop working. It wasn't completely obvious to us for few months that there was a problem with indexing as it didn't seem to be every record.
Idea Value
Having an alert to III would save time troubleshooting if it's a metadata problem and raising tickets for something that could have an alert on it.
Eliza Richards
shared this idea
-
Kimberly Allen
commented
We have now had more experience with this. It appears that large data loads can trigger a java process spike with the keyword indexing/Lucene searcher and indexer. III saw out of memory errors and increased the memory of the searcher and indexer. However, we continue to see issues corresponding to large loads. Now our admin monitors "slow request" warnings in sierradb:/iiidb/errlog/lucenes-app.log. He opens a ticket when they become excessive. III then restarts the keyword indexing/Lucene engine.
-
Kimberly Allen
commented
We've hit this more than once. In those cases catalogers discovered it by happenstance. We really need an alert! So that we can quickly debug and resolve it.
-
Alison Pruntel
commented
It seems like something that should be in the admin app, system messages.