-
Notifications
You must be signed in to change notification settings - Fork 197
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Increase Timeout in demo? #307
Comments
I'm not really sure a timeout increase will help. I've found that sometimes the ML node does not seem to respond immediately after deploying a model, and regardless of how long you wait the first request always times out and then everything starts to work. I could not really find a solution, I don't see this happening very often, but it does happen to me sometimes. Do you have a suggestion of a timeout to use that works reliably for you? |
I just assumed a longer timeout would work... Though maybe what we really need is a retry ;-) |
I've noticed that even if you pass the elser install, use later will timeout, depending on your docker config for several minutes. Once it is all done, things work fine. So, folks using this example probably should retry until it works before showing anyone, and just keep that ES configuration hot. It would be nice to have a solution that shortens this. Possibly easier said than done thoughts:
|
@serenachou is this something your team can help with? |
I noticed that with my under powered laptop, when I run ES in Docker, and run the
flask create-index
i get a time out the first time, but it works teh second time:The text was updated successfully, but these errors were encountered: