Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Query fails if one or more cluster nodes do not have records in the set #77

Closed
jhecking opened this issue Mar 29, 2019 · 0 comments
Closed
Labels
Milestone

Comments

@jhecking
Copy link
Contributor

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

@jhecking jhecking added the bug label Mar 29, 2019
@jhecking jhecking added this to the v2.9.1 milestone Mar 29, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant