error parsing Link headers in node.js when getting a bucket

Rick Olson technoweenie at
Mon May 10 03:29:24 EDT 2010

Hey guys, I enjoyed going through the Riak Fast Track, so I wrote a
node.js library for it:

I ran into one problem though: node.js choked on the Link headers when
getting a bucket's properties.  I realize this is a node.js bug, but I
found it kind of odd:

  $ curl -i
  HTTP/1.1 200 OK
  Vary: Accept-Encoding
  Server: MochiWeb/1.1 WebMachine/1.6 (eat around the stinger)
  Link: </riak/goog/2006-05-22>; riaktag="contained",
</riak/goog/2006-05-04>; riaktag="contained", ETC

If there are 1400 links, node.js has problems.  If there are several
thousand, even curl starts having problems:

  curl: (27) Avoided giant realloc for header (max is 102400)!

So, if I grab the contents of a bucket to get the list of keys, it
also sends a giant Link header pointing to each key?  The Link header
ends up being much larger than the response body.  Is it really
necessary to point to each resource, when the body contains an array
of keys?

At any rate, here's how the map reduce API looks while implementing
the sample functions from the fast track:

Rick Olson

More information about the riak-users mailing list