-
Notifications
You must be signed in to change notification settings - Fork 25k
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
Facet query crashes the cluster #28
Comments
It seems to be related to running more than one node - if I use just one node and run the query below, then it works correctly:
However, multiple facets are broken:
|
Facet query crashes the cluster. Wrong serialzation of facets caused for construction of a rough sized array list. closed by 008b00f. |
Sorry - reposting in the issue: I'm afraid your facet fix still doesn't work. I can now check for multiple facets (which if I remember correctly wasn't working yesterday) when running with one node, but with a second node, a facet search still crashes the cluster. Test script below:
|
Closes #28. (cherry picked from commit 829d78c)
`GET` and `DELETE` should return `404` error. Closes #28.
In certain environments (such as inside a docker container) 'metadata' does not resolve. Forcing URL to `http://metadata.google.internal/computeMetadata/v1/instance/service-accounts/default/token` fix this. See https://developers.google.com/compute/docs/metadata#metadataserver Closes #28. Closes #30.
Also replace deprecated code in Lucene. Closes #28.
Currently, `testFastElectionWhenLeaderDropsConnections ` does not call `assertUniqueLeaderAndExpectedModes` at the end, which was the whole point of that test: an election should complete quickly if the leader drops all its connections. This fixes this oversight, and the fact that this assertion would have failed had it been present.
Added functionality to install rpm from elastic url instead of the repo.
* Added epoch_md5 document id type * Updated README and added SHA1 id to the document id benchmark * Refactoring of document id challenge following review * Updated note about disk space requirements * Updated note about index size and disk space requirements * Updates following review
Hiya
In my test script, I create two indices, then add 28 documents, then try searching on those.
When I get to the final facets query, the cluster never responds, and then remains unresponsive to all further queries. One of the nodes balloons to 631MB of resident memory - I presume this is some sort of max allowed by java.
Then when closing down the nodes, two close down fine, and the third throws exceptions like the ones listed below.
Test script: (see bottom for facets query)
Node errors:
The text was updated successfully, but these errors were encountered: