The bucket (type) that you're working with -- what are your allow_mult, and last_write_wins settings?
On Mon, Dec 29, 2014 at 4:05 AM, Jason Ryan <jason.r...@trustev.com> wrote: > It seems to move between 4 keys in particular, these keys are actually empty > at the moment (i.e. an empty JSON document). > > CPU utilization is close to zero. > > Can't see anything in particular, bar the error message I just posted > before. > > Jason > > > On 29 December 2014 at 11:58, Ciprian Manea <cipr...@basho.com> wrote: >> >> Hi Jason, >> >> Are these random timeouts happening for only one key, or is common for >> more? >> >> What is the CPU utilisation in the cluster when you're experience these >> timeouts? >> >> Can you spot anything peculiar in your server's $ dmesg outputs? Any I/O >> errors there? >> >> >> Regards, >> Ciprian >> >> On Mon, Dec 29, 2014 at 1:55 PM, Sargun Dhillon <sar...@sargun.me> wrote: >>> >>> Several things: >>> 1) I recommend you have a 5-node cluster: >>> http://basho.com/why-your-riak-cluster-should-have-at-least-five-nodes/ >>> 2) What version of Riak are you using? >>> 3) What backend(s) are you using? >>> 4) What's the size of your keyspace? >>> 5) Are you actively rewriting keys, or writing keys to the cluster? >>> 6) Do you know how much I/O the cluster is currently doing? >>> >>> On Mon, Dec 29, 2014 at 2:51 AM, Jason Ryan <jason.r...@trustev.com> >>> wrote: >>> > Hi, >>> > >>> > We are getting random timeouts from our application (>60seconds) when >>> > we try >>> > to retrieve a key from our Riak cluster (4 nodes with a load balancer >>> > in >>> > front of them). Our application just uses the standard REST API to >>> > query >>> > Riak. >>> > >>> > We are pretty new to Riak - so would like to understand how best to >>> > debug >>> > this issue? Is there any good pointers on what to start with? This is >>> > our >>> > production cluster. >>> > >>> > Thanks, >>> > Jason >>> > >>> > >>> > This message is for the named person's use only. If you received this >>> > message in error, please immediately delete it and all copies and >>> > notify the >>> > sender. You must not, directly or indirectly, use, disclose, >>> > distribute, >>> > print, or copy any part of this message if you are not the intended >>> > recipient. Any views expressed in this message are those of the >>> > individual >>> > sender and not Trustev Ltd. Trustev is registered in Ireland No. 516425 >>> > and >>> > trades from 2100 Cork Airport Business Park, Cork, Ireland. >>> > >>> > >>> > _______________________________________________ >>> > riak-users mailing list >>> > riak-users@lists.basho.com >>> > http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com >>> > >>> >>> _______________________________________________ >>> riak-users mailing list >>> riak-users@lists.basho.com >>> http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com >> >> > > > This message is for the named person's use only. If you received this > message in error, please immediately delete it and all copies and notify the > sender. You must not, directly or indirectly, use, disclose, distribute, > print, or copy any part of this message if you are not the intended > recipient. Any views expressed in this message are those of the individual > sender and not Trustev Ltd. Trustev is registered in Ireland No. 516425 and > trades from 2100 Cork Airport Business Park, Cork, Ireland. _______________________________________________ riak-users mailing list riak-users@lists.basho.com http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
