diff --git a/content/embeds/json-active-active-conflict-resolution.md b/content/embeds/json-active-active-conflict-resolution.md index d97a58fd0e..cf641b40c8 100644 --- a/content/embeds/json-active-active-conflict-resolution.md +++ b/content/embeds/json-active-active-conflict-resolution.md @@ -45,7 +45,7 @@ The instance with the smaller ID wins, so the key becomes an object in the given | Time | Description | Instance 1 | Instance 2 | | :---: | :--- | :--- | :--- | | t1 | Set the same key to an object or an array | JSON.SET doc $.a '{}' | JSON.SET doc $.a '[]' | -| t2 | Add data to the object and array | JSON.SET doc $.a.x '“y”'

Result:
{"a": {"x": "y"}} | JSON.SET doc $.a '["z"]'

Result:
{“a”: ["z"]} | +| t2 | Add data to the object and array | JSON.SET doc $.a.x '"y"'

Result:
{"a": {"x": "y"}} | JSON.SET doc $.a '["z"]'

Result:
{"a": ["z"]} | | t3 | Active-Active synchronization | – Sync – | – Sync – | | t4 | Instance 1 wins | JSON.GET doc $

Result:
{"a": {"x": "y"}} | JSON.GET doc $

Result:
{"a": {"x": "y"}} | @@ -267,8 +267,8 @@ Merges the results of all operations on the array. Preserves the original elemen | Time | Description | Instance 1 | Instance 2 | | :---: | :--- | :--- | :--- | | t1 | The document exists on both instances | JSON.GET doc $

Result:
'["a", "b", "c"]' | JSON.GET doc $

Result:
'["a", "b", "c"]' | -| t2 | Instance 1 removes an array element; instance 2 adds one | JSON.ARRPOP doc $ 1

Result:
["a", "c"] | JSON.ARRINSERT doc $ 0 ‘“y”’

Result:
["y", "a", "b", "c"] | -| t3 | Both instances add another element to the array | JSON.ARRINSERT doc $ 1 ‘“x”’

Result:
["a", "x", "c"] | JSON.ARRINSERT doc $ 2 ‘“z”’

Result:
["y", "a", "z", "b", "c"] | +| t2 | Instance 1 removes an array element; instance 2 adds one | JSON.ARRPOP doc $ 1

Result:
["a", "c"] | JSON.ARRINSERT doc $ 0 ‘"y"’

Result:
["y", "a", "b", "c"] | +| t3 | Both instances add another element to the array | JSON.ARRINSERT doc $ 1 ‘"x"’

Result:
["a", "x", "c"] | JSON.ARRINSERT doc $ 2 ‘"z"’

Result:
["y", "a", "z", "b", "c"] | | t4 | Active-Active synchronization | – Sync – | – Sync – | | t5 | Merge results from both instances | JSON.GET doc $

Result:
["y", "a", "x", "z", "c"] | JSON.GET doc $

Result:
["y", "a", "x", "z", "c"] | @@ -292,11 +292,11 @@ Deletion wins over updates. | Time | Description | Instance 1 | Instance 2 | | :---: | :--- | :--- | :--- | -| t1 | The document exists on both instances | JSON.GET doc $

Result:
{“todo”: [{“title”: “buy milk”, “done”: false}]} | JSON.GET doc $

Result:
{“todo”: [{“title”: “buy milk”, “done”: false}]} | +| t1 | The document exists on both instances | JSON.GET doc $

Result:
{"todo": [{"title": "buy milk", "done": false}]} | JSON.GET doc $

Result:
{"todo": [{"title": "buy milk", "done": false}]} | | t2 | Instance 1 removes an array element; instance 2 updates the same element | JSON.ARRPOP doc $.todo 0 | JSON.SET doc '$.todo[0]["done"]' 'true'’ | -| t3 | | JSON.GET doc $

Result:
{“todo”: []} | JSON.GET doc $

Result:
[{“title”: “buy milk”, “done”: true}]} | +| t3 | | JSON.GET doc $

Result:
{"todo": []} | JSON.GET doc $

Result:
[{"title": "buy milk", "done": true}]} | | t4 | Active-Active synchronization | – Sync – | – Sync – | -| t5 | Instance 1 wins | JSON.GET doc $

Result:
doc = {“todo”: []} | JSON.GET doc $

Result:
doc = {“todo”: []} | +| t5 | Instance 1 wins | JSON.GET doc $

Result:
doc = {"todo": []} | JSON.GET doc $

Result:
doc = {"todo": []} | ### Update versus update object @@ -317,8 +317,8 @@ Merges the results of all operations on the object. | Time | Description | Instance 1 | Instance 2 | | :---: | :--- | :--- | :--- | | t1 | The document exists on both instances | JSON.GET doc $

Result:
'{"grocery": []}' | JSON.GET doc $

Result:
'{"grocery": []}' | -| t2 | Add new elements to the array | JSON.ARRAPPEND doc $.grocery ‘“eggs”’ | JSON.ARRAPPEND doc $.grocery ‘“milk”’ | -| t3 | Add new elements to the array | JSON.ARRAPPEND doc $.grocery ‘“ham”’ | JSON.ARRAPPEND doc $.grocery ‘“flour”’ | +| t2 | Add new elements to the array | JSON.ARRAPPEND doc $.grocery ‘"eggs"’ | JSON.ARRAPPEND doc $.grocery ‘"milk"’ | +| t3 | Add new elements to the array | JSON.ARRAPPEND doc $.grocery ‘"ham"’ | JSON.ARRAPPEND doc $.grocery ‘"flour"’ | | t4 | | JSON.GET doc $

Result:
{"grocery":["eggs", "ham"]} | JSON.GET doc $

Result:
{"grocery":["milk", "flour"]} | | t5 | Active-Active synchronization | – Sync – | – Sync – | | t6 | Merges the results from both instances | JSON.GET doc .

Result:
{"grocery":["eggs","ham","milk", "flour"]} | JSON.GET doc .

