Hi Vishal, the sequence is going to be as follows:
during the time of the partition / node loss you are going to see timeouts.
Once the partition has been marked as unavailable you will see AEROSPIKE_ERR_CLUSTER in the following circumstances:
- Partition is unavailable but client has not got new partition map, Aerospike C client versions 4.4.1 and lower
- Partition is unavailable and Aerospike C client version >=4.5 no other node has claimed partition ownership and node is running.
In Aerospike C Client 4.4.1 you can get AEROSPIKE_ERR_CLIENT once the partition has been marked as unavailable and the clients have new partition maps. In these versions, if a node did not claim ownership of a partition (due to it being unavailable) the entry would be removed from the partition map.