Skip to content
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

top hits: huge number in "size" makes node go OOM even with very few docs #12510

Closed
brwe opened this issue Jul 28, 2015 · 0 comments
Closed

top hits: huge number in "size" makes node go OOM even with very few docs #12510

brwe opened this issue Jul 28, 2015 · 0 comments
Assignees

Comments

@brwe
Copy link
Contributor

brwe commented Jul 28, 2015

To reproduce, start a node with 1g heap and then:

DELETE test

PUT index/doc/id
{
  "text": "text"
}

POST index/_search
{
  "aggs": {
    "text": {
      "terms": {
        "field": "text",
        "size": 10
      },
      "aggs": {
        "top_hits": {
          "top_hits": {
            "size": 200000000
          }
        }
      }
    }
  }
}

Tested 1.7.0.
While it is not a good idea to retrieve 200000000 documents I would still not expect an OOM with only one document.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants