---
title: "Downgrade from Database 7.1.0 to 7.0.0"
description: "Guide for downgrading Aerospike Database from version 7.1.0 to 7.0.0 with essential configuration changes."
---

# Downgrade from Database 7.1.0 to 7.0.0

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

## Configuration changes

1.  Replace the [`flush-size`](https://aerospike.com/docs/database/reference/config#namespace__flush-size) namespace configuration parameter with an explicit `write-block-size 8M`. In Database 7.1.0 and later the [`write-block-size`](https://aerospike.com/docs/database/reference/config#namespace__write-block-size) was pinned to 8MiB. To reduce it, [zeroize the drives](https://support.aerospike.com/s/article/How-do-I-change-the-write-block-size-configuration) on each downgraded node before restarting it. If you do not explicitly adjust the `write-block-size` correctly, it will implicitly be assigned a 1MiB value, which is smaller than the 8MiB storage. This will manifest in the following error on startup:
    
    ```plaintext
    May 19 2024 17:26:14 GMT: INFO (drv_ssd): (drv_ssd.c:1056) /test/dev/xvdf has 5120 wblocks of size 1048576 May 19 2024 17:26:14 GMT: CRITICAL (drv_ssd): (drv_ssd.c:2390) /test/dev/xvdf: can't change write-block-size from 8388608 to 1048576
    ```
    
2.  Replace your [`post-write-cache`](https://aerospike.com/docs/database/reference/config#namespace__post-write-cache) namespace configuration parameter with a [`post-write-queue`](https://aerospike.com/docs/database/reference/config#namespace__post-write-queue). If you keep your `write-block-size` at 8MiB, you can divide the `post-write-cache` by 8MiB to get the number of write-blocks to cache.
    
3.  Remove any configuration parameters [added in Database 7.1.0](https://aerospike.com/docs/database/release/7-1) from your configuration file: `default-password-file`, `indexes-memory-budget`, `evict-indexes-memory-pct`, `default-read-touch-ttl-pct`, `auto-revive`, `tls-refresh-period`, `batch-max-requests`.