I've got a question regarding the reindexing of the ElasticSearch fusionauth_user index.
When we perform a reindex it seems that some users/documents get "lost".
Some observations:
- We've enabled debugging on ElasticSearch and don't see any errors being thrown when the index is dropped and recreated.
- The query that fails afterwards is a "nested" search for a particular registration users have.
- When we
PATCHor lock/unlock users then they appear in the ElasticSearch index again and the query succeeds.
What happens when the reindex is performed? I'm struggling to understand why or how this could happen because I assumed all users/documents are inserted in the new index again?
Right now our workaround is to PATCH all users so that we can be sure that they're in the index.
Any ideas? Pointers?