-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Low
-
Affects Version/s: None
-
Component/s: Search - Core
Exceptions thrown from worker threads in an executor service are swallowed without any logging. If we lose connectivity to the database for any reason during a reindex, this will not show up in the logs. We need to log if this ever happens, and if possible, attempt to reconnect and resume reindexing.
- incorporates
-
CONFSERVER-20435 Reindexing threads should use shorter transactions
- Closed
- is related to
-
CONFSERVER-20878 Manual re-indexing process hangs at 99%
-
- Closed
-