You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have just loaded in my ldap db to ldapjs-riak however it stopped loading halfway through. Then when i tried even a basic search it failed.
When I repeated the search on the command line using curl I noticed the error appears to be that when you have keys set to true, you hit a max buffer in riak, but if you change it to streams then it works ok.
curl -v http://127.0.0.1:8098/riak/ufds?keys=true&props=false -H "Accept: text/plain"
curl: (27) Avoided giant realloc for header (max is 102400)!
I looked to just change this in the nodejs under line 184 of riak.js, this however blew up with the following reply to an ldapsearch call:
text: riak failure: Unexpected token {
I am guessing what ever calls the search does not handle a stream and is looking for a single reply ? but I am not sure where to look to help update this to handle streams and a larger payload.
Regards
Mark
The text was updated successfully, but these errors were encountered:
Sorry - I've abandoned this project for some time :\ -- internally we switched to using a custom sharded postgres system for the backend (we eventually got to where we really needed strong consistency).
Sorry - I've abandoned this project for some time :\ -- internally we switched to using a custom sharded postgres system for the backend (we eventually got to where we really needed strong consistency).
Reply to this email directly or view it on GitHub: #6 (comment)
Hi,
I have just loaded in my ldap db to ldapjs-riak however it stopped loading halfway through. Then when i tried even a basic search it failed.
When I repeated the search on the command line using curl I noticed the error appears to be that when you have keys set to true, you hit a max buffer in riak, but if you change it to streams then it works ok.
curl -v http://127.0.0.1:8098/riak/ufds?keys=true&props=false -H "Accept: text/plain"
curl: (27) Avoided giant realloc for header (max is 102400)!
curl -v http://127.0.0.1:8098/riak/ufds?keys=stream&props=false -H "Accept: text/plain"
I looked to just change this in the nodejs under line 184 of riak.js, this however blew up with the following reply to an ldapsearch call:
text: riak failure: Unexpected token {
I am guessing what ever calls the search does not handle a stream and is looking for a single reply ? but I am not sure where to look to help update this to handle streams and a larger payload.
Regards
Mark
The text was updated successfully, but these errors were encountered: