Generally when the node doesn't crash and the rest of normal operations are
still working, you don't have to worry. Note that the bug you mention has
been fixed and will be available in 1.0 when released. I understand there
will be some preview-release packages you will be able to try for several
w
Hi Sean,
I have the same issue as mentioned here :
http://lists.basho.com/pipermail/riak-users_lists.basho.com/2011-June/004639.html
It happens few time every day, the node doesn't crash, I'm not sure if I
have to be worried about this or not.
I have plenty of memory available on this server.
He
{jsanon,****
>
> <<"function(value,keyData,arg){var
>
> ** **
>
> David
>
> ** **
>
> ** **
>
> ** **
>
> *From:* David Mitchell
> *Sent:* Tuesday, June 21, 2011 5:10 PM
> *To:* 'riak-users@lists.basho.com
{state,true,
{javascript,
{map,
{jsanon,
<<"function(value,keyData,arg){var
David
From: David Mitchell
Sent: Tuesday, June 21, 2011 5:10 PM
To: 'riak-users@lists.basho.com'
Subject: Re: R
Erlang: R13B04
Riak: 0.14.2
I am having the same issue as Jeremy.
I just did 208 MapReduce jobs using anonymous JavaScript functions in the map
and reduce phases. I am sending the MapReduce jobs to a single node, riak01.
Out of the 208 jobs, I got two "mapexec_error" {error,timeout} on riak02
Hi Jeremy,
The flow_timeout error would not cause a node to crash. Supervisor and error
reports are normal log entries and do not usually correspond to a node
crash. Can you provide all the log files from the crashing node? Also, can
you look for an erl_crash.dump file?
Thanks,
Dan
Daniel Reverr
Ok thanks. Where do I increase the timeout? Would the timeout cause the node
to crash?
- Jeremy
On Tue, Jun 21, 2011 at 9:27 AM, Mathias Meyer wrote:
> Jeremy,
>
> looks like you're hitting the timeout for the MapReduce job you're running,
> so the issue isn't memory-related. You could either
Jeremy,
looks like you're hitting the timeout for the MapReduce job you're running, so
the issue isn't memory-related. You could either increase the timeout for the
whole job, or split up the single MapReduce request in multiple, ensuring a
shorter runtime of a single job, then collecting the r
I increased the memory to 3GB on the VMs I'm using for Riak and also
replaced a JavaScript reduce function I had missed converting to Erlang with
the Erlang version. Monitoring the memory on the machines indicates that
Riak is not running out of memory. There is lots of disk space on the
machines (
I see this from time to time on our production 5-node cluster, with no
indications of any other problems. And I'm certain it's not a memory or disk
issue.
On Sunday, June 19, 2011 at 6:01 PM, Jeremy Raymond wrote:
> Actually it's a bit later on where I see this:
>
> = Fri Jun 17 16:26:46 E
Actually it's a bit later on where I see this:
= Fri Jun 17 16:26:46 EDT 2011
=ERROR REPORT 17-Jun-2011::16:26:46 ===
** Generic server riak_kv_stat terminating
** Last message in was {'$gen_cast',{update,vnode_get,63475547206}}
** When Server state == {state,
I see these messages near the time of the crash. Indicators of low system
memory?
=INFO REPORT 17-Jun-2011::12:27:35 ===
Spidermonkey VM (pool: riak_kv_js_map) host stopping (<0.160.0>)
(riak@10.90.80.167)1>
=INFO REPORT 17-Jun-2011::12:27:35 ===
Spidermonkey VM (pool: riak_kv_js_map) host
Jeremy,
There is an open pull request for fixing this bug. Details of the bug are
here: https://issues.basho.com/show_bug.cgi?id=1072 It will not cause your
entire to node to crash, there is likely some other cause. Node exits tend
to only happen when you run out of RAM or disk space, or can't b
13 matches
Mail list logo
