Hi Bryan, Thanks much for the info. We're running Riak 1.0.3. I think in our case what would've made this easier to track down would have been not having the error output cut off in the log -- since the inputs to the reduce comprised a pretty large set, the output cut off before the call trace, which appears after the dump of the inputs. It was pretty easy to track down once I narrowed down the inputs to a manageable size that still reproduced the error.
Thanks! Mat On Wed, Feb 1, 2012 at 10:53, Bryan Fink <br...@basho.com> wrote: > On Tue, Jan 31, 2012 at 1:46 PM, Matthew A. Brown <mat.a.br...@gmail.com> > wrote: >> [error] error:undef done() >> >> The error message is followed by a dump of the reduce inputs which is, >> sadly, truncated before the bit where it would give the call trace. >> >> Our Erlang reduce code does not define or reference a function done(), >> but I do note that this function is defined in riak_kv: >> >> https://github.com/basho/riak_kv/blob/master/src/riak_kv_w_reduce.erl#L163 > > The "done()" you're seeing comes from 6 lines below where you were looking: > > https://github.com/basho/riak_kv/blob/master/src/riak_kv_w_reduce.erl#L169 > > It is intended to give an idea of what stage the reduce fitting was in > when the error happened. Other strings you'll find are "reducing", > "riak_kv_w_reduce init", and "reducing handoff". > > I would be interested in knowing what version of Riak you were using > when you encountered this error message. Improving MapReduce errors > is something we're always working on. > > -Bryan _______________________________________________ riak-users mailing list riak-users@lists.basho.com http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
