itchell
Cc: riak-users@lists.basho.com
Subject: Re: Mysterious JavaScript MapReduce crashes and timeouts with 0.14.2
On Samstag, 25. Juni 2011 at 00:23, David Mitchell wrote:
> Hi Mathias,
>
> Thank you for responding, and give me things to try.
>
> I am testing Raik using a hypervis
On Samstag, 25. Juni 2011 at 00:23, David Mitchell wrote:
> Hi Mathias,
>
> Thank you for responding, and give me things to try.
>
> I am testing Raik using a hypervisor, so each node only has one CPU and 1.5
> GB of RAM. I have 222,526 total keys stored.
>
I'd suggest testing your setup on s
Message-
From: Mathias Meyer [mailto:math...@basho.com]
Sent: Friday, June 24, 2011 3:37 PM
To: David Mitchell
Cc: riak-users@lists.basho.com
Subject: Re: Mysterious JavaScript MapReduce crashes and timeouts with 0.14.2
David,
given your description of the error behaviour and the MapReduce job
David,
given your description of the error behaviour and the MapReduce job shown
below, here's an outline of what's happening in your cluster when you fire that
job 208 times in quick succession:
* All nodes in the cluster go through their keys using the filter you supplied,
that's 208 times o
I just reran the 208 MapReduce jobs, and I got two timeouts (but no crashes).
They were both in the map phase.
=ERROR REPORT 24-Jun-2011::15:23:27 ===
** State machine <0.4087.0> terminating
** Last event in was {mapexec_error,{157389,'riak@10.0.60.210'},
I am doing 208 MapReduce jobs in rapid-fire succession using anonymous
JavaScript functions. I am sending the MapReduce jobs to a single node,
riak01. There are about 75,000 keys in the bucket.
Erlang: R13B04
Riak: 0.14.2
When I had my MapReduce timeout set to 120,000 ("timeout":12), I was
