创建主动-主动数据库 （REAADB）

适用于 Kubernetes 的 Redis Enterprise
注意：
此功能在 6.4.2-6 及更高版本中正式发布受支持。其中一些功能在 6.4.2-4 和 6.4.2-5 中作为预览版提供。请升级到 6.4.2-6 以获取完整的正式发布功能和错误修复。

先决条件

要创建主动-主动数据库，请确保您已完成以下所有步骤，并收集了每个步骤下方列出的信息。

  1. 配置准入控制器和 ValidatingWebhook。

    注意：
    默认情况下，这些选项在通过 OpenShift OperatorHub 创建的集群上安装和启用。

  2. 创建两个或多个具有足够内存资源的 RedisEnterpriseCluster （REC） 自定义资源。

    • 每个 REC 的名称 （<rec-name>)
    • 每个 REC 的命名空间 （<rec-namespace>)

  3. 配置 RECingressOrRoutes田并创建 DNS 记录。

    • REC API 主机名 （api-<rec-name>-<rec-namespace>.<subdomain>)
    • 数据库主机名后缀 （-db-<rec-name>-<rec-namespace>.<subdomain>)

  4. 准备参与的集群

    • RERC 名称 （<rerc-name>)
    • RERC 密钥名称 （redis-enterprise-<rerc-name>)

有关本文中使用的示例值的列表，请参阅 Example values 部分。

创造RedisEnterpriseRemoteCluster资源

  1. 创建一个RedisEnterpriseRemoteCluster（RERC） 自定义资源文件。

    以下是两个参与集群的 RERC 资源示例。替换您自己的值以创建自己的资源。

    示例 RERC （rerc-ohare） 对于名为rec-chicago在命名空间中ns-illinois:

    apiVersion: app.redislabs.com/v1alpha1
kind: RedisEnterpriseRemoteCluster
metadata:
  name: rerc-ohare
spec:
  recName: rec-chicago
  recNamespace: ns-illinois
  apiFqdnUrl: api-rec-chicago-ns-illinois.example.com
  dbFqdnSuffix: -db-rec-chicago-ns-illinois.example.com
  secretName: redis-enterprise-rerc-ohare

    Example RERC (rerc-raegan) for the REC named rec-arlington in the namespace ns-virginia:

    apiVersion: app.redislabs.com/v1alpha1
kind: RedisEnterpriseRemoteCluster
metadata:
  name: rerc-reagan
spec:
  recName: rec-arlington
  recNamespace: ns-virginia
  apiFqdnUrl: test-example-api-rec-arlington-ns-virginia.example.com
  dbFqdnSuffix: -example-cluster-rec-arlington-ns-virginia.example.com
  secretName: redis-enterprise-rerc-reagan

    For more details on RERC fields, see the RERC API reference.

  2. Create a Redis Enterprise remote cluster from each RERC custom resource file.

    kubectl create -f <rerc-file>

  3. Check the status of your RERC. If STATUS is Active and SPEC STATUS is Valid, then your configurations are correct.

    kubectl get rerc <rerc-name>

    The output should look similar to:

    kubectl get rerc rerc-ohare

NAME        STATUS   SPEC STATUS   LOCAL
rerc-ohare   Active   Valid         true

    In case of errors, review the RERC custom resource events and the Redis Enterprise operator logs.

Create RedisEnterpriseActiveActiveDatabase resource

  1. Create a RedisEnterpriseActiveActiveDatabase (REAADB) custom resource file meeting the naming requirements and listing the names of the RERC custom resources created in the last step.

    Naming requirements:

    • less than 63 characters
    • contains only lowercase letters, numbers, or hyphens
    • starts with a letter
    • ends with a letter or digit

    Example REAADB named reaadb-boeing linked to the REC named rec-chicago with two participating clusters and a global database configuration with shard count set to 3:

    apiVersion: app.redislabs.com/v1alpha1
kind: RedisEnterpriseActiveActiveDatabase
metadata:
  name: reaadb-boeing
spec:
  globalConfigurations:
    databaseSecretName: <my-secret>
    memorySize: 200MB
    shardCount: 3
  participatingClusters:
      - name: rerc-ohare
      - name: rerc-reagan
    Note:
    Sharding is disabled on Active-Active databases created with a shardCount of 1. Sharding cannot be enabled after database creation.

    For more details on RERC fields, see the RERC API reference.

  2. Create a Redis Enterprise Active-Active database from the REAADB custom resource file.

    kubectl create -f <reaadb-file>

  3. Check the status of your RERC. If STATUS is Active and SPEC STATUS is Valid, your configurations are correct.

    kubectl get reaadb <reaadb-name>

    The output should look similar to:

    kubectl get reaadb reaadb-boeing

NAME              STATUS   SPEC STATUS   LINKED REDBS   REPLICATION STATUS
reaadb-boeing     active   Valid                        up

    In case of errors, review the REAADB custom resource events and the Redis Enterprise operator logs.

Example values

This article uses the following example values:

Example cluster 1

  • REC name: rec-chicago
  • REC namespace: ns-illinois
  • RERC name: rerc-ohare
  • RERC secret name: redis-enterprise-rerc-ohare
  • API FQDN: api-rec-chicago-ns-illinois.example.com
  • DB FQDN suffix: -db-rec-chicago-ns-illinois.example.com

Example cluster 2

  • REC name: rec-arlington
  • REC namespace: ns-virginia
  • RERC name: rerc-raegan
  • RERC secret name: redis-enterprise-rerc-reagan
  • API FQDN: api-rec-arlington-ns-virginia.example.com
  • DB FQDN suffix: -db-rec-arlington-ns-virginia.example.com
RATE THIS PAGE
Back to top ↑