Re: Cannot start riak
Lijun, Could you check the logs for errors, and send them to the list? Cheers, Sean On Wednesday, July 11, 2012 at 10:48 PM, Lijun Wang wrote: > I am evaluating riak. On FreeBSD, I got, application_start_failure, os_mon > when starting it. The issue is other than this how do I know what is really > going on? > > > Thanks, > Lijun > > Sent from my iPhone > ___ > riak-users mailing list > riak-users@lists.basho.com (mailto: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
Re: Riak significant downtime
John,
Please make sure in /etc/pam.d/su, that the following line is uncommented:
sessionrequired pam_limits.so
I have noticed lately in Ubuntu that this line is commented out by default.
Best,
Sean
On Wednesday, August 1, 2012 at 5:47 PM, Jared Morrow wrote:
> You will need to make the adjustments in the /etc/security/limits.conf file
> as described here http://wiki.basho.com/Open-Files-Limit.html
>
> -Jared
>
>
> On Aug 1, 2012, at 3:33 PM, John Roy (mailto:j...@thoughtleadr.com)> wrote:
> > Hi Reid --
> >
> > I added a risk.conf file in /etc/default with the line:
> >
> > ulimit -n 8192
> >
> > then rebooted, restarted risk and then did the attach.
> >
> > I got this line (which is also in the crash.log), then the limit of 1024.
> > See below:
> >
> > 16:28:58.041 [error] Hintfile
> > '/disk1/riak/bitcask/159851741583067506678528028578343455274867621888/12.bitcask.hint'
> > contains pointer 118308596 570 that is greater than total data size
> > 118308864
> >
> > > os:cmd("ulimit -n").
> > "1024\n"
> >
> >
> > I also set in manually prior to the reboot and got the same result.
> >
> >
> > On Aug 1, 2012, at 2:09 PM, Reid Draper wrote:
> >
> > > ulimit of 4096 might be too low. I'd also double-check the ulimit
> > > has taken effect either by attaching to the node (riak attach) or
> > > starting the node in the console (riak console), then type this:
> > >
> > > os:cmd("ulimit -n").
> > >
> > > Be sure to include the period (.) that
> > > is above as well.
> > >
> > > Reid
> > >
> > >
> > > On Aug 1, 2012, at 5:00 PM, John Roy wrote:
> > > > Hi --
> > > >
> > > > Riak 1.1.1
> > > > three nodes
> > > > Ubuntu 10.04.1 LTS
> > > > downtime means one node drops off then the other two follow so the
> > > > entire cluster falls down.
> > > >
> > > > On Aug 1, 2012, at 1:48 PM, Mark Phillips wrote:
> > > > > Hey John,
> > > > >
> > > > > First questions would be:
> > > > >
> > > > > * What version of Riak?
> > > > > * How many nodes?
> > > > > * Which OS?
> > > > > * When you say "downtime" do you mean the entire cluster? Or just a
> > > > > subset of your nodes?
> > > > >
> > > > > Mark
> > > > >
> > > > > On Wed, Aug 1, 2012 at 1:42 PM, John Roy > > > > (mailto:j...@thoughtleadr.com)> wrote:
> > > > > > I'm seeing significant downtime on Riak now. Much like the "Riak
> > > > > > Crashing Constantly" thread. However in this case we get a "Too
> > > > > > many open files" error, and also "contains pointer that is greater
> > > > > > than the total data size." See the error messages below for more
> > > > > > details.
> > > > > >
> > > > > > If others have an idea on this I'd appreciate your help.
> > > > > >
> > > > > > Thanks!
> > > > > >
> > > > > > John
> > > > > >
> > > > > > 2012-08-01 14:53:28 =ERROR REPORT
> > > > > > Hintfile
> > > > > > '/disk1/riak/bitcask/1347321821914426127719021955160323408745312813056/12.bitcask.hint'
> > > > > > contains pointer 119561351 4415 that is greater than total data
> > > > > > size 119562240
> > > > > >
> > > > > > 2012-08-01 14:54:26 =CRASH REPORT
> > > > > > crasher:
> > > > > > initial call: riak_core_vnode:init/1
> > > > > > pid: <0.29239.0>
> > > > > > registered_name: []
> > > > > > exception exit: [{riak_kv_eleveldb_backend,{db_open,"IO error:
> > > > > > /disk1/riak/leveldb/753586781748746817198774991869333432010090217472/CURRENT:
> > > > > > Too many open files"}}]
> > > > > > in function gen_fsm:init_it/6
> > > > > > in call from proc_lib:init_p_do_apply/3
> > > > > > ancestors: [riak_core_vnode_sup,riak_core_sup,<0.88.0>]
> > > > > > messages: []
> > > > > > links: [<0.92.0>]
> > > > > > dictionary:
> > > > > > [{#Ref<0.0.0.37922>,{bc_state,"/disk1/riak/bitcask/753586781748746817198774991869333432010090217472",fresh,undefined,[{filestate,read_only,"/disk1/riak/bitcask/753586781748746817198774991869333432010090217472/1.bitcask.data",1,<<>>,undefined,0,0},{filestate,read_only,"/disk1/riak/bitcask/753586781748746817198774991869333432010090217472/2.bitcask.data",2,<<>>,undefined,0,0}],2147483648,[{expiry_secs,-1},{read_write,true}],<<>>}},{random_seed,{17770,26756,17419}}]
> > > > > > trap_exit: true
> > > > > > status: running
> > > > > > heap_size: 4181
> > > > > > stack_size: 24
> > > > > > reductions: 13734
> > > > > > neighbours:
> > > > > > 2012-08-01 14:54:26 =SUPERVISOR REPORT
> > > > > > Supervisor: {local,riak_core_vnode_sup}
> > > > > > Context:child_terminated
> > > > > > Reason: [{riak_kv_eleveldb_backend,{db_open,"IO error:
> > > > > > /disk1/riak/leveldb/753586781748746817198774991869333432010090217472/CURRENT:
> > > > > > Too many open files"}}]
> > > > > > Offender:
> > > > > > [{pid,<0.29239.0>},{name,undefined},{mfargs,{riak_core_vnode,start_link,undefined}},{restart_type,temporary},{shutdown,30},{child_type,worker}]
> > > > > >
> > > > > > 2012-08-01 14:
Re: Riak significant downtime
John,
Glad things are starting to run smoothly. This pam.d setting has tripped me a
couple of times.
Best,
Sean
On Wednesday, August 1, 2012 at 8:16 PM, John Roy wrote:
> All --
>
> The pam.d/su and limits.conf changes seem to have brought us back to
> reliability -- so far so good. The time consuming part was the reboot. I
> double checked the ulimit in the risk console and all came up to 8192 -- my
> new limit.
>
> thanks for all your help,
>
> John
>
>
> On Aug 1, 2012, at 2:56 PM, Sean Carey wrote:
> > John,
> > Please make sure in /etc/pam.d/su, that the following line is uncommented:
> >
> > sessionrequired pam_limits.so
> >
> > I have noticed lately in Ubuntu that this line is commented out by default.
> >
> >
> > Best,
> >
> >
> > Sean
> >
> > On Wednesday, August 1, 2012 at 5:47 PM, Jared Morrow wrote:
> >
> > > You will need to make the adjustments in the /etc/security/limits.conf
> > > file as described here http://wiki.basho.com/Open-Files-Limit.html
> > >
> > > -Jared
> > >
> > >
> > > On Aug 1, 2012, at 3:33 PM, John Roy > > (mailto:j...@thoughtleadr.com)> wrote:
> > > > Hi Reid --
> > > >
> > > > I added a risk.conf file in /etc/default with the line:
> > > >
> > > > ulimit -n 8192
> > > >
> > > > then rebooted, restarted risk and then did the attach.
> > > >
> > > > I got this line (which is also in the crash.log), then the limit of
> > > > 1024. See below:
> > > >
> > > > 16:28:58.041 [error] Hintfile
> > > > '/disk1/riak/bitcask/159851741583067506678528028578343455274867621888/12.bitcask.hint'
> > > > contains pointer 118308596 570 that is greater than total data size
> > > > 118308864
> > > >
> > > > > os:cmd("ulimit -n").
> > > > "1024\n"
> > > >
> > > >
> > > > I also set in manually prior to the reboot and got the same result.
> > > >
> > > >
> > > > On Aug 1, 2012, at 2:09 PM, Reid Draper wrote:
> > > >
> > > > > ulimit of 4096 might be too low. I'd also double-check the ulimit
> > > > > has taken effect either by attaching to the node (riak attach) or
> > > > > starting the node in the console (riak console), then type this:
> > > > >
> > > > > os:cmd("ulimit -n").
> > > > >
> > > > > Be sure to include the period (.) that
> > > > > is above as well.
> > > > >
> > > > > Reid
> > > > >
> > > > >
> > > > > On Aug 1, 2012, at 5:00 PM, John Roy wrote:
> > > > > > Hi --
> > > > > >
> > > > > > Riak 1.1.1
> > > > > > three nodes
> > > > > > Ubuntu 10.04.1 LTS
> > > > > > downtime means one node drops off then the other two follow so the
> > > > > > entire cluster falls down.
> > > > > >
> > > > > > On Aug 1, 2012, at 1:48 PM, Mark Phillips wrote:
> > > > > > > Hey John,
> > > > > > >
> > > > > > > First questions would be:
> > > > > > >
> > > > > > > * What version of Riak?
> > > > > > > * How many nodes?
> > > > > > > * Which OS?
> > > > > > > * When you say "downtime" do you mean the entire cluster? Or just
> > > > > > > a subset of your nodes?
> > > > > > >
> > > > > > > Mark
> > > > > > >
> > > > > > > On Wed, Aug 1, 2012 at 1:42 PM, John Roy > > > > > > (mailto:j...@thoughtleadr.com)> wrote:
> > > > > > > > I'm seeing significant downtime on Riak now. Much like the
> > > > > > > > "Riak Crashing Constantly" thread. However in this case we get
> > > > > > > > a "Too many open files" error, and also "contains pointer that
> > > > > > > > is greater than the total data size." See the error messages
> > > > > > > > below for more details.
> > > > > > > >
> > > > > > > > If others have an idea on this I'd ap
Re: Reasons to think of MTU size and avg value size?
Hey Patrick, You could try jumbo frames and it will buy you some extra CPU. We have done this in a couple of configurations and didn't notice anything crazy. Are you thinking increasing MTU might benefit in some other way, other than CPU. I'd be interested in knowing your thoughts/results if you test. What kind of switches are you using? Also, I have never tried Super Jumbo. Thanks, Sean On Monday, August 20, 2012 at 10:54 AM, Patrik Sundberg wrote: > Hi, > > I was just pondering a bit here - any pointers to think about in terms of MTU > settings for a network with a riak cluster and clients? (let's ignore any > other traffic on the network) It'd seem a good idea for MTU > median/mean > value size (when we're talking about value sizes that aren't huge, > kilobytes), but then there's the internal chatter in the cluster etc and it's > not obvious what the trade off is. > > I didn't see it discussed in the mailing list much before. > > Thanks, > Patrik > > ___ > riak-users mailing list > riak-users@lists.basho.com (mailto: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
Re: Riak behind a Load Balancer
Matt, Haproxy is my load balancer of choice. You can always run multiple copies of haproxy and use some type of dynamic dns with it. We do this in many cases. Haproxy scales well. I've seen a single node sustain multiple gigabits per second with almost no sweat. Thanks. Sean On Monday, June 25, 2012 at 7:36 AM, Matt Black wrote: > Dear list, > > Does anyone have an opinion on the concept of putting a Riak cluster behind a > load balancer? > > We wish to be able to automatically add/remove nodes from the cluster, so > adding an extra layer at the front is desirable. We should also benefit for > incoming requests behind shared across all nodes. > > Can anyone see any drawbacks / problems with doing this? > > Thanks > Matt > > ___ > riak-users mailing list > riak-users@lists.basho.com (mailto: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
Re: Riak on SmartOs won't start
Could you send along your erlang crash log and config files?
On Wednesday, September 19, 2012 at 2:59 PM, Callixte Cauchois wrote:
> Hello,
>
> I am trying to get riak working on SmartOs using Joyent provided dataset
> (399e09fc-c448-11e1-b3c8-a3d517dfbb07 smartos 2012-07-02 sdc:sdc:riak:1.6.1).
> It doesn't start. When using riak console, I get this error message:
> 18:48:37.011 [error] CRASH REPORT Process riak_core_handoff_listener with 1
> neighbours exited with reason: bad argument in gen_server:init_it/6 line 328
> /opt/local/lib/riak/lib/os_mon-2.2.9/priv/bin/memsup: Erlang has closed.
>
> I have created the vm with a very simple json:
> {
> "alias": "riak1",
> "brand": "joyent",
> "dataset_uuid": "399e09fc-c448-11e1-b3c8-a3d517dfbb07",
> "max_physical_memory": 2048,
> "nics": [
> {
> "nic_tag": "admin",
> "ip": "dhcp"
> }
> ]
> }
>
> It is riak v.1.1.4. I tried to upgrade to 1.2.0 using the compiled package
> and got the same error.
>
> Am I missing something?
>
> Thanks.
> Callixte.
>
> ___
> riak-users mailing list
> riak-users@lists.basho.com (mailto: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
Re: Scaling up or out
Ken, Are your vms on different bare metal? Could they potentially be on the same bare metal? Are you seeing any io contention? Sean Carey @densone On Wednesday, December 5, 2012 at 20:41, Ken Perkins wrote: > Yes, we're thrashing on all of the boxes, due to disk access when looking > through merge_index. It's not noisy neighbors, given how consistent the > thrashing is. We had a box with a corrupted index (we had to remove > merge_index and rebuild) and that machine instantly went to 0% thrashing. So > we have a pretty good indication of the source. > > The cost for 10 8GB VMs is roughly equivalent to 5 16GB ones. > > Thanks for your input Michael! > > Ken > > > On Wed, Dec 5, 2012 at 4:47 PM, Michael Johnson (mailto:m...@mediatemple.net)> wrote: > > There are a lot of things that go into this, but I would tend to suggest in > > a hosted VM senario, upping the ram is likely the right solution. > > > > You mention thrashing, but what is that thrashing coming from? I assume > > all the boxes are thrashing and not just one or two of them? Is it due to > > swapping or is it just the raw disk access? Maybe you logging too > > aggressively? > > > > Perhaps your are suffering from a bad neighbor effect. If this is the > > case, increasing the amount of ram will likely put you on a physical host > > with few customers and thus you would be less likely to have a bad > > neighbor. > > > > Cost-wise in the VM world, you might be better off adding a few nodes > > rather than increasing the ram in your existing vm's. > > > > But then we are talking VMs and thus it should be fairly painless to > > experiment. I would try adding ram first and if that doesn't work, add a > > few nodes. Someone else my have a different opinion, but that is my two > > cents. > > > > > > On Wed, Dec 5, 2012 at 4:33 PM, Ken Perkins > (mailto:k...@clipboard.com)> wrote: > > > Hello all, > > > > > > We're seeing enough thrashing and low-memory on our production ring that > > > we've decided to upgrade our hardware. The real question is should we > > > scale up or out. > > > > > > Currently our ring is 512 partitions. We know that it's a sub-optimal > > > size but we can't easily solve that now. We're currently running a > > > search-heavy app on 5 8GB VMs. I'm debating between moving the VMs up to > > > 16GB, or adding a few more 8GB VMs. > > > > > > Some of the talk in #riak has pushed me towards adding more machines > > > (thus lowering the per node number of partitions) but I wanted to do a > > > quick sanity check here with folks that it's better than scaling up my > > > current machines. > > > > > > Thanks! > > > Ken Perkins > > > clipboard.com (http://clipboard.com) > > > > > > ___ > > > riak-users mailing list > > > riak-users@lists.basho.com (mailto: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 > > ___ riak-users mailing list riak-users@lists.basho.com http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
Re: Scaling up or out
So Ken, Fair amount? < 5% or > 20% If there's iowait and memory issues, adding nodes could alleviate that. If there's almost no iowait or minimal iowait, adding memory will help. Also, tuning vm.dirty on linux might get you more memory and less iowait. Or at least more consistent iowait. Which linux distro are you on and which scheduler are you using? -Sean On Thursday, December 6, 2012 at 12:15 AM, Ken Perkins wrote: > VMs, not the same host, rackspace has VM affinity to protect against that. We > do see a fair amount of IO Wait. > > Rackspace has a new affinity based SSD block device service that I plan to > evaluate, but I'm not ready for that in production. > > > On Wed, Dec 5, 2012 at 7:45 PM, Sean Carey (mailto:ca...@basho.com)> wrote: > > Ken, > > Are your vms on different bare metal? Could they potentially be on the same > > bare metal? > > > > Are you seeing any io contention? > > > > > > Sean Carey > > @densone > > > > > > On Wednesday, December 5, 2012 at 20:41, Ken Perkins wrote: > > > > > Yes, we're thrashing on all of the boxes, due to disk access when looking > > > through merge_index. It's not noisy neighbors, given how consistent the > > > thrashing is. We had a box with a corrupted index (we had to remove > > > merge_index and rebuild) and that machine instantly went to 0% thrashing. > > > So we have a pretty good indication of the source. > > > > > > The cost for 10 8GB VMs is roughly equivalent to 5 16GB ones. > > > > > > Thanks for your input Michael! > > > > > > Ken > > > > > > > > > On Wed, Dec 5, 2012 at 4:47 PM, Michael Johnson > > (mailto:m...@mediatemple.net)> wrote: > > > > There are a lot of things that go into this, but I would tend to > > > > suggest in a hosted VM senario, upping the ram is likely the right > > > > solution. > > > > > > > > You mention thrashing, but what is that thrashing coming from? I > > > > assume all the boxes are thrashing and not just one or two of them? Is > > > > it due to swapping or is it just the raw disk access? Maybe you > > > > logging too aggressively? > > > > > > > > Perhaps your are suffering from a bad neighbor effect. If this is the > > > > case, increasing the amount of ram will likely put you on a physical > > > > host with few customers and thus you would be less likely to have a bad > > > > neighbor. > > > > > > > > Cost-wise in the VM world, you might be better off adding a few nodes > > > > rather than increasing the ram in your existing vm's. > > > > > > > > But then we are talking VMs and thus it should be fairly painless to > > > > experiment. I would try adding ram first and if that doesn't work, add > > > > a few nodes. Someone else my have a different opinion, but that is my > > > > two cents. > > > > > > > > > > > > On Wed, Dec 5, 2012 at 4:33 PM, Ken Perkins > > > (mailto:k...@clipboard.com)> wrote: > > > > > Hello all, > > > > > > > > > > We're seeing enough thrashing and low-memory on our production ring > > > > > that we've decided to upgrade our hardware. The real question is > > > > > should we scale up or out. > > > > > > > > > > Currently our ring is 512 partitions. We know that it's a sub-optimal > > > > > size but we can't easily solve that now. We're currently running a > > > > > search-heavy app on 5 8GB VMs. I'm debating between moving the VMs up > > > > > to 16GB, or adding a few more 8GB VMs. > > > > > > > > > > Some of the talk in #riak has pushed me towards adding more machines > > > > > (thus lowering the per node number of partitions) but I wanted to do > > > > > a quick sanity check here with folks that it's better than scaling up > > > > > my current machines. > > > > > > > > > > Thanks! > > > > > Ken Perkins > > > > > clipboard.com (http://clipboard.com) > > > > > > > > > > ___ > > > > > riak-users mailing list > > > > > riak-users@lists.basho.com (mailto: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 (mailto: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
Re: Scaling up or out
If your jumping between 5-25% iowait, I'd add nodes. Also tuning pdflush will help with the jumpy iowait. Lucid by default uses up to 20% of your ram before flushing. So say you have 10gb of ram, your system could be trying to flush 2gb of data causing huge iowait spikes. Sean Carey @densone On Thursday, December 6, 2012 at 11:49, Ken Perkins wrote: > We're around ~20% Swapping, IO Wait in the 5-25% range, depending on the > machine. > > We're running Lucid, with the deadline scheduler. I'm strongly biasing > towards adding a few more nodes, but I'm not married to it :) > > > On Wed, Dec 5, 2012 at 9:22 PM, Sean Carey (mailto:ca...@basho.com)> wrote: > > So Ken, > > Fair amount? < 5% or > 20% > > > > If there's iowait and memory issues, adding nodes could alleviate that. If > > there's almost no iowait or minimal iowait, adding memory will help. Also, > > tuning vm.dirty on linux might get you more memory and less iowait. Or at > > least more consistent iowait. > > > > > > Which linux distro are you on and which scheduler are you using? > > > > > > -Sean > > > > > > > > > > > > > > On Thursday, December 6, 2012 at 12:15 AM, Ken Perkins wrote: > > > > > VMs, not the same host, rackspace has VM affinity to protect against > > > that. We do see a fair amount of IO Wait. > > > > > > Rackspace has a new affinity based SSD block device service that I plan > > > to evaluate, but I'm not ready for that in production. > > > > > > > > > On Wed, Dec 5, 2012 at 7:45 PM, Sean Carey > > (mailto:ca...@basho.com)> wrote: > > > > Ken, > > > > Are your vms on different bare metal? Could they potentially be on the > > > > same bare metal? > > > > > > > > Are you seeing any io contention? > > > > > > > > > > > > Sean Carey > > > > @densone > > > > > > > > > > > > On Wednesday, December 5, 2012 at 20:41, Ken Perkins wrote: > > > > > > > > > Yes, we're thrashing on all of the boxes, due to disk access when > > > > > looking through merge_index. It's not noisy neighbors, given how > > > > > consistent the thrashing is. We had a box with a corrupted index (we > > > > > had to remove merge_index and rebuild) and that machine instantly > > > > > went to 0% thrashing. So we have a pretty good indication of the > > > > > source. > > > > > > > > > > The cost for 10 8GB VMs is roughly equivalent to 5 16GB ones. > > > > > > > > > > Thanks for your input Michael! > > > > > > > > > > Ken > > > > > > > > > > > > > > > On Wed, Dec 5, 2012 at 4:47 PM, Michael Johnson > > > > (mailto:m...@mediatemple.net)> wrote: > > > > > > There are a lot of things that go into this, but I would tend to > > > > > > suggest in a hosted VM senario, upping the ram is likely the right > > > > > > solution. > > > > > > > > > > > > You mention thrashing, but what is that thrashing coming from? I > > > > > > assume all the boxes are thrashing and not just one or two of them? > > > > > > Is it due to swapping or is it just the raw disk access? Maybe > > > > > > you logging too aggressively? > > > > > > > > > > > > Perhaps your are suffering from a bad neighbor effect. If this is > > > > > > the case, increasing the amount of ram will likely put you on a > > > > > > physical host with few customers and thus you would be less likely > > > > > > to have a bad neighbor. > > > > > > > > > > > > Cost-wise in the VM world, you might be better off adding a few > > > > > > nodes rather than increasing the ram in your existing vm's. > > > > > > > > > > > > But then we are talking VMs and thus it should be fairly painless > > > > > > to experiment. I would try adding ram first and if that doesn't > > > > > > work, add a few nodes. Someone else my have a different opinion, > > > > > > but that is my two cents. > > > > > > >
Re: Cluster setup
Kevin,
Send us more detailed logs of the startup error. Also a copy
/etc/riak/app.config on the machine where the error is happening, and also the
output of `netstat -tln`
-Sean
On Monday, December 10, 2012 at 2:56 PM, Kevin Burton wrote:
> Each node is on a separate machine. This not a development build. The
> instructions just indicate that I should start the Riak Server but does not
> indicate what should be done when it doesn't start.
>
> On Dec 10, 2012, at 1:52 PM, Jared Morrow (mailto:ja...@basho.com)> wrote:
>
> > Are you trying to start all nodes on the same machine/vm? Each riak "node"
> > needs to be on its own machine, unless you are simply trying to test out a
> > development environment. In that case, you need to look at
> > http://docs.basho.com/riak/latest/tutorials/fast-track/Building-a-Development-Environment/
> > for those instructions. It will help in starting multiple nodes per
> > machine.
> >
> > -Jared
> >
> >
> > On Mon, Dec 10, 2012 at 12:43 PM, Kevin Burton > (mailto:rkevinbur...@charter.net)> wrote:
> > > The first node started up without error (/etc/init.d/riak start). But
> > > nodes 2 and 3 failed to start. I looked in /var/log/riak/error.log and
> > > found about three lines with {error,eaddrnotavail} in the error message.
> > > What does this mean? Is there a work around? I don't understand why this
> > > address is "not available". 'ifconfig' confirms that this is the machines
> > > address.
> > >
> > >
> > > On Dec 10, 2012, at 12:33 PM, Jared Morrow > > (mailto:ja...@basho.com)> wrote:
> > >
> > > > The init.d script for RIak is included in the RPM. If you list the
> > > > file contained in the RPM do you see the init.d/riak script? If you do
> > > > have that file, you'll need to add the rc.d scripts by hand to
> > > > auto-start / auto-stop on startup / shutdown or use a tool like
> > > > `chkconfig` http://linux.die.net/man/8/chkconfig
> > > >
> > > > -Jared
> > > >
> > > >
> > > > On Mon, Dec 10, 2012 at 11:17 AM, Kevin Burton
> > > > mailto:rkevinbur...@charter.net)> wrote:
> > > > > I did these steps and while I see that Riak has been added to the
> > > > > system files (like /etc/riak). I don't see any links to auto start
> > > > > like in init.d. Do I add these links manually?
> > > > >
> > > > >
> > > > > On Dec 10, 2012, at 11:32 AM, Jared Morrow > > > > (mailto:ja...@basho.com)> wrote:
> > > > >
> > > > > > If you are looking install and /etc/init.d support, you should
> > > > > > really just be installing the packages.
> > > > > > http://s3.amazonaws.com/downloads.basho.com/riak/CURRENT/rhel/6/riak-1.2.1-1.el6.x86_64.rpm
> > > > > > is the package for Centos 6 found here
> > > > > > http://basho.com/resources/downloads/. Building from source is
> > > > > > there for those who need a feature not currently in a release, want
> > > > > > to make additions to Riak, or are on an unsupported platform.
> > > > > >
> > > > > > -Jared
> > > > > >
> > > > > >
> > > > > > On Mon, Dec 10, 2012 at 10:25 AM, > > > > > (mailto:rkevinbur...@charter.net)> wrote:
> > > > > > > I am looking at
> > > > > > > http://docs.basho.com/riak/latest/cookbooks/Basic-Cluster-Setup/
> > > > > > > which provides me with a lot of information. But I have one
> > > > > > > question. I have a source distribution and I have already done
> > > > > > > 'make rel'. Once I have performed all of the steps outlined in
> > > > > > > setting up a cluster how do I make sure that this configuration
> > > > > > > is restored when the machine reboots. I am assuming that it will
> > > > > > > involve something with /etc/init.d. Is there something like 'make
> > > > > > > install' that would shorten the process? How is the cluster
> > > > > > > information persisted so that each node will join the cluster
> > > > > > > when the respective machine comes up after a reboot? Thank you.
> > > > > > >
> > > > > > >
> > > > > > > ___
> > > > > > > riak-users mailing list
> > > > > > > riak-users@lists.basho.com (mailto: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 (mailto: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
Re: Cluster setup
Look at the section in your config called pb_ip. The ip is wrong.
On Monday, December 10, 2012 at 4:02 PM, rkevinbur...@charter.net wrote:
> I moved on to the next step and from the "seed node" I execute 'sudo
> riak-admin cluster join riak@10.79.110.52 (mailto:riak@10.79.110.52)' and I
> get
>
> Attempting to restart script through sudo -H -u riak
> Node riak@10.79.110.52 (mailto:riak@10.79.110.52) is not reachable!
>
> I can ping the node:
> PING 10.79.110.52 (10.79.110.52) 56(84) bytes of data.
> 64 bytes from 10.79.110.52: icmp_seq=1 ttl=63 time=1.08 ms
> 64 bytes from 10.79.110.52: icmp_seq=2 ttl=63 time=1.77 ms
> 64 bytes from 10.79.110.52: icmp_seq=3 ttl=63 time=2.67 ms
> 64 bytes from 10.79.110.52: icmp_seq=4 ttl=63 time=0.663 ms
>
> Any ideas what this problem is?
> I went to node2 and could not start riak
> The vm.args on the second node looks like:
> ## Name of the riak node
> -name riak@10.79.110.52 (mailto:riak@10.79.110.52)
>
>
> ifconfig looks like:
> eth0 Link encap:Ethernet HWaddr 00:15:5D:50:3B:27
> inet addr:10.79.110.52 Bcast:10.79.111.255 Mask:255.255.254.0
> inet6 addr: fe80::215:5dff:fe50:3b27/64 Scope:Link
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:345671 errors:0 dropped:0 overruns:0 frame:0
> TX packets:136590 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:480181840 (457.9 MiB) TX bytes:13833066 (13.1 MiB)
>
> loLink encap:Local Loopback
> inet addr:127.0.0.1 Mask:255.0.0.0
> inet6 addr: ::1/128 Scope:Host
> UP LOOPBACK RUNNING MTU:16436 Metric:1
> RX packets:1555 errors:0 dropped:0 overruns:0 frame:0
> TX packets:1555 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:90413 (88.2 KiB) TX bytes:90413 (88.2 KiB)
>
> netstat -tln
> Proto Recv-Q Send-Q Local Address Foreign Address
> State
> tcp0 0 0.0.0.0:111 0.0.0.0:*
> LISTEN
> tcp0 0 0.0.0.0:43690.0.0.0:*
> LISTEN
> tcp0 0 0.0.0.0:46130 0.0.0.0:*
> LISTEN
> tcp0 0 0.0.0.0:22 0.0.0.0:*
> LISTEN
> tcp0 0 127.0.0.1:631 0.0.0.0:*
> LISTEN
> tcp0 0 127.0.0.1:250.0.0.0:*
> LISTEN
> tcp0 0 10.79.110.52:16001 0.0.0.0:*
> LISTEN
> tcp0 0 0.0.0.0:56720.0.0.0:*
> LISTEN
> tcp0 0 :::38381:::*
> LISTEN
> tcp0 0 :::111 :::*
> LISTEN
> tcp0 0 :::22 :::*
> LISTEN
> tcp0 0 ::1:631 :::*
> LISTEN
> tcp0 0 ::1:25 :::*
> LISTEN
> tcp0 0 :::5672 :::*
> LISTEN
>
> app.config looks like:
> [
>
> %% Riak Client APIs config
> {riak_api, [
> %% pb_backlog is the maximum length to which the queue of pending
> %% connections may grow. If set, it must be an integer >= 0.
> %% By default the value is 5. If you anticipate a huge number of
> %% connections being initialised *simultaneously*, set this number
> %% higher.
> %% {pb_backlog, 64},
> %% pb_ip is the IP address that the Riak Protocol Buffers
> interface
> %% will bind to. If this is undefined, the interface will not
> run.
> {pb_ip, "10.79.110.52" },
> %% pb_port is the TCP port that the Riak Protocol Buffers
> interface
> %% will bind to
> {pb_port, 8089 }
> ]},
> %% Riak Core config
> {riak_core, [
> %% Default location of ringstate
> {ring_state_dir, "/var/lib/riak/ring"},
>
> %% Default ring creation size. Make sure it is a power of 2,
> %% e.g. 16, 32, 64, 128, 256, 512 etc
> %{ring_creation_size, 64},
>
> %% http is a list of IP addresses and TCP ports that the Riak
> %% HTTP interface will bind.
> {http, [ {"10.79.110.52", 8099 } ]},
>
>
> %% pb_ip is the IP address that the Riak Protocol Buffers
> interface
> %% will bind to. If this is undefined, the interface will not
> run.
> {pb_ip, "10.79.80.11" },
>
> %% pb_port is the TCP port that the Riak Protocol Buffers
> interface
> %% will bind to
> {pb_port, 8090 }
> ]},
>
> Finally
Re: nebie with volumes and best practices with /var/lib/riak data directory
Hey David,
You are correct. You can do 1 of two things here:
1) Mount your 1TB volume to /var/lib/riak. All ring, and backend data will be
stored there.
2) Mount your volume somewhere like /data/riak and switch the platform_data_dir
config option to reflect that mounted path.
If you wanted to snapshot your riak data, it all lives in platform_data_dir
Hope this helps,
Sean
@densone
On Wednesday, December 12, 2012 at 12:32 AM, David Montgomery wrote:
> Hi,
>
> I use datapipe for by cloud provider. An I am rather new from a sysadmin
> perspective of having to attach volumes. I am using ubuntu 12.04 64.
>
> So...now that I can attach a 1T volume on machine bootby question is this.
>
> When I mount the new volume.should I mount /var/lib/riak? I see that
> the data directory is {platform_data_dir, "/var/lib/riak"}, from the
> app.config file. Thus data will be written to the new drive solely this
> making use of the 1T? Data will not be stored on the default volume which is
> 20 gigs on datapipe. Then at this point I can snapshot the volume to capture
> all data?
>
> Thanks
>
> David
> ___
> riak-users mailing list
> riak-users@lists.basho.com (mailto: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
Re: nebie with volumes and best practices with /var/lib/riak data directory
Hey David,
My comments are inline.
On Wednesday, December 12, 2012 at 3:38 AM, David Montgomery wrote:
> Thanks.,that helps...
>
> So..what happens if I have in existing path on a smaller drive and I attach
> a new volume and switch?
- Stop riak.
- Copy the data out.
- Mount the new volume with the same permissions.
- Copy the data in.
- Start riak.
- Things should work.
> In essence looking for best practice on how ot handle this.
>
>
> Is it better to do a rolling upgrade where I start new machines fresh with 1T
> then remove the smaller nodes 1 by one? So...I have three nodes with 20 gigs
> each. Increase to 6 nodes. Then one one by remove the old nod and now back
> to three with 1T each. It does seem that a rolling upgrade involves much
> less risk.
>
If you don't have enough disk space. Mount a temporary volume somewhere and
back the data up (make sure riak is stopped. I would not focus on leaves and
joins.
Make sure to do the copy process 1 node at a time..
Please let me know if you need more details. This should work fine and we do
this all the time.
> Thanks
>
>
>
>
>
>
>
>
>
> On Wed, Dec 12, 2012 at 2:13 PM, Sean Carey (mailto:ca...@basho.com)> wrote:
> > Hey David,
> > You are correct. You can do 1 of two things here:
> >
> > 1) Mount your 1TB volume to /var/lib/riak. All ring, and backend data will
> > be stored there.
> >
> > 2) Mount your volume somewhere like /data/riak and switch the
> > platform_data_dir config option to reflect that mounted path.
> >
> > If you wanted to snapshot your riak data, it all lives in platform_data_dir
> >
> >
> > Hope this helps,
> >
> >
> > Sean
> > @densone
> >
> >
> >
> > On Wednesday, December 12, 2012 at 12:32 AM, David Montgomery wrote:
> >
> >
> >
> > > Hi,
> > >
> > > I use datapipe for by cloud provider. An I am rather new from a sysadmin
> > > perspective of having to attach volumes. I am using ubuntu 12.04 64.
> > >
> > > So...now that I can attach a 1T volume on machine bootby question is
> > > this.
> > >
> > > When I mount the new volume.should I mount /var/lib/riak? I see
> > > that the data directory is {platform_data_dir, "/var/lib/riak"}, from
> > > the app.config file. Thus data will be written to the new drive solely
> > > this making use of the 1T? Data will not be stored on the default volume
> > > which is 20 gigs on datapipe. Then at this point I can snapshot the
> > > volume to capture all data?
> > >
> > > Thanks
> > >
> > > David
> > > ___
> > > riak-users mailing list
> > > riak-users@lists.basho.com (mailto: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
Re: Installing Riak on Ubuntu Server.
Follow the instructions for Precise Pangolin. Sean Carey @densone On Wednesday, December 26, 2012 at 16:13, Kevin Burton wrote: > I was following the instructions on > http://docs.basho.com/riak/1.2.1/tutorials/installation/Installing-on-Debian-and-Ubuntu/ > but it seem to differentiate between different versions of Ubuntu. I only > know that I have a Ubuntu Server 12.04.1 LTS. Which of the installation steps > should I pick? > > Thank you. > > > ___ > 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
Re: Tuning a Riak cluster.
Kevin, Disk and CPU, and Network? Sean Carey @densone On Thursday, February 21, 2013 at 20:31, Kevin Burton wrote: > > I have a cluster of 4 machines (4 Linux VM machines each allocated about 1 Gb > of memory – yea I know it isn’t a lot). I would like to get some pointers on > getting the fastest query time possible given these meager resources. Thank > you. > > > ___ > 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
Re: Installing Riak on Ubuntu server.
Kevin, Our apt and yum repos run on s3. There may have been a momentary blip. I was able to pull down the apt key without issue. Our datacenter maintenance would not affect this. Try it again :) Sean Carey @densone On Tuesday, February 26, 2013 at 21:22, Jared Morrow wrote: > Some maintenance was happening tonight on the servers hosting the yum and apt > repositories. If possible try again in the morning, sorry for any > inconvenience. > > -Jared > > > On Feb 26, 2013, at 6:08 PM, "Kevin Burton" (mailto:rkevinbur...@charter.net)> wrote: > > > I was looking at: > > > > And I started the first step > > curl http://apt.basho.com/gpg/basho.apt.key > > but I get > > > > 403 Forbidden > > > > 403 Forbidden > > > > Code: AccessDenied > > Message: Access Denied > > RequestId: 236910E76E5D619F > > HostId: > > twSF8oGr3bg5dReZYF2Q2m98cFjrBjzPtgGjtM8DfuRr/44T4rEy1ua8M5l8DWVE > > > > > > > > > > > > Any ideas? > > > > > > > > > > ___ > > riak-users mailing list > > riak-users@lists.basho.com (mailto: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 > > ___ riak-users mailing list riak-users@lists.basho.com http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
Updated Chef Cookbook for Riak 1.0.2
Dear Riak Users, We are pleased to announce that the Riak Chef Cookbook has been updated. You can now install and configure the latest version of Riak (1.0.2) with the Chef configuration management tools. You can download the cookbook from the OpsCode Community site: http://community.opscode.com/cookbooks/riak If you would like to contribute, please feel free to fork our GitHub repository: https://github.com/densone/riak-chef-cookbook The Readme file can be found on GitHub: https://github.com/densone/riak-chef-cookbook/blob/master/README.md As always, thanks for being such a supportive (and patient) community! - Basho Engineering ___ riak-users mailing list riak-users@lists.basho.com http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
Re: Updated Chef Cookbook for Riak 1.0.2
Quick Correction, Please use the Basho repositories. To see the Readme and clone. If you would like to contribute, please feel free to fork our GitHub repository: https://github.com/basho/riak-chef-cookbook The Readme file can be found on GitHub: https://github.com/basho/riak-chef-cookbook/blob/master/README.md ___ riak-users mailing list riak-users@lists.basho.com http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
Re: Add a SPF record to DNS of basho smtp list server
Carlos, Thanks for alerting us. We updated our SPF Records to include the mailing list. Best, Sean Carey On Dec 21, 2011, at 2:05 PM, Carlo Pires wrote: > Hi, > > Sysadm at Basho should add SPF record to DNS serving smtp of lists.basho.com. > > Gmail is giving a big red warning for mail phishing to riak mailing mail > messages. > > -- > Carlo Pires > > ___ > 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
Updated (1.0.3) Riak Chef Cookbook Available
Dear Riak Users, We are pleased to announce that the Riak Chef Cookbook has been updated. You can now install and configure the latest version of Riak (1.0.3) with the Chef configuration management tools. You can download the cookbook from the OpsCode Community site: http://community.opscode.com/cookbooks/riak If you would like to contribute, please feel free to fork our GitHub repository: https://github.com/basho/riak-chef-cookbook The Readme file can be found on GitHub: https://github.com/basho/riak-chef-cookbook/blob/master/README.md As always, thanks for being such a supportive community! Sean Carey Basho Technologies ___ riak-users mailing list riak-users@lists.basho.com http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
Re: Updated (1.0.3) Riak Chef Cookbook Available
Hey Mark, Good question. It's currently on my backlog. Once I get a puppet plugin in a stable state, I will be sure to contact you. Best Regards, Sean Carey On Jan 19, 2012, at 12:59 PM, Mark Steele wrote: > Puppet in the works? > > Mark Steele, CISSP, CSM > Bering Media Inc. > > On Thu, Jan 19, 2012 at 12:07 PM, Sean Carey wrote: > Dear Riak Users, > We are pleased to announce that the Riak Chef Cookbook has been updated. You > can now install and configure the latest version of Riak (1.0.3) with the > Chef configuration management tools. > > > You can download the cookbook from the OpsCode Community site: > > http://community.opscode.com/cookbooks/riak > > If you would like to contribute, please feel free to fork our GitHub > repository: > > https://github.com/basho/riak-chef-cookbook > > > The Readme file can be found on GitHub: > > https://github.com/basho/riak-chef-cookbook/blob/master/README.md > > > > As always, thanks for being such a supportive community! > > > > Sean Carey > Basho Technologies > > > ___ > 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
Re: Installing riak fails due to missing libssl
Carl, Use apt to install libssl 0.9.x. This will solve your issues. -Sean On Jan 22, 2012, at 6:04 PM, Carl wrote: > I am trying to install Riak 1.0.3 on my Linux Mint 12 system. Linux > Mint is basically Ubuntu but with a more pure GNOME user interface. > > I wanted to be able to run multiple instances on one node so first I > tried to build from source. I have Erlang R15B installed. I modified > the various rebar.config files to allow that platform, but it never got > that far, first getting a few 'fatal' errors about git, and then > stopping claiming it could not find a libssl >= 0.9.8. > > So then I tried the prebuilt install using the i386 .deb file. This got > the same errors: > > ... > ==> riak-1.0.3 (get-deps) > ./rebar compile generate > fatal: Not a git repository (or any parent up to mount parent ) > Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set). > fatal: Not a git repository (or any parent up to mount parent ) > Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set). > fatal: Not a git repository (or any parent up to mount parent ) > Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set). > ==> cluster_info (compile) > Compiled src/cluster_info_ex.erl > Compiled src/cluster_info.erl > Compiled src/cluster_info_basic.erl > ==> skerl (compile) > Compiled src/skerl.erl > Compiled src/hex.erl > Compiling c_src/skein.c > Compiling c_src/skein_api.c > Compiling c_src/skein_block.c > Compiling c_src/skein_debug.c > Compiling c_src/skerl_nifs.c > /usr/bin/ld: cannot find -lstdc++ > collect2: ld returned 1 exit status > ERROR: cc c_src/skein.o c_src/skein_api.o c_src/skein_block.o > c_src/skein_debug.o c_src/skerl_nifs.o -lstdc++ -shared > -L/usr/lib/erlang/lib/erl_interface-3.7.6/lib -lerl_interface -lei -o > priv/skerl_nifs.so failed with error: 1 and output: > /usr/bin/ld: cannot find -lstdc++ > collect2: ld returned 1 exit status > > make: *** [rel] Error 1 > > But according to 'aptitude' I have libssl 1.0.0 installed. So then I go > look in /usr/lib and find these files. > > /build/riak-1.0.3> find /usr/lib -name 'libstdc*' > /usr/lib/ure/lib/libstdc++.so.6 > /usr/lib/i386-linux-gnu/libstdc++.so.6.0.16 > /usr/lib/i386-linux-gnu/libstdc++.so.6 > > > ___ > 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
Re: Riak had overload My cpu
Kser, How's disk io? Can you send an 'iostat 2' dump? Let it run for 30 seconds when the load is high. Sean On Feb 10, 2012, at 12:48 AM, kser wrote: > Would it be the database size get too large, makes the cpu over load? > > -- > View this message in context: > http://riak-users.197444.n3.nabble.com/Riak-had-overload-My-cpu-tp3731675p3731722.html > Sent from the Riak Users mailing list archive at Nabble.com. > > ___ > 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
Re: Riak had overload My cpu
Kser, What's the machines load average? Sean On Feb 19, 2012, at 1:28 AM, kser wrote: > Sorry for late, Here is the : > > avg-cpu: %user %nice %system %iowait %steal %idle > 44.140.00 14.840.010.00 41.01 > > Device:tps Blk_read/s Blk_wrtn/s Blk_read Blk_wrtn > cciss/c0d0 19.8022.85 427.00 19541608 365233421 > > avg-cpu: %user %nice %system %iowait %steal %idle > 42.030.00 16.700.000.00 41.28 > > Device:tps Blk_read/s Blk_wrtn/s Blk_read Blk_wrtn > cciss/c0d00.00 0.00 0.00 0 0 > > avg-cpu: %user %nice %system %iowait %steal %idle > 33.580.00 18.700.000.00 47.72 > > Device:tps Blk_read/s Blk_wrtn/s Blk_read Blk_wrtn > cciss/c0d0 33.00 0.00 640.00 0 1280 > > avg-cpu: %user %nice %system %iowait %steal %idle > 32.710.00 17.670.000.00 49.61 > > Device:tps Blk_read/s Blk_wrtn/s Blk_read Blk_wrtn > cciss/c0d02.50 0.0048.00 0 96 > > avg-cpu: %user %nice %system %iowait %steal %idle > 30.390.00 18.810.000.00 50.79 > > Device:tps Blk_read/s Blk_wrtn/s Blk_read Blk_wrtn > cciss/c0d0 62.00 0.00 916.00 0 1832 > > avg-cpu: %user %nice %system %iowait %steal %idle > 27.600.00 17.600.000.00 54.79 > > Device:tps Blk_read/s Blk_wrtn/s Blk_read Blk_wrtn > cciss/c0d00.00 0.00 0.00 0 0 > > avg-cpu: %user %nice %system %iowait %steal %idle > 30.390.00 19.550.000.00 50.06 > > Device:tps Blk_read/s Blk_wrtn/s Blk_read Blk_wrtn > cciss/c0d04.50 0.0068.00 0136 > > avg-cpu: %user %nice %system %iowait %steal %idle > 31.680.00 17.500.000.00 50.82 > > Device:tps Blk_read/s Blk_wrtn/s Blk_read Blk_wrtn > cciss/c0d0 27.00 0.00 480.00 0960 > > avg-cpu: %user %nice %system %iowait %steal %idle > 39.510.00 15.590.000.00 44.90 > > Device:tps Blk_read/s Blk_wrtn/s Blk_read Blk_wrtn > cciss/c0d0 10.00 0.00 108.00 0216 > > avg-cpu: %user %nice %system %iowait %steal %idle > 34.340.00 17.770.000.00 47.89 > > Device:tps Blk_read/s Blk_wrtn/s Blk_read Blk_wrtn > cciss/c0d05.00 0.0068.00 0136 > > avg-cpu: %user %nice %system %iowait %steal %idle > 33.980.00 17.430.000.00 48.59 > > Device:tps Blk_read/s Blk_wrtn/s Blk_read Blk_wrtn > cciss/c0d0 33.00 0.00 1472.00 0 2944 > > avg-cpu: %user %nice %system %iowait %steal %idle > 34.620.00 20.830.000.00 44.55 > > Device:tps Blk_read/s Blk_wrtn/s Blk_read Blk_wrtn > cciss/c0d02.00 0.0036.00 0 72 > > > -- > View this message in context: > http://riak-users.197444.n3.nabble.com/Riak-had-overload-My-cpu-tp3731675p3757531.html > Sent from the Riak Users mailing list archive at Nabble.com. > > ___ > 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
Re: riakkit, a python riak object mapper, has hit beta!
Keep up the great work Shuhao! On Mar 1, 2012, at 7:36 PM, Shuhao Wu wrote: Hey guys, I started writing riakkit approximately 3 months ago and announced it here. In case you missed that, Riakkit is basically an object mapper for python and riak, which seemed to be lacking in at the time. Now that 3 months has passed and I have developed this project into much more than what I had envisioned to begin with. It's currently also being used and tested in a project of mine (web application) as well and functioning quite nicely. I would say that currently this is the only object mapper that can compete with their counterparts in other languages for Riak in Python, although a lot of work still needs to be done before it could fully compete. So today I felt that riakkit is "stable" and "clean" enough to deserve the first beta release. So I whipped up a website and it's released to pypi. Here's (again), a demo (the full tutorial can be found on the links below) class User(Document): client = riak.RiakClient() bucket_name = "users" name = StringProperty(required=True) >>> user = User(name="foo") >>> user.save() >>> print user.name foo If anyone is interested, you can find the website here: http://ultimatebuster.github.com/riakkit and the code at http://github.com/ultimatebuster/riakkit Cheers! Shuhao ___ 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
