Flush

To delete the data in a database without deleting the database configuration, you can flush the data from the database.

You can use the Cluster Manager UI to flush data from Active-Active databases.

{{< warning title="Data Loss Warning" >}} The flush command deletes ALL in-memory and persistence data in the database. We recommend that you [back up your database]({{< relref "/operate/rs/7.4/databases/import-export/schedule-backups.md" >}}) before you flush the data. {{< /warning >}}

Flush data from a database

From the command line, you can flush a database with the redis-cli command or with your favorite Redis client.

To flush data from a database with the redis-cli, run:

redis-cli -h <hostname> -p <portnumber> -a <password> flushall

Example:

redis-cli -h redis-12345.cluster.local -p 9443 -a xyz flushall

{{< note >}} Port 9443 is the default [port configuration]({{< relref "/operate/rs/7.4/networking/port-configurations#https://docs.redis.com/latest/rs/networking/port-configurations#ports-and-port-ranges-used-by-redis-enterprise-software" >}}). {{< /note >}}

Flush data from an Active-Active database

When you flush an Active-Active database (formerly known as CRDB), all of the replicas flush their data at the same time.

To flush data from an Active-Active database:

• Cluster Manager UI

  1. If you are using the new Cluster Manager UI, switch to the legacy admin console.

     {{<image filename="images/rs/screenshots/switch-to-legacy-ui.png" width="300px" alt="Select switch to legacy admin console from the dropdown.">}}

  2. Go to database and select the Active-Active database that you want to flush.

  3. Go to configuration and click Flush at the bottom of the page.

  4. Enter the name of the Active-Active database to confirm that you want to flush the data.

• Command line

  1. To find the ID of the Active-Active database, run:

     shCopy

     crdb-cli crdb list
     

     For example:

     shCopy

     $ crdb-cli crdb list
     CRDB-GUID                                NAME                 REPL-ID CLUSTER-FQDN
     a16fe643-4a7b-4380-a5b2-96109d2e8bca     crdb1                1       cluster1.local
     a16fe643-4a7b-4380-a5b2-96109d2e8bca     crdb1                2       cluster2.local
     a16fe643-4a7b-4380-a5b2-96109d2e8bca     crdb1                3       cluster3.local
     

  2. To flush the Active-Active database, run:

     shCopy

     crdb-cli crdb flush --crdb-guid <CRDB-GUID>
     

     The command output contains the task ID of the flush task, for example:

     shCopy

     $ crdb-cli crdb flush --crdb-guid a16fe643-4a7b-4380-a5b2-96109d2e8bca
     Task 63239280-d060-4639-9bba-fc6a242c19fc created
     ---> Status changed: queued -> started
     

  3. To check the status of the flush task, run:

     shCopy

     crdb-cli task status --task-id <Task-ID>
     

     For example:

     shCopy

     $ crdb-cli task status --task-id 63239280-d060-4639-9bba-fc6a242c19fc
     Task-ID: 63239280-d060-4639-9bba-fc6a242c19fc
     CRDB-GUID: -
     Status: finished
     

• REST API

  1. To find the ID of the Active-Active database, use [GET /v1/crdbs]({{< relref "/operate/rs/7.4/references/rest-api/requests/crdbs#get-all-crdbs" >}}):

     shCopy

     GET https://[host][:port]/v1/crdbs
     

  2. To flush the Active-Active database, use [PUT /v1/crdbs/{guid}/flush]({{< relref "/operate/rs/7.4/references/rest-api/requests/crdbs/flush#put-crdbs-flush" >}}):

     shCopy

     PUT https://[host][:port]/v1/crdbs/<guid>/flush
     

     The command output contains the task ID of the flush task.

  3. To check the status of the flush task, use [GET /v1/crdb_tasks]({{< relref "/operate/rs/7.4/references/rest-api/requests/crdb_tasks#get-crdb_task" >}}):

     shCopy

     GET https://[host][:port]/v1/crdb_tasks/<task-id>