Antoine,
I don't have 1.0.0pre2 installed anywhere handy at the moment, but I do have
pre3 installed and I tested with eleveldb and it works fine for me. Could you
download pre3 and see if that resolves the issue for you? Thanks.
Kelly
On Sep 16, 2011, at 8:08 AM, t3h wrote:
> Hello all,
>
> I got these errors after having upgraded to riak-1.0.0pre2 when using list
> buckets:
>
> {ok, C} = riak:local_client().
> C:list_buckets().
>
> gives:
>
> 2011-09-16 15:01:32.613 [error] <0.971.0> gen_server <0.971.0> terminated
> with reason: bad return value: {break,{buffer,[ ...part of my list of
> buckets... ],#Fun<riak_kv_vnode.11.54298152>,999,4}}
> 2011-09-16 15:01:32.711 [error] <0.971.0> CRASH REPORT Process [] with 0
> neighbours crashed with reason: bad return value: {break,{buffer,[...other
> part of my list of buckets... ],#Fun<riak_kv_vnode.11.54298152>,999,4}}
> 2011-09-16 15:01:32.767 [error] <0.427.0> gen_server <0.427.0> terminated
> with reason: bad return value: {break,{buffer,[...other part of my list of
> buckets... ],#Fun<riak_kv_vnode.11.54298152>,999,10}}
> 2011-09-16 15:01:32.842 [error] <0.427.0> CRASH REPORT Process [] with 0
> neighbours crashed with reason: bad return value: {break,{buffer,[...other
> part of my list of buckets... ],#Fun<riak_kv_vnode.11.54298152>,999,10}}
> 2011-09-16 15:01:32.937 [error] <0.426.0> Supervisor poolboy_sup had child
> riak_core_vnode_worker started with
> {riak_core_vnode_worker,start_link,undefined} at <0.427.0> exit with reason
> bad return value: {break,{buffer,[...other part of my list of buckets...
> ],#Fun<riak_kv_vnode.11.54298152>,999,10}} in context child_terminated
>
> and so on for each poolboy supervisor...
>
> I tested it against a new empty cluster to be sure not to mix legacy key
> listing with new key listing.
> I use the eleveldb_backend and objects stored have indexes.
> I can list the keys in a bucket without any issue.
> Am I missing something I should have changed upgrading to 1.0.0?
>
> As well, riak objects used to have x-riak-index-$bucket and x-riak-index-$key
> indexes when I first attempted to use secondary indexes. I do not see this
> anymore. What is the reason for this change and should I be careful not to
> override any "built-in" indexes when writting my index headers (using the PBC
> api)?
>
> Thanks,
> Antoine
>
>
> _______________________________________________
> riak-users mailing list
> [email protected]
> http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
_______________________________________________
riak-users mailing list
[email protected]
http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
