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.

Sign up for GitHub

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

Jump to bottom

Counting messages fails with high number of indices #4136

Closed
joschi opened this issue Sep 10, 2017 · 0 comments
Closed

Counting messages fails with high number of indices #4136

joschi opened this issue Sep 10, 2017 · 0 comments
Assignees
@joschi
Labels
bug elasticsearch
Milestone
2.3.2

Comments

@joschi
Copy link
Contributor

joschi commented Sep 10, 2017

Retrieving the indexer overview page (/system/indexer/overview/{index_set_id}) fails if there is a large number of indices in the Graylog cluster.

This occurrence seems to have been missed in #4054.

Refs https://community.graylog.org/t/cant-get-index-message-counts-after-2-2-6-2-3-1-upgrade/2391
@joschi joschi added this to the 2.3.2 milestone Sep 10, 2017
joschi pushed a commit that referenced this issue Sep 13, 2017
Replace "deprecated" Counts API with Multi Search with size=0
0d56867 
The Elasticsearch Count API doesn't allow setting the indices in the HTTP request body
and suffers from the issue that users with a large number of indices run into the default
HTTP header size limit of Elasticsearch (4 KB).

This change set replaces the (kind of) deprecated Counts API with a regular search with
size=0 issued via the Elasticsearch Multi Search API which allows specifiying the list
of indices in the request body.

Fixes #4136
Refs elastic/elasticsearch#13928
joschi pushed a commit that referenced this issue Sep 14, 2017
Replace "deprecated" Counts API with Multi Search with size=0
98b1064 
The Elasticsearch Count API doesn't allow setting the indices in the HTTP request body
and suffers from the issue that users with a large number of indices run into the default
HTTP header size limit of Elasticsearch (4 KB).

This change set replaces the (kind of) deprecated Counts API with a regular search with
size=0 issued via the Elasticsearch Multi Search API which allows specifiying the list
of indices in the request body.

Fixes #4136
Refs elastic/elasticsearch#13928
@joschi joschi mentioned this issue Sep 14, 2017
Merged
@ghost ghost assigned joschi Sep 14, 2017
@ghost ghost added the in progress label Sep 14, 2017
@ghost ghost removed the in progress label Sep 19, 2017
bernd pushed a commit that referenced this issue Sep 19, 2017
@joschi @bernd
Replace "deprecated" Counts API with Multi Search with size=0 (#4147)
302cee2 
* Replace "deprecated" Counts API with Multi Search with size=0

The Elasticsearch Count API doesn't allow setting the indices in the HTTP request body
and suffers from the issue that users with a large number of indices run into the default
HTTP header size limit of Elasticsearch (4 KB).

This change set replaces the (kind of) deprecated Counts API with a regular search with
size=0 issued via the Elasticsearch Multi Search API which allows specifiying the list
of indices in the request body.

Fixes #4136
Refs elastic/elasticsearch#13928

* Use MultiSearchResult.MultiSearchResponse instead of working on JSON object

* Fix JestUtilsTest
@joschi joschi mentioned this issue Nov 2, 2017
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@joschi joschi

Labels
bug elasticsearch
Projects
None yet
Milestone
2.3.2
Development

No branches or pull requests
1 participant
@joschi