Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
HSEARCH-4218 When mass indexing, wait for ID producing threads to finish
Previously we were only waiting on indexing threads. Obviously those would never finish before the identifier producing threads were done producing identifiers, but they could finish between the end of the identifier production and the time where the ID producing threads were actually done with some finalizing tasks. This could result in some failure notifications to be pushed to the failure handler *after* startAndWait() returned, which made MassIndexingIncludedEntityMapHierarchyIT fail from time to time. Reasons for this change: 1. This won't impact performance much: when indexing threads finish, ID producing threads are mostly done anyway (worst case they still need to report an exception, but that's all). 2. We will now wait for all threads to finish reporting errors before we consider indexing successful. 3. We will now propagate exceptions thrown by ID producing threads to the caller of `massIndexer.startAndWait()`, instead of considering indexing successful.
- Loading branch information
Showing
7 changed files
with
292 additions
and
88 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.