-
Notifications
You must be signed in to change notification settings - Fork 852
On execution of FULLTEXT search / AQL query db is restarting #4185
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
Comments
arangodb 3.2 setup is working fine with same configuration |
@xbirdblack : could you please provide some basic information about the AQL query you are executing? It would help if you could post the query string here and the list of indexes for the collection in question. Thanks! |
Query from node js driver |
A potential fix for the issue is contained in this pull request: #4239 |
Hi @xbirdblack, thanks for reporting the bug. Version 3.3.3 including the fix for FULLTEXT search is released. |
Uh oh!
There was an error while loading. Please reload this page.
my environment running ArangoDB
I'm using the latest ArangoDB of the respective release series:
Mode:
Storage-Engine:
On this operating system:
this is an AQL-related issue:
[ ] I'm using graph features
I'm issuing AQL via:
I've run
db._explain("<my aql query>")
and it didn't shed more light on this.The AQL query in question is:
The issue can be reproduced using this dataset:
log
2017/12/30 07:55:42 single has terminated, quickly, in 24.861013999s (recent failures: 1)
2017/12/30 07:55:42 restarting single
2017/12/30 07:55:42 Looking for a running instance of single on port 8529
2017/12/30 07:55:42 Starting single on port 8529
2017-12-30T07:55:42Z [20746] INFO ArangoDB 3.3.1 [linux] 64bit, using jemalloc, VPack 0.1.30, RocksDB 5.6.0, ICU 58.1, V8 5.7.492.77, OpenSSL 1.0.2g 1 Mar 2016
2017-12-30T07:55:42Z [20746] INFO detected operating system: Linux version 4.13.0-1002-gcp (buildd@lgw01-amd64-060) (gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ub
untu1~16.04.5)) #5-Ubuntu SMP Tue Dec 5 13:20:17 UTC 2017
The text was updated successfully, but these errors were encountered: