Periodic and/or UI initiated reindex #1641
Replies: 2 comments 2 replies
-
Were the indexes not updating (as in, the actual files not changing) or was it that the results returned by |
Beta Was this translation helpful? Give feedback.
-
I'm still having issues with the index getting stale and needing to be recreated. I've speculated a lot of the open issues I see come across about DT not finding Vulnerabilities might be connected to this as you'll never be able to recreate it locally. For the fourth time this year I recently stopped the server, sudo rm -rf dependency-track/index/vulnerablesoftware/, restarted and suddenly vulnerabilities are found. These were observable in the database prior to shutdown and removal of the lucene index. I've been instructed to write a job to do this on a schedule from now on but I really think this should be addressed for DT as a whole. I'm not sure how many other people running DT have another source to independently validate their results like we do. but it's pretty clear to me that for whatever reason the index degrades over time and results in fewer findings. |
Beta Was this translation helpful? Give feedback.
-
I noticed my vulnerable software index stopped updating at various times in the last month on all 3 of my instances (prod, test, local-dev). The only way I know to fix this is stop DT, delete the index files and restart it. Is anyone else running into this? Can this be made more resilient? I was going to start looking into ways to detect that the index was stale or possibly investigate ways make vulnerability updates more transactional between the DB and lucene index. It's possible I'm only running into this because of my work on fuzzy matching but I've also noticed lucene indexes can end up incomplete or corrupt if the system is interrupted during it's initial startup. Any thoughts?
Beta Was this translation helpful? Give feedback.
All reactions