# Stale Data Comes Up on Node restart temporarily

**URL:** <https://discuss.aerospike.com/t/stale-data-comes-up-on-node-restart-temporarily/3966>\
**Category:** How Aerospike Works\
**Created:** [March 21, 2017, 6:38am UTC](https://discuss.aerospike.com/t/stale-data-comes-up-on-node-restart-temporarily/3966 "2017-03-21T06:38:36Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Arpit\_Wanchoo](https://avatars.discourse-cdn.com/v4/letter/a/bbce88/32.png) [@Arpit\_Wanchoo](https://discuss.aerospike.com/u/Arpit_Wanchoo)\
**Post date:** [March 21, 2017, 6:38am UTC](https://discuss.aerospike.com/t/stale-data-comes-up-on-node-restart-temporarily/3966/1 "2017-03-21T06:38:36Z")

</div>

Scenario:

1. In a 3 node cluster with replication factor 2, a node was stopped.
2. Some updates were pushed to all the keys in a given set
3. Down node was started again with cold start empty false.
4. When down node was up, i connected to aerospike via aql and checked the keys of that set, and saw stale data for 1/3rd of keys.
5. After some time when I queried, the data was fine which means eventually it was showing consistent data

Is this behaviour as expected? Can the cluster serve stale data for some period of time when a node is restarted? How is this thing handled?

---

<div class="post-metadata">

**Author:** ![shakthimaan](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.aerospike.com/shakthimaan/32/714_2.png) [@shakthimaan](https://discuss.aerospike.com/u/shakthimaan)\
**Post date:** [March 21, 2017, 7:45am UTC](https://discuss.aerospike.com/t/stale-data-comes-up-on-node-restart-temporarily/3966/2 "2017-03-21T07:45:14Z")

</div>

Which version of Aerospike are you using, and on which OS?

---

<div class="post-metadata">

**Author:** ![Arpit\_Wanchoo](https://avatars.discourse-cdn.com/v4/letter/a/bbce88/32.png) [@Arpit\_Wanchoo](https://discuss.aerospike.com/u/Arpit_Wanchoo)\
**Post date:** [March 21, 2017, 7:49am UTC](https://discuss.aerospike.com/t/stale-data-comes-up-on-node-restart-temporarily/3966/3 "2017-03-21T07:49:37Z")

</div>

We are using 3.9.1 version of aerospike OS is Linux (Amazon Linux AMI [Amazon Linux AMI 2016.03 Release Notes](https://aws.amazon.com/amazon-linux-ami/2016.03-release-notes/) )

---

<div class="post-metadata">

**Author:** ![meher](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.aerospike.com/meher/32/1644_2.png) [@meher](https://discuss.aerospike.com/u/meher)\
**Post date:** [March 21, 2017, 4:00pm UTC](https://discuss.aerospike.com/t/stale-data-comes-up-on-node-restart-temporarily/3966/7 "2017-03-21T16:00:10Z")

</div>

You may want to read about read consistency levels to understand how this works and adjust the policy on your client, or server, based on your needs:

Here are the details:

> **[Architecture overview](https://aerospike.com/docs/database/learn/architecture)**
>
> Aerospike's architecture includes a client layer, a distribution layer that manages communication, and a data storage layer for fast retrieval.

And this is one article that describes how this can be overwritten at the server level:

[https://discuss.aerospike.com/t/understanding-consistency-level-overrides/711](https://discuss.aerospike.com/t/understanding-consistency-level-overrides/711)