AFAIK you need to make sure that all nodes are upgraded first, and then turn
legacy_keylisting off. The crash you see is not (necessarily) related to
keylisting, but MapReduce. I hope to push out a new version of the Ruby
client in the next few weeks to support the new features.
On Sun, Sep 11, 2011 at 3:38 AM, Ryan Caught <rcau...@gmail.com> wrote:
> Hi,
> I'm testing out a rolling upgrade with 1.0 pre2 and found that when I turn
> off legacy_keylisting Riak crashes on me. Things work fine when
> legacy_keylisting is turned on.
>
> Here is what I found in the crash log.
>
> 2011-09-11 07:15:44 =SUPERVISOR REPORT====
>> Supervisor: {local,riak_pipe_fitting_sup}
>> Context: child_terminated
>> Reason: killed
>> Offender:
>> [{pid,<0.2725.0>},{name,undefined},{mfargs,{riak_pipe_fitting,start_link,undefined}},{restart_type,temporary},{shutdown,2000},{child_type,worker}]
>
>
> I'm using Ubuntu with Ripple (0.9.5).
>
>
> Ryan
>
> _______________________________________________
> riak-users mailing list
> riak-users@lists.basho.com
> http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
>
>
--
Sean Cribbs <s...@basho.com>
Developer Advocate
Basho Technologies, Inc.
http://www.basho.com/
_______________________________________________
riak-users mailing list
riak-users@lists.basho.com
http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
