New Index range handling slow with ES 1.x #1465
Closed
Comments
joschi
pushed a commit
that referenced
this issue
Oct 19, 2015
…rvice Index range information is now stored in MongoDB again, but in the format being used in Elasticsearch and not in the legacy format (which only included partial information). The IndexRangesMigrationPeriodical has been extended to now migrate old index ranges from MongoDB (Graylog 1.1.x and earlier) and the current index ranges from Elasticsearch into MongoDB and will only run the migration once. EsIndexRangeService is now deprecated and shouldn't be used anymore (except for the migration of old index range information from Elasticsearch in IndexRangesMigrationPeriodical). Fixes #1465
joschi
pushed a commit
that referenced
this issue
Oct 19, 2015
…rvice Index range information is now stored in MongoDB again, but in the format being used in Elasticsearch and not in the legacy format (which only included partial information). The IndexRangesMigrationPeriodical has been extended to now migrate old index ranges from MongoDB (Graylog 1.1.x and earlier) and the current index ranges from Elasticsearch into MongoDB and will only run the migration once. EsIndexRangeService is now deprecated and shouldn't be used anymore (except for the migration of old index range information from Elasticsearch in IndexRangesMigrationPeriodical). Fixes #1465
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Storing the index range information in Elasticsearch can lead to excessive cluster state exchanges, which can seriously impact performance in certain situations.
Compare https://groups.google.com/forum/#!topic/graylog2/obgyM74FMsE
The text was updated successfully, but these errors were encountered: