8000 Add known issue about ArangoSearch column cache and upgrading AF depl… · konsultaner/arangodb-docs@50d2f4f · GitHub
[go: up one dir, main page]
Skip to content

Commit 50d2f4f

Browse files
Simran-BSimran-B
authored
Add known issue about ArangoSearch column cache and upgrading AF deployments (arangodb#1263)
1 parent 97c11ab commit 50d2f4f

File tree

4 files changed

+24
-0
lines changed

4 files changed

+24
-0
lines changed

‎3.10/arangosearch-views.md

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -153,6 +153,13 @@ During view modification the following directives apply:
153153

154154
### View Properties
155155

156+
{% hint 'info' %}
157+< 10000 /span>
If you use ArangoSearch caching in supported 3.9 versions and upgrade an
158+
Active Failover deployment to 3.10, you may need to re-configure the
159+
cache-related options and thus recreate inverted indexes and Views. See
160+
[Known Issues in 3.10](release-notes-known-issues310.html#arangosearch).
161+
{% endhint %}
162+
156163
- **primarySort** (_optional_; type: `array`; default: `[]`; _immutable_)
157164

158165
A primary sort order can be defined to enable an AQL optimization. If a query

‎3.10/http/indexes-inverted.md

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -4,4 +4,11 @@ description: Working with Inverted Indexes
44
---
55
# Working with Inverted Indexes
66

7+
{% hint 'info' %}
8+
If you use ArangoSearch caching in supported 3.9 versions and upgrade an
9+
Active Failover deployment to 3.10, you may need to re-configure the
10+
cache-related options and thus recreate inverted indexes and Views. See
11+
[Known Issues in 3.10](../release-notes-known-issues310.html#arangosearch).
12+
{% endhint %}
13+
714
{% docublock post_api_index_inverted %}

‎3.10/release-notes-known-issues310.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -26,6 +26,7 @@ ArangoSearch
2626
| **Date Added:** 2022-09-29 <br> **Component:** ArangoSearch <br> **Deployment Mode:** All <br> **Description:** New Views of the search-alias type may return an incorrect amount of documents or other inconsistent results if they contain nested fields. <br> **Affected Versions:** 3.10.0 <br> **Fixed in Versions:** 3.10.1 <br> **Reference:** [SEARCH-391](https://arangodb.atlassian.net/browse/SEARCH-391){:target="_blank"} (internal) |
2727
| **Date Added:** 2022-09-29 <br> **Component:** ArangoSearch <br> **Deployment Mode:** All <br> **Description:** When using an inverted index, if the same nested field in the document is referenced multiple times and nested fields' definitions are different, only one definition will be used. <br> **Affected Versions:** 3.10.x <br> **Fixed in Versions:** - <br> **Reference:** [SEARCH-390](https://arangodb.atlassian.net/browse/SEARCH-390){:target="_blank"} (internal) |
2828
| **Date Added:** 2022-09-29 <br> **Component:** ArangoSearch <br> **Deployment Mode:** Cluster <br> **Description:** In a cluster deployment using the new View of the `search-alias` type, running the `arangodump`/`arangorestore` commands fails. <br> **Affected Versions:** 3.10.0 <br> **Fixed in Versions:** 3.10.1 <br> **Reference:** [SEARCH-401](https://arangodb.atlassian.net/browse/SEARCH-401){:target="_blank"} (internal) |
29+
| **Date Added:** 2023-02-08 <br> **Component:** ArangoSearch <br> **Deployment Mode:** Active Failover <br> **Description:** ArangoSearch caching is available in some 3.9 versions but not v3.10.0 and v3.10.1. If you upgrade deployments to one of these two versions, the column cache is unavailable, but cache-related options are remembered. If you upgrade to v3.10.2 or later, the feature is automatically available again. However, an exception are Active Failover deployments. If a failover (leader change) occurs with v3.10.0 or v3.10.1, then the cache options are reset. You need to re-configure them, requiring that you recreate inverted indexes and Views as necessary as most of these options are immutable. <br> **Affected Versions:** 3.10.0, 3.10.1 <br> **Fixed in Versions:** 3.10.2 <br> **Reference:** N/A |
2930

3031
AQL
3132
---

‎3.10/release-notes-new-features310.md

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -351,6 +351,8 @@ options.
351351
- A new `primaryKeyCache` property for inverted indexes to always cache the
352352
primary key column in memory.
353353

354+
---
355+
354356
The cache size can be controlled with the new `--arangosearch.columns-cache-limit`
355357
startup option and monitored via the new `arangodb_search_columns_cache_size`
356358
metric.
@@ -360,6 +362,13 @@ ArangoSearch caching is only available in the Enterprise Edition.
360362
See [Optimizing View and inverted index query performance](arangosearch-performance.html)
361363
for examples.
362364

365+
{% hint 'info' %}
366+
If you use ArangoSearch caching in supported 3.9 versions and upgrade an
367+
Active Failover deployment to 3.10, you may need to re-configure the
368+
cache-related options and thus recreate inverted indexes and Views. See
369+
[Known Issues in 3.10](release-notes-known-issues310.html#arangosearch).
370+
{% endhint %}
371+
363372
### New startup options
364373

365374
With `--arangosearch.skip-recovery`, you can skip data recovery for the specified View links

0 commit comments

Comments
 (0)
0