Result:
{"grocery":["eggs","ham","milk", "flour" ]} | diff --git a/content/embeds/rs-observability.md b/content/embeds/rs-observability.md index d4b765cdd0..18509886f5 100644 --- a/content/embeds/rs-observability.md +++ b/content/embeds/rs-observability.md @@ -278,7 +278,7 @@ Dashboard displaying connection metrics between zones - [Synchronization Dashboa CRDT provides three fundamental benefits over other geo-distributed solutions: * It offers local latency on read and write operations, regardless of the number of geo-replicated regions and their distance from each other. -* It enables seamless conflict resolution (“conflict-free”) for simple and complex data types like those of Redis core. +* It enables seamless conflict resolution ("conflict-free") for simple and complex data types like those of Redis core. * Even if most of the geo-replicated regions in a CRDT database (for example, 3 out of 5) are down, the remaining geo-replicated regions are uninterrupted and can continue to handle read and write operations, ensuring business continuity. ## Database performance indicators diff --git a/content/operate/rs/7.4/databases/active-active/develop/_index.md b/content/operate/rs/7.4/databases/active-active/develop/_index.md index f9ef41ffdf..32832500b4 100644 --- a/content/operate/rs/7.4/databases/active-active/develop/_index.md +++ b/content/operate/rs/7.4/databases/active-active/develop/_index.md @@ -56,12 +56,12 @@ in between. | **Time** | **CRDB Instance1** | **CRDB Instance2** | | ------: | :------: | :------: | -| t1 | SET key1 “a” | | -| t2 | | SET key1 “b” | +| t1 | SET key1 "a" | | +| t2 | | SET key1 "b" | | t3 | — Sync — | — Sync — | -| t4 | SET key1 “c” | | +| t4 | SET key1 "c" | | | t5 | — Sync — | — Sync — | -| t6 | | SET key1 “d” | +| t6 | | SET key1 "d" | [Learn more about synchronization for diff --git a/content/operate/rs/7.4/databases/active-active/develop/data-types/hashes.md b/content/operate/rs/7.4/databases/active-active/develop/data-types/hashes.md index c9bf60d120..37a5b2f7f6 100644 --- a/content/operate/rs/7.4/databases/active-active/develop/data-types/hashes.md +++ b/content/operate/rs/7.4/databases/active-active/develop/data-types/hashes.md @@ -37,7 +37,7 @@ Here is an example of an "add wins" case: | **Time** | **CRDB Instance1** | **CRDB Instance2** | | ------: | :------: | :------: | -| t1 | HSET key1 field1 “a” | | -| t2 | | HSET key1 field2 “b” | +| t1 | HSET key1 field1 "a" | | +| t2 | | HSET key1 field2 "b" | | t4 | - Sync - | - Sync - | -| t5 | HGETALL key1
1) “field2”
2) “b”
3) “field1”
4) “a” | HGETALL key1
1) “field2”
2) “b”
3) “field1”
4) “a” | +| t5 | HGETALL key1
1) "field2"
2) "b"
3) "field1"
4) "a" | HGETALL key1
1) "field2"
2) "b"
3) "field1"
4) "a" | diff --git a/content/operate/rs/7.4/databases/active-active/develop/data-types/lists.md b/content/operate/rs/7.4/databases/active-active/develop/data-types/lists.md index ed9082b43b..97a2c714c0 100644 --- a/content/operate/rs/7.4/databases/active-active/develop/data-types/lists.md +++ b/content/operate/rs/7.4/databases/active-active/develop/data-types/lists.md @@ -27,11 +27,11 @@ example: | **Time** | **CRDB Instance 1** | **CRDB Instance 2** | | ------: | :------: | :------: | -| t1 | LPUSH mylist “hello” | | +| t1 | LPUSH mylist "hello" | | | t2 | — Sync — | — Sync — | -| t3 | | LPUSH mylist “world” | +| t3 | | LPUSH mylist "world" | | t4 | — Sync — | — Sync — | -| t5 | LRANGE mylist 0 -1 =>“world” “hello” | LRANGE mylist 0 -1 => “world” “hello” | +| t5 | LRANGE mylist 0 -1 =>"world" "hello" | LRANGE mylist 0 -1 => "world" "hello" | **Explanation**: The final list contains both the "world" and "hello" elements, in that diff --git a/content/operate/rs/7.4/databases/active-active/develop/data-types/sets.md b/content/operate/rs/7.4/databases/active-active/develop/data-types/sets.md index a2964ed38c..685b6eeb43 100644 --- a/content/operate/rs/7.4/databases/active-active/develop/data-types/sets.md +++ b/content/operate/rs/7.4/databases/active-active/develop/data-types/sets.md @@ -31,18 +31,18 @@ Here is an example of an "add wins" case: | **Time** | **CRDB Instance1** | **CRDB Instance2** | | ------: | :------: | :------: | -| t1 | SADD key1 “a” | | -| t2 | | SADD key1 “b” | -| t3 | SMEMBERS key1 “a” | SMEMBERS key1 “b” | +| t1 | SADD key1 "a" | | +| t2 | | SADD key1 "b" | +| t3 | SMEMBERS key1 "a" | SMEMBERS key1 "b" | | t4 | — Sync — | — Sync — | -| t3 | SMEMBERS key1 “a” “b” | SMEMBERS key1 “a” “b” | +| t3 | SMEMBERS key1 "a" "b" | SMEMBERS key1 "a" "b" | Here is an example of an "observed remove" case. | **Time** | **CRDB Instance1** | **CRDB Instance2** | | ------: | :------: | :------: | -| t1 | SMEMBERS key1 “a” “b” | SMEMBERS key1 “a” “b” | -| t2 | SREM key1 “a” | SADD key1 “c” | -| t3 | SREM key1 “c” | | +| t1 | SMEMBERS key1 "a" "b" | SMEMBERS key1 "a" "b" | +| t2 | SREM key1 "a" | SADD key1 "c" | +| t3 | SREM key1 "c" | | | t4 | — Sync — | — Sync — | -| t3 | SMEMBERS key1 “c” “b” | SMEMBERS key1 “c” “b” | +| t3 | SMEMBERS key1 "c" "b" | SMEMBERS key1 "c" "b" | diff --git a/content/operate/rs/7.4/databases/active-active/develop/data-types/strings.md b/content/operate/rs/7.4/databases/active-active/develop/data-types/strings.md index f347262fe5..bbf9191e67 100644 --- a/content/operate/rs/7.4/databases/active-active/develop/data-types/strings.md +++ b/content/operate/rs/7.4/databases/active-active/develop/data-types/strings.md @@ -34,12 +34,12 @@ time (t2) wins over the update at t1. | **Time** | **Region 1** | **Region 2** | | :------: | :------: | :------: | -| t1 | SET text “a” | | -| t2 | | SET text “b” | +| t1 | SET text "a" | | +| t2 | | SET text "b" | | t3 | — Sync — | — Sync — | -| t4 | SET text “c” | | +| t4 | SET text "c" | | | t5 | — Sync — | — Sync — | -| t6 | | SET text “d” | +| t6 | | SET text "d" | ### String counter support diff --git a/content/operate/rs/7.4/databases/auto-tiering/_index.md b/content/operate/rs/7.4/databases/auto-tiering/_index.md index 48d1f8233d..f5d67e68ea 100644 --- a/content/operate/rs/7.4/databases/auto-tiering/_index.md +++ b/content/operate/rs/7.4/databases/auto-tiering/_index.md @@ -53,9 +53,9 @@ When using Auto Tiering, RAM storage holds: - Dictionaries - Hot data (working set) -All data is accessed through RAM. If a value in flash memory is accessed, it becomes part of the working set and is moved to RAM. These values are referred to as “hot data”. +All data is accessed through RAM. If a value in flash memory is accessed, it becomes part of the working set and is moved to RAM. These values are referred to as "hot data". -Inactive or infrequently accessed data is referred to as “warm data” and stored in flash memory. When more space is needed in RAM, warm data is moved from RAM to flash storage. +Inactive or infrequently accessed data is referred to as "warm data" and stored in flash memory. When more space is needed in RAM, warm data is moved from RAM to flash storage. {{}} When using Auto Tiering with RediSearch, it’s important to note that RediSearch indexes are also stored in RAM.{{}} diff --git a/content/operate/rs/7.4/installing-upgrading/product-lifecycle.md b/content/operate/rs/7.4/installing-upgrading/product-lifecycle.md index e5ecaf1445..b794307c8c 100644 --- a/content/operate/rs/7.4/installing-upgrading/product-lifecycle.md +++ b/content/operate/rs/7.4/installing-upgrading/product-lifecycle.md @@ -19,7 +19,7 @@ Redis Enterprise modules follow the [modules lifecycle]({{< relref "/operate/oss ## Release numbers Redis uses a four-place numbering scheme to designate released versions of its products. -The format is “Major1.Major2.Minor-Build”. +The format is "Major1.Major2.Minor-Build". - Major sections of the version number represents fundamental changes and additions in capabilities to Redis Enterprise Software. The Major1 and Major2 part of the diff --git a/content/operate/rs/7.4/networking/cluster-lba-setup.md b/content/operate/rs/7.4/networking/cluster-lba-setup.md index 903c2560d4..de1b564e77 100644 --- a/content/operate/rs/7.4/networking/cluster-lba-setup.md +++ b/content/operate/rs/7.4/networking/cluster-lba-setup.md @@ -44,7 +44,7 @@ The architecture is shown in the following diagram with a 3-node Redis Enterpris - [Install]({{< relref "/operate/rs/7.4/installing-upgrading" >}}) the latest version of Redis Enterprise Software on your clusters - Configure the cluster with the cluster name (FQDN) even though DNS is not in use. Remember that the same cluster name is used to issue the license keys. - We recommend that you use a “.local” suffix in the FQDN. + We recommend that you use a ".local" suffix in the FQDN. ### Configure load balancers diff --git a/content/operate/rs/7.4/references/rest-api/requests/bdbs/modules/config.md b/content/operate/rs/7.4/references/rest-api/requests/bdbs/modules/config.md index 31d70ef179..fe053c693d 100644 --- a/content/operate/rs/7.4/references/rest-api/requests/bdbs/modules/config.md +++ b/content/operate/rs/7.4/references/rest-api/requests/bdbs/modules/config.md @@ -61,7 +61,7 @@ Use the module runtime configuration command (if defined) to configure new argum |-------|------|-------------| | modules | list of JSON objects | List of modules (module_name) and their new configuration settings (module_args) | | module_name | `search`
`ReJSON`
`graph`
`timeseries`
`bf` | Module's name | -| module_args | string | Module command line arguments (pattern does not allow special characters &,<,>,”) | +| module_args | string | Module command line arguments (pattern does not allow special characters &,<,>,") | ### Response {#post-response} diff --git a/content/operate/rs/7.4/references/rest-api/requests/modules/config.md b/content/operate/rs/7.4/references/rest-api/requests/modules/config.md index 104c39c8fa..40caab3062 100644 --- a/content/operate/rs/7.4/references/rest-api/requests/modules/config.md +++ b/content/operate/rs/7.4/references/rest-api/requests/modules/config.md @@ -61,7 +61,7 @@ Use the module runtime configuration command (if defined) to configure new argum |-------|------|-------------| | modules | list of JSON objects | List of modules (module_name) and their new configuration settings (module_args) | | module_name | `search`
`ReJSON`
`graph`
`timeseries`
`bf` | Module's name | -| module_args | string | Module command line arguments (pattern does not allow special characters &,<,>,”) | +| module_args | string | Module command line arguments (pattern does not allow special characters &,<,>,") | ### Response {#post-response} diff --git a/content/operate/rs/7.4/references/rest-api/requests/ocsp/test.md b/content/operate/rs/7.4/references/rest-api/requests/ocsp/test.md index 6274182e02..bc02b970be 100644 --- a/content/operate/rs/7.4/references/rest-api/requests/ocsp/test.md +++ b/content/operate/rs/7.4/references/rest-api/requests/ocsp/test.md @@ -66,7 +66,7 @@ When errors occur, the server returns a JSON object with `error_code` and `messa |------|-------------| | no_responder_url | Tried to test OCSP status with no responder URL configured | | ocsp_unsupported_by_capability | Not all nodes support OCSP capability | -| task_queued_for_too_long | OCSP polling task was in status “queued” for over 5 seconds | +| task_queued_for_too_long | OCSP polling task was in status "queued" for over 5 seconds | | invalid_ocsp_response | The server returned a response that is not compatible with OCSP | ### Status codes {#post-status-codes} diff --git a/content/operate/rs/7.4/security/access-control/ldap/update-database-acls.md b/content/operate/rs/7.4/security/access-control/ldap/update-database-acls.md index a7c8705211..e0d37b77b9 100644 --- a/content/operate/rs/7.4/security/access-control/ldap/update-database-acls.md +++ b/content/operate/rs/7.4/security/access-control/ldap/update-database-acls.md @@ -23,7 +23,7 @@ To grant LDAP users access to a database, assign the mapped access role to the a 1. Select the appropriate roles and then save your changes. -If you assign multiple roles to an ACL and a user is authorized by more than one of these roles, their access is determined by the first “matching” rule in the list. +If you assign multiple roles to an ACL and a user is authorized by more than one of these roles, their access is determined by the first "matching" rule in the list. If the first rule gives them read access and the third rule authorizes write access, the user will only be able to read data. diff --git a/content/operate/rs/7.4/security/encryption/internode-encryption.md b/content/operate/rs/7.4/security/encryption/internode-encryption.md index cb33cf0480..3d079054a7 100644 --- a/content/operate/rs/7.4/security/encryption/internode-encryption.md +++ b/content/operate/rs/7.4/security/encryption/internode-encryption.md @@ -52,7 +52,7 @@ To enable internode encryption for a database (also called _data internode encry ``` rest put /v1/bdbs/${database_id} - { “data_internode_encryption” : true } + { "data_internode_encryption" : true } ``` When you change the data internode encryption setting for a database, all active remote client connections are disconnected. This restarts the internal (DMC) proxy and disconnects all client connections. diff --git a/content/operate/rs/7.8/databases/active-active/develop/_index.md b/content/operate/rs/7.8/databases/active-active/develop/_index.md index afea33fc79..68c8ebc9c0 100644 --- a/content/operate/rs/7.8/databases/active-active/develop/_index.md +++ b/content/operate/rs/7.8/databases/active-active/develop/_index.md @@ -56,12 +56,12 @@ in between. | **Time** | **CRDB Instance1** | **CRDB Instance2** | | ------: | :------: | :------: | -| t1 | SET key1 “a” | | -| t2 | | SET key1 “b” | +| t1 | SET key1 "a" | | +| t2 | | SET key1 "b" | | t3 | — Sync — | — Sync — | -| t4 | SET key1 “c” | | +| t4 | SET key1 "c" | | | t5 | — Sync — | — Sync — | -| t6 | | SET key1 “d” | +| t6 | | SET key1 "d" | [Learn more about synchronization for diff --git a/content/operate/rs/7.8/databases/active-active/develop/data-types/hashes.md b/content/operate/rs/7.8/databases/active-active/develop/data-types/hashes.md index 4f42ddf690..c79046f07d 100644 --- a/content/operate/rs/7.8/databases/active-active/develop/data-types/hashes.md +++ b/content/operate/rs/7.8/databases/active-active/develop/data-types/hashes.md @@ -37,7 +37,7 @@ Here is an example of an "add wins" case: | **Time** | **CRDB Instance1** | **CRDB Instance2** | | ------: | :------: | :------: | -| t1 | HSET key1 field1 “a” | | -| t2 | | HSET key1 field2 “b” | +| t1 | HSET key1 field1 "a" | | +| t2 | | HSET key1 field2 "b" | | t4 | - Sync - | - Sync - | -| t5 | HGETALL key1
1) “field2”
2) “b”
3) “field1”
4) “a” | HGETALL key1
1) “field2”
2) “b”
3) “field1”
4) “a” | +| t5 | HGETALL key1
1) "field2"
2) "b"
3) "field1"
4) "a" | HGETALL key1
1) "field2"
2) "b"
3) "field1"
4) "a" | diff --git a/content/operate/rs/7.8/databases/active-active/develop/data-types/lists.md b/content/operate/rs/7.8/databases/active-active/develop/data-types/lists.md index 4dddc64c4d..a296911250 100644 --- a/content/operate/rs/7.8/databases/active-active/develop/data-types/lists.md +++ b/content/operate/rs/7.8/databases/active-active/develop/data-types/lists.md @@ -27,11 +27,11 @@ example: | **Time** | **CRDB Instance 1** | **CRDB Instance 2** | | ------: | :------: | :------: | -| t1 | LPUSH mylist “hello” | | +| t1 | LPUSH mylist "hello" | | | t2 | — Sync — | — Sync — | -| t3 | | LPUSH mylist “world” | +| t3 | | LPUSH mylist "world" | | t4 | — Sync — | — Sync — | -| t5 | LRANGE mylist 0 -1 =>“world” “hello” | LRANGE mylist 0 -1 => “world” “hello” | +| t5 | LRANGE mylist 0 -1 =>"world" "hello" | LRANGE mylist 0 -1 => "world" "hello" | **Explanation**: The final list contains both the "world" and "hello" elements, in that diff --git a/content/operate/rs/7.8/databases/active-active/develop/data-types/sets.md b/content/operate/rs/7.8/databases/active-active/develop/data-types/sets.md index 401fe018bb..e542eb3680 100644 --- a/content/operate/rs/7.8/databases/active-active/develop/data-types/sets.md +++ b/content/operate/rs/7.8/databases/active-active/develop/data-types/sets.md @@ -31,18 +31,18 @@ Here is an example of an "add wins" case: | **Time** | **CRDB Instance1** | **CRDB Instance2** | | ------: | :------: | :------: | -| t1 | SADD key1 “a” | | -| t2 | | SADD key1 “b” | -| t3 | SMEMBERS key1 “a” | SMEMBERS key1 “b” | +| t1 | SADD key1 "a" | | +| t2 | | SADD key1 "b" | +| t3 | SMEMBERS key1 "a" | SMEMBERS key1 "b" | | t4 | — Sync — | — Sync — | -| t3 | SMEMBERS key1 “a” “b” | SMEMBERS key1 “a” “b” | +| t3 | SMEMBERS key1 "a" "b" | SMEMBERS key1 "a" "b" | Here is an example of an "observed remove" case. | **Time** | **CRDB Instance1** | **CRDB Instance2** | | ------: | :------: | :------: | -| t1 | SMEMBERS key1 “a” “b” | SMEMBERS key1 “a” “b” | -| t2 | SREM key1 “a” | SADD key1 “c” | -| t3 | SREM key1 “c” | | +| t1 | SMEMBERS key1 "a" "b" | SMEMBERS key1 "a" "b" | +| t2 | SREM key1 "a" | SADD key1 "c" | +| t3 | SREM key1 "c" | | | t4 | — Sync — | — Sync — | -| t3 | SMEMBERS key1 “c” “b” | SMEMBERS key1 “c” “b” | +| t3 | SMEMBERS key1 "c" "b" | SMEMBERS key1 "c" "b" | diff --git a/content/operate/rs/7.8/databases/active-active/develop/data-types/strings.md b/content/operate/rs/7.8/databases/active-active/develop/data-types/strings.md index 0ec7bbf836..6529b652cd 100644 --- a/content/operate/rs/7.8/databases/active-active/develop/data-types/strings.md +++ b/content/operate/rs/7.8/databases/active-active/develop/data-types/strings.md @@ -34,12 +34,12 @@ time (t2) wins over the update at t1. | **Time** | **Region 1** | **Region 2** | | :------: | :------: | :------: | -| t1 | SET text “a” | | -| t2 | | SET text “b” | +| t1 | SET text "a" | | +| t2 | | SET text "b" | | t3 | — Sync — | — Sync — | -| t4 | SET text “c” | | +| t4 | SET text "c" | | | t5 | — Sync — | — Sync — | -| t6 | | SET text “d” | +| t6 | | SET text "d" | ### String counter support diff --git a/content/operate/rs/7.8/databases/auto-tiering/_index.md b/content/operate/rs/7.8/databases/auto-tiering/_index.md index 4dd0db2941..4f761e4e54 100644 --- a/content/operate/rs/7.8/databases/auto-tiering/_index.md +++ b/content/operate/rs/7.8/databases/auto-tiering/_index.md @@ -53,9 +53,9 @@ When using Auto Tiering, RAM storage holds: - Dictionaries - Hot data (working set) -All data is accessed through RAM. If a value in flash memory is accessed, it becomes part of the working set and is moved to RAM. These values are referred to as “hot data”. +All data is accessed through RAM. If a value in flash memory is accessed, it becomes part of the working set and is moved to RAM. These values are referred to as "hot data". -Inactive or infrequently accessed data is referred to as “warm data” and stored in flash memory. When more space is needed in RAM, warm data is moved from RAM to flash storage. +Inactive or infrequently accessed data is referred to as "warm data" and stored in flash memory. When more space is needed in RAM, warm data is moved from RAM to flash storage. {{}} When using Auto Tiering with RediSearch, it’s important to note that RediSearch indexes are also stored in RAM.{{}} diff --git a/content/operate/rs/7.8/installing-upgrading/product-lifecycle.md b/content/operate/rs/7.8/installing-upgrading/product-lifecycle.md index 6ebff3c518..9078c78baf 100644 --- a/content/operate/rs/7.8/installing-upgrading/product-lifecycle.md +++ b/content/operate/rs/7.8/installing-upgrading/product-lifecycle.md @@ -19,7 +19,7 @@ Redis Enterprise modules follow the [modules lifecycle]({{< relref "/operate/oss ## Release numbers Redis uses a four-place numbering scheme to designate released versions of its products. -The format is “Major1.Major2.Minor-Build”. +The format is "Major1.Major2.Minor-Build". - Major sections of the version number represents fundamental changes and additions in capabilities to Redis Enterprise Software. The Major1 and Major2 part of the diff --git a/content/operate/rs/7.8/networking/cluster-lba-setup.md b/content/operate/rs/7.8/networking/cluster-lba-setup.md index 36691ab771..1e5ae450dc 100644 --- a/content/operate/rs/7.8/networking/cluster-lba-setup.md +++ b/content/operate/rs/7.8/networking/cluster-lba-setup.md @@ -44,7 +44,7 @@ The architecture is shown in the following diagram with a 3-node Redis Enterpris - [Install]({{< relref "/operate/rs/7.8/installing-upgrading" >}}) the latest version of Redis Enterprise Software on your clusters - Configure the cluster with the cluster name (FQDN) even though DNS is not in use. Remember that the same cluster name is used to issue the license keys. - We recommend that you use a “.local” suffix in the FQDN. + We recommend that you use a ".local" suffix in the FQDN. ### Configure load balancers diff --git a/content/operate/rs/7.8/references/rest-api/requests/bdbs/modules/config.md b/content/operate/rs/7.8/references/rest-api/requests/bdbs/modules/config.md index 0406180f37..2c86504f19 100644 --- a/content/operate/rs/7.8/references/rest-api/requests/bdbs/modules/config.md +++ b/content/operate/rs/7.8/references/rest-api/requests/bdbs/modules/config.md @@ -61,7 +61,7 @@ Use the module runtime configuration command (if defined) to configure new argum |-------|------|-------------| | modules | list of JSON objects | List of modules (module_name) and their new configuration settings (module_args) | | module_name | `search`
`ReJSON`
`graph`
`timeseries`
`bf` | Module's name | -| module_args | string | Module command line arguments (pattern does not allow special characters &,<,>,”) | +| module_args | string | Module command line arguments (pattern does not allow special characters &,<,>,") | ### Response {#post-response} diff --git a/content/operate/rs/7.8/references/rest-api/requests/modules/config.md b/content/operate/rs/7.8/references/rest-api/requests/modules/config.md index 10406fd74d..2a3bf9fe51 100644 --- a/content/operate/rs/7.8/references/rest-api/requests/modules/config.md +++ b/content/operate/rs/7.8/references/rest-api/requests/modules/config.md @@ -61,7 +61,7 @@ Use the module runtime configuration command (if defined) to configure new argum |-------|------|-------------| | modules | list of JSON objects | List of modules (module_name) and their new configuration settings (module_args) | | module_name | `search`
`ReJSON`
`graph`
`timeseries`
`bf` | Module's name | -| module_args | string | Module command line arguments (pattern does not allow special characters &,<,>,”) | +| module_args | string | Module command line arguments (pattern does not allow special characters &,<,>,") | ### Response {#post-response} diff --git a/content/operate/rs/7.8/references/rest-api/requests/ocsp/test.md b/content/operate/rs/7.8/references/rest-api/requests/ocsp/test.md index 5e793a26cb..bfd8fb170b 100644 --- a/content/operate/rs/7.8/references/rest-api/requests/ocsp/test.md +++ b/content/operate/rs/7.8/references/rest-api/requests/ocsp/test.md @@ -66,7 +66,7 @@ When errors occur, the server returns a JSON object with `error_code` and `messa |------|-------------| | no_responder_url | Tried to test OCSP status with no responder URL configured | | ocsp_unsupported_by_capability | Not all nodes support OCSP capability | -| task_queued_for_too_long | OCSP polling task was in status “queued” for over 5 seconds | +| task_queued_for_too_long | OCSP polling task was in status "queued" for over 5 seconds | | invalid_ocsp_response | The server returned a response that is not compatible with OCSP | ### Status codes {#post-status-codes} diff --git a/content/operate/rs/7.8/security/access-control/ldap/update-database-acls.md b/content/operate/rs/7.8/security/access-control/ldap/update-database-acls.md index 75fae59c1e..59c10b6d57 100644 --- a/content/operate/rs/7.8/security/access-control/ldap/update-database-acls.md +++ b/content/operate/rs/7.8/security/access-control/ldap/update-database-acls.md @@ -23,7 +23,7 @@ To grant LDAP users access to a database, assign the mapped access role to the a 1. Select the appropriate roles and then save your changes. -If you assign multiple roles to an ACL and a user is authorized by more than one of these roles, their access is determined by the first “matching” rule in the list. +If you assign multiple roles to an ACL and a user is authorized by more than one of these roles, their access is determined by the first "matching" rule in the list. If the first rule gives them read access and the third rule authorizes write access, the user will only be able to read data. diff --git a/content/operate/rs/7.8/security/encryption/internode-encryption.md b/content/operate/rs/7.8/security/encryption/internode-encryption.md index cc8c267118..3bb398d34a 100644 --- a/content/operate/rs/7.8/security/encryption/internode-encryption.md +++ b/content/operate/rs/7.8/security/encryption/internode-encryption.md @@ -52,7 +52,7 @@ To enable internode encryption for a database (also called _data internode encry ``` rest put /v1/bdbs/${database_id} - { “data_internode_encryption” : true } + { "data_internode_encryption" : true } ``` When you change the data internode encryption setting for a database, all active remote client connections are disconnected. This restarts the internal (DMC) proxy and disconnects all client connections. diff --git a/content/operate/rs/databases/active-active/develop/_index.md b/content/operate/rs/databases/active-active/develop/_index.md index 0d20bd84fe..a650fd8933 100644 --- a/content/operate/rs/databases/active-active/develop/_index.md +++ b/content/operate/rs/databases/active-active/develop/_index.md @@ -55,12 +55,12 @@ in between. | **Time** | **CRDB Instance1** | **CRDB Instance2** | | ------: | :------: | :------: | -| t1 | SET key1 “a” | | -| t2 | | SET key1 “b” | +| t1 | SET key1 "a" | | +| t2 | | SET key1 "b" | | t3 | — Sync — | — Sync — | -| t4 | SET key1 “c” | | +| t4 | SET key1 "c" | | | t5 | — Sync — | — Sync — | -| t6 | | SET key1 “d” | +| t6 | | SET key1 "d" | [Learn more about synchronization for diff --git a/content/operate/rs/databases/active-active/develop/data-types/hashes.md b/content/operate/rs/databases/active-active/develop/data-types/hashes.md index 86959250a5..acba9bf23d 100644 --- a/content/operate/rs/databases/active-active/develop/data-types/hashes.md +++ b/content/operate/rs/databases/active-active/develop/data-types/hashes.md @@ -36,7 +36,7 @@ Here is an example of an "add wins" case: | **Time** | **CRDB Instance1** | **CRDB Instance2** | | ------: | :------: | :------: | -| t1 | HSET key1 field1 “a” | | -| t2 | | HSET key1 field2 “b” | +| t1 | HSET key1 field1 "a" | | +| t2 | | HSET key1 field2 "b" | | t4 | - Sync - | - Sync - | -| t5 | HGETALL key1
1) “field2”
2) “b”
3) “field1”
4) “a” | HGETALL key1
1) “field2”
2) “b”
3) “field1”
4) “a” | +| t5 | HGETALL key1
1) "field2"
2) "b"
3) "field1"
4) "a" | HGETALL key1
1) "field2"
2) "b"
3) "field1"
4) "a" | diff --git a/content/operate/rs/databases/active-active/develop/data-types/lists.md b/content/operate/rs/databases/active-active/develop/data-types/lists.md index 63604ad298..95df255051 100644 --- a/content/operate/rs/databases/active-active/develop/data-types/lists.md +++ b/content/operate/rs/databases/active-active/develop/data-types/lists.md @@ -26,11 +26,11 @@ example: | **Time** | **CRDB Instance 1** | **CRDB Instance 2** | | ------: | :------: | :------: | -| t1 | LPUSH mylist “hello” | | +| t1 | LPUSH mylist "hello" | | | t2 | — Sync — | — Sync — | -| t3 | | LPUSH mylist “world” | +| t3 | | LPUSH mylist "world" | | t4 | — Sync — | — Sync — | -| t5 | LRANGE mylist 0 -1 =>“world” “hello” | LRANGE mylist 0 -1 => “world” “hello” | +| t5 | LRANGE mylist 0 -1 =>"world" "hello" | LRANGE mylist 0 -1 => "world" "hello" | **Explanation**: The final list contains both the "world" and "hello" elements, in that diff --git a/content/operate/rs/databases/active-active/develop/data-types/sets.md b/content/operate/rs/databases/active-active/develop/data-types/sets.md index 732b661010..ff91ee22ed 100644 --- a/content/operate/rs/databases/active-active/develop/data-types/sets.md +++ b/content/operate/rs/databases/active-active/develop/data-types/sets.md @@ -30,18 +30,18 @@ Here is an example of an "add wins" case: | **Time** | **CRDB Instance1** | **CRDB Instance2** | | ------: | :------: | :------: | -| t1 | SADD key1 “a” | | -| t2 | | SADD key1 “b” | -| t3 | SMEMBERS key1 “a” | SMEMBERS key1 “b” | +| t1 | SADD key1 "a" | | +| t2 | | SADD key1 "b" | +| t3 | SMEMBERS key1 "a" | SMEMBERS key1 "b" | | t4 | — Sync — | — Sync — | -| t3 | SMEMBERS key1 “a” “b” | SMEMBERS key1 “a” “b” | +| t3 | SMEMBERS key1 "a" "b" | SMEMBERS key1 "a" "b" | Here is an example of an "observed remove" case. | **Time** | **CRDB Instance1** | **CRDB Instance2** | | ------: | :------: | :------: | -| t1 | SMEMBERS key1 “a” “b” | SMEMBERS key1 “a” “b” | -| t2 | SREM key1 “a” | SADD key1 “c” | -| t3 | SREM key1 “c” | | +| t1 | SMEMBERS key1 "a" "b" | SMEMBERS key1 "a" "b" | +| t2 | SREM key1 "a" | SADD key1 "c" | +| t3 | SREM key1 "c" | | | t4 | — Sync — | — Sync — | -| t3 | SMEMBERS key1 “c” “b” | SMEMBERS key1 “c” “b” | +| t3 | SMEMBERS key1 "c" "b" | SMEMBERS key1 "c" "b" | diff --git a/content/operate/rs/databases/active-active/develop/data-types/strings.md b/content/operate/rs/databases/active-active/develop/data-types/strings.md index c8c01a9e94..a7e37e7cc7 100644 --- a/content/operate/rs/databases/active-active/develop/data-types/strings.md +++ b/content/operate/rs/databases/active-active/develop/data-types/strings.md @@ -33,12 +33,12 @@ time (t2) wins over the update at t1. | **Time** | **Region 1** | **Region 2** | | :------: | :------: | :------: | -| t1 | SET text “a” | | -| t2 | | SET text “b” | +| t1 | SET text "a" | | +| t2 | | SET text "b" | | t3 | — Sync — | — Sync — | -| t4 | SET text “c” | | +| t4 | SET text "c" | | | t5 | — Sync — | — Sync — | -| t6 | | SET text “d” | +| t6 | | SET text "d" | ### String counter support diff --git a/content/operate/rs/databases/auto-tiering/_index.md b/content/operate/rs/databases/auto-tiering/_index.md index 4b7ea88f52..1f50abba7e 100644 --- a/content/operate/rs/databases/auto-tiering/_index.md +++ b/content/operate/rs/databases/auto-tiering/_index.md @@ -52,9 +52,9 @@ When using Auto Tiering, RAM storage holds: - Dictionaries - Hot data (working set) -All data is accessed through RAM. If a value in flash memory is accessed, it becomes part of the working set and is moved to RAM. These values are referred to as “hot data”. +All data is accessed through RAM. If a value in flash memory is accessed, it becomes part of the working set and is moved to RAM. These values are referred to as "hot data". -Inactive or infrequently accessed data is referred to as “warm data” and stored in flash memory. When more space is needed in RAM, warm data is moved from RAM to flash storage. +Inactive or infrequently accessed data is referred to as "warm data" and stored in flash memory. When more space is needed in RAM, warm data is moved from RAM to flash storage. {{}} When using Auto Tiering with RediSearch, it’s important to note that RediSearch indexes are also stored in RAM.{{}} diff --git a/content/operate/rs/installing-upgrading/product-lifecycle.md b/content/operate/rs/installing-upgrading/product-lifecycle.md index f1db3ac2dd..b401ba5bf8 100644 --- a/content/operate/rs/installing-upgrading/product-lifecycle.md +++ b/content/operate/rs/installing-upgrading/product-lifecycle.md @@ -18,7 +18,7 @@ Redis Enterprise modules follow the [modules lifecycle]({{< relref "/operate/oss ## Release numbers Redis uses a four-place numbering scheme to designate released versions of its products. -The format is “Major1.Major2.Minor-Build”. +The format is "Major1.Major2.Minor-Build". - Major sections of the version number represents fundamental changes and additions in capabilities to Redis Enterprise Software. The Major1 and Major2 part of the diff --git a/content/operate/rs/networking/cluster-lba-setup.md b/content/operate/rs/networking/cluster-lba-setup.md index dc4170a283..1d37f1b0be 100644 --- a/content/operate/rs/networking/cluster-lba-setup.md +++ b/content/operate/rs/networking/cluster-lba-setup.md @@ -43,7 +43,7 @@ The architecture is shown in the following diagram with a 3-node Redis Enterpris - [Install]({{< relref "/operate/rs/installing-upgrading" >}}) the latest version of Redis Enterprise Software on your clusters - Configure the cluster with the cluster name (FQDN) even though DNS is not in use. Remember that the same cluster name is used to issue the license keys. - We recommend that you use a “.local” suffix in the FQDN. + We recommend that you use a ".local" suffix in the FQDN. ### Configure load balancers diff --git a/content/operate/rs/references/rest-api/requests/bdbs/modules/config.md b/content/operate/rs/references/rest-api/requests/bdbs/modules/config.md index a30dd17c74..d203d7da89 100644 --- a/content/operate/rs/references/rest-api/requests/bdbs/modules/config.md +++ b/content/operate/rs/references/rest-api/requests/bdbs/modules/config.md @@ -60,7 +60,7 @@ Use the module runtime configuration command (if defined) to configure new argum |-------|------|-------------| | modules | list of JSON objects | List of modules (module_name) and their new configuration settings (module_args) | | module_name | `search`
`ReJSON`
`graph`
`timeseries`
`bf` | Module's name | -| module_args | string | Module command line arguments (pattern does not allow special characters &,<,>,”) | +| module_args | string | Module command line arguments (pattern does not allow special characters &,<,>,") | ### Response {#post-response} diff --git a/content/operate/rs/references/rest-api/requests/modules/config.md b/content/operate/rs/references/rest-api/requests/modules/config.md index 38264ac1c1..abb8ca2939 100644 --- a/content/operate/rs/references/rest-api/requests/modules/config.md +++ b/content/operate/rs/references/rest-api/requests/modules/config.md @@ -60,7 +60,7 @@ Use the module runtime configuration command (if defined) to configure new argum |-------|------|-------------| | modules | list of JSON objects | List of modules (module_name) and their new configuration settings (module_args) | | module_name | `search`
`ReJSON`
`graph`
`timeseries`
`bf` | Module's name | -| module_args | string | Module command line arguments (pattern does not allow special characters &,<,>,”) | +| module_args | string | Module command line arguments (pattern does not allow special characters &,<,>,") | ### Response {#post-response} diff --git a/content/operate/rs/references/rest-api/requests/ocsp/test.md b/content/operate/rs/references/rest-api/requests/ocsp/test.md index 6f7683815b..5b3c7496af 100644 --- a/content/operate/rs/references/rest-api/requests/ocsp/test.md +++ b/content/operate/rs/references/rest-api/requests/ocsp/test.md @@ -65,7 +65,7 @@ When errors occur, the server returns a JSON object with `error_code` and `messa |------|-------------| | no_responder_url | Tried to test OCSP status with no responder URL configured | | ocsp_unsupported_by_capability | Not all nodes support OCSP capability | -| task_queued_for_too_long | OCSP polling task was in status “queued” for over 5 seconds | +| task_queued_for_too_long | OCSP polling task was in status "queued" for over 5 seconds | | invalid_ocsp_response | The server returned a response that is not compatible with OCSP | ### Status codes {#post-status-codes} diff --git a/content/operate/rs/release-notes/legacy-release-notes/rs-5-2-2-august-2018.md b/content/operate/rs/release-notes/legacy-release-notes/rs-5-2-2-august-2018.md index ba8e695399..38c79f8263 100644 --- a/content/operate/rs/release-notes/legacy-release-notes/rs-5-2-2-august-2018.md +++ b/content/operate/rs/release-notes/legacy-release-notes/rs-5-2-2-august-2018.md @@ -29,7 +29,7 @@ RediSearch Enterprise, which is installed with Redis Enterprise Software by defa - RED-20506 – Fixed high CPU and File Descriptors utilization by the node watchdog process (node_wd) - RED-20275 – Fixed wrong metrics values while importing a dataset into an RoF database - RED-20214 – Fixed obstacles to login to the UI when using an LDAP integration -- RED-20162 – Fixed known limitation of being able to activate “Require SSL for All Communication” to Redis Enterprise CRDBs via Rest API without providing a certificate +- RED-20162 – Fixed known limitation of being able to activate "Require SSL for All Communication" to Redis Enterprise CRDBs via Rest API without providing a certificate - RED-19758 – Upgraded NGINX from 1.10.3 to 1.13.12 - RED-19415, RED-18945 – Improved support for Lettuce client with OSS Cluster enabled - RED-19287 – Fixed a scenario of a stuck shard migration process diff --git a/content/operate/rs/release-notes/legacy-release-notes/rs-5-6-0-april-2020.md b/content/operate/rs/release-notes/legacy-release-notes/rs-5-6-0-april-2020.md index 2d98677395..a792f448e2 100644 --- a/content/operate/rs/release-notes/legacy-release-notes/rs-5-6-0-april-2020.md +++ b/content/operate/rs/release-notes/legacy-release-notes/rs-5-6-0-april-2020.md @@ -112,7 +112,7 @@ The following GA releases of Redis Modules are bundled in RS 5.6.0: ## Additional capabilities - OSS Redis version [5.0.8](https://raw.githubusercontent.com/antirez/redis/5.0/00-RELEASENOTES) is merged into RS 5.6.0. -- Starting RS 5.6.0, to upgrade modules during database upgrade you must use the module_args option instead of keep_module_args or or “ ” (for no arguments). The module_args option must follow with one of the following (Always in quotation marks): “keep_args” or “ “ or “”. +- Starting RS 5.6.0, to upgrade modules during database upgrade you must use the module_args option instead of keep_module_args or or " " (for no arguments). The module_args option must follow with one of the following (Always in quotation marks): "keep_args" or " " or "". For more info and examples, check out [upgrading Redis Modules documentation]({{< relref "/operate/oss_and_stack/stack-with-enterprise/install/upgrade-module" >}}) . - rladmin adds the ability to demote the cluster master node when setting it to [maintenance mode]({{< relref "/operate/rs/clusters/maintenance-mode.md" >}}) by using the `demote_node` option: diff --git a/content/operate/rs/release-notes/rs-6-0-12-january-2021.md b/content/operate/rs/release-notes/rs-6-0-12-january-2021.md index 0548327974..23bebe4443 100644 --- a/content/operate/rs/release-notes/rs-6-0-12-january-2021.md +++ b/content/operate/rs/release-notes/rs-6-0-12-january-2021.md @@ -102,7 +102,7 @@ To enable the syncer automatic recovery, do these steps on each participating cl 1. Enable the syncer automatic recovery using the REST API: ```sh - curl -v -k -u : -X PUT -H “Content-Type: application/json” -d ‘{crdt_syncer_auto_oom_unlatch”:true}’ http://:8080/v1/bdbs/ + curl -v -k -u : -X PUT -H "Content-Type: application/json" -d ‘{crdt_syncer_auto_oom_unlatch":true}’ http://:8080/v1/bdbs/ ``` The syncer process restarts to with automatic recovery on. diff --git a/content/operate/rs/release-notes/rs-6-0-20-april-2021.md b/content/operate/rs/release-notes/rs-6-0-20-april-2021.md index 1e7d0aa175..0e1b6bf030 100644 --- a/content/operate/rs/release-notes/rs-6-0-20-april-2021.md +++ b/content/operate/rs/release-notes/rs-6-0-20-april-2021.md @@ -186,7 +186,7 @@ All known bugs around setting ciphers were fixed. To learn more, see [Configure - RS57659 - Fixed force removing an Active-Active instance which is hosted on an inaccessible cluster - RS57315 - Fixed creation and editing of an Active-Active database with LDAP users of the new RBAC LDAP integration. This applies to UI access and REST API and does not apply to LDAP users for database access via Redis Clients - RS57073 - Fixed a bug caused in the shard migration process which could leave unattended shards on the node -- RS56508 - Fixed backwards compatibility of client certificate when upgrading from earlier versions and using a certificate chain with Extended Key Usage extension being set to “TLS Web Server Authentication” instead of “TLS Web Client Authentication” +- RS56508 - Fixed backwards compatibility of client certificate when upgrading from earlier versions and using a certificate chain with Extended Key Usage extension being set to "TLS Web Server Authentication" instead of "TLS Web Client Authentication" - RS49289 - Fixed updating the log rotation config file according to the custom config path that was set during the installation - The bundled RedisGraph module was upgraded to v2.4.6 - The bundled RedisTimeSeries module was upgraded to v1.4.9 diff --git a/content/operate/rs/release-notes/rs-6-2-12.md b/content/operate/rs/release-notes/rs-6-2-12.md index c780184476..a0e07b90b4 100644 --- a/content/operate/rs/release-notes/rs-6-2-12.md +++ b/content/operate/rs/release-notes/rs-6-2-12.md @@ -111,7 +111,7 @@ For help upgrading a module, see [Add a module to a cluster]({{< relref "/operat - RS72466, RS68668 Fix false positive alerts for certification expiration - RS69256 Change pre-bootstrap default TLS version to 1.2 - RS67133 Fixed replication for command RESTOREMODAUX -- RS66468 Fixed “Test regex keys” in the UI +- RS66468 Fixed "Test regex keys" in the UI - RS58156 Fixed the installation to abort and alert when encountering issues in NTP - RS67935 Fixed releasing 30MB of memory when deleting an Active-Active database - RS64276 Fixed high memory consumption of the DMC output buffers when running CLIENT LIST diff --git a/content/operate/rs/release-notes/rs-6-2-18-releases/rs-6-2-18-43.md b/content/operate/rs/release-notes/rs-6-2-18-releases/rs-6-2-18-43.md index dc172632b3..3a3221e027 100644 --- a/content/operate/rs/release-notes/rs-6-2-18-releases/rs-6-2-18-43.md +++ b/content/operate/rs/release-notes/rs-6-2-18-releases/rs-6-2-18-43.md @@ -160,7 +160,7 @@ For Redis modules information and lifecycle, see [Module lifecycle]({{< relref " - RS73454 - Updates internal timeouts to enable faster resharding. - RS75783 - Fixes failover due to false identification of dead nodes when master node goes down. - RS75206, RS52686 - Fixes backup_interval_offset in case where the user chose an offset that is higher than backup_interval; Fixes the UI from resetting backup_interval_offset after manual DB configuration. -- RS75176 - Fixes rare case of stuck state machine during “maintenance off”. +- RS75176 - Fixes rare case of stuck state machine during "maintenance off". - RS57200 - Add an IP address to "failed_authentication_attempt" errors. - RS56615 - Changed rladmin tune db db_name max_aof_load_time to receive the value in seconds; Added max_aof_load_time option to rladmin help tune. - RS54745 - Fixes the Rest API to reject BDB creation using negative integers as a uid. diff --git a/content/operate/rs/release-notes/rs-6-2-18-releases/rs-6-2-18-58.md b/content/operate/rs/release-notes/rs-6-2-18-releases/rs-6-2-18-58.md index 55a996dedd..250f306363 100644 --- a/content/operate/rs/release-notes/rs-6-2-18-releases/rs-6-2-18-58.md +++ b/content/operate/rs/release-notes/rs-6-2-18-releases/rs-6-2-18-58.md @@ -41,7 +41,7 @@ See [Upgrade modules]({{< relref "/operate/oss_and_stack/stack-with-enterprise/i ## Resolved issues - RS85369 - Fixes umask validation during installation to allow for temporary umask change -- RS77339 - Fixes the “FROM” email addresses of email alerts +- RS77339 - Fixes the "FROM" email addresses of email alerts - RS86005 - Fixes `bdbs//actions/recover` API to return the bdb status and not the `recovery_plan` ## Known upgrade limitations diff --git a/content/operate/rs/release-notes/rs-6-2-8-october-2021.md b/content/operate/rs/release-notes/rs-6-2-8-october-2021.md index 66f4471678..48d6bd329f 100644 --- a/content/operate/rs/release-notes/rs-6-2-8-october-2021.md +++ b/content/operate/rs/release-notes/rs-6-2-8-october-2021.md @@ -76,7 +76,7 @@ To learn more, see [Upgrade the module for a database]({{< relref "/operate/oss_ - RS60068 / RS59146 - Fixed unresolved endpoint due to PDNS issues - RS52812 - Expand API wrapper to return API 405 errors as JSON/XML - RS57666 - Fixed false shard migration message when the shard fails to bind the port -- RS57444, RS55294, RS4903 - Fixed false “backup finished successfully” message when the backup failed due to restricted access to the backup destination +- RS57444, RS55294, RS4903 - Fixed false "backup finished successfully" message when the backup failed due to restricted access to the backup destination ### Fixes on build #53 - RS67829 - Fixed a bug that caused Modules' auxiliary field not to get replicated between the primary and the replica shards. Applicable for RediSearch, RedisGraph and RedisGears and happening only at following scenarios: diff --git a/content/operate/rs/release-notes/rs-6-4-2-releases/rs-6-4-2-30.md b/content/operate/rs/release-notes/rs-6-4-2-releases/rs-6-4-2-30.md index 61ed84af32..0a9f715331 100644 --- a/content/operate/rs/release-notes/rs-6-4-2-releases/rs-6-4-2-30.md +++ b/content/operate/rs/release-notes/rs-6-4-2-releases/rs-6-4-2-30.md @@ -74,7 +74,7 @@ See [Upgrade modules]({{< relref "/operate/oss_and_stack/stack-with-enterprise/i #### Installations, upgrades, and troubleshooting -- Added the ability for `install.sh` to run even if “upgrade mode” is already enabled to allow reruns in case of a previous run failure (RS77319) +- Added the ability for `install.sh` to run even if "upgrade mode" is already enabled to allow reruns in case of a previous run failure (RS77319) - Added log messages to the `redis_mgr` process (RS77891), the job_scheduler process (RS82673), and the `install.sh` script (RS82673) diff --git a/content/operate/rs/release-notes/rs-6-4-2-releases/rs-6-4-2-94.md b/content/operate/rs/release-notes/rs-6-4-2-releases/rs-6-4-2-94.md index 753c9e9810..463ffe6f9f 100644 --- a/content/operate/rs/release-notes/rs-6-4-2-releases/rs-6-4-2-94.md +++ b/content/operate/rs/release-notes/rs-6-4-2-releases/rs-6-4-2-94.md @@ -54,7 +54,7 @@ See [Upgrade modules]({{< relref "/operate/oss_and_stack/stack-with-enterprise/i ## Resolved issues -- RS100903 - Fixed a v6.4.2 issue: when a database client requests [`SLOWLOG GET [count]`]({{< relref "/commands/slowlog-get" >}}, the proxy ignores “count” and always replies with 128 records +- RS100903 - Fixed a v6.4.2 issue: when a database client requests [`SLOWLOG GET [count]`]({{< relref "/commands/slowlog-get" >}}, the proxy ignores "count" and always replies with 128 records - RS95394 - Fixed Replica Of sync causing high DMC memory usage on source cluster when TLS is enabled "for Replica Of Only". diff --git a/content/operate/rs/release-notes/rs-7-2-4-releases/rs-7-2-4-52.md b/content/operate/rs/release-notes/rs-7-2-4-releases/rs-7-2-4-52.md index da04ff9ca7..ba54f4b515 100644 --- a/content/operate/rs/release-notes/rs-7-2-4-releases/rs-7-2-4-52.md +++ b/content/operate/rs/release-notes/rs-7-2-4-releases/rs-7-2-4-52.md @@ -360,13 +360,13 @@ The [`INFO`]({{< relref "/commands/info" >}}) command includes new fields: - Under the `STATS` section: - - `current_eviction_exceeded_time` - Redis Enterprise reply is always “0” + - `current_eviction_exceeded_time` - Redis Enterprise reply is always "0" - - `total_eviction_exceeded_time` - Redis Enterprise reply is always “0” + - `total_eviction_exceeded_time` - Redis Enterprise reply is always "0" - - `current_active_defrag_time` - Redis Enterprise reply is always “0” + - `current_active_defrag_time` - Redis Enterprise reply is always "0" - - `total_active_defrag_time` - Redis Enterprise reply is always “0” + - `total_active_defrag_time` - Redis Enterprise reply is always "0" - Under the `MEMORY` section: @@ -400,7 +400,7 @@ Starting from Redis Enterprise version 7.2, all future 7.2.x upgrades are suppor - RS104028 - Fix the self-signed certificate script: error generating certificates with multiple FQDNs -- RS87920 - Proxy log is full of the warning message “Failed to check status of running child syncer process 0 : No child processes“ +- RS87920 - Proxy log is full of the warning message "Failed to check status of running child syncer process 0 : No child processes" - RS99916 - Fixed the UI log to include the names of LDAP users at login diff --git a/content/operate/rs/release-notes/rs-7-4-2-releases/rs-7-4-2-104.md b/content/operate/rs/release-notes/rs-7-4-2-releases/rs-7-4-2-104.md index 61a0d2a48e..14c656bbc8 100644 --- a/content/operate/rs/release-notes/rs-7-4-2-releases/rs-7-4-2-104.md +++ b/content/operate/rs/release-notes/rs-7-4-2-releases/rs-7-4-2-104.md @@ -28,7 +28,7 @@ This version offers: - You can change your password from the sign-in screen. - - Added a “User is locked out” label to the **Access Control > Users** screen to help administrators identify and manage locked users. + - Added a "User is locked out" label to the **Access Control > Users** screen to help administrators identify and manage locked users. #### Redis module feature sets diff --git a/content/operate/rs/security/access-control/ldap/update-database-acls.md b/content/operate/rs/security/access-control/ldap/update-database-acls.md index bae0b9b646..f12c9bd908 100644 --- a/content/operate/rs/security/access-control/ldap/update-database-acls.md +++ b/content/operate/rs/security/access-control/ldap/update-database-acls.md @@ -22,7 +22,7 @@ To grant LDAP users access to a database, assign the mapped access role to the a 1. Select the appropriate roles and then save your changes. -If you assign multiple roles to an ACL and a user is authorized by more than one of these roles, their access is determined by the first “matching” rule in the list. +If you assign multiple roles to an ACL and a user is authorized by more than one of these roles, their access is determined by the first "matching" rule in the list. If the first rule gives them read access and the third rule authorizes write access, the user will only be able to read data. diff --git a/content/operate/rs/security/encryption/internode-encryption.md b/content/operate/rs/security/encryption/internode-encryption.md index c83958ac4b..f315bc12db 100644 --- a/content/operate/rs/security/encryption/internode-encryption.md +++ b/content/operate/rs/security/encryption/internode-encryption.md @@ -51,7 +51,7 @@ To enable internode encryption for a database (also called _data internode encry ``` rest put /v1/bdbs/${database_id} - { “data_internode_encryption” : true } + { "data_internode_encryption" : true } ``` When you change the data internode encryption setting for a database, all active remote client connections are disconnected. This restarts the internal (DMC) proxy and disconnects all client connections.