You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/commands/flushall/index.md
+5-2Lines changed: 5 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -62,8 +62,11 @@ It is possible to use one of the following modifiers to dictate the flushing mod
62
62
*`ASYNC`: flushes the databases asynchronously
63
63
*`SYNC`: flushes the databases synchronously
64
64
65
-
Note: an asynchronous `FLUSHALL` command only deletes keys that were present at the time the command was invoked. Keys created during an asynchronous flush will be unaffected.
65
+
## Notes
66
+
67
+
* An asynchronous `FLUSHALL` command only deletes keys that were present at the time the command was invoked. Keys created during an asynchronous flush will be unaffected.
68
+
* This command does not delete functions.
66
69
67
70
## Behavior change history
68
71
69
-
*`>= 6.2.0`: Default flush behavior now configurable by the **lazyfree-lazy-user-flush** configuration directive.
72
+
*`>= 6.2.0`: Default flush behavior now configurable by the **lazyfree-lazy-user-flush** configuration directive.
Copy file name to clipboardExpand all lines: content/commands/flushdb/index.md
+5-2Lines changed: 5 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -62,8 +62,11 @@ It is possible to use one of the following modifiers to dictate the flushing mod
62
62
*`ASYNC`: flushes the database asynchronously
63
63
*`SYNC`: flushes the database synchronously
64
64
65
-
Note: an asynchronous `FLUSHDB` command only deletes keys that were present at the time the command was invoked. Keys created during an asynchronous flush will be unaffected.
65
+
## Notes
66
+
67
+
* An asynchronous `FLUSHDB` command only deletes keys that were present at the time the command was invoked. Keys created during an asynchronous flush will be unaffected.
68
+
* This command does not delete functions.
66
69
67
70
## Behavior change history
68
71
69
-
*`>= 6.2.0`: Default flush behavior now configurable by the **lazyfree-lazy-user-flush** configuration directive.
72
+
*`>= 6.2.0`: Default flush behavior now configurable by the **lazyfree-lazy-user-flush** configuration directive.
Copy file name to clipboardExpand all lines: content/commands/info/index.md
+21Lines changed: 21 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -515,3 +515,24 @@ It won't be included when `INFO` or `INFO ALL` are called, and it is returned on
515
515
**A note about the word slave used in this man page**: Starting with Redis 5, if not for backward compatibility, the Redis project no longer uses the word slave. Unfortunately in this command the word slave is part of the protocol, so we'll be able to remove such occurrences only when this API will be naturally deprecated.
516
516
517
517
**Modules generated sections**: Starting with Redis 6, modules can inject their information into the `INFO` command. These are excluded by default even when the `all` argument is provided (it will include a list of loaded modules but not their generated info fields). To get these you must use either the `modules` argument or `everything`.
| <spantitle="Supported">✅ Standard</span><br /><spantitle="Supported"><nobr>✅ Active-Active</nobr></span> | <spantitle="Supported">✅ Standard</span><br /><spantitle="Supported"><nobr>✅ Active-Active</nobr></span> | In Redis Enterprise, `INFO` returns a different set of fields than Redis Community Edition.<br />Not supported for [scripts]({{<relref "/develop/interact/programmability">}}). |
524
+
525
+
Note: key memory usage is different on Redis Software or Redis Cloud active-active databases than on non-active-active databases. This is because memory usage includes some amount of CRDB overhead.
526
+
527
+
Additionally, for JSON keys, Redis implements a “shared string” mechanism to save memory when the same JSON field names or field values of type string are used more than once (either inter-key or intra-key).
528
+
In such cases, instead of storing the field names or values many times, Redis stores them only once. This mechanism is not in place for active-active databases.
529
+
530
+
On non-active-active databases, `INFO` (Memory > used_memory) reports that the shared memory is counted, but only once for all keys. On active-active databases, there is no shared memory, so if strings are repeated, they are stored multiple times.
531
+
532
+
**Example**
533
+
534
+
Suppose you have ten JSON keys, and each key has 5KB of unique content and 5KB of shared content.
535
+
536
+
For non-active-active databases, `INFO` (used_memory) would report (10 keys * 5KB) + 5KB ~= 55KB. The last term, "+ 5KB", is the size of the shared content.
537
+
538
+
For active-active databases, `INFO` (used_memory) would report 10 keys * 20KB ~= 200KB. This number includes some amount of CRDB overhead per JSON key.
|<spantitle="Supported">✅ Standard</span><br /><spantitle="Supported"><nobr>✅ Active-Active</nobr></span> | <spantitle="Supported">✅ Standard</span><br /><spantitle="Supported"><nobr>✅ Active-Active</nobr></span> | Not supported for [scripts]({{<relref "/develop/interact/programmability">}}) in Redis versions earlier than 7. |
96
+
97
+
Note: key memory usage is different on Redis Software or Redis Cloud active-active databases than on non-active-active databases. This is because memory usage includes some amount of CRDB overhead.
Copy file name to clipboardExpand all lines: content/develop/interact/search-and-query/advanced-concepts/vectors.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -441,7 +441,7 @@ FT.SEARCH movies "(@category:{action} ~@category:{drama})=>[KNN 10 @doc_embeddin
441
441
Among the movies that have `drama` or `action` as a category tag, return the top 10 nearest neighbors and explicitly set the filter mode (hybrid policy) to "ad-hoc brute force" rather than it being auto-selected:
Among the movies that have `action` as a category tag, return the top 10 nearest neighbors and explicitly set the filter mode (hybrid policy) to "batches" and batch size 50 using a query parameter:
Copy file name to clipboardExpand all lines: content/integrate/amazon-bedrock/set-up-redis.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -75,9 +75,9 @@ To set up a Redis Cloud instance for Bedrock, you need to:
75
75
76
76
{{<imagefilename="images/rc/subscription-new-flexible-setup-general.png"width="75%"alt="The General settings of the Setup tab." >}}
77
77
78
-
1. In the **Version** section, select **Redis 7.2**.
78
+
1. In the **Version** section, select **Redis 7.2** or **Redis 7.4**.
79
79
80
-
{{<imagefilename="images/rc/subscription-new-flexible-version-section.png"alt="Version selection between Redis 6.2and 7.2" >}}
80
+
{{<imagefilename="images/rc/subscription-new-flexible-version-section.png"alt="Version selection between Redis 6.2, 7.2, and 7.4" >}}
81
81
82
82
1. In the **Advanced options** section, select Multi-AZ to ensure [high-availability]({{< relref "/operate/rc/databases/configuration/high-availability" >}}).
Copy file name to clipboardExpand all lines: content/operate/oss_and_stack/install/install-redis/install-redis-on-linux.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -72,13 +72,13 @@ If your Linux distribution does not currently have Snap installed, you can insta
72
72
You can start the Redis server as a background process using the `systemctl` command. This only applies to Ubuntu/Debian when installed using `apt`, and Red Hat/Rocky when installed using `yum`.
73
73
74
74
{{< highlight bash >}}
75
-
sudo systemctl start redis
75
+
sudo systemctl start <redis-service-name> # redis or redis-server depending on platform
76
76
{{< / highlight >}}
77
77
78
78
To stop the server, use:
79
79
80
80
{{< highlight bash >}}
81
-
sudo systemctl stop redis
81
+
sudo systemctl stop <redis-service-name> # redis or redis-server depending on platform
82
82
{{< / highlight >}}
83
83
84
84
## Connect to Redis
@@ -107,4 +107,4 @@ Once you have a running Redis instance, you may want to:
107
107
* Connect using one of the [Redis clients]({{< relref "/develop/connect/clients" >}})
Copy file name to clipboardExpand all lines: content/operate/oss_and_stack/stack-with-enterprise/release-notes/redisgears/redisgears-1.2-release-notes.md
+15-1Lines changed: 15 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,11 +16,25 @@ weight: 99
16
16
17
17
## Requirements
18
18
19
-
RedisGears v1.2.9 requires:
19
+
RedisGears v1.2.10 requires:
20
20
21
21
- Minimum Redis compatibility version (database): 6.0.0
22
22
- Minimum Redis Enterprise Software version (cluster): 6.0.12
23
23
24
+
## 1.2.10 (October 2024)
25
+
26
+
This is a maintenance release for RedisGears 1.2
27
+
28
+
Update urgency: `LOW`: No need to upgrade unless there are new features or fixes.
29
+
30
+
Details
31
+
32
+
- Bug fixes:
33
+
-[#1114](https://github.com/redisgears/redisgears/pull/1114) (REPLICAOF and Redis Enterprise A-A only) Cross slot violation. Avoid using `RM_Call` + `SCAN` command which might replicate multiple keys deletion inside a `MULTI EXEC` block when a lazy expire takes place
0 commit comments