# Configuring Cluster with different Nodes

**URL:** <https://discuss.aerospike.com/t/configuring-cluster-with-different-nodes/3846>\
**Category:** Configuration\
**Created:** [February 10, 2017, 3:30pm UTC](https://discuss.aerospike.com/t/configuring-cluster-with-different-nodes/3846 "2017-02-10T15:30:02Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![cracken](https://avatars.discourse-cdn.com/v4/letter/c/5e9695/32.png) [@cracken](https://discuss.aerospike.com/u/cracken)\
**Post date:** [February 10, 2017, 3:30pm UTC](https://discuss.aerospike.com/t/configuring-cluster-with-different-nodes/3846/1 "2017-02-10T15:30:03Z")

</div>

I am trying to create a cluster with two nodenode with different dimensions of RAM and SSD. Now it happen that when aerospike execute migration of data and try load balancing, it always migrate data also if the second node has end its memory. So I think that for aerospike the cluster must be made up of nodes which capacity is available for **|DB| / N** data

where |DB| is total Database size and N is number of nodes. Is it true? Can you set that when one nodes ends its memory (RAM or Disk) aerospike stops load balancing?

---

<div class="post-metadata">

**Author:** ![pgupta](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.aerospike.com/pgupta/32/2351_2.png) [@pgupta](https://discuss.aerospike.com/u/pgupta)\
**Post date:** [February 10, 2017, 4:30pm UTC](https://discuss.aerospike.com/t/configuring-cluster-with-different-nodes/3846/2 "2017-02-10T16:30:10Z")

</div>

You should not try to put together a cluster of differently sized nodes. All nodes should be identical in RAM and SSD. Aerospike is designed to distribute data evenly. The node with lowest RAM / SSD will start hitting the high-water-marks first and data will be evicted from that node. If you set all your records to “never expire”, you will disable eviction and then at some point hit “stop writes” on that node and Aerospike will not accept any further writes on that node. See “expiration”, “eviction” and “stop-writes” related topics on this forum and in Aerospike docs, also read on Aerospike architecture or take one of the Aeropsike Architecture webinars (free).