Hi Alexander,
The node appears to be crashing due to it hitting the Erlang process limit. You
can increase this from the default value of 32768 to e.g. the double by setting
adding the line +P 65536 to the vm.args file. Having said that I am wondering
what is causing you to hit this limit. What ring size are you using? How are
you querying your data?
Best regards,
Christian
On 14 May 2013, at 09:35, Alexander Ilyin <alexan...@rutarget.ru> wrote:
> Hi all,
>
> I have my riak node crashed and can't figure out why this has happened. Any
> help would be appreciated.
>
> I'm using riak 1.3.1 and running a single node on CentOS 6.3 (availability is
> not critical right now).
> This node uses Bitcask backend with the default configuration except for
> expiry_secs property which is set to 15552000.
> The properties of a single bucket used are the following:
> {"props":{"allow_mult":false," basic_quorum":false,"big_
> vclock":50,"chash_keyfun":{"mod":"riak_core_util","fun":"chash_std_keyfun"},"dw":"quorum","last_write_wins":false,"linkfun":{"mod":"riak_kv_wm_link_walker","fun":"mapreduce_linkfun"},"n_val":2,"name":"c","notfound_ok":true,"old_vclock":86400,"postcommit":[],"pr":0,"precommit":[],"pw":0,"r":"one","rw":"quorum","small_vclock":50,"w":"one","young_vclock":20}}
> There is enough disk space and RAM on the server.
> At the moment of the crash size of the most partitions was about 1.1Gb, but
> few of them were smaller.
> Attaching error.log and crash.log
>
> Thanks in advance.
>
> Alexander
> <riak-logs.tar.gz>_______________________________________________
> 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
