Query fails if one or more cluster nodes do not have records in the set
jhecking opened this issue · 0 comments
jhecking commented
If one or more nodes in the cluster do not have the set on which the query executes, those nodes will return an error with status code 2 ("record not found"). The client will then abort the query and throw a KEY_NOT_FOUND error. The client should ignore this status code and instead return the results from the remaining cluster nodes.
Ref. https://discuss.aerospike.com/t/key-not-found/6079/3
Ref. aerospike/aerospike-client-nodejs#253