oblems too.
From: Russell Brown [russell.br...@me.com]
Sent: Friday, March 01, 2013 10:46 AM
To: Belai Beshah
Cc: Kresten Krab Thorup; Jared Morrow; riak-users@lists.basho.com
Subject: Re: Understanding read_repairs
On 1 Mar 2013, at 17:39, Belai Beshah wrote:
> Nothing
riday, March 01, 2013 5:40 AM
> To: Belai Beshah
> Cc: Jared Morrow; riak-users@lists.basho.com; Russell Brown
> Subject: Re: Understanding read_repairs
>
> Interesting. What does the failure look like?
>
> Kresten
>
> On Feb 27, 2013, at 11:25 PM, Belai Beshah
>
Thorup [k...@trifork.com]
Sent: Friday, March 01, 2013 5:40 AM
To: Belai Beshah
Cc: Jared Morrow; riak-users@lists.basho.com; Russell Brown
Subject: Re: Understanding read_repairs
Interesting. What does the failure look like?
Kresten
On Feb 27, 2013, at 11:25 PM, Belai Beshah
mailto:belai.bes...@nwgeo.c
, 2013 2:21 PM
To: Belai Beshah
Cc: Russell Brown; riak-users@lists.basho.com<mailto:riak-users@lists.basho.com>
Subject: Re: Understanding read_repairs
Belai,
Active Anti-Entropy is doing work building trees and checking data, so it will
slow down gets/puts slightly. If you can't accep
$ ./rebar --version
rebar 2.0.0 R14B03 20120816_132849 git 1c98f6c
$ erl
Erlang R15B03 (erts-5.9.3.1) [source] [64-bit] [smp:8:8] [async-threads:0]
[hipe] [kernel-poll:false] [dtrace]
Eshell V5.9.3.1 (abort with ^G)
On 28.02.2013, at 21:46, Jared Morrow wrote:
> I just tried and it worked f
I just tried and it worked for me, here's what I see:
➜ riak_kv git:(master) ./rebar --version
rebar 2.0.0 R14B03 20120816_132849 git 1c98f6c
➜ riak_kv git:(master) erl
Erlang R15B01 (erts-5.9.1) [source] [64-bit] [smp:8:8] [async-threads:0]
[kernel-poll:false]
I also tried erlang 14b04 and it
Jared,
running make in riak_kv dies [0] for me :-/
Best
Sebastian
[0]: https://gist.github.com/tisba/5057828
On 22.02.2013, at 19:56, Jared Morrow wrote:
> compile riak_kv with just 'make'
___
riak-users mailing list
riak-users@lists.basho.com
h
if it works with more.
From: Jared Morrow [ja...@basho.com]
Sent: Wednesday, February 27, 2013 2:21 PM
To: Belai Beshah
Cc: Russell Brown; riak-users@lists.basho.com
Subject: Re: Understanding read_repairs
Belai,
Active Anti-Entropy is doing work building tree
vior we saw. Thanks you guys
> for the help.
>
> --
> *From:* Jared Morrow [ja...@basho.com]
> *Sent:* Friday, February 22, 2013 11:56 AM
> *To:* Belai Beshah
> *Cc:* Russell Brown; riak-users@lists.basho.com
> *Subject:* Re: Understanding read_repairs
>
> Belai,
>
Sent: Friday, February 22, 2013 11:56 AM
To: Belai Beshah
Cc: Russell Brown; riak-users@lists.basho.com
Subject: Re: Understanding read_repairs
Belai,
One other option is to use our "basho-patches" functionality. We use it to run
new code on current installations where sending a new .beam
:56 AM
To: Belai Beshah
Cc: Russell Brown; riak-users@lists.basho.com
Subject: Re: Understanding read_repairs
Belai,
One other option is to use our "basho-patches" functionality. We use it to run
new code on current installations where sending a new .beam file is easier than
re
Thanks, Russell.
In that case I have one more argument to upgrade to 1.3.0 :) I'll try to
confirm that we are hitting this issue and see if we can fix it by applying the
proper patch.
On 24.02.2013, at 16:10, Russell Brown wrote:
>
> On 24 Feb 2013, at 15:01, Sebastian Cohnen wrote:
>
>>
On 24 Feb 2013, at 15:01, Sebastian Cohnen wrote:
> Can you confirm that the PR didn't made it into 1.3.0? It was closed about
> two four weeks ago...
It is not in 1.3. We actually had the code freeze for 1.3.0 a _long_ time ago
(I think it was 16th Nov 2012) and this fix did not make it in t
Can you confirm that the PR didn't made it into 1.3.0? It was closed about two
four weeks ago...
I think I'm hitting the same issue here. In one project I'm using last write
wins and the read repair count is ridiculously high. I'm hoping that this might
also help reducing the latency problem we
On Fri, Feb 22, 2013 at 11:56:31AM -0700, Jared Morrow wrote:
>- stop each node and restart them one at a time
You can actually just drop a file in basho-patches and do a l(module) at
the riak shell (via riak attach). You can then do the code:which trick
to check it worked. You should be aware
elai Beshah wrote:
> Thanks Russel, that looks like exactly the problem we saw. I have never
> built riak from source before but I will give it a try it this weekend.
>
>
> From: Russell Brown [russell.br...@me.com]
> Sent: Friday, Februar
-users@lists.basho.com
Subject: Re: Understanding read_repairs
Hi,
Thanks for trying Riak.
On 21 Feb 2013, at 23:48, Belai Beshah wrote:
> Hi All,
>
> We are evaluating Riak to see if it can be used to cache large blobs of data.
> Here is our test cluster setup:
>
> • si
Hi,
Thanks for trying Riak.
On 21 Feb 2013, at 23:48, Belai Beshah wrote:
> Hi All,
>
> We are evaluating Riak to see if it can be used to cache large blobs of data.
> Here is our test cluster setup:
>
> • six Ubuntu LTS 12.04 dedicated nodes with 8 core 2.6 Ghz CPU, 32 GB
> RAM, 3.6T
18 matches
Mail list logo
