Last Modified: Jun 30, 2021
See more info
Known Affected Versions:
7.0.0, 126.96.36.199, 188.8.131.52, 7.1.0, 184.108.40.206, 220.127.116.11, 18.104.22.168, 7.1.6, 22.214.171.124, 7.1.7, 126.96.36.199, 188.8.131.52, 7.1.8, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, 7.1.9, 188.8.131.52, 184.108.40.206, 220.127.116.11
Opened: Feb 09, 2021
Indexes accumulate beyond their intended time and persist in Elasticsearch. Elasticsearch eventually becomes unresponsive due to lack of memory and disk space.
Although only one index is corrupted, all indexes are impacted. Information is lost from all indexes and it causes the whole elasticsearch cluster to be unresponsive due to no memory and disk space.
In rare cases there is temporal corruption in the elasticsearch cluster, and an index might be created without a template. You will be able to identify the issue if the following message appears in /var/log/appiq/postaggregator.log on the device: Caused by: org.elasticsearch.common.io.stream.NotSerializableExceptionWrapper: : Fielddata is disabled on text fields by default. Set fielddata=true on [dimensions.hash] in order to load fielddata in memory by uninverting the inverted index. Note that this can however use significant memory. Alternatively use a keyword field instead.
Data aggregation no longer causes OOM for all indexes.