Kelly, I tried checking out the pre3 tag and with a subset of the data I used before. If I try to add a few keys (simple empty objects) it's ok I can list the buckets. The error arise for example after the following objects have been saved:
curl -v http://localhost:8098/riak/internal:schemas:schemas/loaded:1316018615776810 * About to connect() to localhost port 8098 (#0) * Trying 127.0.0.1... connected * Connected to localhost (127.0.0.1) port 8098 (#0) > GET /riak/internal:schemas:schemas/loaded:1316018615776810 HTTP/1.1 > User-Agent: curl/7.21.3 (x86_64-pc-linux-gnu) libcurl/7.21.3 OpenSSL/0.9.8o zlib/1.2.3.4 libidn/1.18 > Host: localhost:8098 > Accept: */* > < HTTP/1.1 200 OK < X-Riak-Vclock: a85hYGBgzGDKBVIcypz/fvoVp8/OYEpkzGNlUH3y/DhfFgA= < X-Riak-Meta-user_id: idmog < X-Riak-Meta-source: asusci7-loader < X-Riak-Meta-occured_at: 1316018615776810 < X-Riak-Meta-noticed_at: 1316018615776812 < X-Riak-Meta-mogbox_id: asusci7 < X-Riak-Meta-event_type_id: loaded < X-Riak-Meta-event_type_cat: internal < X-Riak-Meta-client_ip: 192.168.0.10 < X-Riak-Meta-aggr_schema_id: schemas < X-Riak-Meta-aggr_id: schemas < x-riak-index-occured_at_int: 1316018615776810 < x-riak-index-noticed_at_int: 1316018615776812 < x-riak-index-mogbox_id_bin: asusci7 < x-riak-index-event_type_id_bin: loaded < x-riak-index-event_type_cat_bin: internal < x-riak-index-aggr_schema_id_bin: schemas < x-riak-index-aggr_id_bin: schemas < Vary: Accept-Encoding < Server: MochiWeb/1.1 WebMachine/1.9.0 (participate in the frantic) < Link: </riak/schemas/schemas>; riaktag="aggregate", </riak/internal%3Aschemas%3Aschemas>; rel="up" < Last-Modified: Fri, 16 Sep 2011 15:15:49 GMT < ETag: "51h3q7RjTNaHWYpO4P0MJj" < Date: Fri, 16 Sep 2011 15:20:17 GMT < Content-Type: application/x-erlang-term < Content-Length: 353 and curl -v http://localhost:8098/riak/schemas/schemas * About to connect() to localhost port 8098 (#0) * Trying 127.0.0.1... connected * Connected to localhost (127.0.0.1) port 8098 (#0) > GET /riak/schemas/schemas HTTP/1.1 > User-Agent: curl/7.21.3 (x86_64-pc-linux-gnu) libcurl/7.21.3 OpenSSL/0.9.8o zlib/1.2.3.4 libidn/1.18 > Host: localhost:8098 > Accept: */* > < HTTP/1.1 200 OK < X-Riak-Vclock: a85hYGBgzGDKBVIcypz/fvoVp8/IYEpkzGNlUHny/DhfFgA= < X-Riak-Meta-$rev: AUEOhgAHc9MSA2MHOvC-M4uLIDc= < Vary: Accept-Encoding < Server: MochiWeb/1.1 WebMachine/1.9.0 (participate in the frantic) < Link: </riak/schemas>; rel="up" < Last-Modified: Fri, 16 Sep 2011 15:15:48 GMT < ETag: "51h3q7RjTNaHWYpO4P0MJj" < Date: Fri, 16 Sep 2011 15:22:07 GMT < Content-Type: application/json < Content-Length: 629 It was working fine some time ago on master but I cannot remember exactly at which commit. I suspect I try to put objects with some badly formatted/configured headers? However I still manage to put and get the objects. Regards, Antoine On 16 September 2011 16:45, Kelly McLaughlin <[email protected]> wrote: > 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
