Re: Very, very slow data insert on two node cluster

ssume this value does not represent puts between nodes, just direct puts to the node. I think the proper value to check would be "vnode_puts". Box A = "vnode_puts": 2144 Box B = "vnode_puts": 2170 so it does seem it's OK vlatko -------- Original Message -

Re: Very, very slow data insert on two node cluster

On Fri, May 6, 2011 at 6:44 AM, Les Mikesell wrote: > On 5/6/11 8:27 AM, David Leimbach wrote: > >> The default for a bucket is to use quorum writes, but you should be able >> to >> specify that you only want to write to one Riak node as a parameter to the >> write. So you don't necessarily have

Re: Very, very slow data insert on two node cluster

The fact that the other node is idle clues makes me think that the node you're talking to is not reaching the other node. Both nodes should be participating in the storage of the data. On Fri, May 6, 2011 at 5:38 AM, Vlatko Basic wrote: > Hi, > > I've build a cluster with two physical Ubuntu 10.

Very, very slow data insert on two node cluster

Hi, I've build a cluster with two physical Ubuntu 10.10 64-bit 4GB machines (laptop, 2 cores, 2.4GHz and desktop, 4 cores, 3.1GHz) and I am trying to "load_data goog.csv" (around 1500 records) from a Fast Track tutorial. It took over 15 minutes. Riak installation (both from DEB package) is co

Re: Very, very slow data insert on two node cluster

r, w, and dw are just acknowledged reads, writes, or durable writes. nval is the number of replicas written. Jeremiah Peschka Microsoft SQL Server MVP MCITP: Database Developer, DBA On May 6, 2011 9:44 AM, "Les Mikesell" wrote: > On 5/6/11 8:27 AM, David Leimbach wrote: >> The default for a bucke

Re: Very, very slow data insert on two node cluster

I'm not sure what you should be seeing from the Erlang client. I've only ever used the Ruby HTTP client. Jeremiah Peschka Microsoft SQL Server MVP MCITP: Database Developer, DBA On May 6, 2011 9:52 AM, "Vlatko Basic" wrote: ___ riak-users mailing list r

Re: Very, very slow data insert on two node cluster

----- Subject: Re: Very, very slow data insert on two node cluster From: Jeremiah Peschka To: riak-users@lists.basho.com Date: 06.05.2011 12:48 One thing you'll want to do is adjust your nval if this is a development cluster. With an nv

Re: Very, very slow data insert on two node cluster

On 5/6/11 8:27 AM, David Leimbach wrote: The default for a bucket is to use quorum writes, but you should be able to specify that you only want to write to one Riak node as a parameter to the write. So you don't necessarily have to adjust the nval. Does the client directive actually control th

Re: Very, very slow data insert on two node cluster

The default for a bucket is to use quorum writes, but you should be able to specify that you only want to write to one Riak node as a parameter to the write. So you don't necessarily have to adjust the nval. Dave On Fri, May 6, 2011 at 3:48 AM, Jeremiah Peschka wrote: > One thing you'll want t

Re: Very, very slow data insert on two node cluster

One thing you'll want to do is adjust your nval if this is a development cluster. With an nval of 3, one machine is always writing two copies of the data. If this is for dev, you can get away with a single node cluster and an nval of 1. Jeremiah Peschka Founder, Brent Ozar PLF SQL MVP, MCITP: DBA,

Very, very slow data insert on two node cluster

Hi, I've build a cluster with two physical Ubuntu 10.10 64-bit 4GB machines (laptop, 2 cores, 2.4GHz and desktop, 4 cores, 3.1GHz) and I am trying to "load_data goog.csv" (around 1500 records) from a Fast Track tutorial. It took over 15 minutes. Riak installation (both from DEB package) is cor