Thank you for the reply, adding back the other nodes did (after a while) fix the prblem even tho the ring stated it was complete some 10 minutes before the actual query worked again.
2012/9/17 Reid Draper <[email protected]> > Paul, > > It looks like you're running a 3-node cluster. If two of the nodes fail, > you'll likely > not be able to run `coverage` queries like 2i and list-keys. If you need > to be able > to sustain losing 2 nodes and still successfully run 2i, I'd suggest > running at least > a 5 node cluster. > > Reid > > > On Sep 17, 2012, at 6:07 AM, Paul Scheltema <[email protected]> > wrote: > > recently 2 of the vm's running riak crashed. (probably not due to riak) > When i now run "curl $riak/buckets/$2/keys?keys=true" i get the following > error message: > > <html><head><title>500 Internal Server > Error</title></head><body><h1>Internal Server Error</h1>The server > encountered an error while processing this > request:<br><pre>{error,{error,{badmatch,{error,insufficient_vnodes_available}}, > [{riak_kv_wm_keylist,produce_bucket_body,2}, > {webmachine_resource,resource_call,3}, > {webmachine_resource,do,3}, > {webmachine_decision_core,resource_call,1}, > {webmachine_decision_core,decision,1}, > {webmachine_decision_core,handle_request,2}, > {webmachine_mochiweb,loop,1}, > > {mochiweb_http,parse_headers,5}]}}</pre><P><HR><ADDRESS>mochiweb+webmachine > web server</ADDRESS></body></html> > > == ring_status > root@03:/usr/local/riak/bin# ./riak-admin ring_status > ================================== Claimant > =================================== > Claimant: '[email protected]' > Status: up > Ring Ready: true > > ============================== Ownership Handoff > ============================== > No pending changes. > > ============================== Unreachable Nodes > ============================== > All nodes are up and reachable > > == ring ready > root@03:/usr/local/riak/bin# ./riak-admin ringready > TRUE All nodes agree on the ring ['[email protected]', > '[email protected]', > '[email protected]'] > > == member status > root@03:/usr/local/riak/bin# ./riak-admin member_status > ================================= Membership > ================================== > Status Ring Pending Node > > ------------------------------------------------------------------------------- > valid 34.4% -- '[email protected]' > valid 32.8% -- '[email protected]' > valid 32.8% -- '[email protected]' > > ------------------------------------------------------------------------------- > Valid:3 / Leaving:0 / Exiting:0 / Joining:0 / Down:0 > > == ulimit: > root@03:/usr/local/riak/etc# ulimit -a > core file size (blocks, -c) 0 > data seg size (kbytes, -d) unlimited > scheduling priority (-e) 0 > file size (blocks, -f) unlimited > pending signals (-i) 15584 > max locked memory (kbytes, -l) 64 > max memory size (kbytes, -m) unlimited > open files (-n) 1024 > pipe size (512 bytes, -p) 8 > POSIX message queues (bytes, -q) 819200 > real-time priority (-r) 0 > stack size (kbytes, -s) 8192 > cpu time (seconds, -t) unlimited > max user processes (-u) 15584 > virtual memory (kbytes, -v) unlimited > file locks (-x) unlimited > > > > -- > groeten > /paul > > _______________________________________________ > riak-users mailing list > [email protected] > http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com > > > -- groeten /paul
_______________________________________________ riak-users mailing list [email protected] http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
