# Everest Mysql unable scale down from 3 node to 1 **URL:** \ **Category:** Percona Everest\ **Tags:** mysql\ **Created:** [July 18, 2024, 10:13pm UTC](https://forums.percona.com/t/everest-mysql-unable-scale-down-from-3-node-to-1/31698 "2024-07-18T22:13:14Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![benpat](https://avatars.discourse-cdn.com/v4/letter/b/7ea924/32.png) [@benpat](https://forums.percona.com/u/benpat)\ **Post date:** [July 18, 2024, 10:13pm UTC](https://forums.percona.com/t/everest-mysql-unable-scale-down-from-3-node-to-1/31698/1 "2024-07-18T22:13:14Z")
Deployed test cluster with 3node and unable to scale down to 1. `Error: Cannot scale down 3 node cluster to 1. The operation is not supported` Everest v1.0.1 DATABASE SUMMARY 1. Basic Information Namespace: everest-dev Type: MySQL Name: sql-mysql-test Version: 8.0.36-28.1 Storage class: standard-rwo 2. Resources Number of nodes: 1 CPU: 0.6 CPU Memory: 0.512 GB Disk: 2 GB 3. Backups Backups disabled PITR Disabled 4. Advanced Configurations External access enabled Database engine parameters set 5. Monitoring Disabled ---
**Author:** ![matthewb](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/matthewb/32/34_2.png) [@matthewb](https://forums.percona.com/u/matthewb)\ **Post date:** [July 19, 2024, 12:10am UTC](https://forums.percona.com/t/everest-mysql-unable-scale-down-from-3-node-to-1/31698/2 "2024-07-19T00:10:50Z")
Hello @benpat, As you can see from the message, such action is not supported. You cannot have a highly available database system with only 1 node. Everest prevents you from deploying such an unreliable configuration. If you can explain in details why you need such a deployment, I can forward this on to the Everest team as a feature request. ---
**Author:** ![daniil.bazhenov](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/daniil.bazhenov/32/62_2.png) [@daniil.bazhenov](https://forums.percona.com/u/daniil.bazhenov)\ **Post date:** [July 19, 2024, 6:23am UTC](https://forums.percona.com/t/everest-mysql-unable-scale-down-from-3-node-to-1/31698/3 "2024-07-19T06:23:30Z")
You can create a new MySQL database with a single node from the backup. ---
**Author:** ![benpat](https://avatars.discourse-cdn.com/v4/letter/b/7ea924/32.png) [@benpat](https://forums.percona.com/u/benpat)\ **Post date:** [July 19, 2024, 12:44pm UTC](https://forums.percona.com/t/everest-mysql-unable-scale-down-from-3-node-to-1/31698/4 "2024-07-19T12:44:29Z")
In event of development system, users may not want 3node or 2node just a single node to save on resource. ---
**Author:** ![matthewb](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/matthewb/32/34_2.png) [@matthewb](https://forums.percona.com/u/matthewb)\ **Post date:** [July 19, 2024, 1:51pm UTC](https://forums.percona.com/t/everest-mysql-unable-scale-down-from-3-node-to-1/31698/5 "2024-07-19T13:51:01Z")
Hello @benpat, this post has gained some visibility from our Everest product manager. Scaling down to 1 server is on our roadmap. The best I can give is “coming soon”. ---
**Author:** ![daniil.bazhenov](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/daniil.bazhenov/32/62_2.png) [@daniil.bazhenov](https://forums.percona.com/u/daniil.bazhenov)\ **Post date:** [July 19, 2024, 2:14pm UTC](https://forums.percona.com/t/everest-mysql-unable-scale-down-from-3-node-to-1/31698/6 "2024-07-19T14:14:17Z")
> [@benpat](#): > > In event of development system, users may not want 3node or 2node just a single node to save on resource. If backup of the database with 3 nodes is enabled, you can restore the backup to a new database with 1 node, this may work for development.