0

I've installed FusionAuth (awesome product) into a Docker Swarm cluster using the official docker-compose.yml file and everything seems to work brilliantly.

EXCEPT

Periodically, when a user goes to login they will be presented with the above error stating that the search engine is not available. If they try again immediately then everything works correctly! I would, obviously, prefer that they never saw the error.

Elasticsearch is definitely running and is responding to API calls correctly, and I can see the fusionauth_user index is present and populated with docs.

I guess my question is two fold:

1) What role does the ElasticSearch engine play in the FusionAuth ecosystem and can it be disabled?

2) Is there a configurable timeout somewhere that is causing the error message and, if so, where can change it?

I've search the docs for answers to the above but I can't seem to find anything :-(

Chris Clayson
  • 11
  • 2

1 Answers1

0

Thanks for the kind feedback.

1) What role does the ElasticSearch engine play in the FusionAuth ecosystem and can it be disabled?

Elasticsearch provides full text search of user data. Each time a user is created or updated the user is re-indexed. In this case during login, we are updating the search index with the last login instant.

This service is required and cannot be disabled. We have had clients request to make this service optional for embedded applications or small scale scenarios where Elasticsearch may not be required. While this is not currently in plan, it is possible we may revisit this option in the future.

2) Is there a configurable timeout somewhere that is causing the error message and, if so, where can change it?

Not currently.

Full disclosure, I am not a Docker or Docker Swarm expert at all - perhaps there are some nuances to Swarm and response time due to spin up and spin down of resources?

Do you see any exceptions in the log when a user sees this error on the login?

robotdan
  • 1,022
  • 1
  • 9
  • 17