# Replicas invalidated after restart

**URL:** <https://discuss.aerospike.com/t/replicas-invalidated-after-restart/3409>\
**Category:** Upgrading\
**Created:** [September 16, 2016, 5:54pm UTC](https://discuss.aerospike.com/t/replicas-invalidated-after-restart/3409 "2016-09-16T17:54:39Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![Joel\_Eidsath](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.aerospike.com/joel_eidsath/32/620_2.png) [@Joel\_Eidsath](https://discuss.aerospike.com/u/Joel_Eidsath)\
**Post date:** [September 23, 2016, 6:11pm UTC](https://discuss.aerospike.com/t/replicas-invalidated-after-restart/3409/7 "2016-09-23T18:11:11Z")

</div>

We’re using community 3.9.1.1. However it appears that this is the problem: [It looks like Node restarting make all partitions migrate](https://discuss.aerospike.com/t/it-looks-like-node-restarting-make-all-partitions-migrate/212)

> Presently, any cluster change will cause migration of all the partitions. We do not trust the sanity of existing partitions and verifying the same will be similar overhead.

From the above discussion, the behavior appears not to be version specific and has existed for a long time. Our cluster has about 5G objects and 10G replica objects, so the above doesn’t scale very well to our use case.

---

_[View the full topic](https://discuss.aerospike.com/t/replicas-invalidated-after-restart/3409)._