{"action":"created","issue":{"url":"https://api.github.com/repos/aerospike/aerospike-client-nodejs/issues/130","repository_url":"https://api.github.com/repos/aerospike/aerospike-client-nodejs","labels_url":"https://api.github.com/repos/aerospike/aerospike-client-nodejs/issues/130/labels{/name}","comments_url":"https://api.github.com/repos/aerospike/aerospike-client-nodejs/issues/130/comments","events_url":"https://api.github.com/repos/aerospike/aerospike-client-nodejs/issues/130/events","html_url":"https://github.com/aerospike/aerospike-client-nodejs/issues/130","id":156090812,"number":130,"title":"Max node/event loop [...] async connections would be exceeded: 300","user":{"login":"blitzprog","id":438936,"avatar_url":"https://avatars.githubusercontent.com/u/438936?v=3","gravatar_id":"","url":"https://api.github.com/users/blitzprog","html_url":"https://github.com/blitzprog","followers_url":"https://api.github.com/users/blitzprog/followers","following_url":"https://api.github.com/users/blitzprog/following{/other_user}","gists_url":"https://api.github.com/users/blitzprog/gists{/gist_id}","starred_url":"https://api.github.com/users/blitzprog/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/blitzprog/subscriptions","organizations_url":"https://api.github.com/users/blitzprog/orgs","repos_url":"https://api.github.com/users/blitzprog/repos","events_url":"https://api.github.com/users/blitzprog/events{/privacy}","received_events_url":"https://api.github.com/users/blitzprog/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":3,"created_at":"2016-05-21T08:23:28Z","updated_at":"2016-05-24T10:25:06Z","closed_at":null,"body":"I'm getting the error `Unhandled rejection AerospikeError: Max node/event loop [...] async connections would be exceeded: 300` on scan operations.\r\nHow can I overwrite this limit or fix the problem?"},"comment":{"url":"https://api.github.com/repos/aerospike/aerospike-client-nodejs/issues/comments/221228291","html_url":"https://github.com/aerospike/aerospike-client-nodejs/issues/130#issuecomment-221228291","issue_url":"https://api.github.com/repos/aerospike/aerospike-client-nodejs/issues/130","id":221228291,"user":{"login":"jhecking","id":1900876,"avatar_url":"https://avatars.githubusercontent.com/u/1900876?v=3","gravatar_id":"","url":"https://api.github.com/users/jhecking","html_url":"https://github.com/jhecking","followers_url":"https://api.github.com/users/jhecking/followers","following_url":"https://api.github.com/users/jhecking/following{/other_user}","gists_url":"https://api.github.com/users/jhecking/gists{/gist_id}","starred_url":"https://api.github.com/users/jhecking/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jhecking/subscriptions","organizations_url":"https://api.github.com/users/jhecking/orgs","repos_url":"https://api.github.com/users/jhecking/repos","events_url":"https://api.github.com/users/jhecking/events{/privacy}","received_events_url":"https://api.github.com/users/jhecking/received_events","type":"User","site_admin":false},"created_at":"2016-05-24T10:25:06Z","updated_at":"2016-05-24T10:25:06Z","body":"The scan implementation in Aerospike Node.js v1.x is very inefficient. Despite the asynchronous interface it's actually using synchronous, i.e. blocking I/O internally. Scan operations in v1.x often block the event loop and can cause excessive memory consumption. I've described this in much more detail in a recent [blog post](http://www.aerospike.com/blog/win-win-greater-speed-and-lower-latency-with-aerospikes-node-js-client-v2-0/).\r\n\r\nSingle key operations in v1 — such as PUT — use synchronous, blocking I/O as well. They are executed in libuv worker threads. Therefore the parallelism is limited by the size of the libuv threadpool, which is 4 by default."}}
{"actor":{"display_login":"jhecking"}}