-
Notifications
You must be signed in to change notification settings - Fork 23
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
Odinson server cuts connection after 75 seconds #35
Comments
@mcshlain, can you please try running the |
Will do. |
The branch did not solve the issue, I'm still getting the connection cut after 75 seconds: ''' |
I've encountered this:
which is set to exactly 75 seconds, I tried playing with it at some point but couldn't make it work, but I have no experience with the play framework so I might have not been setting it correctly. |
Thanks for testing it out. Would you mind trying once more? I think I've figured out the problem. It seems that in development mode the HTTP server starts before the config is available, so this sort of setting has to be specified in the project's |
The new change worked, the query I used returned after 750 seconds (so it did not got cut after 75). |
Curious to hear what sort of query and corpus you're using, but glad this last change took care of the timeout. |
These changes resolve #35. * netty -> Akka server backend * Change dev settings [In development mode, the HTTP server is started before the config is available](https://www.playframework.com/documentation/2.7.x/ConfigFile#HTTP-server-settings-in-application.conf), so changes to the server (timeouts, host, ports, etc.) must be made in [`build.sbt`](https://github.com/lum-ai/odinson/blob/d3e94a06c36e7e9ff9fc937cda4685ef53b317d6/build.sbt#L84-L90)
We're using the full wikipedia corpus (the index is 100GB) and I tested this with a |
Now that's a real index! You're probably already aware of this, but if you're not using the UI (or at least not the detailed parse view), you can set this config property to false to substantially reduce the size of the index:
|
thanks, I don't actually remember if we used this option or not when creating the index. |
Describe the bug
When executing a long query (against the backend API) the connection is cut by the server.
The connection always terminates at the 1 minute, 15 seconds mark. This makes it hard to work with odinson against very large corpora.
To Reproduce
Any query that doesn't return in 75 seconds.
Expected behavior
I would expect the connection to stay alive until results are returned.
Screenshots/Errors
Two output of
curl
and the timing withdate
(IP parts replaced by X).The text was updated successfully, but these errors were encountered: