Confusing Behavior of client.info('statistics') on Cluster

[aerospike]

Confusing Behavior of client.info('statistics') on Cluster

[jhecking]

The info method works as designed, i.e. it returns the requested info per each cluster node through the callback method as soon it is received by the client. Note that the method also has an additional, 2nd callback, which is called once all the nodes have responded:

Client.prototype.info = function (request, host, policy, infoCb, doneCb) { ... }

See the API docs for the full method signature.

But I get how this behavior be a bit unexpected and that for many use cases it would be more convenient to have all the info returned in a single callback. I'll consider this a feature request for a future update. A pull request would be welcome as well. :-)

[GayathriKaliyamoorthy]

Hi @woozyking

Are you still facing the issue, I tried to reproduce this and could not. Please do share the code snippet if you are facing this issue.

Thanks

[woozyking]

@GayathriKaliyamoorthy I think the code snippet would still be the same I posted above. If it can no longer be reproduced by you using async library, then this should be good to be closed.

I no longer do this check though on our Aerospike cluster, but just a simple connectivity test.

To me client.info('statistics') seemed more appropriate to be client.on('statistics', function(...) {...}) with the original behavior I posted this issue about, at least less confusing. I'm not entirely sure about the new behavior now, but I appreciate your help.

[ameykpatil]

I recently faced the same issue (with node.js client version 2.2.0)
I wanted a count of records in a set, so I was calling
client.info('sets/test/testset', callback) (& then parsing to get n_objects)
I was getting callback already called error when using the multi-node cluster but was working fine on a single node cluster.

[jhecking]

I've added a new Client#infoAll method, which queries all the cluster nodes and returns the results in a single callback method call. This will be included in the next release, which is tentatively scheduled for next week.