-
Notifications
You must be signed in to change notification settings - Fork 18
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
Configure graphdb for production #692
Conversation
The last pattern of the WHERE clause in the query below contains With the
is aborted:
|
With
I restarted the triplestore and then it was aborted correctly. This is hard to reproduce. When increasing the limit to 5 seconds, it always crashes. The config looks ok:
|
The problem is that the concatenated string ( Ontotext will add an option so that the length of the concatenated string can be limited (as of release 8.5 of graphdb). |
Ontotext integrated the configuration option I am trying to reproduce the problem now. |
@subotic As of 8.5.0-RC4 query execution stops after reaching the time limit (before the triplestore crashed with large strings produced by GROUP_CONCAT). Productive versions of Knora should thus use graphdb 8.5 as soon as it is available. |
@subotic @benjamingeer I set the max. query execution time to five seconds and the limit of results to 50000. That seems reasonable to me. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This doesn't break any of our existing tests and older versions of GraphDB don't complain, so LGTM.
As soon as the official release is out, I will update Travis to use the new GraphDB version.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Very reasonable.
Try to find a reasonable setup for graphdb (8.3.1) that prevents the triplestore from crashing but does not break normal queries.
closes #685
closes #549