---
title: "Downgrade from Database 7.2.0"
description: "Instructions for downgrading Aerospike Database 7.2.0 and managing the active-rack parameter."
---

# Downgrade from Database 7.2.0

> For the complete documentation index see: [llms.txt](https://aerospike.com/docs/llms.txt)
> 
> All documentation pages available in markdown.

This page provides important information about performing a downgrade from Database 7.2.0.

## Overview

If [`active-rack`](https://aerospike.com/docs/database/reference/config#namespace__active-rack) has been enabled in Database 7.2.0, it must be disabled on all nodes before downgrading.

::: caution
If you are using [SC mode](https://aerospike.com/docs/database/manage/namespace/consistency) and have not updated the roster with the `active-rack` removed, migrations will fail because roster parsing differs. As you downgrade through a rolling restart, the cluster node will throw the following warnings:

```plaintext
WARNING (roster): (roster_ee.c:151) illegal node id 0

WARNING (roster): (roster_ee.c:237) {test} invalid node list M100|bb...01|
```
:::

### Disable active rack for Available and Partition-tolerant (AP) mode

1.  Use `asadm` to disable `active-rack` in AP namespaces:
    
    ```plaintext
    Admin> enable
    
    Admin+> manage config namespace ns-name param active-rack to 0
    
    ~Set Namespace Param active-rack to 0~
    
             Node|Response
    
    10.1.0.1:3000|ok
    
    10.1.0.2:3000|ok
    
    10.1.0.3:3000|ok
    
    Number of rows: 3
    ```
    
2.  Recluster for your `active-rack` to take effect.
    
    ```plaintext
    Admin+> manage recluster
    
    Successfully started recluster
    ```
    
3.  Remove the `active-rack` line from `aerospike.conf` on all nodes before downgrading from Database 7.2.0.
    

### Disable active rack for Strong Consistency (SC) mode

1.  Use `asadm` to disable `active-rack` in SC namespaces:
    
    ```plaintext
    Admin> enable
    
    Admin+> manage config namespace ns-name param active-rack to 0
    
    ~Set Namespace Param active-rack to 0~
    
             Node|Response
    
    10.1.0.1:3000|ok
    
    10.1.0.2:3000|ok
    
    10.1.0.3:3000|ok
    
    Number of rows: 3
    ```
    
2.  Recluster for your `active-rack` to take effect.
    
    ```plaintext
    Admin+> manage recluster
    
    Successfully started recluster
    ```
    
3.  Modify the pending roster changes.
    
    ```plaintext
    Admin+> manage roster stage observed ns ns-name
    
    Pending roster now contains observed nodes.
    ```
    
4.  Recluster again for changes to take effect.
    
    ```plaintext
    Admin+> manage recluster
    
    Successfully started recluster
    ```
    
5.  Remove the `active-rack` line from `aerospike.conf` on all nodes before downgrading from Database 7.2.0.