![]() ![]() Lucene Handling of tragic event in IndexWriterĪ patch has been proposed to reduce the severity if an internal thread tries to access an already closed index writer but that could hide other bugs in the future so this brought up interesting discussions regarding the origin of the bug. Removing that data from disk destroys incrementality of source-only snapshots though, rendering the feature broken to some degree. The problem is that they create and keep a lot of extra data on disk when creating a snapshot. We received recent reports about excessive disk usage of source-only snapshots. The next step is to allow deleting multiple snapshots at once as well as allow parallel deletes. Recent improvements in snapshot resiliency has allowed us to remove the restriction that you cannot restore a snapshot and delete another snapshot at the same time. We are also working on a change to more aggressively cancel queries that need to spend a lot of time in the terms dictionary (multi-terms query) and the BKD-tree (range and geo queries).Ĭurrently we need to wait until the end of these costly operations before exiting a cancelled query, this delay can have an impact on the cluster for very costly queries such as leading wildcards (we need to scan the entire dictionary). Queries that may have a high per-document cost (percolate queries).Queries that have a high up-front cost (fuzzy queries, prefix queries without index_prefixes, wildcard queries, range queries on keyword fields).Queries that need to do linear scans to identify matches (script queries).This work helped to identify what should be considered as a slow query in Elasticsearch: We have started to work on a setting to disallow slow queries. We spent the last many months working out not only the scripting code necessary to make all those cases work, but also adding tons of tests to ensure each and every case is covered well for the initial release of this new feature. We are happy to announce that password protected keystore is now here! It was always our intent to offer real password protection, but grabbing this password at startup from various different mechanisms like the console, systemd or environment variables in docker is tricky. Up until now, the keystore has only been protected through obfuscation. This means that any subsequently added phase will be executed when the policy is updated, rather than requiring manual re-adjustment of the index’s lifecycle execution state. To solve this frustration, we have introduced a PR which changes the behavior of ILM to only execute as far as the last configured phase. For example, adding a delete phase to a policy where indices have already reached the terminal (“completed”) phase did not actually delete the indices. One challenge ILM users face is when adding a phase to be executed after an index had already executed its policy.
0 Comments
Leave a Reply. |