Skip to content

Commit cf11a59

Browse files
authored
Add known issue for bbq_hnsw rescoring (#132009)
1 parent bd2cd2c commit cf11a59

File tree

1 file changed

+4
-0
lines changed

1 file changed

+4
-0
lines changed

docs/release-notes/known-issues.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -7,6 +7,10 @@ mapped_pages:
77
# Elasticsearch known issues [elasticsearch-known-issues]
88
Known issues are significant defects or limitations that may impact your implementation. These issues are actively being worked on and will be addressed in a future release. Review the Elasticsearch known issues to help you make informed decisions, such as upgrading to a new version.
99

10+
## 9.1.0 [elasticsearch-9.1.0-known-issues]
11+
* An error in the configuration of vector indices with type `bbq_hnsw` may lead to significant search performance degradation on 9.1.0. To mitigate this, set the `-Dvector.rescoring.directio=false` JVM option on all search nodes, then restart the nodes.
12+
This option can be removed in 9.1.1.
13+
1014
## 9.0.3 [elasticsearch-9.0.3-known-issues]
1115
* A bug in the merge scheduler in Elasticsearch 9.0.3 may prevent shards from closing when there isn’t enough disk space to complete a merge. As a result, operations such as closing or relocating an index may hang until sufficient disk space becomes available.
1216
To mitigate this issue, the disk space checker is disabled by default in 9.0.3 by setting `indices.merge.disk.check_interval` to `0` seconds. Manually enabling this setting is not recommended.

0 commit comments

Comments
 (0)