The following stack is possible because a different engine could be initializing the same index after the check for a valid index to exist:
We should catch the LockObtainFailedException and consider the index "probabily initialized fine" at this point, logging a warning.
|