# Inconsistent reads during a node's start up

**URL:** <https://discuss.aerospike.com/t/inconsistent-reads-during-a-nodes-start-up/3047>\
**Category:** Operations\
**Created:** [June 8, 2016, 12:17pm UTC](https://discuss.aerospike.com/t/inconsistent-reads-during-a-nodes-start-up/3047 "2016-06-08T12:17:54Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![maxim\_ky](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.aerospike.com/maxim_ky/32/1388_2.png) [@maxim\_ky](https://discuss.aerospike.com/u/maxim_ky)\
**Post date:** [June 8, 2016, 12:17pm UTC](https://discuss.aerospike.com/t/inconsistent-reads-during-a-nodes-start-up/3047/1 "2016-06-08T12:17:54Z")

</div>

Hi guys,

I had an issue with 3.8.2 and a 5-node cluster. The scenario is following:

- Restart one node
- Write a key to the cluster while the node’s starting (before the “cake” log message)
- Try to read (not a batch) the written key and it doesn’t exist
- “Cake” appears and the key is here

Consistency levels (both) are default.

To me it looks like [Inconsistent data after simulated failure](https://discuss.aerospike.com/t/inconsistent-data-after-simulated-failure/476) Could you tell me if the given scenario is some kind of well-known behavior? What could I do to avoid such case (apart from “read-consistency: all”)? If you require any additional information please ask.

Regards

---

<div class="post-metadata">

**Author:** ![maxim\_ky](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.aerospike.com/maxim_ky/32/1388_2.png) [@maxim\_ky](https://discuss.aerospike.com/u/maxim_ky)\
**Post date:** [June 17, 2016, 4:53pm UTC](https://discuss.aerospike.com/t/inconsistent-reads-during-a-nodes-start-up/3047/2 "2016-06-17T16:53:54Z")

</div>

I’m sorry for the misleading information. The problem wasn’t due to non-existing keys, but operation timeouts (1000 ms). So I guess it could be explained by some migration overloads and/or Paxos lags.

---

<div class="post-metadata">

**Author:** ![kporter](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.aerospike.com/kporter/32/515_2.png) [@kporter](https://discuss.aerospike.com/u/kporter)\
**Post date:** [June 17, 2016, 5:35pm UTC](https://discuss.aerospike.com/t/inconsistent-reads-during-a-nodes-start-up/3047/3 "2016-06-17T17:35:29Z")

</div>

Hm, have you tried the different keys? The reason I ask is that I am curious if it matters if the key joins a primary or replica partition on the added node. If the issue varies by key, it would suggest the partition’s state plays a role here.