url
stringlengths 38
157
| content
stringlengths 72
15.1M
|
|---|---|
https://redis.io/docs/latest/operate/rs/release-notes/rs-7-2-4-releases/rs-7-2-4-109/.html | <section class="prose w-full py-12 max-w-none">
<h1>
Redis Enterprise Software release notes 7.2.4-109 (May 2024)
</h1>
<p class="text-lg -mt-5 mb-10">
Bug fixes.
</p>
<p>
This is a maintenance release for
<a href="https://redis.com/redis-enterprise-software/download-center/software/">
Redis Enterprise Software version 7.2.4
</a>
.
</p>
<h2 id="highlights">
Highlights
</h2>
<p>
This version offers:
</p>
<ul>
<li>
Bug fixes
</li>
</ul>
<h2 id="new-in-this-release">
New in this release
</h2>
<h3 id="enhancements">
Enhancements
</h3>
<h4 id="redis-modules">
Redis modules
</h4>
<p>
Redis Enterprise Software versions 7.2.4-109 includes the following Redis Stack modules:
</p>
<ul>
<li>
<p>
<a href="/docs/latest/operate/oss_and_stack/stack-with-enterprise/release-notes/redisearch/redisearch-2.8-release-notes">
RediSearch 2.8.9
</a>
</p>
</li>
<li>
<p>
<a href="/docs/latest/operate/oss_and_stack/stack-with-enterprise/release-notes/redisjson/redisjson-2.6-release-notes">
RedisJSON 2.6.6
</a>
</p>
</li>
<li>
<p>
<a href="/docs/latest/operate/oss_and_stack/stack-with-enterprise/release-notes/redistimeseries/redistimeseries-1.10-release-notes">
RedisTimeSeries 1.10.6
</a>
</p>
</li>
<li>
<p>
<a href="/docs/latest/operate/oss_and_stack/stack-with-enterprise/release-notes/redisbloom/redisbloom-2.6-release-notes">
RedisBloom 2.6.11
</a>
</p>
</li>
<li>
<p>
<a href="https://github.com/RedisGears/RedisGears/releases/tag/v2.0.17-m18">
RedisGears 2.0.17
</a>
</p>
</li>
</ul>
<h3 id="resolved-issues">
Resolved issues
</h3>
<ul>
<li>
<p>
RS121673: Search commands no longer return an error after fixing incorrect configuration.
</p>
</li>
<li>
<p>
RS123237: CRDT syncer prevents potential data mismatches or data loss due to missing keys when removing and re-adding a cluster in an Active-Active setup with at least three participating clusters after removing older clusters without re-adding them.
</p>
</li>
<li>
<p>
RS122221:
<code>
redis-server
</code>
creates PID file only after binding to a socket.
</p>
</li>
</ul>
<h2 id="version-changes">
Version changes
</h2>
<h3 id="supported-platforms">
Supported platforms
</h3>
<p>
The following table provides a snapshot of supported platforms as of this Redis Enterprise Software release. See the
<a href="/docs/latest/operate/rs/references/supported-platforms/">
supported platforms reference
</a>
for more details about operating system compatibility.
</p>
<p>
<span title="Check mark icon">
✅
</span>
Supported – The platform is supported for this version of Redis Enterprise Software and Redis Stack modules.
</p>
<p>
<span class="font-serif" title="Warning icon">
⚠️
</span>
Deprecation warning – The platform is still supported for this version of Redis Enterprise Software, but support will be removed in a future release.
</p>
<table>
<thead>
<tr>
<th>
Redis Enterprise
<br/>
major versions
</th>
<th style="text-align:center">
7.4
</th>
<th style="text-align:center">
7.2
</th>
<th style="text-align:center">
6.4
</th>
<th style="text-align:center">
6.2
</th>
</tr>
</thead>
<tbody>
<tr>
<td>
<strong>
Release date
</strong>
</td>
<td style="text-align:center">
Feb 2024
</td>
<td style="text-align:center">
Aug 2023
</td>
<td style="text-align:center">
Feb 2023
</td>
<td style="text-align:center">
Aug 2021
</td>
</tr>
<tr>
<td>
<a href="/docs/latest/operate/rs/installing-upgrading/product-lifecycle/#endoflife-schedule">
<strong>
End-of-life date
</strong>
</a>
</td>
<td style="text-align:center">
Determined after
<br/>
next major release
</td>
<td style="text-align:center">
July 2025
</td>
<td style="text-align:center">
Feb 2025
</td>
<td style="text-align:center">
Aug 2024
</td>
</tr>
<tr>
<td>
<strong>
Platforms
</strong>
</td>
<td style="text-align:center">
</td>
<td style="text-align:center">
</td>
<td style="text-align:center">
</td>
<td style="text-align:center">
</td>
</tr>
<tr>
<td>
RHEL 9 &
<br/>
compatible distros
<sup>
<a href="#table-note-1">
1
</a>
</sup>
</td>
<td style="text-align:center">
<span title="Supported">
✅
</span>
</td>
<td style="text-align:center">
–
</td>
<td style="text-align:center">
–
</td>
<td style="text-align:center">
–
</td>
</tr>
<tr>
<td>
RHEL 8 &
<br/>
compatible distros
<sup>
<a href="#table-note-1">
1
</a>
</sup>
</td>
<td style="text-align:center">
<span title="Supported">
✅
</span>
</td>
<td style="text-align:center">
<span title="Supported">
✅
</span>
</td>
<td style="text-align:center">
<span title="Supported">
✅
</span>
</td>
<td style="text-align:center">
<span title="Supported">
✅
</span>
</td>
</tr>
<tr>
<td>
RHEL 7 &
<br/>
compatible distros
<sup>
<a href="#table-note-1">
1
</a>
</sup>
</td>
<td style="text-align:center">
–
</td>
<td style="text-align:center">
<span class="font-serif" title="Deprecated">
⚠️
</span>
</td>
<td style="text-align:center">
<span title="Supported">
✅
</span>
</td>
<td style="text-align:center">
<span title="Supported">
✅
</span>
</td>
</tr>
<tr>
<td>
Ubuntu 20.04
<sup>
<a href="#table-note-2">
2
</a>
</sup>
</td>
<td style="text-align:center">
<span title="Supported">
✅
</span>
</td>
<td style="text-align:center">
<span title="Supported">
✅
</span>
</td>
<td style="text-align:center">
<span title="Supported">
✅
</span>
</td>
<td style="text-align:center">
–
</td>
</tr>
<tr>
<td>
Ubuntu 18.04
<sup>
<a href="#table-note-2">
2
</a>
</sup>
</td>
<td style="text-align:center">
<span class="font-serif" title="Deprecated">
⚠️
</span>
</td>
<td style="text-align:center">
<span class="font-serif" title="Deprecated">
⚠️
</span>
</td>
<td style="text-align:center">
<span title="Supported">
✅
</span>
</td>
<td style="text-align:center">
<span title="Supported">
✅
</span>
</td>
</tr>
<tr>
<td>
Ubuntu 16.04
<sup>
<a href="#table-note-2">
2
</a>
</sup>
</td>
<td style="text-align:center">
–
</td>
<td style="text-align:center">
<span class="font-serif" title="Deprecated">
⚠️
</span>
</td>
<td style="text-align:center">
<span title="Supported">
✅
</span>
</td>
<td style="text-align:center">
<span title="Supported">
✅
</span>
</td>
</tr>
<tr>
<td>
Amazon Linux 2
</td>
<td style="text-align:center">
<span title="Supported">
✅
</span>
</td>
<td style="text-align:center">
<span title="Supported">
✅
</span>
</td>
<td style="text-align:center">
<span title="Supported">
✅
</span>
</td>
<td style="text-align:center">
–
</td>
</tr>
<tr>
<td>
Amazon Linux 1
</td>
<td style="text-align:center">
–
</td>
<td style="text-align:center">
<span title="Supported">
✅
</span>
</td>
<td style="text-align:center">
<span title="Supported">
✅
</span>
</td>
<td style="text-align:center">
<span title="Supported">
✅
</span>
</td>
</tr>
<tr>
<td>
Kubernetes
<sup>
<a href="#table-note-3">
3
</a>
</sup>
</td>
<td style="text-align:center">
<span title="Supported">
✅
</span>
</td>
<td style="text-align:center">
<span title="Supported">
✅
</span>
</td>
<td style="text-align:center">
<span title="Supported">
✅
</span>
</td>
<td style="text-align:center">
<span title="Supported">
✅
</span>
</td>
</tr>
<tr>
<td>
Docker
<sup>
<a href="#table-note-4">
4
</a>
</sup>
</td>
<td style="text-align:center">
<span title="Supported">
✅
</span>
</td>
<td style="text-align:center">
<span title="Supported">
✅
</span>
</td>
<td style="text-align:center">
<span title="Supported">
✅
</span>
</td>
<td style="text-align:center">
<span title="Supported">
✅
</span>
</td>
</tr>
</tbody>
</table>
<ol>
<li>
<p>
<a name="table-note-1" style="display: block; height: 80px; margin-top: -80px;">
</a>
The RHEL-compatible distributions CentOS, CentOS Stream, Alma, and Rocky are supported if they have full RHEL compatibility. Oracle Linux running the Red Hat Compatible Kernel (RHCK) is supported, but the Unbreakable Enterprise Kernel (UEK) is not supported.
</p>
</li>
<li>
<p>
<a name="table-note-2" style="display: block; height: 80px; margin-top: -80px;">
</a>
The server version of Ubuntu is recommended for production installations. The desktop version is only recommended for development deployments.
</p>
</li>
<li>
<p>
<a name="table-note-3" style="display: block; height: 80px; margin-top: -80px;">
</a>
See the
<a href="/docs/latest/operate/kubernetes/reference/supported_k8s_distributions/">
Redis Enterprise for Kubernetes documentation
</a>
for details about support per version and Kubernetes distribution.
</p>
</li>
<li>
<p>
<a name="table-note-4" style="display: block; height: 80px; margin-top: -80px;">
</a>
<a href="/docs/latest/operate/rs/installing-upgrading/quickstarts/docker-quickstart/">
Docker images
</a>
of Redis Enterprise Software are certified for development and testing only.
</p>
</li>
</ol>
<h2 id="downloads">
Downloads
</h2>
<p>
The following table shows the MD5 checksums for the available packages:
</p>
<table>
<thead>
<tr>
<th>
Package
</th>
<th>
MD5 checksum (7.2.4-109 May release)
</th>
</tr>
</thead>
<tbody>
<tr>
<td>
Ubuntu 18
</td>
<td>
ae041ffa0eee0652afe69767683a64e4
</td>
</tr>
<tr>
<td>
Ubuntu 20
</td>
<td>
9e33c630f357a657eed8f084eec70d8d
</td>
</tr>
<tr>
<td>
Red Hat Enterprise Linux (RHEL) 7
</td>
<td>
8f3c56ad8ae2a790a31e2253eaaa1ccc
</td>
</tr>
<tr>
<td>
Red Hat Enterprise Linux (RHEL) 8
</td>
<td>
974c6815bfd53bf74e349b2beae1780f
</td>
</tr>
<tr>
<td>
Amazon Linux 2
</td>
<td>
70c7a8560ee96d72065132e77cb79fe0
</td>
</tr>
</tbody>
</table>
<h2 id="security">
Security
</h2>
<h4 id="open-source-redis-security-fixes-compatibility">
Open source Redis security fixes compatibility
</h4>
<p>
As part of Redis's commitment to security, Redis Enterprise Software implements the latest
<a href="https://github.com/redis/redis/releases">
security fixes
</a>
available with
<a href="https://github.com/redis/redis">
open source Redis
</a>
. Redis Enterprise has already included the fixes for the relevant CVEs.
</p>
<p>
Some CVEs announced for open source Redis do not affect Redis Enterprise due to different or additional functionality available in Redis Enterprise that is not available in open source Redis.
</p>
<p>
Redis Enterprise 7.2.4-109 supports open source Redis 7.2, 6.2, and 6.0. Below is the list of open source Redis CVEs fixed by version.
</p>
<p>
Redis 7.2.x:
</p>
<ul>
<li>
<p>
(CVE-2024-31449) An authenticated user may use a specially crafted Lua script to trigger a stack buffer overflow in the bit library, which may potentially lead to remote code execution.
</p>
</li>
<li>
<p>
(CVE-2024-31228) An authenticated user can trigger a denial-of-service by using specially crafted, long string match patterns on supported commands such as
<code>
KEYS
</code>
,
<code>
SCAN
</code>
,
<code>
PSUBSCRIBE
</code>
,
<code>
FUNCTION LIST
</code>
,
<code>
COMMAND LIST
</code>
, and ACL definitions. Matching of extremely long patterns may result in unbounded recursion, leading to stack overflow and process crashes.
</p>
</li>
<li>
<p>
(CVE-2023-41056) In some cases, Redis may incorrectly handle resizing of memory buffers, which can result in incorrect accounting of buffer sizes and lead to heap overflow and potential remote code execution.
</p>
</li>
<li>
<p>
(CVE-2023-41053) Redis does not correctly identify keys accessed by
<code>
SORT_RO
</code>
and, as a result, may grant users executing this command access to keys that are not explicitly authorized by the ACL configuration. (Redis 7.2.1)
</p>
</li>
</ul>
<p>
Redis 7.0.x:
</p>
<ul>
<li>
<p>
(CVE-2024-31449) An authenticated user may use a specially crafted Lua script to trigger a stack buffer overflow in the bit library, which may potentially lead to remote code execution.
</p>
</li>
<li>
<p>
(CVE-2024-31228) An authenticated user can trigger a denial-of-service by using specially crafted, long string match patterns on supported commands such as
<code>
KEYS
</code>
,
<code>
SCAN
</code>
,
<code>
PSUBSCRIBE
</code>
,
<code>
FUNCTION LIST
</code>
,
<code>
COMMAND LIST
</code>
, and ACL definitions. Matching of extremely long patterns may result in unbounded recursion, leading to stack overflow and process crashes.
</p>
</li>
<li>
<p>
(CVE-2023-41056) In some cases, Redis may incorrectly handle resizing of memory buffers, which can result in incorrect accounting of buffer sizes and lead to heap overflow and potential remote code execution.
</p>
</li>
<li>
<p>
(CVE-2023-41053) Redis does not correctly identify keys accessed by
<code>
SORT_RO
</code>
and, as a result, may grant users executing this command access to keys that are not explicitly authorized by the ACL configuration. (Redis 7.0.13)
</p>
</li>
<li>
<p>
(CVE-2023-36824) Extracting key names from a command and a list of arguments may, in some cases, trigger a heap overflow and result in reading random heap memory, heap corruption, and potentially remote code execution. Specifically: using
<code>
COMMAND GETKEYS*
</code>
and validation of key names in ACL rules. (Redis 7.0.12)
</p>
</li>
<li>
<p>
(CVE-2023-28856) Authenticated users can use the
<code>
HINCRBYFLOAT
</code>
command to create an invalid hash field that will crash Redis on access. (Redis 7.0.11)
</p>
</li>
<li>
<p>
(CVE-2023-28425) Specially crafted
<code>
MSETNX
</code>
command can lead to assertion and denial-of-service. (Redis 7.0.10)
</p>
</li>
<li>
<p>
(CVE-2023-25155) Specially crafted
<code>
SRANDMEMBER
</code>
,
<code>
ZRANDMEMBER
</code>
, and
<code>
HRANDFIELD
</code>
commands can trigger an integer overflow, resulting in a runtime assertion and termination of the Redis server process. (Redis 7.0.9)
</p>
</li>
<li>
<p>
(CVE-2023-22458) Integer overflow in the Redis
<code>
HRANDFIELD
</code>
and
<code>
ZRANDMEMBER
</code>
commands can lead to denial-of-service. (Redis 7.0.8)
</p>
</li>
<li>
<p>
(CVE-2022-36021) String matching commands (like
<code>
SCAN
</code>
or
<code>
KEYS
</code>
) with a specially crafted pattern to trigger a denial-of-service attack on Redis, causing it to hang and consume 100% CPU time. (Redis 7.0.9)
</p>
</li>
<li>
<p>
(CVE-2022-35977) Integer overflow in the Redis
<code>
SETRANGE
</code>
and
<code>
SORT
</code>
/
<code>
SORT_RO
</code>
commands can drive Redis to OOM panic. (Redis 7.0.8)
</p>
</li>
<li>
<p>
(CVE-2022-35951) Executing an
<code>
XAUTOCLAIM
</code>
command on a stream key in a specific state, with a specially crafted
<code>
COUNT
</code>
argument, may cause an integer overflow, a subsequent heap overflow, and potentially lead to remote code execution. The problem affects Redis versions 7.0.0 or newer. (Redis 7.0.5)
</p>
</li>
<li>
<p>
(CVE-2022-31144) A specially crafted
<code>
XAUTOCLAIM
</code>
command on a stream key in a specific state may result in heap overflow and potentially remote code execution. The problem affects Redis versions 7.0.0 or newer. (Redis 7.0.4)
</p>
</li>
<li>
<p>
(CVE-2022-24834) A specially crafted Lua script executing in Redis can trigger a heap overflow in the cjson and cmsgpack libraries, and result in heap corruption and potentially remote code execution. The problem exists in all versions of Redis with Lua scripting support, starting from 2.6, and affects only authenticated and authorized users. (Redis 7.0.12)
</p>
</li>
<li>
<p>
(CVE-2022-24736) An attacker attempting to load a specially crafted Lua script can cause NULL pointer dereference which will result in a crash of the
<code>
redis-server
</code>
process. This issue affects all versions of Redis. (Redis 7.0.0)
</p>
</li>
<li>
<p>
(CVE-2022-24735) By exploiting weaknesses in the Lua script execution environment, an attacker with access to Redis can inject Lua code that will execute with the (potentially higher) privileges of another Redis user. (Redis 7.0.0)
</p>
</li>
</ul>
<p>
Redis 6.2.x:
</p>
<ul>
<li>
<p>
(CVE-2024-31449) An authenticated user may use a specially crafted Lua script to trigger a stack buffer overflow in the bit library, which may potentially lead to remote code execution.
</p>
</li>
<li>
<p>
(CVE-2024-31228) An authenticated user can trigger a denial-of-service by using specially crafted, long string match patterns on supported commands such as
<code>
KEYS
</code>
,
<code>
SCAN
</code>
,
<code>
PSUBSCRIBE
</code>
,
<code>
FUNCTION LIST
</code>
,
<code>
COMMAND LIST
</code>
, and ACL definitions. Matching of extremely long patterns may result in unbounded recursion, leading to stack overflow and process crashes.
</p>
</li>
<li>
<p>
(CVE-2023-45145) The wrong order of listen(2) and chmod(2) calls creates a
race condition that can be used by another process to bypass desired Unix
socket permissions on startup. (Redis 6.2.14)
</p>
</li>
<li>
<p>
(CVE-2023-28856) Authenticated users can use the
<code>
HINCRBYFLOAT
</code>
command to create an invalid hash field that will crash Redis on access. (Redis 6.2.12)
</p>
</li>
<li>
<p>
(CVE-2023-25155) Specially crafted
<code>
SRANDMEMBER
</code>
,
<code>
ZRANDMEMBER
</code>
, and
<code>
HRANDFIELD
</code>
commands can trigger an integer overflow, resulting in a runtime assertion and termination of the Redis server process. (Redis 6.2.11)
</p>
</li>
<li>
<p>
(CVE-2023-22458) Integer overflow in the Redis
<code>
HRANDFIELD
</code>
and
<code>
ZRANDMEMBER
</code>
commands can lead to denial-of-service. (Redis 6.2.9)
</p>
</li>
<li>
<p>
(CVE-2022-36021) String matching commands (like
<code>
SCAN
</code>
or
<code>
KEYS
</code>
) with a specially crafted pattern to trigger a denial-of-service attack on Redis, causing it to hang and consume 100% CPU time. (Redis 6.2.11)
</p>
</li>
<li>
<p>
(CVE-2022-35977) Integer overflow in the Redis
<code>
SETRANGE
</code>
and
<code>
SORT
</code>
/
<code>
SORT_RO
</code>
commands can drive Redis to OOM panic. (Redis 6.2.9)
</p>
</li>
<li>
<p>
(CVE-2022-24834) A specially crafted Lua script executing in Redis can trigger a heap overflow in the cjson and cmsgpack libraries, and result in heap corruption and potentially remote code execution. The problem exists in all versions of Redis with Lua scripting support, starting from 2.6, and affects only authenticated and authorized users. (Redis 6.2.13)
</p>
</li>
<li>
<p>
(CVE-2022-24736) An attacker attempting to load a specially crafted Lua script can cause NULL pointer dereference which will result in a crash of the
<code>
redis-server
</code>
process. This issue affects all versions of Redis. (Redis 6.2.7)
</p>
</li>
<li>
<p>
(CVE-2022-24735) By exploiting weaknesses in the Lua script execution environment, an attacker with access to Redis can inject Lua code that will execute with the (potentially higher) privileges of another Redis user. (Redis 6.2.7)
</p>
</li>
<li>
<p>
(CVE-2021-41099) Integer to heap buffer overflow handling certain string commands and network payloads, when
<code>
proto-max-bulk-len
</code>
is manually configured to a non-default, very large value. (Redis 6.2.6)
</p>
</li>
<li>
<p>
(CVE-2021-32762) Integer to heap buffer overflow issue in
<code>
redis-cli
</code>
and
<code>
redis-sentinel
</code>
parsing large multi-bulk replies on some older and less common platforms. (Redis 6.2.6)
</p>
</li>
<li>
<p>
(CVE-2021-32761) An integer overflow bug in Redis version 2.2 or newer can be exploited using the
<code>
BITFIELD
</code>
command to corrupt the heap and potentially result with remote code execution. (Redis 6.2.5)
</p>
</li>
<li>
<p>
(CVE-2021-32687) Integer to heap buffer overflow with intsets, when
<code>
set-max-intset-entries
</code>
is manually configured to a non-default, very large value. (Redis 6.2.6)
</p>
</li>
<li>
<p>
(CVE-2021-32675) Denial Of Service when processing RESP request payloads with a large number of elements on many connections. (Redis 6.2.6)
</p>
</li>
<li>
<p>
(CVE-2021-32672) Random heap reading issue with Lua Debugger. (Redis 6.2.6)
</p>
</li>
<li>
<p>
(CVE-2021-32628) Integer to heap buffer overflow handling ziplist-encoded data types, when configuring a large, non-default value for
<code>
hash-max-ziplist-entries
</code>
,
<code>
hash-max-ziplist-value
</code>
,
<code>
zset-max-ziplist-entries
</code>
or
<code>
zset-max-ziplist-value
</code>
. (Redis 6.2.6)
</p>
</li>
<li>
<p>
(CVE-2021-32627) Integer to heap buffer overflow issue with streams, when configuring a non-default, large value for
<code>
proto-max-bulk-len
</code>
and
<code>
client-query-buffer-limit
</code>
. (Redis 6.2.6)
</p>
</li>
<li>
<p>
(CVE-2021-32626) Specially crafted Lua scripts may result with Heap buffer overflow. (Redis 6.2.6)
</p>
</li>
<li>
<p>
(CVE-2021-32625) An integer overflow bug in Redis version 6.0 or newer can be exploited using the STRALGO LCS command to corrupt the heap and potentially result with remote code execution. This is a result of an incomplete fix by CVE-2021-29477. (Redis 6.2.4)
</p>
</li>
<li>
<p>
(CVE-2021-29478) An integer overflow bug in Redis 6.2 could be exploited to corrupt the heap and potentially result with remote code execution. The vulnerability involves changing the default set-max-intset-entries configuration value, creating a large set key that consists of integer values and using the COPY command to duplicate it. The integer overflow bug exists in all versions of Redis starting with 2.6, where it could result with a corrupted RDB or DUMP payload, but not exploited through COPY (which did not exist before 6.2). (Redis 6.2.3)
</p>
</li>
<li>
<p>
(CVE-2021-29477) An integer overflow bug in Redis version 6.0 or newer could be exploited using the STRALGO LCS command to corrupt the heap and potentially result in remote code execution. The integer overflow bug exists in all versions of Redis starting with 6.0. (Redis 6.2.3)
</p>
</li>
</ul>
<p>
Redis 6.0.x:
</p>
<ul>
<li>
<p>
(CVE-2022-24834) A specially crafted Lua script executing in Redis can trigger a heap overflow in the cjson and cmsgpack libraries, and result in heap corruption and potentially remote code execution. The problem exists in all versions of Redis with Lua scripting support, starting from 2.6, and affects only authenticated and authorized users. (Redis 6.0.20)
</p>
</li>
<li>
<p>
(CVE-2023-28856) Authenticated users can use the
<code>
HINCRBYFLOAT
</code>
command to create an invalid hash field that will crash Redis on access. (Redis 6.0.19)
</p>
</li>
<li>
<p>
(CVE-2023-25155) Specially crafted
<code>
SRANDMEMBER
</code>
,
<code>
ZRANDMEMBER
</code>
, and
<code>
HRANDFIELD
</code>
commands can trigger an integer overflow, resulting in a runtime assertion and termination of the Redis server process. (Redis 6.0.18)
</p>
</li>
<li>
<p>
(CVE-2022-36021) String matching commands (like
<code>
SCAN
</code>
or
<code>
KEYS
</code>
) with a specially crafted pattern to trigger a denial-of-service attack on Redis, causing it to hang and consume 100% CPU time. (Redis 6.0.18)
</p>
</li>
<li>
<p>
(CVE-2022-35977) Integer overflow in the Redis
<code>
SETRANGE
</code>
and
<code>
SORT
</code>
/
<code>
SORT_RO
</code>
commands can drive Redis to OOM panic. (Redis 6.0.17)
</p>
</li>
</ul>
<form class="text-sm w-full mt-24 pt-5 border-t border-t-redis-pen-700 border-opacity-50" id="page-feedback" name="page-feedback">
<input class="hidden" name="origin" value="https://redis.io/docs/latest/operate/rs/release-notes/rs-7-2-4-releases/rs-7-2-4-109/"/>
<div class="flex flex-row justify-between">
<div class="grid justify-center">
<span class="font-mono">
RATE THIS PAGE
</span>
<div class="star-rating">
<input id="5-stars" name="rating" onchange="document.querySelector('#feedback-form').classList.remove('hidden')" type="radio" value="5"/>
<label class="star" for="5-stars">
★
</label>
<input id="4-stars" name="rating" onchange="document.querySelector('#feedback-form').classList.remove('hidden')" type="radio" value="4"/>
<label class="star" for="4-stars">
★
</label>
<input id="3-stars" name="rating" onchange="document.querySelector('#feedback-form').classList.remove('hidden')" type="radio" value="3"/>
<label class="star" for="3-stars">
★
</label>
<input id="2-stars" name="rating" onchange="document.querySelector('#feedback-form').classList.remove('hidden')" type="radio" value="2"/>
<label class="star" for="2-stars">
★
</label>
<input id="1-stars" name="rating" onchange="document.querySelector('#feedback-form').classList.remove('hidden')" type="radio" value="1"/>
<label class="star" for="1-stars">
★
</label>
</div>
</div>
<a class="font-mono no-underline" href="#">
Back to top ↑
</a>
</div>
<div class="hidden" id="feedback-form">
<div class="grid gap-2">
<textarea class="p-2 mt-1 block w-full h-24 border border-opacity-50 border-redis-ink-900 rounded-md" name="comment" placeholder="Why did you choose this rating?" rows="3"></textarea>
<button class="font-mono button text-redis-ink-900 border border-solid border-transparent bg-redis-red-500 hover:bg-redis-red-600 focus:bg-red-600 focus:ring-red-600; w-min justify-self-end" type="submit">
Submit
</button>
</div>
</div>
</form>
<script>
document.addEventListener("DOMContentLoaded", function() {
const form = document.querySelector("#page-feedback");
form.addEventListener("submit", function(event) {
event.preventDefault();
var xhr = new XMLHttpRequest();
var url = "\/docusight\/api\/rate";
var params = new URLSearchParams(new FormData(form));
xhr.open("POST", url, true);
xhr.setRequestHeader("Content-Type", "application/x-www-form-urlencoded");
xhr.onreadystatechange = function() {
if (xhr.readyState === 4 && xhr.status === 200) {
const responseData = JSON.parse(xhr.responseText);
const responseMessage = responseData.response;
const newText = document.createTextNode(responseMessage);
form.parentNode.replaceChild(newText, form);
}
};
xhr.send(params);
});
});
</script>
</section>
|
https://redis.io/docs/latest/operate/rs/references/compatibility/commands/.html | <section class="prose w-full py-12 max-w-none">
<h1>
Compatibility with Redis Community Edition commands
</h1>
<p class="text-lg -mt-5 mb-10">
Redis Community Edition commands compatible with Redis Enterprise.
</p>
<p>
Learn which Redis Community Edition commands are compatible with Redis Enterprise Software and
<a href="/docs/latest/operate/rc/">
Redis Cloud
</a>
.
</p>
<p>
Select a command group for more details about compatibility with standard and Active-Active Redis Enterprise.
</p>
<table>
<thead>
<tr>
<th style="text-align:left">
Command group
</th>
<th style="text-align:left">
Description
</th>
</tr>
</thead>
<tbody>
<tr>
<td style="text-align:left">
<a href="/docs/latest/operate/rs/references/compatibility/commands/cluster/">
Cluster management
</a>
</td>
<td style="text-align:left">
Cluster management commands compatible with Redis Enterprise.
</td>
</tr>
<tr>
<td style="text-align:left">
<a href="/docs/latest/operate/rs/references/compatibility/commands/connection/">
Connection management
</a>
</td>
<td style="text-align:left">
Connection management commands compatibility.
</td>
</tr>
<tr>
<td style="text-align:left">
<a href="/docs/latest/operate/rs/references/compatibility/commands/data-types/">
Data types
</a>
</td>
<td style="text-align:left">
Data type commands compatibility (bitmaps, geospatial indices, hashes, HyperLogLogs, lists, sets, sorted sets, streams, strings).
</td>
</tr>
<tr>
<td style="text-align:left">
<a href="/docs/latest/operate/rs/references/compatibility/commands/generic/">
Keys (generic)
</a>
</td>
<td style="text-align:left">
Generic key commands compatible with Redis Enterprise.
</td>
</tr>
<tr>
<td style="text-align:left">
<a href="/docs/latest/operate/rs/references/compatibility/commands/pub-sub/">
Pub/sub
</a>
</td>
<td style="text-align:left">
Pub/sub commands compatibility.
</td>
</tr>
<tr>
<td style="text-align:left">
<a href="/docs/latest/operate/rs/references/compatibility/commands/scripting/">
Scripting
</a>
</td>
<td style="text-align:left">
Scripting and function commands compatibility.
</td>
</tr>
<tr>
<td style="text-align:left">
<a href="/docs/latest/operate/rs/references/compatibility/commands/server/">
Server management
</a>
</td>
<td style="text-align:left">
Server management commands compatibility.
</td>
</tr>
<tr>
<td style="text-align:left">
<a href="/docs/latest/operate/rs/references/compatibility/commands/transactions/">
Transactions
</a>
</td>
<td style="text-align:left">
Transaction commands compatibility.
</td>
</tr>
</tbody>
</table>
<form class="text-sm w-full mt-24 pt-5 border-t border-t-redis-pen-700 border-opacity-50" id="page-feedback" name="page-feedback">
<input class="hidden" name="origin" value="https://redis.io/docs/latest/operate/rs/references/compatibility/commands/"/>
<div class="flex flex-row justify-between">
<div class="grid justify-center">
<span class="font-mono">
RATE THIS PAGE
</span>
<div class="star-rating">
<input id="5-stars" name="rating" onchange="document.querySelector('#feedback-form').classList.remove('hidden')" type="radio" value="5"/>
<label class="star" for="5-stars">
★
</label>
<input id="4-stars" name="rating" onchange="document.querySelector('#feedback-form').classList.remove('hidden')" type="radio" value="4"/>
<label class="star" for="4-stars">
★
</label>
<input id="3-stars" name="rating" onchange="document.querySelector('#feedback-form').classList.remove('hidden')" type="radio" value="3"/>
<label class="star" for="3-stars">
★
</label>
<input id="2-stars" name="rating" onchange="document.querySelector('#feedback-form').classList.remove('hidden')" type="radio" value="2"/>
<label class="star" for="2-stars">
★
</label>
<input id="1-stars" name="rating" onchange="document.querySelector('#feedback-form').classList.remove('hidden')" type="radio" value="1"/>
<label class="star" for="1-stars">
★
</label>
</div>
</div>
<a class="font-mono no-underline" href="#">
Back to top ↑
</a>
</div>
<div class="hidden" id="feedback-form">
<div class="grid gap-2">
<textarea class="p-2 mt-1 block w-full h-24 border border-opacity-50 border-redis-ink-900 rounded-md" name="comment" placeholder="Why did you choose this rating?" rows="3"></textarea>
<button class="font-mono button text-redis-ink-900 border border-solid border-transparent bg-redis-red-500 hover:bg-redis-red-600 focus:bg-red-600 focus:ring-red-600; w-min justify-self-end" type="submit">
Submit
</button>
</div>
</div>
</form>
<script>
document.addEventListener("DOMContentLoaded", function() {
const form = document.querySelector("#page-feedback");
form.addEventListener("submit", function(event) {
event.preventDefault();
var xhr = new XMLHttpRequest();
var url = "\/docusight\/api\/rate";
var params = new URLSearchParams(new FormData(form));
xhr.open("POST", url, true);
xhr.setRequestHeader("Content-Type", "application/x-www-form-urlencoded");
xhr.onreadystatechange = function() {
if (xhr.readyState === 4 && xhr.status === 200) {
const responseData = JSON.parse(xhr.responseText);
const responseMessage = responseData.response;
const newText = document.createTextNode(responseMessage);
form.parentNode.replaceChild(newText, form);
}
};
xhr.send(params);
});
});
</script>
</section>
|
https://redis.io/docs/latest/operate/rc/subscriptions/maintenance/set-maintenance-windows/.html | <section class="prose w-full py-12 max-w-none">
<h1>
Set maintenance windows
</h1>
<p class="text-lg -mt-5 mb-10">
Shows how to set manual maintenance windows and skip maintenance.
</p>
<p>
By default, Redis will maintain your Redis Cloud subscriptions and databases as needed. During maintenance, you may notice some latency when connecting to your databases. For more information about the types of maintenance and how Redis maintains your subscriptions, see
<a href="/docs/latest/operate/rc/subscriptions/maintenance/">
Maintenance
</a>
.
</p>
<p>
For Redis Cloud Pro plans, Redis will perform maintenance automatically while limiting service disruption as much as possible. If you want to control when Redis performs maintenance for a Redis Cloud Pro subscription, you can
<a href="#set-manual-maintenance-windows">
set manual maintenance windows
</a>
to ensure non-urgent maintenance will occur at set times. Configuring or altering the maintenance window will not have any impact on your subscription or databases.
</p>
<div class="alert p-3 relative flex flex-row items-center text-base bg-redis-pencil-200 rounded-md">
<div class="p-2 pr-5">
<svg fill="none" height="21" viewbox="0 0 21 21" width="21" xmlns="http://www.w3.org/2000/svg">
<circle cx="10.5" cy="10.5" r="9.75" stroke="currentColor" stroke-width="1.5">
</circle>
<path d="M10.5 14V16" stroke="currentColor" stroke-width="2">
</path>
<path d="M10.5 5V12" stroke="currentColor" stroke-width="2">
</path>
</svg>
</div>
<div class="p-1 pl-6 border-l border-l-redis-ink-900 border-opacity-50">
<div class="font-medium">
Note:
</div>
You can only set manual maintenance windows for Redis Cloud Pro plans. A Redis Cloud Essentials database has a set maintenance window based on the region where it is located. See
<a href="/docs/latest/operate/rc/subscriptions/maintenance/#redis-cloud-essentials">
Essentials maintenance
</a>
for more information.
</div>
</div>
<h2 id="set-manual-maintenance-windows">
Set manual maintenance windows
</h2>
<p>
To set manual maintenance windows for a single Redis Cloud Pro subscription:
</p>
<ol>
<li>
<p>
From the
<a href="https://cloud.redis.io/">
Redis Cloud console
</a>
, select the
<strong>
Subscriptions
</strong>
menu and then select your subscription from the list.
</p>
</li>
<li>
<p>
Select the
<strong>
Overview
</strong>
tab.
</p>
</li>
<li>
<p>
In the
<strong>
Maintenance Windows
</strong>
panel, select
<strong>
Manual
</strong>
.
</p>
</li>
<li>
<p>
Click
<strong>
Activate
</strong>
to confirm your selection.
</p>
</li>
<li>
<p>
Enter the maintenance window time frame details.
</p>
<a href="/docs/latest/images/rc/subscriptions-set-maintenance-window.png" sdata-lightbox="/images/rc/subscriptions-set-maintenance-window.png">
<img alt="The set maintenance windows panel" src="/docs/latest/images/rc/subscriptions-set-maintenance-window.png"/>
</a>
<ul>
<li>
Select the days that Redis can perform maintenance in the
<strong>
Days
</strong>
drop-down.
</li>
<li>
Select the time that Redis can start performing maintenance on those days in the
<strong>
From
</strong>
drop-down.
</li>
<li>
Select the amount of time that Redis can perform maintenance in the
<strong>
Duration
</strong>
drop-down.
</li>
<li>
Select
<strong>
+ Time Frame
</strong>
to add another time frame for maintenance.
</li>
</ul>
<p>
Redis recommends allowing maintenance on at least two different days for 8 hours on each day.
</p>
</li>
<li>
<p>
Click
<strong>
Save
</strong>
.
</p>
</li>
</ol>
<h2 id="skip-maintenance-temporarily">
Skip maintenance temporarily
</h2>
<p>
To skip maintenance temporarily for a subscription:
</p>
<ol>
<li>
<p>
From the
<a href="https://cloud.redis.io/">
Redis Cloud console
</a>
, select the
<strong>
Subscriptions
</strong>
menu and then select your subscription from the list.
</p>
</li>
<li>
<p>
Select the
<strong>
Overview
</strong>
tab.
</p>
</li>
<li>
<p>
In the
<strong>
Maintenance Windows
</strong>
panel, select
<strong>
Skip the next 7 days
</strong>
.
</p>
</li>
<li>
<p>
Click
<strong>
Continue
</strong>
to confirm your selection.
</p>
</li>
</ol>
<p>
You will only be allowed to skip maintenance twice in one month.
</p>
<p>
During the skipped maintenance period, Redis will not perform any minor or major upgrades. Redis may perform
<a href="/docs/latest/operate/rc/subscriptions/maintenance/#urgent-maintenance">
urgent maintenance
</a>
on your subscription, but only if it is absolutely necessary.
</p>
<form class="text-sm w-full mt-24 pt-5 border-t border-t-redis-pen-700 border-opacity-50" id="page-feedback" name="page-feedback">
<input class="hidden" name="origin" value="https://redis.io/docs/latest/operate/rc/subscriptions/maintenance/set-maintenance-windows/"/>
<div class="flex flex-row justify-between">
<div class="grid justify-center">
<span class="font-mono">
RATE THIS PAGE
</span>
<div class="star-rating">
<input id="5-stars" name="rating" onchange="document.querySelector('#feedback-form').classList.remove('hidden')" type="radio" value="5"/>
<label class="star" for="5-stars">
★
</label>
<input id="4-stars" name="rating" onchange="document.querySelector('#feedback-form').classList.remove('hidden')" type="radio" value="4"/>
<label class="star" for="4-stars">
★
</label>
<input id="3-stars" name="rating" onchange="document.querySelector('#feedback-form').classList.remove('hidden')" type="radio" value="3"/>
<label class="star" for="3-stars">
★
</label>
<input id="2-stars" name="rating" onchange="document.querySelector('#feedback-form').classList.remove('hidden')" type="radio" value="2"/>
<label class="star" for="2-stars">
★
</label>
<input id="1-stars" name="rating" onchange="document.querySelector('#feedback-form').classList.remove('hidden')" type="radio" value="1"/>
<label class="star" for="1-stars">
★
</label>
</div>
</div>
<a class="font-mono no-underline" href="#">
Back to top ↑
</a>
</div>
<div class="hidden" id="feedback-form">
<div class="grid gap-2">
<textarea class="p-2 mt-1 block w-full h-24 border border-opacity-50 border-redis-ink-900 rounded-md" name="comment" placeholder="Why did you choose this rating?" rows="3"></textarea>
<button class="font-mono button text-redis-ink-900 border border-solid border-transparent bg-redis-red-500 hover:bg-redis-red-600 focus:bg-red-600 focus:ring-red-600; w-min justify-self-end" type="submit">
Submit
</button>
</div>
</div>
</form>
<script>
document.addEventListener("DOMContentLoaded", function() {
const form = document.querySelector("#page-feedback");
form.addEventListener("submit", function(event) {
event.preventDefault();
var xhr = new XMLHttpRequest();
var url = "\/docusight\/api\/rate";
var params = new URLSearchParams(new FormData(form));
xhr.open("POST", url, true);
xhr.setRequestHeader("Content-Type", "application/x-www-form-urlencoded");
xhr.onreadystatechange = function() {
if (xhr.readyState === 4 && xhr.status === 200) {
const responseData = JSON.parse(xhr.responseText);
const responseMessage = responseData.response;
const newText = document.createTextNode(responseMessage);
form.parentNode.replaceChild(newText, form);
}
};
xhr.send(params);
});
});
</script>
</section>
|
https://redis.io/docs/latest/operate/oss_and_stack/stack-with-enterprise/modules-lifecycle/.html | <section class="prose w-full py-12 max-w-none">
<h1>
Module lifecycle
</h1>
<p>
Redis Enterprise Software follows the
<a href="/docs/latest/operate/rs/installing-upgrading/product-lifecycle/">
Redis Enterprise lifecycle
</a>
. (For complete details, see the Redis Enterprise Software
<a href="https://redis.com/software-subscription-agreement">
subscription agreement
</a>
.)
</p>
<p>
The modules included in Redis Stack also follow a release lifecycle and schedule. Here, you'll find the "end-of-life" dates for each module and release.
</p>
<h2 id="module-release-numbering">
Module release numbering
</h2>
<p>
Redis modules use a three-place numbering scheme to identify released versions.
</p>
<p>
The format is “Major1.Major2.Minor”.
</p>
<ul>
<li>
<p>
Major sections of the version number represent fundamental changes to functionality and feature capabilities. The
<em>
Major1
</em>
and
<em>
Major2
</em>
part of the version number are incremented according to the size and scale of the changes in each release.
</p>
</li>
<li>
<p>
The
<em>
Minor
</em>
section of the version number represents quality improvements and fixes to existing capabilities. The minor release number is increased when release quality improves.
</p>
</li>
</ul>
<h2 id="modules-endoflife-schedule">
Module end-of-life schedule
</h2>
<p>
End-of-Life for a given Major version is 18 months after the formal release of
that version or 12 months after the release of the next subsequent (following) version, whichever comes last.
</p>
<h3 id="redisearch">
RediSearch
</h3>
<table>
<thead>
<tr>
<th>
Release Date
</th>
<th>
End-of-Life (EOL)
</th>
</tr>
</thead>
<tbody>
</tbody>
<tbody>
<tr>
<td align="left">
2.8 - July 2023
</td>
<td align="left">
-
</td>
</tr>
</tbody>
<tbody>
<tr>
<td align="left">
2.6 - November 2022
</td>
<td align="left">
July 31, 2024
</td>
</tr>
</tbody>
<tbody>
<tr>
<td align="left">
2.4 - March 2022
</td>
<td align="left">
November 30, 2023
</td>
</tr>
</tbody>
<tbody>
<tr>
<td align="left">
2.2 - November 2021
</td>
<td align="left">
May 31, 2023
</td>
</tr>
</tbody>
<tbody>
<tr>
<td align="left">
2.0 – September 2020
</td>
<td align="left">
November 30, 2022
</td>
</tr>
</tbody>
<tbody>
<tr>
<td align="left">
1.6 – January 2020
</td>
<td align="left">
March 31, 2022
</td>
</tr>
</tbody>
<tbody>
<tr>
<td align="left">
1.4 – August 2018
</td>
<td align="left">
March 31, 2021
</td>
</tr>
</tbody>
<tbody>
<tr>
<td align="left">
1.2 – June 2018
</td>
<td align="left">
December 31, 2019
</td>
</tr>
</tbody>
<tbody>
<tr>
<td align="left">
1.1 – April 2018
</td>
<td align="left">
October 31, 2019
</td>
</tr>
</tbody>
<tbody>
<tr>
<td align="left">
1.0 – November 2017
</td>
<td align="left">
May 31, 2019
</td>
</tr>
</tbody>
</table>
<h3 id="redisjson">
RedisJSON
</h3>
<table>
<thead>
<tr>
<th>
Release Date
</th>
<th>
End-of-Life (EOL)
</th>
</tr>
</thead>
<tbody>
</tbody>
<tbody>
<tr>
<td align="left">
2.6 - July 2023
</td>
<td align="left">
-
</td>
</tr>
</tbody>
<tbody>
<tr>
<td align="left">
2.4 - November 2022
</td>
<td align="left">
July 31, 2024
</td>
</tr>
</tbody>
<tbody>
<tr>
<td align="left">
2.2 - July 2022
</td>
<td align="left">
November 30, 2023
</td>
</tr>
</tbody>
<tbody>
<tr>
<td align="left">
2.0 – November 2021
</td>
<td align="left">
July 31, 2023
</td>
</tr>
</tbody>
<tbody>
<tr>
<td align="left">
1.0 – November 2017
</td>
<td align="left">
November 30, 2022
</td>
</tr>
</tbody>
</table>
<h3 id="redisgraph">
RedisGraph
</h3>
<table>
<thead>
<tr>
<th>
Release Date
</th>
<th>
End-of-Life (EOL)
</th>
</tr>
</thead>
<tbody>
</tbody>
<tbody>
<tr>
<td align="left">
2.10 - June 2023
</td>
<td align="left">
January 31, 2025
</td>
</tr>
</tbody>
<tbody>
<tr>
<td align="left">
2.8 – February 2022
</td>
<td align="left">
January 31, 2025
</td>
</tr>
</tbody>
<tbody>
<tr>
<td align="left">
2.4 – March 2021
</td>
<td align="left">
February 28, 2023
</td>
</tr>
</tbody>
<tbody>
<tr>
<td align="left">
2.2 – November 2020
</td>
<td align="left">
May 31, 2022
</td>
</tr>
</tbody>
<tbody>
<tr>
<td align="left">
2.0 – January 2020
</td>
<td align="left">
November 30, 2021
</td>
</tr>
</tbody>
<tbody>
<tr>
<td align="left">
1.2 – April 2019
</td>
<td align="left">
December 31, 2020
</td>
</tr>
</tbody>
<tbody>
<tr>
<td align="left">
1.0 – November 2018
</td>
<td align="left">
May 31, 2020
</td>
</tr>
</tbody>
</table>
<h3 id="redistimeseries">
RedisTimeSeries
</h3>
<table>
<thead>
<tr>
<th>
Release Date
</th>
<th>
End-of-Life (EOL)
</th>
</tr>
</thead>
<tbody>
</tbody>
<tbody>
<tr>
<td align="left">
1.10 - July 2023
</td>
<td align="left">
-
</td>
</tr>
</tbody>
<tbody>
<tr>
<td align="left">
1.8 - November 2022
</td>
<td align="left">
July 31, 2024
</td>
</tr>
</tbody>
<tbody>
<tr>
<td align="left">
1.6 - January 2022
</td>
<td align="left">
November 30, 2023
</td>
</tr>
</tbody>
<tbody>
<tr>
<td align="left">
1.4 – September 2020
</td>
<td align="left">
January 31, 2023
</td>
</tr>
</tbody>
<tbody>
<tr>
<td align="left">
1.2 – January 2020
</td>
<td align="left">
September 30, 2021
</td>
</tr>
</tbody>
<tbody>
<tr>
<td align="left">
1.0 – June 2019
</td>
<td align="left">
December 31, 2020
</td>
</tr>
</tbody>
</table>
<h3 id="redisbloom">
RedisBloom
</h3>
<table>
<thead>
<tr>
<th>
Release Date
</th>
<th>
End-of-Life (EOL)
</th>
</tr>
</thead>
<tbody>
</tbody>
<tbody>
<tr>
<td align="left">
2.6 - July 2023
</td>
<td align="left">
-
</td>
</tr>
</tbody>
<tbody>
<tr>
<td align="left">
2.4 - November 2022
</td>
<td align="left">
July 31, 2024
</td>
</tr>
</tbody>
<tbody>
<tr>
<td align="left">
2.2 – December 2019
</td>
<td align="left">
November 30, 2023
</td>
</tr>
</tbody>
<tbody>
<tr>
<td align="left">
2.0 – June 2019
</td>
<td align="left">
December 31, 2020
</td>
</tr>
</tbody>
<tbody>
<tr>
<td align="left">
1.1 – February 2019
</td>
<td align="left">
August 31, 2020
</td>
</tr>
</tbody>
<tbody>
<tr>
<td align="left">
1.0 – September 2017
</td>
<td align="left">
March 31, 2019
</td>
</tr>
</tbody>
</table>
<h3 id="redisgears">
RedisGears
</h3>
<table>
<thead>
<tr>
<th>
Release Date
</th>
<th>
End-of-Life (EOL)
</th>
</tr>
</thead>
<tbody>
</tbody>
<tbody>
<tr>
<td align="left">
1.2 – February 2022
</td>
<td align="left">
-
</td>
</tr>
</tbody>
<tbody>
<tr>
<td align="left">
1.0 – May 2020
</td>
<td align="left">
February 28, 2023
</td>
</tr>
</tbody>
</table>
<form class="text-sm w-full mt-24 pt-5 border-t border-t-redis-pen-700 border-opacity-50" id="page-feedback" name="page-feedback">
<input class="hidden" name="origin" value="https://redis.io/docs/latest/operate/oss_and_stack/stack-with-enterprise/modules-lifecycle/"/>
<div class="flex flex-row justify-between">
<div class="grid justify-center">
<span class="font-mono">
RATE THIS PAGE
</span>
<div class="star-rating">
<input id="5-stars" name="rating" onchange="document.querySelector('#feedback-form').classList.remove('hidden')" type="radio" value="5"/>
<label class="star" for="5-stars">
★
</label>
<input id="4-stars" name="rating" onchange="document.querySelector('#feedback-form').classList.remove('hidden')" type="radio" value="4"/>
<label class="star" for="4-stars">
★
</label>
<input id="3-stars" name="rating" onchange="document.querySelector('#feedback-form').classList.remove('hidden')" type="radio" value="3"/>
<label class="star" for="3-stars">
★
</label>
<input id="2-stars" name="rating" onchange="document.querySelector('#feedback-form').classList.remove('hidden')" type="radio" value="2"/>
<label class="star" for="2-stars">
★
</label>
<input id="1-stars" name="rating" onchange="document.querySelector('#feedback-form').classList.remove('hidden')" type="radio" value="1"/>
<label class="star" for="1-stars">
★
</label>
</div>
</div>
<a class="font-mono no-underline" href="#">
Back to top ↑
</a>
</div>
<div class="hidden" id="feedback-form">
<div class="grid gap-2">
<textarea class="p-2 mt-1 block w-full h-24 border border-opacity-50 border-redis-ink-900 rounded-md" name="comment" placeholder="Why did you choose this rating?" rows="3"></textarea>
<button class="font-mono button text-redis-ink-900 border border-solid border-transparent bg-redis-red-500 hover:bg-redis-red-600 focus:bg-red-600 focus:ring-red-600; w-min justify-self-end" type="submit">
Submit
</button>
</div>
</div>
</form>
<script>
document.addEventListener("DOMContentLoaded", function() {
const form = document.querySelector("#page-feedback");
form.addEventListener("submit", function(event) {
event.preventDefault();
var xhr = new XMLHttpRequest();
var url = "\/docusight\/api\/rate";
var params = new URLSearchParams(new FormData(form));
xhr.open("POST", url, true);
xhr.setRequestHeader("Content-Type", "application/x-www-form-urlencoded");
xhr.onreadystatechange = function() {
if (xhr.readyState === 4 && xhr.status === 200) {
const responseData = JSON.parse(xhr.responseText);
const responseMessage = responseData.response;
const newText = document.createTextNode(responseMessage);
form.parentNode.replaceChild(newText, form);
}
};
xhr.send(params);
});
});
</script>
</section>
|
https://redis.io/docs/latest/operate/oss_and_stack/stack-with-enterprise/gears-v1/jvm/classes/readers/shardsidreader/.html | <section class="prose w-full py-12 max-w-none">
<h1>
ShardsIDReader
</h1>
<p class="text-lg -mt-5 mb-10">
Gets the shard ID for each shard in a database.
</p>
<p>
The
<code>
ShardsIDReader
</code>
creates a single record on each shard that represents the current shard's ID.
</p>
<p>
Use this reader when you want to run an operation on each shard in the database.
</p>
<h2 id="parameters">
Parameters
</h2>
<p>
None
</p>
<h2 id="output-records">
Output records
</h2>
<p>
Creates a record for each shard with the shard's cluster identifier.
</p>
<h2 id="example">
Example
</h2>
<div class="highlight">
<pre class="chroma"><code class="language-java" data-lang="java"><span class="line"><span class="cl"><span class="n">ShardsIDReader</span> <span class="n">reader</span> <span class="o">=</span> <span class="k">new</span> <span class="n">ShardsIDReader</span><span class="o">();</span>
</span></span></code></pre>
</div>
<form class="text-sm w-full mt-24 pt-5 border-t border-t-redis-pen-700 border-opacity-50" id="page-feedback" name="page-feedback">
<input class="hidden" name="origin" value="https://redis.io/docs/latest/operate/oss_and_stack/stack-with-enterprise/gears-v1/jvm/classes/readers/shardsidreader/"/>
<div class="flex flex-row justify-between">
<div class="grid justify-center">
<span class="font-mono">
RATE THIS PAGE
</span>
<div class="star-rating">
<input id="5-stars" name="rating" onchange="document.querySelector('#feedback-form').classList.remove('hidden')" type="radio" value="5"/>
<label class="star" for="5-stars">
★
</label>
<input id="4-stars" name="rating" onchange="document.querySelector('#feedback-form').classList.remove('hidden')" type="radio" value="4"/>
<label class="star" for="4-stars">
★
</label>
<input id="3-stars" name="rating" onchange="document.querySelector('#feedback-form').classList.remove('hidden')" type="radio" value="3"/>
<label class="star" for="3-stars">
★
</label>
<input id="2-stars" name="rating" onchange="document.querySelector('#feedback-form').classList.remove('hidden')" type="radio" value="2"/>
<label class="star" for="2-stars">
★
</label>
<input id="1-stars" name="rating" onchange="document.querySelector('#feedback-form').classList.remove('hidden')" type="radio" value="1"/>
<label class="star" for="1-stars">
★
</label>
</div>
</div>
<a class="font-mono no-underline" href="#">
Back to top ↑
</a>
</div>
<div class="hidden" id="feedback-form">
<div class="grid gap-2">
<textarea class="p-2 mt-1 block w-full h-24 border border-opacity-50 border-redis-ink-900 rounded-md" name="comment" placeholder="Why did you choose this rating?" rows="3"></textarea>
<button class="font-mono button text-redis-ink-900 border border-solid border-transparent bg-redis-red-500 hover:bg-redis-red-600 focus:bg-red-600 focus:ring-red-600; w-min justify-self-end" type="submit">
Submit
</button>
</div>
</div>
</form>
<script>
document.addEventListener("DOMContentLoaded", function() {
const form = document.querySelector("#page-feedback");
form.addEventListener("submit", function(event) {
event.preventDefault();
var xhr = new XMLHttpRequest();
var url = "\/docusight\/api\/rate";
var params = new URLSearchParams(new FormData(form));
xhr.open("POST", url, true);
xhr.setRequestHeader("Content-Type", "application/x-www-form-urlencoded");
xhr.onreadystatechange = function() {
if (xhr.readyState === 4 && xhr.status === 200) {
const responseData = JSON.parse(xhr.responseText);
const responseMessage = responseData.response;
const newText = document.createTextNode(responseMessage);
form.parentNode.replaceChild(newText, form);
}
};
xhr.send(params);
});
});
</script>
</section>
|
https://redis.io/docs/latest/operate/rs/7.4/clusters/configure/sync-clocks/.html | <section class="prose w-full py-12 max-w-none">
<h1>
Synchronize cluster node clocks
</h1>
<p class="text-lg -mt-5 mb-10">
Sync node clocks to avoid problems with internal custer communication.
</p>
<p>
To avoid problems with internal cluster communications that can impact your data integrity,
make sure that the clocks on all of the cluster nodes are synchronized using Chrony and/or NTP.
</p>
<p>
When you install Redis Enterprise Software,
the install script checks if Chrony or NTP is running.
If they are not, the installation process asks for permission to configure a scheduled Cron job.
This should make sure that the node's clock is always synchronized.
If you did not confirm configuring this job during the installation process,
you must use the Network Time Protocol (NTP) regularly to make sure that all server clocks are synchronized.
</p>
<p>
To synchronize the server clock, run the command that is appropriate for your operating system.
</p>
<h2 id="set-up-ntp-synchronization">
Set up NTP synchronization
</h2>
<p>
To set up NTP synchronization, see the following sections for instructions for specific operating systems.
</p>
<h3 id="ubuntu-1804-and-ubuntu-2004">
Ubuntu 18.04 and Ubuntu 20.04
</h3>
<ol>
<li>
<p>
Install Chrony, a replacement for NTP:
</p>
<div class="highlight">
<pre class="chroma"><code class="language-sh" data-lang="sh"><span class="line"><span class="cl">sudo apt install chrony
</span></span></code></pre>
</div>
</li>
<li>
<p>
Edit the Chrony configuration file:
</p>
<div class="highlight">
<pre class="chroma"><code class="language-sh" data-lang="sh"><span class="line"><span class="cl">sudo nano /etc/chrony/chrony.conf
</span></span></code></pre>
</div>
</li>
<li>
<p>
Add
<code>
server pool.ntp.org
</code>
to the file, replace
<code>
pool.ntp.org
</code>
with your own NTP server, then save.
</p>
</li>
<li>
<p>
Restart the Chrony service:
</p>
<div class="highlight">
<pre class="chroma"><code class="language-sh" data-lang="sh"><span class="line"><span class="cl">sudo systemctl restart chrony
</span></span></code></pre>
</div>
</li>
<li>
<p>
Check the Chrony service status:
</p>
<div class="highlight">
<pre class="chroma"><code class="language-sh" data-lang="sh"><span class="line"><span class="cl">sudo systemctl status chrony
</span></span></code></pre>
</div>
</li>
</ol>
<p>
For more details, refer to the official
<a href="https://ubuntu.com/server/docs/network-ntp">
Ubuntu 20.04 documentation
</a>
.
</p>
<h3 id="rhel-7">
RHEL 7
</h3>
<ol>
<li>
<p>
Install Chrony, a replacement for NTP:
</p>
<div class="highlight">
<pre class="chroma"><code class="language-sh" data-lang="sh"><span class="line"><span class="cl"> sudo yum install chrony
</span></span></code></pre>
</div>
</li>
<li>
<p>
Edit the Chrony configuration file:
</p>
<div class="highlight">
<pre class="chroma"><code class="language-sh" data-lang="sh"><span class="line"><span class="cl">sudo nano /etc/chrony.conf
</span></span></code></pre>
</div>
</li>
<li>
<p>
Add
<code>
server pool.ntp.org
</code>
to the file, replace
<code>
pool.ntp.org
</code>
with your own NTP server, then save.
</p>
</li>
<li>
<p>
Enable and start the Chrony service:
</p>
<div class="highlight">
<pre class="chroma"><code class="language-sh" data-lang="sh"><span class="line"><span class="cl">sudo systemctl <span class="nb">enable</span> chronyd <span class="o">&&</span> sudo systemctl start chronyd
</span></span></code></pre>
</div>
</li>
<li>
<p>
Check the Chrony service status:
</p>
<div class="highlight">
<pre class="chroma"><code class="language-sh" data-lang="sh"><span class="line"><span class="cl">sudo systemctl status chronyd
</span></span></code></pre>
</div>
</li>
</ol>
<p>
For more details, refer to the official
<a href="https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/system_administrators_guide/ch-configuring_ntp_using_the_chrony_suite#sect-Using_chrony">
RHEL 7 documentation
</a>
.
</p>
<h3 id="rhel-8-and-rhel-9">
RHEL 8 and RHEL 9
</h3>
<ol>
<li>
<p>
Install Chrony, a replacement for NTP:
</p>
<div class="highlight">
<pre class="chroma"><code class="language-sh" data-lang="sh"><span class="line"><span class="cl">sudo dnf install chrony
</span></span></code></pre>
</div>
</li>
<li>
<p>
Edit the Chrony configuration file:
</p>
<div class="highlight">
<pre class="chroma"><code class="language-sh" data-lang="sh"><span class="line"><span class="cl">sudo nano /etc/chrony.conf
</span></span></code></pre>
</div>
</li>
<li>
<p>
Add
<code>
server pool.ntp.org
</code>
to the file, replace
<code>
pool.ntp.org
</code>
with your own NTP server, then save.
</p>
</li>
<li>
<p>
Enable and start the Chrony service:
</p>
<div class="highlight">
<pre class="chroma"><code class="language-sh" data-lang="sh"><span class="line"><span class="cl">sudo systemctl <span class="nb">enable</span> chronyd <span class="o">&&</span> sudo systemctl start chronyd
</span></span></code></pre>
</div>
</li>
<li>
<p>
Check the Chrony service status:
</p>
<div class="highlight">
<pre class="chroma"><code class="language-sh" data-lang="sh"><span class="line"><span class="cl">sudo systemctl status chronyd
</span></span></code></pre>
</div>
</li>
</ol>
<p>
For more details, refer to the official
<a href="https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/configuring_basic_system_settings/configuring-time-synchronization_configuring-basic-system-settings">
RHEL 8 and 9 documentation
</a>
.
</p>
<h3 id="amazon-linux-2">
Amazon Linux 2
</h3>
<ol>
<li>
<p>
Install Chrony, a replacement for NTP:
</p>
<div class="highlight">
<pre class="chroma"><code class="language-sh" data-lang="sh"><span class="line"><span class="cl">sudo yum install chrony
</span></span></code></pre>
</div>
</li>
<li>
<p>
Edit the Chrony configuration file:
</p>
<div class="highlight">
<pre class="chroma"><code class="language-sh" data-lang="sh"><span class="line"><span class="cl"> sudo nano /etc/chrony.conf
</span></span></code></pre>
</div>
</li>
<li>
<p>
Add
<code>
server pool.ntp.org
</code>
to the file, replace
<code>
pool.ntp.org
</code>
with your own NTP server, then save.
</p>
</li>
<li>
<p>
Enable and start the Chrony service:
</p>
<div class="highlight">
<pre class="chroma"><code class="language-sh" data-lang="sh"><span class="line"><span class="cl">sudo systemctl <span class="nb">enable</span> chronyd <span class="o">&&</span> sudo systemctl start chronyd
</span></span></code></pre>
</div>
</li>
<li>
<p>
Check the Chrony service status:
</p>
<div class="highlight">
<pre class="chroma"><code class="language-sh" data-lang="sh"><span class="line"><span class="cl">sudo systemctl status chronyd
</span></span></code></pre>
</div>
</li>
</ol>
<p>
For more details, refer to the official
<a href="https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/set-time.html">
Amazon Linux 2 documentation
</a>
.
</p>
<p>
If you are using Active-Active databases, you must use
<a href="/docs/latest/operate/rs/7.4/databases/active-active/#network-time-service-ntp-or-chrony">
Network Time Service (ntpd)
</a>
to synchronize OS clocks consistently across clusters to handle conflict resolution according to the OS time.
</p>
<form class="text-sm w-full mt-24 pt-5 border-t border-t-redis-pen-700 border-opacity-50" id="page-feedback" name="page-feedback">
<input class="hidden" name="origin" value="https://redis.io/docs/latest/operate/rs/7.4/clusters/configure/sync-clocks/"/>
<div class="flex flex-row justify-between">
<div class="grid justify-center">
<span class="font-mono">
RATE THIS PAGE
</span>
<div class="star-rating">
<input id="5-stars" name="rating" onchange="document.querySelector('#feedback-form').classList.remove('hidden')" type="radio" value="5"/>
<label class="star" for="5-stars">
★
</label>
<input id="4-stars" name="rating" onchange="document.querySelector('#feedback-form').classList.remove('hidden')" type="radio" value="4"/>
<label class="star" for="4-stars">
★
</label>
<input id="3-stars" name="rating" onchange="document.querySelector('#feedback-form').classList.remove('hidden')" type="radio" value="3"/>
<label class="star" for="3-stars">
★
</label>
<input id="2-stars" name="rating" onchange="document.querySelector('#feedback-form').classList.remove('hidden')" type="radio" value="2"/>
<label class="star" for="2-stars">
★
</label>
<input id="1-stars" name="rating" onchange="document.querySelector('#feedback-form').classList.remove('hidden')" type="radio" value="1"/>
<label class="star" for="1-stars">
★
</label>
</div>
</div>
<a class="font-mono no-underline" href="#">
Back to top ↑
</a>
</div>
<div class="hidden" id="feedback-form">
<div class="grid gap-2">
<textarea class="p-2 mt-1 block w-full h-24 border border-opacity-50 border-redis-ink-900 rounded-md" name="comment" placeholder="Why did you choose this rating?" rows="3"></textarea>
<button class="font-mono button text-redis-ink-900 border border-solid border-transparent bg-redis-red-500 hover:bg-redis-red-600 focus:bg-red-600 focus:ring-red-600; w-min justify-self-end" type="submit">
Submit
</button>
</div>
</div>
</form>
<script>
document.addEventListener("DOMContentLoaded", function() {
const form = document.querySelector("#page-feedback");
form.addEventListener("submit", function(event) {
event.preventDefault();
var xhr = new XMLHttpRequest();
var url = "\/docusight\/api\/rate";
var params = new URLSearchParams(new FormData(form));
xhr.open("POST", url, true);
xhr.setRequestHeader("Content-Type", "application/x-www-form-urlencoded");
xhr.onreadystatechange = function() {
if (xhr.readyState === 4 && xhr.status === 200) {
const responseData = JSON.parse(xhr.responseText);
const responseMessage = responseData.response;
const newText = document.createTextNode(responseMessage);
form.parentNode.replaceChild(newText, form);
}
};
xhr.send(params);
});
});
</script>
</section>
|
https://redis.io/docs/latest/integrate/redis-data-integration/reference/data-transformation/remove_field/.html | <section class="prose w-full py-12 max-w-none">
<h1>
remove_field
</h1>
<p class="text-lg -mt-5 mb-10">
Remove fields
</p>
<p>
Remove fields
</p>
<p>
<strong>
Option 1 (alternative):
</strong>
Remove multiple fields
</p>
<p>
<strong>
Properties
</strong>
</p>
<table>
<thead>
<tr>
<th>
Name
</th>
<th>
Type
</th>
<th>
Description
</th>
<th>
Required
</th>
</tr>
</thead>
<tbody>
<tr>
<td>
<a href="#option1fields">
<strong>
fields
</strong>
</a>
</td>
<td>
<code>
object[]
</code>
</td>
<td>
Fields
<br/>
</td>
<td>
yes
</td>
</tr>
</tbody>
</table>
<p>
<strong>
Additional Properties:
</strong>
not allowed
</p>
<p>
<strong>
Example
</strong>
</p>
<div class="highlight">
<pre class="chroma"><code class="language-yaml" data-lang="yaml"><span class="line"><span class="cl"><span class="nt">source</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w"> </span><span class="nt">server_name</span><span class="p">:</span><span class="w"> </span><span class="l">redislabs</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w"> </span><span class="nt">schema</span><span class="p">:</span><span class="w"> </span><span class="l">dbo</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w"> </span><span class="nt">table</span><span class="p">:</span><span class="w"> </span><span class="l">emp</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w"></span><span class="nt">transform</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w"> </span>- <span class="nt">uses</span><span class="p">:</span><span class="w"> </span><span class="l">remove_field</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w"> </span><span class="nt">with</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w"> </span><span class="nt">fields</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w"> </span>- <span class="nt">field</span><span class="p">:</span><span class="w"> </span><span class="l">credit_card</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w"> </span>- <span class="nt">field</span><span class="p">:</span><span class="w"> </span><span class="l">name.mname</span><span class="w">
</span></span></span></code></pre>
</div>
<p>
<strong>
Option 2 (alternative):
</strong>
Remove one field
</p>
<p>
<strong>
Properties
</strong>
</p>
<table>
<thead>
<tr>
<th>
Name
</th>
<th>
Type
</th>
<th>
Description
</th>
<th>
Required
</th>
</tr>
</thead>
<tbody>
<tr>
<td>
<strong>
field
</strong>
</td>
<td>
<code>
string
</code>
</td>
<td>
Field
<br/>
</td>
<td>
yes
</td>
</tr>
</tbody>
</table>
<p>
<strong>
Additional Properties:
</strong>
not allowed
<br/>
<strong>
Example
</strong>
</p>
<div class="highlight">
<pre class="chroma"><code class="language-yaml" data-lang="yaml"><span class="line"><span class="cl"><span class="nt">source</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w"> </span><span class="nt">server_name</span><span class="p">:</span><span class="w"> </span><span class="l">redislabs</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w"> </span><span class="nt">schema</span><span class="p">:</span><span class="w"> </span><span class="l">dbo</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w"> </span><span class="nt">table</span><span class="p">:</span><span class="w"> </span><span class="l">emp</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w"></span><span class="nt">transform</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w"> </span>- <span class="nt">uses</span><span class="p">:</span><span class="w"> </span><span class="l">remove_field</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w"> </span><span class="nt">with</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w"> </span><span class="nt">field</span><span class="p">:</span><span class="w"> </span><span class="l">credit_card</span><span class="w">
</span></span></span></code></pre>
</div>
<p>
<a name="option1fields">
</a>
</p>
<h2 id="option-1-fields-array">
Option 1: fields[]: array
</h2>
<p>
Fields
</p>
<p>
<strong>
Items
</strong>
</p>
<p>
<strong>
Item Properties
</strong>
</p>
<table>
<thead>
<tr>
<th>
Name
</th>
<th>
Type
</th>
<th>
Description
</th>
<th>
Required
</th>
</tr>
</thead>
<tbody>
<tr>
<td>
<strong>
field
</strong>
</td>
<td>
<code>
string
</code>
</td>
<td>
Field
<br/>
</td>
<td>
yes
</td>
</tr>
</tbody>
</table>
<p>
<strong>
Item Additional Properties:
</strong>
not allowed
</p>
<p>
<strong>
Example
</strong>
</p>
<div class="highlight">
<pre class="chroma"><code class="language-yaml" data-lang="yaml"><span class="line"><span class="cl">- {}<span class="w">
</span></span></span></code></pre>
</div>
<form class="text-sm w-full mt-24 pt-5 border-t border-t-redis-pen-700 border-opacity-50" id="page-feedback" name="page-feedback">
<input class="hidden" name="origin" value="https://redis.io/docs/latest/integrate/redis-data-integration/reference/data-transformation/remove_field/"/>
<div class="flex flex-row justify-between">
<div class="grid justify-center">
<span class="font-mono">
RATE THIS PAGE
</span>
<div class="star-rating">
<input id="5-stars" name="rating" onchange="document.querySelector('#feedback-form').classList.remove('hidden')" type="radio" value="5"/>
<label class="star" for="5-stars">
★
</label>
<input id="4-stars" name="rating" onchange="document.querySelector('#feedback-form').classList.remove('hidden')" type="radio" value="4"/>
<label class="star" for="4-stars">
★
</label>
<input id="3-stars" name="rating" onchange="document.querySelector('#feedback-form').classList.remove('hidden')" type="radio" value="3"/>
<label class="star" for="3-stars">
★
</label>
<input id="2-stars" name="rating" onchange="document.querySelector('#feedback-form').classList.remove('hidden')" type="radio" value="2"/>
<label class="star" for="2-stars">
★
</label>
<input id="1-stars" name="rating" onchange="document.querySelector('#feedback-form').classList.remove('hidden')" type="radio" value="1"/>
<label class="star" for="1-stars">
★
</label>
</div>
</div>
<a class="font-mono no-underline" href="#">
Back to top ↑
</a>
</div>
<div class="hidden" id="feedback-form">
<div class="grid gap-2">
<textarea class="p-2 mt-1 block w-full h-24 border border-opacity-50 border-redis-ink-900 rounded-md" name="comment" placeholder="Why did you choose this rating?" rows="3"></textarea>
<button class="font-mono button text-redis-ink-900 border border-solid border-transparent bg-redis-red-500 hover:bg-redis-red-600 focus:bg-red-600 focus:ring-red-600; w-min justify-self-end" type="submit">
Submit
</button>
</div>
</div>
</form>
<script>
document.addEventListener("DOMContentLoaded", function() {
const form = document.querySelector("#page-feedback");
form.addEventListener("submit", function(event) {
event.preventDefault();
var xhr = new XMLHttpRequest();
var url = "\/docusight\/api\/rate";
var params = new URLSearchParams(new FormData(form));
xhr.open("POST", url, true);
xhr.setRequestHeader("Content-Type", "application/x-www-form-urlencoded");
xhr.onreadystatechange = function() {
if (xhr.readyState === 4 && xhr.status === 200) {
const responseData = JSON.parse(xhr.responseText);
const responseMessage = responseData.response;
const newText = document.createTextNode(responseMessage);
form.parentNode.replaceChild(newText, form);
}
};
xhr.send(params);
});
});
</script>
</section>
|
https://redis.io/docs/latest/operate/oss_and_stack/stack-with-enterprise/release-notes/redisbloom/redisbloom-1.1-release-notes/.html | <section class="prose w-full py-12 max-w-none">
<h1>
RedisBloom 1.1 release notes
</h1>
<p class="text-lg -mt-5 mb-10">
Updated version.
</p>
<h2 id="requirements">
Requirements
</h2>
<p>
RedisBloom v1.1.1 requires:
</p>
<ul>
<li>
Minimum Redis compatibility version (database): 4.0.0
</li>
<li>
Minimum Redis Enterprise Software version (cluster): 5.0.0
</li>
</ul>
<h2 id="redisbloom-111-21-february-2019">
RedisBloom 1.1.1 (21 February 2019)
</h2>
<p>
Update version to 1.1.1
</p>
<h2 id="redisbloom-110-12-february-2019">
RedisBloom 1.1.0 (12 February 2019)
</h2>
<p>
Release of 1.1.0
</p>
<form class="text-sm w-full mt-24 pt-5 border-t border-t-redis-pen-700 border-opacity-50" id="page-feedback" name="page-feedback">
<input class="hidden" name="origin" value="https://redis.io/docs/latest/operate/oss_and_stack/stack-with-enterprise/release-notes/redisbloom/redisbloom-1.1-release-notes/"/>
<div class="flex flex-row justify-between">
<div class="grid justify-center">
<span class="font-mono">
RATE THIS PAGE
</span>
<div class="star-rating">
<input id="5-stars" name="rating" onchange="document.querySelector('#feedback-form').classList.remove('hidden')" type="radio" value="5"/>
<label class="star" for="5-stars">
★
</label>
<input id="4-stars" name="rating" onchange="document.querySelector('#feedback-form').classList.remove('hidden')" type="radio" value="4"/>
<label class="star" for="4-stars">
★
</label>
<input id="3-stars" name="rating" onchange="document.querySelector('#feedback-form').classList.remove('hidden')" type="radio" value="3"/>
<label class="star" for="3-stars">
★
</label>
<input id="2-stars" name="rating" onchange="document.querySelector('#feedback-form').classList.remove('hidden')" type="radio" value="2"/>
<label class="star" for="2-stars">
★
</label>
<input id="1-stars" name="rating" onchange="document.querySelector('#feedback-form').classList.remove('hidden')" type="radio" value="1"/>
<label class="star" for="1-stars">
★
</label>
</div>
</div>
<a class="font-mono no-underline" href="#">
Back to top ↑
</a>
</div>
<div class="hidden" id="feedback-form">
<div class="grid gap-2">
<textarea class="p-2 mt-1 block w-full h-24 border border-opacity-50 border-redis-ink-900 rounded-md" name="comment" placeholder="Why did you choose this rating?" rows="3"></textarea>
<button class="font-mono button text-redis-ink-900 border border-solid border-transparent bg-redis-red-500 hover:bg-redis-red-600 focus:bg-red-600 focus:ring-red-600; w-min justify-self-end" type="submit">
Submit
</button>
</div>
</div>
</form>
<script>
document.addEventListener("DOMContentLoaded", function() {
const form = document.querySelector("#page-feedback");
form.addEventListener("submit", function(event) {
event.preventDefault();
var xhr = new XMLHttpRequest();
var url = "\/docusight\/api\/rate";
var params = new URLSearchParams(new FormData(form));
xhr.open("POST", url, true);
xhr.setRequestHeader("Content-Type", "application/x-www-form-urlencoded");
xhr.onreadystatechange = function() {
if (xhr.readyState === 4 && xhr.status === 200) {
const responseData = JSON.parse(xhr.responseText);
const responseMessage = responseData.response;
const newText = document.createTextNode(responseMessage);
form.parentNode.replaceChild(newText, form);
}
};
xhr.send(params);
});
});
</script>
</section>
|
https://redis.io/docs/latest/commands/decr/.html | <section class="prose w-full py-12">
<h1 class="command-name">
DECR
</h1>
<div class="font-semibold text-redis-ink-900">
Syntax
</div>
<pre class="command-syntax">DECR key</pre>
<dl class="grid grid-cols-[auto,1fr] gap-2 mb-12">
<dt class="font-semibold text-redis-ink-900 m-0">
Available since:
</dt>
<dd class="m-0">
1.0.0
</dd>
<dt class="font-semibold text-redis-ink-900 m-0">
Time complexity:
</dt>
<dd class="m-0">
O(1)
</dd>
<dt class="font-semibold text-redis-ink-900 m-0">
ACL categories:
</dt>
<dd class="m-0">
<code>
@write
</code>
<span class="mr-1 last:hidden">
,
</span>
<code>
@string
</code>
<span class="mr-1 last:hidden">
,
</span>
<code>
@fast
</code>
<span class="mr-1 last:hidden">
,
</span>
</dd>
</dl>
<p>
Decrements the number stored at
<code>
key
</code>
by one.
If the key does not exist, it is set to
<code>
0
</code>
before performing the operation.
An error is returned if the key contains a value of the wrong type or contains a
string that can not be represented as integer.
This operation is limited to
<strong>
64 bit signed integers
</strong>
.
</p>
<p>
See
<a href="/docs/latest/commands/incr/">
<code>
INCR
</code>
</a>
for extra information on increment/decrement operations.
</p>
<h2 id="examples">
Examples
</h2>
<div class="bg-slate-900 border-b border-slate-700 rounded-t-xl px-4 py-3 w-full flex">
<svg class="shrink-0 h-[1.0625rem] w-[1.0625rem] fill-slate-50" fill="currentColor" viewbox="0 0 20 20">
<path d="M2.5 10C2.5 5.85786 5.85786 2.5 10 2.5C14.1421 2.5 17.5 5.85786 17.5 10C17.5 14.1421 14.1421 17.5 10 17.5C5.85786 17.5 2.5 14.1421 2.5 10Z">
</path>
</svg>
<svg class="shrink-0 h-[1.0625rem] w-[1.0625rem] fill-slate-50" fill="currentColor" viewbox="0 0 20 20">
<path d="M10 2.5L18.6603 17.5L1.33975 17.5L10 2.5Z">
</path>
</svg>
<svg class="shrink-0 h-[1.0625rem] w-[1.0625rem] fill-slate-50" fill="currentColor" viewbox="0 0 20 20">
<path d="M10 2.5L12.0776 7.9322L17.886 8.22949L13.3617 11.8841L14.8738 17.5L10 14.3264L5.1262 17.5L6.63834 11.8841L2.11403 8.22949L7.92238 7.9322L10 2.5Z">
</path>
</svg>
</div>
<form class="redis-cli overflow-y-auto max-h-80">
<pre tabindex="0">redis> SET mykey "10"
"OK"
redis> DECR mykey
(integer) 9
redis> SET mykey "234293482390480948029348230948"
"OK"
redis> DECR mykey
(error) value is not an integer or out of range
</pre>
<div class="prompt" style="">
<span>
redis>
</span>
<input autocomplete="off" name="prompt" spellcheck="false" type="text"/>
</div>
</form>
<h2 id="resp2resp3-reply">
RESP2/RESP3 Reply
</h2>
<a href="../../develop/reference/protocol-spec#integers">
Integer reply
</a>
: the value of the key after decrementing it.
<br/>
<form class="text-sm w-full mt-24 pt-5 border-t border-t-redis-pen-700 border-opacity-50" id="page-feedback" name="page-feedback">
<input class="hidden" name="origin" value="https://redis.io/docs/latest/commands/decr/"/>
<div class="flex flex-row justify-between">
<div class="grid justify-center">
<span class="font-mono">
RATE THIS PAGE
</span>
<div class="star-rating">
<input id="5-stars" name="rating" onchange="document.querySelector('#feedback-form').classList.remove('hidden')" type="radio" value="5"/>
<label class="star" for="5-stars">
★
</label>
<input id="4-stars" name="rating" onchange="document.querySelector('#feedback-form').classList.remove('hidden')" type="radio" value="4"/>
<label class="star" for="4-stars">
★
</label>
<input id="3-stars" name="rating" onchange="document.querySelector('#feedback-form').classList.remove('hidden')" type="radio" value="3"/>
<label class="star" for="3-stars">
★
</label>
<input id="2-stars" name="rating" onchange="document.querySelector('#feedback-form').classList.remove('hidden')" type="radio" value="2"/>
<label class="star" for="2-stars">
★
</label>
<input id="1-stars" name="rating" onchange="document.querySelector('#feedback-form').classList.remove('hidden')" type="radio" value="1"/>
<label class="star" for="1-stars">
★
</label>
</div>
</div>
<a class="font-mono no-underline" href="#">
Back to top ↑
</a>
</div>
<div class="hidden" id="feedback-form">
<div class="grid gap-2">
<textarea class="p-2 mt-1 block w-full h-24 border border-opacity-50 border-redis-ink-900 rounded-md" name="comment" placeholder="Why did you choose this rating?" rows="3"></textarea>
<button class="font-mono button text-redis-ink-900 border border-solid border-transparent bg-redis-red-500 hover:bg-redis-red-600 focus:bg-red-600 focus:ring-red-600; w-min justify-self-end" type="submit">
Submit
</button>
</div>
</div>
</form>
<script>
document.addEventListener("DOMContentLoaded", function() {
const form = document.querySelector("#page-feedback");
form.addEventListener("submit", function(event) {
event.preventDefault();
var xhr = new XMLHttpRequest();
var url = "\/docusight\/api\/rate";
var params = new URLSearchParams(new FormData(form));
xhr.open("POST", url, true);
xhr.setRequestHeader("Content-Type", "application/x-www-form-urlencoded");
xhr.onreadystatechange = function() {
if (xhr.readyState === 4 && xhr.status === 200) {
const responseData = JSON.parse(xhr.responseText);
const responseMessage = responseData.response;
const newText = document.createTextNode(responseMessage);
form.parentNode.replaceChild(newText, form);
}
};
xhr.send(params);
});
});
</script>
</section>
|
https://redis.io/docs/latest/commands/groupcf.html | <section class="prose w-full py-12">
<h1>
Commands
</h1>
</section>
|
https://redis.io/docs/latest/operate/rc/databases/view-edit-database/.html | <section class="prose w-full py-12 max-w-none">
<h1>
View and edit databases
</h1>
<p>
Use the
<strong>
Databases
</strong>
menu of the Redis Cloud console to manage your databases.
</p>
<p>
To view the details of a database:
</p>
<ol>
<li>
<p>
Sign in to the
<a href="https://cloud.redis.io/">
Redis Cloud console
</a>
. (Create an account if you don't already have one.)
</p>
</li>
<li>
<p>
Select the
<strong>
Databases
</strong>
menu to display a searchable list of all databases.
</p>
</li>
<li>
<p>
Locate the database in the list.
</p>
</li>
<li>
<p>
Select the database name to open the
<strong>
Database
</strong>
page.
</p>
<a href="/docs/latest/images/rc/database-details-configuration-tab-general-flexible.png" sdata-lightbox="/images/rc/database-details-configuration-tab-general-flexible.png">
<img alt="The Configuration tab of the Database details screen." src="/docs/latest/images/rc/database-details-configuration-tab-general-flexible.png"/>
</a>
</li>
</ol>
<p>
The
<strong>
Database
</strong>
screen lets you review:
</p>
<ul>
<li>
Configuration details of a database
</li>
<li>
Graphs showing performance metrics
</li>
<li>
Recent activity via a "[slowlog](/docs/latest/commands/slowlog/," which lists queries that exceed a certain execution time.
</li>
</ul>
<p>
For help changing database settings, see
<a href="#edit-database-details">
Edit database details
</a>
.
</p>
<h2 id="configuration-tab">
Configuration tab
</h2>
<p>
The
<strong>
Configuration
</strong>
screen is divided into sections, each dedicated to a specific category. Note that not every section or setting is available to every
<a href="/docs/latest/operate/rc/subscriptions/">
subscription plan
</a>
.
</p>
<h3 id="general-settings">
General settings
</h3>
<p>
The
<strong>
General
</strong>
section defines basic properties about your database.
</p>
<p>
The available settings vary according to your plan, cloud provider, and design choices. For example, if you do not select an Advanced Capability when creating a database, the
<strong>
Advanced Capabilities
</strong>
setting is not displayed when you view its configuration details.
</p>
<table>
<thead>
<tr>
<th style="text-align:left">
Setting name
</th>
<th style="text-align:left">
Description
</th>
</tr>
</thead>
<tbody>
<tr>
<td style="text-align:left">
<strong>
Database Name
</strong>
</td>
<td style="text-align:left">
The name given to your database
</td>
</tr>
<tr>
<td style="text-align:left">
<strong>
Public endpoint
</strong>
</td>
<td style="text-align:left">
Public URI used by any application or client to access the database.
</td>
</tr>
<tr>
<td style="text-align:left">
<strong>
Private endpoint
</strong>
</td>
<td style="text-align:left">
Private endpoint URI available to approved clients; use CIDR allow list and VPC peering to enable access (
<em>
Redis Cloud Pro only
</em>
)
</td>
</tr>
<tr>
<td style="text-align:left">
<strong>
Tags
</strong>
</td>
<td style="text-align:left">
A list of the
<a href="/docs/latest/operate/rc/databases/tag-database/">
tags
</a>
associated with the database. Select
<a href="/docs/latest/operate/rc/databases/tag-database/#configuration-tab">
Manage tags
</a>
to manage the database tags.
</td>
</tr>
<tr>
<td style="text-align:left">
<strong>
Type
</strong>
</td>
<td style="text-align:left">
Displays 'Redis', 'Redis Stack' or 'memcached' based on the value selected when the database was created
</td>
</tr>
<tr>
<td style="text-align:left">
<strong>
Redis version
</strong>
</td>
<td style="text-align:left">
Redis version used to create the database
</td>
</tr>
<tr>
<td style="text-align:left">
<strong>
Auto Tiering
</strong>
</td>
<td style="text-align:left">
Checked when the subscription supports Auto Tiering (
<em>
Redis Cloud Pro only
</em>
)
</td>
</tr>
<tr>
<td style="text-align:left">
<strong>
Creation time
</strong>
</td>
<td style="text-align:left">
Date and time the database was created
</td>
</tr>
<tr>
<td style="text-align:left">
<strong>
Active-Active Redis
</strong>
</td>
<td style="text-align:left">
Checked when the database is part of an
<a href="/docs/latest/operate/rc/databases/configuration/active-active-redis/">
Active-Active
</a>
relationship (
<em>
Redis Cloud Pro only
</em>
)
</td>
</tr>
<tr>
<td style="text-align:left">
<strong>
Last changed
</strong>
</td>
<td style="text-align:left">
Date and time of last update
</td>
</tr>
<tr>
<td style="text-align:left">
<strong>
Supported Protocol(s)
</strong>
</td>
<td style="text-align:left">
Shows which version of RESP the database uses. See
<a href="/docs/latest/develop/reference/protocol-spec/#resp-versions">
Redis serialization protocol
</a>
for details
</td>
</tr>
<tr>
<td style="text-align:left">
<strong>
Advanced Capabilites
</strong>
</td>
<td style="text-align:left">
This setting appears when an
<a href="/docs/latest/operate/rc/databases/configuration/advanced-capabilities/">
advanced capability
</a>
is enabled for a database
</td>
</tr>
</tbody>
</table>
<h3 id="scalability-section">
Scalability section
</h3>
<p>
The
<strong>
Scalability
</strong>
section describes the memory size, throughput, and hashing policy for a database.
</p>
<a href="/docs/latest/images/rc/database-details-configuration-tab-scalability-flexible.png" sdata-lightbox="/images/rc/database-details-configuration-tab-scalability-flexible.png">
<img alt="Use the Scalability section to control the size, throughput, and hashing policy for a database." src="/docs/latest/images/rc/database-details-configuration-tab-scalability-flexible.png"/>
</a>
<p>
The
<strong>
Scalability
</strong>
section is primarily for Redis Cloud Pro plans. Redis Cloud Essentials plans have options for memory limit and memory used.
</p>
<table>
<thead>
<tr>
<th style="text-align:left">
Setting name
</th>
<th style="text-align:left">
Description
</th>
</tr>
</thead>
<tbody>
<tr>
<td style="text-align:left">
<strong>
Dataset size
</strong>
</td>
<td style="text-align:left">
Maximum size (in GB) for your dataset.
</td>
</tr>
<tr>
<td style="text-align:left">
<strong>
Memory used
</strong>
</td>
<td style="text-align:left">
Memory currently used for your database.
</td>
</tr>
<tr>
<td style="text-align:left">
<strong>
Throughput
</strong>
</td>
<td style="text-align:left">
Defines throughput in terms of maximum operations per second for the database
</td>
</tr>
<tr>
<td style="text-align:left">
<strong>
High availability
</strong>
</td>
<td style="text-align:left">
Replicates your data across multiple nodes;
<a href="/docs/latest/operate/rc/databases/configuration/high-availability/">
available options
</a>
depend on your plan type
</td>
</tr>
<tr>
<td style="text-align:left">
<strong>
Hashing policy
</strong>
</td>
<td style="text-align:left">
Defines the
<a href="/docs/latest/operate/rc/databases/configuration/clustering/#manage-the-hashing-policy">
hashing policy
</a>
.
</td>
</tr>
<tr>
<td style="text-align:left">
<strong>
OSS Cluster API
</strong>
</td>
<td style="text-align:left">
Enables the
<a href="/docs/latest/operate/rc/databases/create-database/#oss-cluster-api">
Cluster API
</a>
for a database.
<br/>
<br/>
When this option is enabled, you cannot define a custom hashing policy.
</td>
</tr>
</tbody>
</table>
<p>
To learn more about these settings and when to use them, see
<a href="/docs/latest/operate/rc/databases/configuration/clustering/">
Database clustering
</a>
.
</p>
<h3 id="durability-section">
Durability section
</h3>
<p>
The Durability section helps protect your data when problems occur. These settings define replication, persistence, backup, and eviction policies.
</p>
<a href="/docs/latest/images/rc/database-details-configuration-tab-durability-flexible.png" sdata-lightbox="/images/rc/database-details-configuration-tab-durability-flexible.png">
<img alt="Use the Durability section to protect your data from unexpected problems." src="/docs/latest/images/rc/database-details-configuration-tab-durability-flexible.png"/>
</a>
<table>
<thead>
<tr>
<th style="text-align:left">
Setting name
</th>
<th style="text-align:left">
Description
</th>
</tr>
</thead>
<tbody>
<tr>
<td style="text-align:left">
<strong>
Data persistence
</strong>
</td>
<td style="text-align:left">
Defines whether (and how) data is saved to disk;
<a href="/docs/latest/operate/rc/databases/configuration/data-persistence/">
available options
</a>
depend on your plan type
</td>
</tr>
<tr>
<td style="text-align:left">
<strong>
Data eviction policy
</strong>
</td>
<td style="text-align:left">
Configures which
<a href="/docs/latest/operate/rc/databases/configuration/data-eviction-policies/">
policy
</a>
is applied when your database reaches its memory limit
</td>
</tr>
<tr>
<td style="text-align:left">
<strong>
Remote backup
</strong>
</td>
<td style="text-align:left">
When enabled, identifies a location and interval for
<a href="/docs/latest/operate/rc/databases/back-up-data/">
data backups
</a>
. (
<em>
Paid plans only
</em>
)
</td>
</tr>
<tr>
<td style="text-align:left">
<strong>
Active-Passive Redis
</strong>
</td>
<td style="text-align:left">
When enabled, identifies a path to the
<a href="/docs/latest/operate/rc/databases/migrate-databases/#sync-using-active-passive">
linked database
</a>
. (
<em>
Redis Cloud Pro only
</em>
)
</td>
</tr>
</tbody>
</table>
<h3 id="security-section">
Security section
</h3>
<p>
The
<strong>
Security
</strong>
section helps you control access to your database.
</p>
<a href="/docs/latest/images/rc/database-details-configuration-tab-security-flexible.png" sdata-lightbox="/images/rc/database-details-configuration-tab-security-flexible.png">
<img alt="Use the Security settings to control access to your database." src="/docs/latest/images/rc/database-details-configuration-tab-security-flexible.png"/>
</a>
<table>
<thead>
<tr>
<th style="text-align:left">
Setting name
</th>
<th style="text-align:left">
Description
</th>
</tr>
</thead>
<tbody>
<tr>
<td style="text-align:left">
<strong>
Default user
</strong>
</td>
<td style="text-align:left">
When enabled, permits access using a simple password
</td>
</tr>
<tr>
<td style="text-align:left">
<strong>
Default user password
</strong>
</td>
<td style="text-align:left">
Password for default user. A default password is assigned to the database on creation and may be updated.
</td>
</tr>
<tr>
<td style="text-align:left">
<strong>
CIDR allow list
</strong>
</td>
<td style="text-align:left">
<a href="/docs/latest/operate/rc/security/cidr-whitelist/">
Allow list
</a>
of IP addresses/security groups permitted to access the database. (
<em>
Paid plans only
</em>
)
</td>
</tr>
<tr>
<td style="text-align:left">
<strong>
Transport layer security (TLS)
</strong>
</td>
<td style="text-align:left">
Enables
<a href="/docs/latest/operate/rc/security/database-security/tls-ssl/">
transport layer security
</a>
(TLS) encryption for database access. (
<em>
Pro plans only
</em>
)
</td>
</tr>
</tbody>
</table>
<h3 id="alerts-section">
Alerts section
</h3>
<p>
The
<strong>
Alerts
</strong>
section defines notification emails sent to your account and the conditions that trigger them.
</p>
<a href="/docs/latest/images/rc/database-details-configuration-tab-alerts-flexible.png" sdata-lightbox="/images/rc/database-details-configuration-tab-alerts-flexible.png">
<img alt="The Alerts section defines the notification emails and their triggering conditions." src="/docs/latest/images/rc/database-details-configuration-tab-alerts-flexible.png"/>
</a>
<p>
The available alerts vary according to the plan type.
</p>
<table>
<thead>
<tr>
<th style="text-align:left">
Setting name
</th>
<th style="text-align:left">
Description
</th>
</tr>
</thead>
<tbody>
<tr>
<td style="text-align:left">
<strong>
Dataset size has reached
</strong>
</td>
<td style="text-align:left">
When enabled, sends an an email when the database reaches the defined memory limit (
<em>
Free Essentials or Pro only
</em>
)
</td>
</tr>
<tr>
<td style="text-align:left">
<strong>
Total size of datasets under this plan reached
</strong>
</td>
<td style="text-align:left">
When enabled, sends an an email when the database reaches the defined memory limit (
<em>
Paid Essentials plans only
</em>
)
</td>
</tr>
<tr>
<td style="text-align:left">
<strong>
Throughput is higher than
</strong>
</td>
<td style="text-align:left">
When enabled, sends an email when the operations per second exceed the defined threshold (
<em>
Paid Essentials or Pro plans only
</em>
)
</td>
</tr>
<tr>
<td style="text-align:left">
<strong>
Throughput is lower than
</strong>
</td>
<td style="text-align:left">
When enabled, sends an email when the operations per second falls below the defined threshold (
<em>
Paid Essentials or Pro plans only
</em>
)
</td>
</tr>
<tr>
<td style="text-align:left">
<strong>
Latency is higher than
</strong>
</td>
<td style="text-align:left">
When enabled, sends an an email when the latency exceeds the defined limit (
<em>
Paid Essentials plans only
</em>
)
</td>
</tr>
<tr>
<td style="text-align:left">
<strong>
Number of connections
</strong>
</td>
<td style="text-align:left">
When enabled, sends an email when the connections exceeds the defined limit. (
<em>
Essentials plans only
</em>
)
</td>
</tr>
<tr>
<td style="text-align:left">
<strong>
Replica Of - database unable to sync with source
</strong>
</td>
<td style="text-align:left">
When enabled, sends email when the replica database cannot sync with the primary (source) database (
<em>
Pro plans only
</em>
)
</td>
</tr>
<tr>
<td style="text-align:left">
<strong>
Replica Of - sync lag is higher than
</strong>
</td>
<td style="text-align:left">
When enabled, sends email when the sync lag exceeds the defined threshold (
<em>
Pro plans only
</em>
)
</td>
</tr>
</tbody>
</table>
<h3 id="danger-zone">
Danger zone
</h3>
<p>
Actions in the
<strong>
Danger Zone
</strong>
are permanent and should not be taken lightly.
</p>
<a href="/docs/latest/images/rc/database-details-configuration-tab-danger-flexible.png" sdata-lightbox="/images/rc/database-details-configuration-tab-danger-flexible.png">
<img alt="The Danger Zone includes activities that impact data, such as deleting a database. Use with care." src="/docs/latest/images/rc/database-details-configuration-tab-danger-flexible.png"/>
</a>
<p>
Here, you can:
</p>
<ul>
<li>
<p>
Delete the database.
</p>
<p>
Databases must be active and empty before they can be deleted. To learn more, see
<a href="/docs/latest/operate/rc/databases/delete-database/">
Delete a database
</a>
.
</p>
</li>
<li>
<p>
Import data into the database.
</p>
<p>
When you choose this action, you're asked to specify the source and location of the data to import
</p>
<a href="/docs/latest/images/rc/database-import-dialog.png" sdata-lightbox="/images/rc/database-import-dialog.png">
<img alt="The Import data dialog helps you import data into a database." src="/docs/latest/images/rc/database-import-dialog.png"/>
</a>
<p>
To learn more, see
<a href="/docs/latest/operate/rc/databases/import-data/">
Import data
</a>
.
</p>
</li>
</ul>
<p>
For best results, we recommend backing up data before starting any
<strong>
Danger Zone
</strong>
actions.
</p>
<h2 id="manage-the-database-list">
Manage the database list
</h2>
<p>
The
<strong>
Databases
</strong>
list summarizes the status of all databases associated with your account.
</p>
<p>
You can:
</p>
<ul>
<li>
<p>
Search by typing into the search box located above the database list.
</p>
<a href="/docs/latest/images/rc/database-list-search.png" sdata-lightbox="/images/rc/database-list-search.png">
<img alt="Use the search bar to filter the list." src="/docs/latest/images/rc/database-list-search.png"/>
</a>
</li>
<li>
<p>
Filter by selecting a filter type and then selecting the checkbox next to the options you want to include from the dropdown. Select the Filter toggle, located on the right of the search bar, if the filter types are hidden.
</p>
<a href="/docs/latest/images/rc/database-list-filter.png" sdata-lightbox="/images/rc/database-list-filter.png">
<img alt="Use the filter toggle to display filter options." src="/docs/latest/images/rc/database-list-filter.png"/>
</a>
<p>
You can filter the list on
<strong>
Status
</strong>
,
<strong>
Subscription
</strong>
,
<strong>
Capabilities
</strong>
,
<strong>
Options
</strong>
, and
<strong>
Tags
</strong>
. String matches are
<em>
not
</em>
case-sensitive. You can specify more than one filter expression at a time.
</p>
<p>
A list of selected filters appears below the filter types.
</p>
<p>
To remove a filter click the
<strong>
x
</strong>
to the right of the name of that filter. To remove all filters, select
<strong>
Clear all
</strong>
.
</p>
<a href="/docs/latest/images/rc/database-list-filter-selected.png" sdata-lightbox="/images/rc/database-list-filter-selected.png">
<img alt="Use the filter toggle to display filter options." src="/docs/latest/images/rc/database-list-filter-selected.png"/>
</a>
</li>
<li>
<p>
Sort the list in descending or ascending order using the arrow displayed to right of the field name in the header. Supported fields include
<strong>
Subscription
</strong>
,
<strong>
Database name
</strong>
,
<strong>
Memory
</strong>
, and
<strong>
Tags
</strong>
.
</p>
<p>
<a href="/docs/latest/images/rc/icon-database-list-sort-ascending.png" sdata-lightbox="/images/rc/icon-database-list-sort-ascending.png">
<img alt="Use the arrows in the list header to sort the list." src="/docs/latest/images/rc/icon-database-list-sort-ascending.png"/>
</a>
<a href="/docs/latest/images/rc/icon-database-list-sort-descending.png" sdata-lightbox="/images/rc/icon-database-list-sort-descending.png">
<img alt="The direction of the arrow corresponds to the direction of the sort." src="/docs/latest/images/rc/icon-database-list-sort-descending.png"/>
</a>
</p>
<p>
Select the arrow icon to change the sort order. One sort order can be active at any given time.
</p>
</li>
<li>
<p>
Use the controls in the list footer to change the number of items displayed in the list or to navigate.
</p>
</li>
</ul>
<p>
Sort orders and filter expressions are not saved between console sessions.
</p>
<h2 id="other-actions-and-info">
Other actions and info
</h2>
<p>
The
<strong>
View Database
</strong>
screen also has tabs that let you view:
</p>
<ul>
<li>
<p>
<strong>
Metrics
</strong>
: a series of graphs showing database performance over time. See
<a href="/docs/latest/operate/rc/databases/monitor-performance/">
Monitor performance
</a>
</p>
</li>
<li>
<p>
<strong>
Slowlog
</strong>
: a log showing recent
<a href="/docs/latest/commands/slowlog/">
slow queries
</a>
run against your database. The log displays when the action started, the duration, the complexity of the operation, and any parameters passed to the operation.
</p>
</li>
</ul>
<h2 id="edit-database-details">
Edit database details
</h2>
<p>
Use the
<strong>
Edit database
</strong>
button to edit database details.
</p>
<a href="/docs/latest/images/rc/button-database-edit.png" sdata-lightbox="/images/rc/button-database-edit.png">
<img alt="The Edit database button lets you change selected database properties." src="/docs/latest/images/rc/button-database-edit.png"/>
</a>
<p>
Because databases exist within the context of a deployment, certain fields cannot be updated, especially those that might lead to data loss.
</p>
<p>
Here's what you can change:
</p>
<table>
<thead>
<tr>
<th style="text-align:left">
Section
</th>
<th style="text-align:left">
Setting
</th>
<th style="text-align:left">
Comments
</th>
</tr>
</thead>
<tbody>
<tr>
<td style="text-align:left">
General
</td>
<td style="text-align:left">
Database name
</td>
<td>
</td>
</tr>
<tr>
<td style="text-align:left">
</td>
<td style="text-align:left">
Supported protocol(s)
</td>
<td>
</td>
</tr>
<tr>
<td style="text-align:left">
</td>
<td style="text-align:left">
Tags
</td>
<td>
</td>
</tr>
<tr>
<td style="text-align:left">
Scalability
</td>
<td style="text-align:left">
Memory limit
</td>
<td style="text-align:left">
</td>
</tr>
<tr>
<td style="text-align:left">
</td>
<td style="text-align:left">
Throughput
</td>
<td style="text-align:left">
<em>
Pro plans only
</em>
</td>
</tr>
<tr>
<td style="text-align:left">
</td>
<td style="text-align:left">
Hashing policy
</td>
<td style="text-align:left">
<em>
Pro plans only
</em>
</td>
</tr>
<tr>
<td style="text-align:left">
</td>
<td style="text-align:left">
OSS Cluster API
</td>
<td style="text-align:left">
<em>
Pro plans only
</em>
</td>
</tr>
<tr>
<td style="text-align:left">
Durability
</td>
<td style="text-align:left">
High-availability
</td>
<td style="text-align:left">
<em>
Paid plans only
</em>
</td>
</tr>
<tr>
<td style="text-align:left">
</td>
<td style="text-align:left">
Data persistence
</td>
<td style="text-align:left">
<em>
Paid plans only
</em>
</td>
</tr>
<tr>
<td style="text-align:left">
</td>
<td style="text-align:left">
Data eviction policy
</td>
<td style="text-align:left">
</td>
</tr>
<tr>
<td style="text-align:left">
</td>
<td style="text-align:left">
Remote backup
</td>
<td style="text-align:left">
<em>
Paid plans only
</em>
</td>
</tr>
<tr>
<td style="text-align:left">
</td>
<td style="text-align:left">
Active-Passive Redis
</td>
<td style="text-align:left">
<em>
Pro plans only
</em>
</td>
</tr>
<tr>
<td style="text-align:left">
Security
</td>
<td style="text-align:left">
Default user
</td>
<td style="text-align:left">
</td>
</tr>
<tr>
<td style="text-align:left">
</td>
<td style="text-align:left">
Default user password
</td>
<td>
</td>
</tr>
<tr>
<td style="text-align:left">
</td>
<td style="text-align:left">
CIDR allow list
</td>
<td style="text-align:left">
<em>
Paid plans only
</em>
</td>
</tr>
<tr>
<td style="text-align:left">
</td>
<td style="text-align:left">
Transport layer security (TLS)
</td>
<td style="text-align:left">
<em>
Pro plans only
</em>
</td>
</tr>
<tr>
<td style="text-align:left">
Alerts
</td>
<td style="text-align:left">
all available for plan type
</td>
<td>
</td>
</tr>
</tbody>
</table>
<p>
Choose
<strong>
Save database
</strong>
to save your changes.
</p>
<a href="/docs/latest/images/rc/button-database-save.png" sdata-lightbox="/images/rc/button-database-save.png">
<img alt="Use the Save database button to save database changes." src="/docs/latest/images/rc/button-database-save.png"/>
</a>
<p>
If you need to change other details, create a new database and then migrate existing data.
</p>
<form class="text-sm w-full mt-24 pt-5 border-t border-t-redis-pen-700 border-opacity-50" id="page-feedback" name="page-feedback">
<input class="hidden" name="origin" value="https://redis.io/docs/latest/operate/rc/databases/view-edit-database/"/>
<div class="flex flex-row justify-between">
<div class="grid justify-center">
<span class="font-mono">
RATE THIS PAGE
</span>
<div class="star-rating">
<input id="5-stars" name="rating" onchange="document.querySelector('#feedback-form').classList.remove('hidden')" type="radio" value="5"/>
<label class="star" for="5-stars">
★
</label>
<input id="4-stars" name="rating" onchange="document.querySelector('#feedback-form').classList.remove('hidden')" type="radio" value="4"/>
<label class="star" for="4-stars">
★
</label>
<input id="3-stars" name="rating" onchange="document.querySelector('#feedback-form').classList.remove('hidden')" type="radio" value="3"/>
<label class="star" for="3-stars">
★
</label>
<input id="2-stars" name="rating" onchange="document.querySelector('#feedback-form').classList.remove('hidden')" type="radio" value="2"/>
<label class="star" for="2-stars">
★
</label>
<input id="1-stars" name="rating" onchange="document.querySelector('#feedback-form').classList.remove('hidden')" type="radio" value="1"/>
<label class="star" for="1-stars">
★
</label>
</div>
</div>
<a class="font-mono no-underline" href="#">
Back to top ↑
</a>
</div>
<div class="hidden" id="feedback-form">
<div class="grid gap-2">
<textarea class="p-2 mt-1 block w-full h-24 border border-opacity-50 border-redis-ink-900 rounded-md" name="comment" placeholder="Why did you choose this rating?" rows="3"></textarea>
<button class="font-mono button text-redis-ink-900 border border-solid border-transparent bg-redis-red-500 hover:bg-redis-red-600 focus:bg-red-600 focus:ring-red-600; w-min justify-self-end" type="submit">
Submit
</button>
</div>
</div>
</form>
<script>
document.addEventListener("DOMContentLoaded", function() {
const form = document.querySelector("#page-feedback");
form.addEventListener("submit", function(event) {
event.preventDefault();
var xhr = new XMLHttpRequest();
var url = "\/docusight\/api\/rate";
var params = new URLSearchParams(new FormData(form));
xhr.open("POST", url, true);
xhr.setRequestHeader("Content-Type", "application/x-www-form-urlencoded");
xhr.onreadystatechange = function() {
if (xhr.readyState === 4 && xhr.status === 200) {
const responseData = JSON.parse(xhr.responseText);
const responseMessage = responseData.response;
const newText = document.createTextNode(responseMessage);
form.parentNode.replaceChild(newText, form);
}
};
xhr.send(params);
});
});
</script>
</section>
|
https://redis.io/docs/latest/operate/rs/7.4/security/access-control/create-cluster-roles/.html | <section class="prose w-full py-12 max-w-none">
<h1>
Create roles with cluster access only
</h1>
<p class="text-lg -mt-5 mb-10">
Create roles with cluster access only.
</p>
<p>
Roles with cluster access allow access to the Cluster Management UI and REST API.
</p>
<h2 id="default-management-roles">
Default management roles
</h2>
<p>
Redis Enterprise Software includes five predefined roles that determine a user's level of access to the Cluster Manager UI and
<a href="/docs/latest/operate/rs/7.4/references/rest-api/">
REST API
</a>
.
</p>
<ol>
<li>
<strong>
DB Viewer
</strong>
- Read database settings
</li>
<li>
<strong>
DB Member
</strong>
- Administer databases
</li>
<li>
<strong>
Cluster Viewer
</strong>
- Read cluster settings
</li>
<li>
<strong>
Cluster Member
</strong>
- Administer the cluster
</li>
<li>
<strong>
Admin
</strong>
- Full cluster access
</li>
<li>
<strong>
None
</strong>
- For data access only - cannot access the Cluster Manager UI or use the REST API
</li>
</ol>
<p>
For more details about the privileges granted by each of these roles, see
<a href="#cluster-manager-ui-permissions">
Cluster Manager UI permissions
</a>
or
<a href="/docs/latest/operate/rs/7.4/references/rest-api/permissions/">
REST API permissions
</a>
.
</p>
<h2 id="cluster-manager-ui-permissions">
Cluster Manager UI permissions
</h2>
<p>
Here's a summary of the Cluster Manager UI actions permitted by each default management role:
</p>
<table>
<thead>
<tr>
<th>
Action
</th>
<th style="text-align:center">
DB Viewer
</th>
<th style="text-align:center">
DB Member
</th>
<th style="text-align:center">
Cluster Viewer
</th>
<th style="text-align:center">
Cluster Member
</th>
<th style="text-align:center">
Admin
</th>
</tr>
</thead>
<tbody>
<tr>
<td>
Create support package
</td>
<td style="text-align:center">
<span title="Not allowed">
❌ No
</span>
</td>
<td style="text-align:center">
<span title="Allowed">
✅ Yes
</span>
</td>
<td style="text-align:center">
<span title="Not allowed">
❌ No
</span>
</td>
<td style="text-align:center">
<span title="Allowed">
✅ Yes
</span>
</td>
<td style="text-align:center">
<span title="Allowed">
✅ Yes
</span>
</td>
</tr>
<tr>
<td>
Edit database configuration
</td>
<td style="text-align:center">
<span title="Not allowed">
❌ No
</span>
</td>
<td style="text-align:center">
<span title="Allowed">
✅ Yes
</span>
</td>
<td style="text-align:center">
<span title="Not allowed">
❌ No
</span>
</td>
<td style="text-align:center">
<span title="Allowed">
✅ Yes
</span>
</td>
<td style="text-align:center">
<span title="Allowed">
✅ Yes
</span>
</td>
</tr>
<tr>
<td>
Reset slow log
</td>
<td style="text-align:center">
<span title="Not allowed">
❌ No
</span>
</td>
<td style="text-align:center">
<span title="Allowed">
✅ Yes
</span>
</td>
<td style="text-align:center">
<span title="Not allowed">
❌ No
</span>
</td>
<td style="text-align:center">
<span title="Allowed">
✅ Yes
</span>
</td>
<td style="text-align:center">
<span title="Allowed">
✅ Yes
</span>
</td>
</tr>
<tr>
<td>
View cluster configuration
</td>
<td style="text-align:center">
<span title="Not allowed">
❌ No
</span>
</td>
<td style="text-align:center">
<span title="Not allowed">
❌ No
</span>
</td>
<td style="text-align:center">
<span title="Allowed">
✅ Yes
</span>
</td>
<td style="text-align:center">
<span title="Allowed">
✅ Yes
</span>
</td>
<td style="text-align:center">
<span title="Allowed">
✅ Yes
</span>
</td>
</tr>
<tr>
<td>
View cluster logs
</td>
<td style="text-align:center">
<span title="Not allowed">
❌ No
</span>
</td>
<td style="text-align:center">
<span title="Allowed">
✅ Yes
</span>
</td>
<td style="text-align:center">
<span title="Allowed">
✅ Yes
</span>
</td>
<td style="text-align:center">
<span title="Allowed">
✅ Yes
</span>
</td>
<td style="text-align:center">
<span title="Allowed">
✅ Yes
</span>
<br/>
</td>
</tr>
<tr>
<td>
View cluster metrics
</td>
<td style="text-align:center">
<span title="Not allowed">
❌ No
</span>
</td>
<td style="text-align:center">
<span title="Not allowed">
❌ No
</span>
</td>
<td style="text-align:center">
<span title="Allowed">
✅ Yes
</span>
</td>
<td style="text-align:center">
<span title="Allowed">
✅ Yes
</span>
</td>
<td style="text-align:center">
<span title="Allowed">
✅ Yes
</span>
</td>
</tr>
<tr>
<td>
View database configuration
</td>
<td style="text-align:center">
<span title="Allowed">
✅ Yes
</span>
</td>
<td style="text-align:center">
<span title="Allowed">
✅ Yes
</span>
</td>
<td style="text-align:center">
<span title="Allowed">
✅ Yes
</span>
</td>
<td style="text-align:center">
<span title="Allowed">
✅ Yes
</span>
</td>
<td style="text-align:center">
<span title="Allowed">
✅ Yes
</span>
</td>
</tr>
<tr>
<td>
View database metrics
</td>
<td style="text-align:center">
<span title="Allowed">
✅ Yes
</span>
</td>
<td style="text-align:center">
<span title="Allowed">
✅ Yes
</span>
</td>
<td style="text-align:center">
<span title="Allowed">
✅ Yes
</span>
</td>
<td style="text-align:center">
<span title="Allowed">
✅ Yes
</span>
</td>
<td style="text-align:center">
<span title="Allowed">
✅ Yes
</span>
</td>
</tr>
<tr>
<td>
View node configuration
</td>
<td style="text-align:center">
<span title="Not allowed">
❌ No
</span>
</td>
<td style="text-align:center">
<span title="Not allowed">
❌ No
</span>
</td>
<td style="text-align:center">
<span title="Allowed">
✅ Yes
</span>
</td>
<td style="text-align:center">
<span title="Allowed">
✅ Yes
</span>
</td>
<td style="text-align:center">
<span title="Allowed">
✅ Yes
</span>
</td>
</tr>
<tr>
<td>
View node metrics
</td>
<td style="text-align:center">
<span title="Not allowed">
❌ No
</span>
</td>
<td style="text-align:center">
<span title="Not allowed">
❌ No
</span>
</td>
<td style="text-align:center">
<span title="Allowed">
✅ Yes
</span>
</td>
<td style="text-align:center">
<span title="Allowed">
✅ Yes
</span>
</td>
<td style="text-align:center">
<span title="Allowed">
✅ Yes
</span>
</td>
</tr>
<tr>
<td>
View Redis database password
</td>
<td style="text-align:center">
<span title="Not allowed">
❌ No
</span>
</td>
<td style="text-align:center">
<span title="Allowed">
✅ Yes
</span>
</td>
<td style="text-align:center">
<span title="Not allowed">
❌ No
</span>
</td>
<td style="text-align:center">
<span title="Allowed">
✅ Yes
</span>
</td>
<td style="text-align:center">
<span title="Allowed">
✅ Yes
</span>
</td>
</tr>
<tr>
<td>
View slow log
</td>
<td style="text-align:center">
<span title="Not allowed">
❌ No
</span>
</td>
<td style="text-align:center">
<span title="Allowed">
✅ Yes
</span>
</td>
<td style="text-align:center">
<span title="Not allowed">
❌ No
</span>
</td>
<td style="text-align:center">
<span title="Allowed">
✅ Yes
</span>
</td>
<td style="text-align:center">
<span title="Allowed">
✅ Yes
</span>
</td>
</tr>
<tr>
<td>
View and edit cluster settings
</td>
<td style="text-align:center">
<span title="Not allowed">
❌ No
</span>
</td>
<td style="text-align:center">
<span title="Not allowed">
❌ No
</span>
</td>
<td style="text-align:center">
<span title="Not allowed">
❌ No
</span>
</td>
<td style="text-align:center">
<span title="Not allowed">
❌ No
</span>
</td>
<td style="text-align:center">
<span title="Allowed">
✅ Yes
</span>
</td>
</tr>
</tbody>
</table>
<h2 id="create-cluster-role">
Create roles for cluster access
</h2>
<p>
To create a role that grants cluster access but does not grant access to any databases:
</p>
<ol>
<li>
<p>
From
<strong>
Access Control
</strong>
>
<strong>
Roles
</strong>
, you can:
</p>
<ul>
<li>
<p>
Point to a role and select
<a href="/docs/latest/images/rs/buttons/edit-button.png#no-click" sdata-lightbox="/images/rs/buttons/edit-button.png#no-click">
<img alt="The Edit button" class="inline" src="/docs/latest/images/rs/buttons/edit-button.png#no-click" width="25px"/>
</a>
to edit an existing role.
</p>
</li>
<li>
<p>
Select
<strong>
+ Add role
</strong>
to create a new role.
</p>
</li>
</ul>
<a href="/docs/latest/images/rs/access-control-role-panel.png" sdata-lightbox="/images/rs/access-control-role-panel.png">
<img alt="Add role with name" src="/docs/latest/images/rs/access-control-role-panel.png"/>
</a>
</li>
<li>
<p>
Enter a descriptive name for the role.
</p>
</li>
<li>
<p>
Choose a
<strong>
Cluster management role
</strong>
to determine cluster management permissions.
</p>
<a href="/docs/latest/images/rs/screenshots/access-control/rbac-create-role-cluster-only.png" sdata-lightbox="/images/rs/screenshots/access-control/rbac-create-role-cluster-only.png">
<img alt="Select a cluster management role to set the level of cluster management permissions for the new role." src="/docs/latest/images/rs/screenshots/access-control/rbac-create-role-cluster-only.png"/>
</a>
</li>
<li>
<p>
To prevent database access when using this role, do not add any ACLs.
</p>
</li>
<li>
<p>
Select
<strong>
Save
</strong>
.
</p>
</li>
</ol>
<p>
You can
<a href="/docs/latest/operate/rs/7.4/security/access-control/create-users/#assign-roles-to-users">
assign the new role to users
</a>
to grant cluster access.
</p>
<form class="text-sm w-full mt-24 pt-5 border-t border-t-redis-pen-700 border-opacity-50" id="page-feedback" name="page-feedback">
<input class="hidden" name="origin" value="https://redis.io/docs/latest/operate/rs/7.4/security/access-control/create-cluster-roles/"/>
<div class="flex flex-row justify-between">
<div class="grid justify-center">
<span class="font-mono">
RATE THIS PAGE
</span>
<div class="star-rating">
<input id="5-stars" name="rating" onchange="document.querySelector('#feedback-form').classList.remove('hidden')" type="radio" value="5"/>
<label class="star" for="5-stars">
★
</label>
<input id="4-stars" name="rating" onchange="document.querySelector('#feedback-form').classList.remove('hidden')" type="radio" value="4"/>
<label class="star" for="4-stars">
★
</label>
<input id="3-stars" name="rating" onchange="document.querySelector('#feedback-form').classList.remove('hidden')" type="radio" value="3"/>
<label class="star" for="3-stars">
★
</label>
<input id="2-stars" name="rating" onchange="document.querySelector('#feedback-form').classList.remove('hidden')" type="radio" value="2"/>
<label class="star" for="2-stars">
★
</label>
<input id="1-stars" name="rating" onchange="document.querySelector('#feedback-form').classList.remove('hidden')" type="radio" value="1"/>
<label class="star" for="1-stars">
★
</label>
</div>
</div>
<a class="font-mono no-underline" href="#">
Back to top ↑
</a>
</div>
<div class="hidden" id="feedback-form">
<div class="grid gap-2">
<textarea class="p-2 mt-1 block w-full h-24 border border-opacity-50 border-redis-ink-900 rounded-md" name="comment" placeholder="Why did you choose this rating?" rows="3"></textarea>
<button class="font-mono button text-redis-ink-900 border border-solid border-transparent bg-redis-red-500 hover:bg-redis-red-600 focus:bg-red-600 focus:ring-red-600; w-min justify-self-end" type="submit">
Submit
</button>
</div>
</div>
</form>
<script>
document.addEventListener("DOMContentLoaded", function() {
const form = document.querySelector("#page-feedback");
form.addEventListener("submit", function(event) {
event.preventDefault();
var xhr = new XMLHttpRequest();
var url = "\/docusight\/api\/rate";
var params = new URLSearchParams(new FormData(form));
xhr.open("POST", url, true);
xhr.setRequestHeader("Content-Type", "application/x-www-form-urlencoded");
xhr.onreadystatechange = function() {
if (xhr.readyState === 4 && xhr.status === 200) {
const responseData = JSON.parse(xhr.responseText);
const responseMessage = responseData.response;
const newText = document.createTextNode(responseMessage);
form.parentNode.replaceChild(newText, form);
}
};
xhr.send(params);
});
});
</script>
</section>
|
https://redis.io/docs/latest/commands/ft.cursor-del.html | <section class="prose w-full py-12">
<h1 class="command-name">
FT.CURSOR DEL
</h1>
<div class="font-semibold text-redis-ink-900">
Syntax
</div>
<pre class="command-syntax">FT.CURSOR DEL index cursor_id
</pre>
<dl class="grid grid-cols-[auto,1fr] gap-2 mb-12">
<dt class="font-semibold text-redis-ink-900 m-0">
Available in:
</dt>
<dd class="m-0">
<a href="/docs/stack">
Redis Stack
</a>
/
<a href="/docs/interact/search-and-query">
Search 1.1.0
</a>
</dd>
<dt class="font-semibold text-redis-ink-900 m-0">
Time complexity:
</dt>
<dd class="m-0">
O(1)
</dd>
</dl>
<p>
Delete a cursor
</p>
<p>
<a href="#examples">
Examples
</a>
</p>
<h2 id="required-arguments">
Required arguments
</h2>
<details open="">
<summary>
<code>
index
</code>
</summary>
<p>
is index name.
</p>
</details>
<details open="">
<summary>
<code>
cursor_id
</code>
</summary>
<p>
is id of the cursor.
</p>
</details>
<h2 id="returns">
Returns
</h2>
<p>
FT.CURSOR DEL returns a simple string reply
<code>
OK
</code>
if executed correctly, or an error reply otherwise.
</p>
<h2 id="examples">
Examples
</h2>
<details open="">
<summary>
<b>
Delete a cursor
</b>
</summary>
<div class="highlight">
<pre class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">redis> FT.CURSOR DEL idx <span class="m">342459320</span>
</span></span><span class="line"><span class="cl">OK</span></span></code></pre>
</div>
<p>
Check that the cursor is deleted.
</p>
<div class="highlight">
<pre class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">127.0.0.1:6379> FT.CURSOR DEL idx <span class="m">342459320</span>
</span></span><span class="line"><span class="cl"><span class="o">(</span>error<span class="o">)</span> Cursor does not exist</span></span></code></pre>
</div>
</details>
<h2 id="see-also">
See also
</h2>
<p>
<a href="/docs/latest/commands/ft.cursor-read/">
<code>
FT.CURSOR READ
</code>
</a>
</p>
<h2 id="related-topics">
Related topics
</h2>
<p>
<a href="/docs/latest/develop/interact/search-and-query/">
RediSearch
</a>
</p>
<br/>
<form class="text-sm w-full mt-24 pt-5 border-t border-t-redis-pen-700 border-opacity-50" id="page-feedback" name="page-feedback">
<input class="hidden" name="origin" value="https://redis.io/docs/latest/commands/ft.cursor-del/"/>
<div class="flex flex-row justify-between">
<div class="grid justify-center">
<span class="font-mono">
RATE THIS PAGE
</span>
<div class="star-rating">
<input id="5-stars" name="rating" onchange="document.querySelector('#feedback-form').classList.remove('hidden')" type="radio" value="5"/>
<label class="star" for="5-stars">
★
</label>
<input id="4-stars" name="rating" onchange="document.querySelector('#feedback-form').classList.remove('hidden')" type="radio" value="4"/>
<label class="star" for="4-stars">
★
</label>
<input id="3-stars" name="rating" onchange="document.querySelector('#feedback-form').classList.remove('hidden')" type="radio" value="3"/>
<label class="star" for="3-stars">
★
</label>
<input id="2-stars" name="rating" onchange="document.querySelector('#feedback-form').classList.remove('hidden')" type="radio" value="2"/>
<label class="star" for="2-stars">
★
</label>
<input id="1-stars" name="rating" onchange="document.querySelector('#feedback-form').classList.remove('hidden')" type="radio" value="1"/>
<label class="star" for="1-stars">
★
</label>
</div>
</div>
<a class="font-mono no-underline" href="#">
Back to top ↑
</a>
</div>
<div class="hidden" id="feedback-form">
<div class="grid gap-2">
<textarea class="p-2 mt-1 block w-full h-24 border border-opacity-50 border-redis-ink-900 rounded-md" name="comment" placeholder="Why did you choose this rating?" rows="3"></textarea>
<button class="font-mono button text-redis-ink-900 border border-solid border-transparent bg-redis-red-500 hover:bg-redis-red-600 focus:bg-red-600 focus:ring-red-600; w-min justify-self-end" type="submit">
Submit
</button>
</div>
</div>
</form>
<script>
document.addEventListener("DOMContentLoaded", function() {
const form = document.querySelector("#page-feedback");
form.addEventListener("submit", function(event) {
event.preventDefault();
var xhr = new XMLHttpRequest();
var url = "\/docusight\/api\/rate";
var params = new URLSearchParams(new FormData(form));
xhr.open("POST", url, true);
xhr.setRequestHeader("Content-Type", "application/x-www-form-urlencoded");
xhr.onreadystatechange = function() {
if (xhr.readyState === 4 && xhr.status === 200) {
const responseData = JSON.parse(xhr.responseText);
const responseMessage = responseData.response;
const newText = document.createTextNode(responseMessage);
form.parentNode.replaceChild(newText, form);
}
};
xhr.send(params);
});
});
</script>
</section>
|
https://redis.io/docs/latest/commands/cf.del/.html | <section class="prose w-full py-12">
<h1 class="command-name">
CF.DEL
</h1>
<div class="font-semibold text-redis-ink-900">
Syntax
</div>
<pre class="command-syntax">CF.DEL key item</pre>
<dl class="grid grid-cols-[auto,1fr] gap-2 mb-12">
<dt class="font-semibold text-redis-ink-900 m-0">
Available in:
</dt>
<dd class="m-0">
<a href="/docs/stack">
Redis Stack
</a>
/
<a href="/docs/data-types/probabilistic">
Bloom 1.0.0
</a>
</dd>
<dt class="font-semibold text-redis-ink-900 m-0">
Time complexity:
</dt>
<dd class="m-0">
O(k), where k is the number of sub-filters
</dd>
</dl>
<p>
Deletes an item once from the filter.
</p>
<p>
If the item exists only once, it will be removed from the filter. If the item was added multiple times, it will still be present.
</p>
<p>
<note>
<b>
Note:
</b>
</note>
</p>
<ul>
<li>
Deleting an item that are not in the filter may delete a different item, resulting in false negatives.
</li>
</ul>
<h2 id="required-arguments">
Required arguments
</h2>
<details open="">
<summary>
<code>
key
</code>
</summary>
<p>
is key name for a cuckoo filter.
</p>
</details>
<details open="">
<summary>
<code>
item
</code>
</summary>
<p>
is an item to delete.
</p>
</details>
<h2 id="complexity">
Complexity
</h2>
<p>
O(n), where n is the number of
<code>
sub-filters
</code>
. Both alternative locations are
checked on all
<code>
sub-filters
</code>
.
</p>
<h2 id="return-value">
Return value
</h2>
<p>
Returns one of these replies:
</p>
<ul>
<li>
<a href="/docs/latest/develop/reference/protocol-spec/#integers">
Integer reply
</a>
- where "1" means that the item has been deleted, and "0" means that such item was not found in the filter
</li>
<li>
[] on error (invalid arguments, wrong key type, etc.)
</li>
</ul>
<h2 id="examples">
Examples
</h2>
<div class="highlight">
<pre class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">redis> CF.INSERT cf ITEMS item1 item2 item2
</span></span><span class="line"><span class="cl">1<span class="o">)</span> <span class="o">(</span>integer<span class="o">)</span> <span class="m">1</span>
</span></span><span class="line"><span class="cl">2<span class="o">)</span> <span class="o">(</span>integer<span class="o">)</span> <span class="m">1</span>
</span></span><span class="line"><span class="cl">3<span class="o">)</span> <span class="o">(</span>integer<span class="o">)</span> <span class="m">1</span>
</span></span><span class="line"><span class="cl">redis> CF.DEL cf item1
</span></span><span class="line"><span class="cl"><span class="o">(</span>integer<span class="o">)</span> <span class="m">1</span>
</span></span><span class="line"><span class="cl">redis> CF.DEL cf item1
</span></span><span class="line"><span class="cl"><span class="o">(</span>integer<span class="o">)</span> <span class="m">0</span>
</span></span><span class="line"><span class="cl">redis> CF.DEL cf item2
</span></span><span class="line"><span class="cl"><span class="o">(</span>integer<span class="o">)</span> <span class="m">1</span>
</span></span><span class="line"><span class="cl">redis> CF.DEL cf item2
</span></span><span class="line"><span class="cl"><span class="o">(</span>integer<span class="o">)</span> <span class="m">1</span>
</span></span><span class="line"><span class="cl">redis> CF.DEL cf item2
</span></span><span class="line"><span class="cl"><span class="o">(</span>integer<span class="o">)</span> <span class="m">0</span></span></span></code></pre>
</div>
<br/>
<form class="text-sm w-full mt-24 pt-5 border-t border-t-redis-pen-700 border-opacity-50" id="page-feedback" name="page-feedback">
<input class="hidden" name="origin" value="https://redis.io/docs/latest/commands/cf.del/"/>
<div class="flex flex-row justify-between">
<div class="grid justify-center">
<span class="font-mono">
RATE THIS PAGE
</span>
<div class="star-rating">
<input id="5-stars" name="rating" onchange="document.querySelector('#feedback-form').classList.remove('hidden')" type="radio" value="5"/>
<label class="star" for="5-stars">
★
</label>
<input id="4-stars" name="rating" onchange="document.querySelector('#feedback-form').classList.remove('hidden')" type="radio" value="4"/>
<label class="star" for="4-stars">
★
</label>
<input id="3-stars" name="rating" onchange="document.querySelector('#feedback-form').classList.remove('hidden')" type="radio" value="3"/>
<label class="star" for="3-stars">
★
</label>
<input id="2-stars" name="rating" onchange="document.querySelector('#feedback-form').classList.remove('hidden')" type="radio" value="2"/>
<label class="star" for="2-stars">
★
</label>
<input id="1-stars" name="rating" onchange="document.querySelector('#feedback-form').classList.remove('hidden')" type="radio" value="1"/>
<label class="star" for="1-stars">
★
</label>
</div>
</div>
<a class="font-mono no-underline" href="#">
Back to top ↑
</a>
</div>
<div class="hidden" id="feedback-form">
<div class="grid gap-2">
<textarea class="p-2 mt-1 block w-full h-24 border border-opacity-50 border-redis-ink-900 rounded-md" name="comment" placeholder="Why did you choose this rating?" rows="3"></textarea>
<button class="font-mono button text-redis-ink-900 border border-solid border-transparent bg-redis-red-500 hover:bg-redis-red-600 focus:bg-red-600 focus:ring-red-600; w-min justify-self-end" type="submit">
Submit
</button>
</div>
</div>
</form>
<script>
document.addEventListener("DOMContentLoaded", function() {
const form = document.querySelector("#page-feedback");
form.addEventListener("submit", function(event) {
event.preventDefault();
var xhr = new XMLHttpRequest();
var url = "\/docusight\/api\/rate";
var params = new URLSearchParams(new FormData(form));
xhr.open("POST", url, true);
xhr.setRequestHeader("Content-Type", "application/x-www-form-urlencoded");
xhr.onreadystatechange = function() {
if (xhr.readyState === 4 && xhr.status === 200) {
const responseData = JSON.parse(xhr.responseText);
const responseMessage = responseData.response;
const newText = document.createTextNode(responseMessage);
form.parentNode.replaceChild(newText, form);
}
};
xhr.send(params);
});
});
</script>
</section>
|
https://redis.io/docs/latest/commands/setex/.html | <section class="prose w-full py-12">
<h1 class="command-name">
SETEX
<span class="text-base">
(deprecated)
</span>
</h1>
<div class="border-l-8 pl-4">
<p>
As of Redis version 2.6.12, this command is regarded as deprecated.
</p>
<p>
It can be replaced by
<a href="/docs/latest/commands/set/">
<code>
SET
</code>
</a>
with the
<code>
EX
</code>
argument when migrating or writing new code.
</p>
</div>
<div class="font-semibold text-redis-ink-900">
Syntax
</div>
<pre class="command-syntax">SETEX key seconds value</pre>
<dl class="grid grid-cols-[auto,1fr] gap-2 mb-12">
<dt class="font-semibold text-redis-ink-900 m-0">
Available since:
</dt>
<dd class="m-0">
2.0.0
</dd>
<dt class="font-semibold text-redis-ink-900 m-0">
Time complexity:
</dt>
<dd class="m-0">
O(1)
</dd>
<dt class="font-semibold text-redis-ink-900 m-0">
ACL categories:
</dt>
<dd class="m-0">
<code>
@write
</code>
<span class="mr-1 last:hidden">
,
</span>
<code>
@string
</code>
<span class="mr-1 last:hidden">
,
</span>
<code>
@slow
</code>
<span class="mr-1 last:hidden">
,
</span>
</dd>
</dl>
<p>
Set
<code>
key
</code>
to hold the string
<code>
value
</code>
and set
<code>
key
</code>
to timeout after a given
number of seconds.
This command is equivalent to:
</p>
<pre tabindex="0"><code>SET key value EX seconds
</code></pre>
<p>
An error is returned when
<code>
seconds
</code>
is invalid.
</p>
<h2 id="examples">
Examples
</h2>
<div class="bg-slate-900 border-b border-slate-700 rounded-t-xl px-4 py-3 w-full flex">
<svg class="shrink-0 h-[1.0625rem] w-[1.0625rem] fill-slate-50" fill="currentColor" viewbox="0 0 20 20">
<path d="M2.5 10C2.5 5.85786 5.85786 2.5 10 2.5C14.1421 2.5 17.5 5.85786 17.5 10C17.5 14.1421 14.1421 17.5 10 17.5C5.85786 17.5 2.5 14.1421 2.5 10Z">
</path>
</svg>
<svg class="shrink-0 h-[1.0625rem] w-[1.0625rem] fill-slate-50" fill="currentColor" viewbox="0 0 20 20">
<path d="M10 2.5L18.6603 17.5L1.33975 17.5L10 2.5Z">
</path>
</svg>
<svg class="shrink-0 h-[1.0625rem] w-[1.0625rem] fill-slate-50" fill="currentColor" viewbox="0 0 20 20">
<path d="M10 2.5L12.0776 7.9322L17.886 8.22949L13.3617 11.8841L14.8738 17.5L10 14.3264L5.1262 17.5L6.63834 11.8841L2.11403 8.22949L7.92238 7.9322L10 2.5Z">
</path>
</svg>
</div>
<form class="redis-cli overflow-y-auto max-h-80">
<pre tabindex="0">redis> SETEX mykey 10 "Hello"
"OK"
redis> TTL mykey
(integer) 10
redis> GET mykey
"Hello"
</pre>
<div class="prompt" style="">
<span>
redis>
</span>
<input autocomplete="off" name="prompt" spellcheck="false" type="text"/>
</div>
</form>
<h2 id="see-also">
See also
</h2>
<p>
<a href="/docs/latest/commands/ttl/">
<code>
TTL
</code>
</a>
</p>
<h2 id="resp2resp3-reply">
RESP2/RESP3 Reply
</h2>
<a href="../../develop/reference/protocol-spec#simple-strings">
Simple string reply
</a>
:
<code>
OK
</code>
.
<br/>
<form class="text-sm w-full mt-24 pt-5 border-t border-t-redis-pen-700 border-opacity-50" id="page-feedback" name="page-feedback">
<input class="hidden" name="origin" value="https://redis.io/docs/latest/commands/setex/"/>
<div class="flex flex-row justify-between">
<div class="grid justify-center">
<span class="font-mono">
RATE THIS PAGE
</span>
<div class="star-rating">
<input id="5-stars" name="rating" onchange="document.querySelector('#feedback-form').classList.remove('hidden')" type="radio" value="5"/>
<label class="star" for="5-stars">
★
</label>
<input id="4-stars" name="rating" onchange="document.querySelector('#feedback-form').classList.remove('hidden')" type="radio" value="4"/>
<label class="star" for="4-stars">
★
</label>
<input id="3-stars" name="rating" onchange="document.querySelector('#feedback-form').classList.remove('hidden')" type="radio" value="3"/>
<label class="star" for="3-stars">
★
</label>
<input id="2-stars" name="rating" onchange="document.querySelector('#feedback-form').classList.remove('hidden')" type="radio" value="2"/>
<label class="star" for="2-stars">
★
</label>
<input id="1-stars" name="rating" onchange="document.querySelector('#feedback-form').classList.remove('hidden')" type="radio" value="1"/>
<label class="star" for="1-stars">
★
</label>
</div>
</div>
<a class="font-mono no-underline" href="#">
Back to top ↑
</a>
</div>
<div class="hidden" id="feedback-form">
<div class="grid gap-2">
<textarea class="p-2 mt-1 block w-full h-24 border border-opacity-50 border-redis-ink-900 rounded-md" name="comment" placeholder="Why did you choose this rating?" rows="3"></textarea>
<button class="font-mono button text-redis-ink-900 border border-solid border-transparent bg-redis-red-500 hover:bg-redis-red-600 focus:bg-red-600 focus:ring-red-600; w-min justify-self-end" type="submit">
Submit
</button>
</div>
</div>
</form>
<script>
document.addEventListener("DOMContentLoaded", function() {
const form = document.querySelector("#page-feedback");
form.addEventListener("submit", function(event) {
event.preventDefault();
var xhr = new XMLHttpRequest();
var url = "\/docusight\/api\/rate";
var params = new URLSearchParams(new FormData(form));
xhr.open("POST", url, true);
xhr.setRequestHeader("Content-Type", "application/x-www-form-urlencoded");
xhr.onreadystatechange = function() {
if (xhr.readyState === 4 && xhr.status === 200) {
const responseData = JSON.parse(xhr.responseText);
const responseMessage = responseData.response;
const newText = document.createTextNode(responseMessage);
form.parentNode.replaceChild(newText, form);
}
};
xhr.send(params);
});
});
</script>
</section>
|
https://redis.io/docs/latest/integrate/write-behind/reference/debezium/mysql/.html | <section class="prose w-full py-12 max-w-none">
<h1>
Write-behind configuration for mysql
</h1>
<p class="text-lg -mt-5 mb-10">
Describes the
<code>
application.properties
</code>
settings that configure Debezium Server for mysql
</p>
<h2 id="applicationproperties">
application.properties
</h2>
<div class="highlight">
<pre class="chroma"><code class="language-properties" data-lang="properties"><span class="line"><span class="cl"><span class="na">debezium.sink.type</span><span class="o">=</span><span class="s">redis</span>
</span></span><span class="line"><span class="cl"><span class="na">debezium.sink.redis.message.format</span><span class="o">=</span><span class="s">extended</span>
</span></span><span class="line"><span class="cl"><span class="na">debezium.sink.redis.address</span><span class="o">=</span><span class="s"><RDI_HOST>:<RDI_PORT></span>
</span></span><span class="line"><span class="cl"><span class="c1"># Comment the following line if not using a password for Write-behind.</span>
</span></span><span class="line"><span class="cl"><span class="na">debezium.sink.redis.password</span><span class="o">=</span><span class="s"><RDI_PASSWORD></span>
</span></span><span class="line"><span class="cl"><span class="na">debezium.sink.redis.memory.limit.mb</span><span class="o">=</span><span class="s">80</span>
</span></span><span class="line"><span class="cl"><span class="c1"># Redis SSL/TLS</span>
</span></span><span class="line"><span class="cl"><span class="c1">#debezium.sink.redis.ssl.enabled=true</span>
</span></span><span class="line"><span class="cl"><span class="c1"># When Redis is configured with a replica shard, these properties allow to verify that the data has been written to the replica.</span>
</span></span><span class="line"><span class="cl"><span class="c1">#debezium.sink.redis.wait.enabled=true</span>
</span></span><span class="line"><span class="cl"><span class="c1">#debezium.sink.redis.wait.timeout.ms=1000</span>
</span></span><span class="line"><span class="cl"><span class="c1">#debezium.sink.redis.wait.retry.enabled=true</span>
</span></span><span class="line"><span class="cl"><span class="c1">#debezium.sink.redis.wait.retry.delay.ms=1000</span>
</span></span><span class="line"><span class="cl"><span class="c1">#debezium.source.database.history.redis.ssl.enabled=true</span>
</span></span><span class="line"><span class="cl"><span class="c1"># Location of the Java keystore file containing an application process' own certificate and private key.</span>
</span></span><span class="line"><span class="cl"><span class="c1">#javax.net.ssl.keyStore=<KEY_STORE_FILE_PATH></span>
</span></span><span class="line"><span class="cl"><span class="c1"># Password to access the private key from the keystore file specified by javax.net.ssl.keyStore. This password is used twice: To unlock the keystore file (store password), and To decrypt the private key stored in the keystore (key password).</span>
</span></span><span class="line"><span class="cl"><span class="c1">#javax.net.ssl.keyStorePassword=<KEY_STORE_PASSWORD></span>
</span></span><span class="line"><span class="cl"><span class="c1"># Location of the Java keystore file containing the collection of CA certificates trusted by this application process (trust store).</span>
</span></span><span class="line"><span class="cl"><span class="c1">#javax.net.ssl.trustStore=<TRUSE_STORE_FILE_PATH></span>
</span></span><span class="line"><span class="cl"><span class="c1"># Password to unlock the keystore file (store password) specified by javax.net.ssl.trustStore.</span>
</span></span><span class="line"><span class="cl"><span class="c1">#javax.net.ssl.trustStorePassword=<TRUST_STORE_PASSWORD></span>
</span></span><span class="line"><span class="cl">
</span></span><span class="line"><span class="cl"><span class="na">debezium.source.connector.class</span><span class="o">=</span><span class="s">io.debezium.connector.mysql.MySqlConnector</span>
</span></span><span class="line"><span class="cl"><span class="c1"># A numeric ID of this database client, which must be unique across all currently-running database processes in the MySQL cluster.</span>
</span></span><span class="line"><span class="cl"><span class="na">debezium.source.database.server.id</span><span class="o">=</span><span class="s">1</span>
</span></span><span class="line"><span class="cl"><span class="na">debezium.source.offset.storage</span><span class="o">=</span><span class="s">io.debezium.storage.redis.offset.RedisOffsetBackingStore</span>
</span></span><span class="line"><span class="cl"><span class="na">debezium.source.topic.prefix</span><span class="o">=</span><span class="s"><SOURCE_LOGICAL_SERVER_NAME></span>
</span></span><span class="line"><span class="cl">
</span></span><span class="line"><span class="cl"><span class="na">debezium.source.database.hostname</span><span class="o">=</span><span class="s"><SOURCE_DB_HOST></span>
</span></span><span class="line"><span class="cl"><span class="na">debezium.source.database.port</span><span class="o">=</span><span class="s"><SOURCE_DB_PORT></span>
</span></span><span class="line"><span class="cl"><span class="na">debezium.source.database.user</span><span class="o">=</span><span class="s"><SOURCE_DB_USER></span>
</span></span><span class="line"><span class="cl"><span class="na">debezium.source.database.password</span><span class="o">=</span><span class="s"><SOURCE_DB_PASSWORD></span>
</span></span><span class="line"><span class="cl"><span class="na">debezium.source.include.schema.changes</span><span class="o">=</span><span class="s">false</span>
</span></span><span class="line"><span class="cl"><span class="c1"># Determines whether the connector should omit publishing change events when there are no modifications in the included columns.</span>
</span></span><span class="line"><span class="cl"><span class="na">debezium.source.skip.messages.without.change</span><span class="o">=</span><span class="s">true</span>
</span></span><span class="line"><span class="cl"><span class="na">debezium.source.offset.flush.interval.ms</span><span class="o">=</span><span class="s">1000</span>
</span></span><span class="line"><span class="cl"><span class="na">debezium.source.tombstones.on.delete</span><span class="o">=</span><span class="s">false</span>
</span></span><span class="line"><span class="cl"><span class="na">debezium.source.schema.history.internal</span><span class="o">=</span><span class="s">io.debezium.storage.redis.history.RedisSchemaHistory</span>
</span></span><span class="line"><span class="cl">
</span></span><span class="line"><span class="cl"><span class="c1"># Important: Do NOT use `include` and `exclude` database lists at the same time, use either `include` or `exclude`.</span>
</span></span><span class="line"><span class="cl"><span class="c1"># An optional, comma-separated list of regular expressions that match database names to be monitored.</span>
</span></span><span class="line"><span class="cl"><span class="c1"># By default, all databases are monitored.</span>
</span></span><span class="line"><span class="cl"><span class="c1">#debezium.source.database.include.list=<DB_NAME1>,<DB_NAME2>...</span>
</span></span><span class="line"><span class="cl"><span class="c1"># An optional, comma-separated list of regular expressions that match database names for which you do not want to capture changes.</span>
</span></span><span class="line"><span class="cl"><span class="c1">#debezium.source.database.exclude.list=<DB_NAME1>,<DB_NAME2>...</span>
</span></span><span class="line"><span class="cl"><span class="c1"># Important: Do NOT use `include` and `exclude` table lists at the same time, use either `include` or `exclude`.</span>
</span></span><span class="line"><span class="cl"><span class="c1"># An optional, comma-separated list of regular expressions that match fully-qualified table identifiers of tables whose changes you want to capture.</span>
</span></span><span class="line"><span class="cl"><span class="c1">#debezium.source.table.include.list=<DB_NAME.TABLE_NAME1>,<DB_NAME.TABLE_NAME2>...</span>
</span></span><span class="line"><span class="cl"><span class="c1"># An optional, comma-separated list of regular expressions that match fully-qualified table identifiers for tables whose changes you do not want to capture.</span>
</span></span><span class="line"><span class="cl"><span class="c1">#debezium.source.table.exclude.list=<DB_NAME.TABLE_NAME1>,<DB_NAME.TABLE_NAME2>...</span>
</span></span><span class="line"><span class="cl">
</span></span><span class="line"><span class="cl"><span class="c1"># Important: Do NOT use include and exclude column lists at the same time, use either include or exclude.</span>
</span></span><span class="line"><span class="cl"><span class="c1"># An optional, comma-separated list of regular expressions that match the fully-qualified names of columns to include in change event record values.</span>
</span></span><span class="line"><span class="cl"><span class="c1">#debezium.source.column.include.list=<DB_NAME.TABLE_NAME.COLUMN_NAME1>,<DB_NAME.TABLE_NAME.COLUMN_NAME2>...</span>
</span></span><span class="line"><span class="cl"><span class="c1"># An optional, comma-separated list of regular expressions that match the fully-qualified names of columns to exclude from change event record values.</span>
</span></span><span class="line"><span class="cl"><span class="c1">#debezium.source.column.exclude.list=<DB_NAME.TABLE_NAME.COLUMN_NAME1>,<DB_NAME.TABLE_NAME.COLUMN_NAME2>...</span>
</span></span><span class="line"><span class="cl">
</span></span><span class="line"><span class="cl"><span class="c1"># Records only DDL statements that are relevant to tables whose changes are being captured by Debezium.</span>
</span></span><span class="line"><span class="cl"><span class="c1"># In case of changing the captured tables, run `redis-di reset`.</span>
</span></span><span class="line"><span class="cl"><span class="na">debezium.source.schema.history.internal.store.only.captured.tables.ddl</span><span class="o">=</span><span class="s">true</span>
</span></span><span class="line"><span class="cl">
</span></span><span class="line"><span class="cl"><span class="c1"># Whether to include the detailed schema information generated by Debezium in each record written to RDI.</span>
</span></span><span class="line"><span class="cl"><span class="c1"># Note: Including the schema reduces the initial sync throughput and is not recommended for large data sets.</span>
</span></span><span class="line"><span class="cl"><span class="na">debezium.source.key.converter.schemas.enable</span><span class="o">=</span><span class="s">false</span>
</span></span><span class="line"><span class="cl"><span class="na">debezium.source.value.converter.schemas.enable</span><span class="o">=</span><span class="s">false</span>
</span></span><span class="line"><span class="cl"><span class="c1"># When detailed schema information is excluded, handle decimal numeric types as strings.</span>
</span></span><span class="line"><span class="cl"><span class="na">debezium.source.decimal.handling.mode</span><span class="o">=</span><span class="s">string</span>
</span></span><span class="line"><span class="cl">
</span></span><span class="line"><span class="cl"><span class="na">debezium.transforms</span><span class="o">=</span><span class="s">AddPrefix</span>
</span></span><span class="line"><span class="cl"><span class="na">debezium.transforms.AddPrefix.type</span><span class="o">=</span><span class="s">org.apache.kafka.connect.transforms.RegexRouter</span>
</span></span><span class="line"><span class="cl"><span class="na">debezium.transforms.AddPrefix.regex</span><span class="o">=</span><span class="s">.*</span>
</span></span><span class="line"><span class="cl"><span class="na">debezium.transforms.AddPrefix.replacement</span><span class="o">=</span><span class="s">data:$0</span>
</span></span><span class="line"><span class="cl">
</span></span><span class="line"><span class="cl"><span class="c1"># Logging</span>
</span></span><span class="line"><span class="cl"><span class="c1"># Uncomment the following lines if running Debezium Server as a Java standalone process (non-containerized).</span>
</span></span><span class="line"><span class="cl"><span class="c1">#quarkus.log.file.enable=true</span>
</span></span><span class="line"><span class="cl"><span class="c1">#quarkus.log.file.path=<LOG_FILE_PATH></span>
</span></span><span class="line"><span class="cl"><span class="c1">#quarkus.log.file.rotation.max-file-size=100M</span>
</span></span><span class="line"><span class="cl"><span class="c1">#quarkus.log.file.rotation.rotate-on-boot=true</span>
</span></span><span class="line"><span class="cl"><span class="c1">#quarkus.log.file.rotation.file-suffix=.yyyy-MM-dd.gz</span>
</span></span><span class="line"><span class="cl"><span class="c1">#quarkus.log.file.rotation.max-backup-index=3</span>
</span></span><span class="line"><span class="cl">
</span></span><span class="line"><span class="cl"><span class="c1"># The default minimum log level for every log category, change only quarkus.log.level when needed.</span>
</span></span><span class="line"><span class="cl"><span class="na">quarkus.log.min-level</span><span class="o">=</span><span class="s">TRACE</span>
</span></span><span class="line"><span class="cl"><span class="c1"># The default log level for every log category.</span>
</span></span><span class="line"><span class="cl"><span class="na">quarkus.log.level</span><span class="o">=</span><span class="s">INFO</span>
</span></span><span class="line"><span class="cl"><span class="c1"># Determine whether to enable the JSON console formatting extension, which disables "normal" console formatting.</span>
</span></span><span class="line"><span class="cl"><span class="na">quarkus.log.console.json</span><span class="o">=</span><span class="s">false</span>
</span></span><span class="line"><span class="cl"><span class="c1"># The port on which Debezium exposes Microprofile Health endpoint and other exposed status information.</span>
</span></span><span class="line"><span class="cl"><span class="na">quarkus.http.port</span><span class="o">=</span><span class="s">8088</span>
</span></span></code></pre>
</div>
<form class="text-sm w-full mt-24 pt-5 border-t border-t-redis-pen-700 border-opacity-50" id="page-feedback" name="page-feedback">
<input class="hidden" name="origin" value="https://redis.io/docs/latest/integrate/write-behind/reference/debezium/mysql/"/>
<div class="flex flex-row justify-between">
<div class="grid justify-center">
<span class="font-mono">
RATE THIS PAGE
</span>
<div class="star-rating">
<input id="5-stars" name="rating" onchange="document.querySelector('#feedback-form').classList.remove('hidden')" type="radio" value="5"/>
<label class="star" for="5-stars">
★
</label>
<input id="4-stars" name="rating" onchange="document.querySelector('#feedback-form').classList.remove('hidden')" type="radio" value="4"/>
<label class="star" for="4-stars">
★
</label>
<input id="3-stars" name="rating" onchange="document.querySelector('#feedback-form').classList.remove('hidden')" type="radio" value="3"/>
<label class="star" for="3-stars">
★
</label>
<input id="2-stars" name="rating" onchange="document.querySelector('#feedback-form').classList.remove('hidden')" type="radio" value="2"/>
<label class="star" for="2-stars">
★
</label>
<input id="1-stars" name="rating" onchange="document.querySelector('#feedback-form').classList.remove('hidden')" type="radio" value="1"/>
<label class="star" for="1-stars">
★
</label>
</div>
</div>
<a class="font-mono no-underline" href="#">
Back to top ↑
</a>
</div>
<div class="hidden" id="feedback-form">
<div class="grid gap-2">
<textarea class="p-2 mt-1 block w-full h-24 border border-opacity-50 border-redis-ink-900 rounded-md" name="comment" placeholder="Why did you choose this rating?" rows="3"></textarea>
<button class="font-mono button text-redis-ink-900 border border-solid border-transparent bg-redis-red-500 hover:bg-redis-red-600 focus:bg-red-600 focus:ring-red-600; w-min justify-self-end" type="submit">
Submit
</button>
</div>
</div>
</form>
<script>
document.addEventListener("DOMContentLoaded", function() {
const form = document.querySelector("#page-feedback");
form.addEventListener("submit", function(event) {
event.preventDefault();
var xhr = new XMLHttpRequest();
var url = "\/docusight\/api\/rate";
var params = new URLSearchParams(new FormData(form));
xhr.open("POST", url, true);
xhr.setRequestHeader("Content-Type", "application/x-www-form-urlencoded");
xhr.onreadystatechange = function() {
if (xhr.readyState === 4 && xhr.status === 200) {
const responseData = JSON.parse(xhr.responseText);
const responseMessage = responseData.response;
const newText = document.createTextNode(responseMessage);
form.parentNode.replaceChild(newText, form);
}
};
xhr.send(params);
});
});
</script>
</section>
|
https://redis.io/docs/latest/operate/rs/7.4/references/cli-utilities/rladmin/cluster/recover/.html | <section class="prose w-full py-12 max-w-none">
<h1>
rladmin cluster recover
</h1>
<p class="text-lg -mt-5 mb-10">
Recovers a cluster from a backup file.
</p>
<p>
Recovers a cluster from a backup file. The default location of the configuration backup file is
<code>
/var/opt/redislabs/persist/ccs/ccs-redis.rdb
</code>
.
</p>
<div class="highlight">
<pre class="chroma"><code class="language-sh" data-lang="sh"><span class="line"><span class="cl">rladmin cluster recover
</span></span><span class="line"><span class="cl"> filename <recovery filename>
</span></span><span class="line"><span class="cl"> <span class="o">[</span> ephemeral_path <path> <span class="o">]</span>
</span></span><span class="line"><span class="cl"> <span class="o">[</span> persistent_path <path> <span class="o">]</span>
</span></span><span class="line"><span class="cl"> <span class="o">[</span> ccs_persistent_path <path> <span class="o">]</span>
</span></span><span class="line"><span class="cl"> <span class="o">[</span> rack_id <ID> <span class="o">]</span>
</span></span><span class="line"><span class="cl"> <span class="o">[</span> override_rack_id <span class="o">]</span>
</span></span><span class="line"><span class="cl"> <span class="o">[</span> node_uid <number> <span class="o">]</span>
</span></span><span class="line"><span class="cl"> <span class="o">[</span> flash_enabled <span class="o">]</span>
</span></span><span class="line"><span class="cl"> <span class="o">[</span> flash_path <path> <span class="o">]</span>
</span></span><span class="line"><span class="cl"> <span class="o">[</span> addr <IP address> <span class="o">]</span>
</span></span><span class="line"><span class="cl"> <span class="o">[</span> external_addr <IP address> <span class="o">]</span>
</span></span></code></pre>
</div>
<h3 id="parameters">
Parameters
</h3>
<table>
<thead>
<tr>
<th>
Parameter
</th>
<th>
Type/Value
</th>
<th>
Description
</th>
</tr>
</thead>
<tbody>
<tr>
<td>
addr
</td>
<td>
IP address
</td>
<td>
Sets a node's internal IP address. If not provided, the node sets the address automatically. (optional)
</td>
</tr>
<tr>
<td>
ccs_persistent_path
</td>
<td>
filepath
</td>
<td>
Path to the location of CCS snapshots (default is the same as persistent_path) (optional)
</td>
</tr>
<tr>
<td>
external_addr
</td>
<td>
IP address
</td>
<td>
Sets a node's external IP address. If not provided, the node sets the address automatically. (optional)
</td>
</tr>
<tr>
<td>
ephemeral_path
</td>
<td>
filepath (default: /var/opt/redislabs)
</td>
<td>
Path to an ephemeral storage location (optional)
</td>
</tr>
<tr>
<td>
filename
</td>
<td>
filepath
</td>
<td>
Backup file to use for recovery
</td>
</tr>
<tr>
<td>
flash_enabled
</td>
<td>
</td>
<td>
Enables flash storage (optional)
</td>
</tr>
<tr>
<td>
flash_path
</td>
<td>
filepath (default: /var/opt/redislabs/flash)
</td>
<td>
Path to the flash storage location in case the node does not support CAPI (required if flash_enabled)
</td>
</tr>
<tr>
<td>
node_uid
</td>
<td>
integer (default: 1)
</td>
<td>
Specifies which node will recover first and become master (optional)
</td>
</tr>
<tr>
<td>
override_rack_id
</td>
<td>
</td>
<td>
Changes to a new rack, specified by
<code>
rack_id
</code>
(optional)
</td>
</tr>
<tr>
<td>
persistent_path
</td>
<td>
filepath
</td>
<td>
Path to the persistent storage location (optional)
</td>
</tr>
<tr>
<td>
rack_id
</td>
<td>
string
</td>
<td>
Switches to the specified rack (optional)
</td>
</tr>
</tbody>
</table>
<h3 id="returns">
Returns
</h3>
<p>
Returns
<code>
ok
</code>
if the cluster recovered successfully. Otherwise, it returns an error message.
</p>
<h3 id="example">
Example
</h3>
<div class="highlight">
<pre class="chroma"><code class="language-sh" data-lang="sh"><span class="line"><span class="cl">$ rladmin cluster recover filename /tmp/persist/ccs/ccs-redis.rdb node_uid <span class="m">1</span> rack_id <span class="m">5</span>
</span></span><span class="line"><span class="cl">Initiating cluster recovery... ok
</span></span></code></pre>
</div>
<form class="text-sm w-full mt-24 pt-5 border-t border-t-redis-pen-700 border-opacity-50" id="page-feedback" name="page-feedback">
<input class="hidden" name="origin" value="https://redis.io/docs/latest/operate/rs/7.4/references/cli-utilities/rladmin/cluster/recover/"/>
<div class="flex flex-row justify-between">
<div class="grid justify-center">
<span class="font-mono">
RATE THIS PAGE
</span>
<div class="star-rating">
<input id="5-stars" name="rating" onchange="document.querySelector('#feedback-form').classList.remove('hidden')" type="radio" value="5"/>
<label class="star" for="5-stars">
★
</label>
<input id="4-stars" name="rating" onchange="document.querySelector('#feedback-form').classList.remove('hidden')" type="radio" value="4"/>
<label class="star" for="4-stars">
★
</label>
<input id="3-stars" name="rating" onchange="document.querySelector('#feedback-form').classList.remove('hidden')" type="radio" value="3"/>
<label class="star" for="3-stars">
★
</label>
<input id="2-stars" name="rating" onchange="document.querySelector('#feedback-form').classList.remove('hidden')" type="radio" value="2"/>
<label class="star" for="2-stars">
★
</label>
<input id="1-stars" name="rating" onchange="document.querySelector('#feedback-form').classList.remove('hidden')" type="radio" value="1"/>
<label class="star" for="1-stars">
★
</label>
</div>
</div>
<a class="font-mono no-underline" href="#">
Back to top ↑
</a>
</div>
<div class="hidden" id="feedback-form">
<div class="grid gap-2">
<textarea class="p-2 mt-1 block w-full h-24 border border-opacity-50 border-redis-ink-900 rounded-md" name="comment" placeholder="Why did you choose this rating?" rows="3"></textarea>
<button class="font-mono button text-redis-ink-900 border border-solid border-transparent bg-redis-red-500 hover:bg-redis-red-600 focus:bg-red-600 focus:ring-red-600; w-min justify-self-end" type="submit">
Submit
</button>
</div>
</div>
</form>
<script>
document.addEventListener("DOMContentLoaded", function() {
const form = document.querySelector("#page-feedback");
form.addEventListener("submit", function(event) {
event.preventDefault();
var xhr = new XMLHttpRequest();
var url = "\/docusight\/api\/rate";
var params = new URLSearchParams(new FormData(form));
xhr.open("POST", url, true);
xhr.setRequestHeader("Content-Type", "application/x-www-form-urlencoded");
xhr.onreadystatechange = function() {
if (xhr.readyState === 4 && xhr.status === 200) {
const responseData = JSON.parse(xhr.responseText);
const responseMessage = responseData.response;
const newText = document.createTextNode(responseMessage);
form.parentNode.replaceChild(newText, form);
}
};
xhr.send(params);
});
});
</script>
</section>
|
End of preview. Expand
in Dataset Viewer.
No dataset card yet
New: Create and edit this dataset card directly on the website!
Contribute a Dataset Card- Downloads last month
- 3