Re: Riak Core Claim Bug Fixes

Whoohoo!! .. I can help with packaging, keep us posted. On Fri, Aug 18, 2017 at 1:33 PM DeadZen wrote: > You the man! > > On Thu, Aug 17, 2017 at 12:06 PM Christopher Meiklejohn < > christopher.meiklej...@gmail.com> wrote: > >> Bravo! >> >> On Thu, Aug 17, 2017 at 3:11 AM,

Re: OTP 19 support

This is a blocker for packaging riak on debian stretch, which comes with erlang (1:19.2.1+dfsg-2) https://github.com/basho/riak/issues/916 Is this a major change updating riak to OTP-19 ? Cheers Steven On Tue, May 30, 2017 at 9:52 PM Torben Hoffmann wrote: > The rebar3

Wildcard Querying fields containing '@'

Hi, We are experiencing a weird issue with wildcard search. Given a field 'email_register' of type text_general, containing value 'ste...@streethawk.com', the query 'email_register: "steve*"' should match it, but it does not seem to be working as expected. the query 'steven*' will match

Re: Reg:Continuous Periodic crashes after long operation

reated. Are you re-using the > RiakClient object or repeatedly creating new ones? Can you provide any > code that reproduces your issue? > > -- > Luke Bakken > Engineer > lbak...@basho.com > > > On Tue, Jan 31, 2017 at 7:47 PM, Steven Joseph <ste...@streeth

Re: Reg:Continuous Periodic crashes after long operation

: > > fs.file-max = 1620211 > > -- > Luke Bakken > Engineer > lbak...@basho.com > > > On Tue, Jan 31, 2017 at 12:22 PM, Steven Joseph <ste...@streethawk.com> > wrote: > > Hi Shaun, > > > > Im having this issue again, this time I have ca

Re: Reg:Continuous Periodic crashes after long operation

n Enter). > > It should be at least 65,536 ideally, although the bigger the better. > > If you find it's lower, then follow this doc to increase it. > > http://docs.basho.com/riak/kv/2.0.2/using/performance/open-files-limit/ > > Have a check and let us know what the ou

Re: Reg:Continuous Periodic crashes after long operation

he better. > > If you find it's lower, then follow this doc to increase it. > > http://docs.basho.com/riak/kv/2.0.2/using/performance/open-files-limit/ > > Have a check and let us know what the output was. > > Kind Regards, > Shaun > > On Thu, Jan 26, 2017 at 10:3

Re: Reg:Continuous Periodic crashes after long operation

t; > > > Which directed me to this page: > > https://github.com/emqtt/emqttd/wiki/linux-kernel-tuning > > > > Basho also has a set of recommended tuning parameters: > > http://docs.basho.com/riak/kv/2.2.0/using/performance/ > > > > Do you have other error entr

Re: Reg:Continuous Periodic crashes after long operation

he better. > > If you find it's lower, then follow this doc to increase it. > > http://docs.basho.com/riak/kv/2.0.2/using/performance/open-files-limit/ > > Have a check and let us know what the output was. > > Kind Regards, > Shaun > > On Thu, Jan 26, 2017 at 10:3

Reg:Continuous Periodic crashes after long operation

quot;, line 476, in search 2017-01-26T10:20:44.517Z hawk5| raise e.args[0] 2017-01-26T10:20:44.517Z hawk5| File "/usr/local/lib/python2.7/dist-packages/riak/client/transport.py", line 134, in _with_retries 2017-01-26T10:20:44.517Z hawk5| return self._with_retries(pool, thunk) 2017-01-26

Reg: value error in mochiglobal:compile/2 line 51

Hi Folks, I've started getting this error in my riak cluster almost periodically. Has anyone else encountered this before: 2017-01-09 03:36:02.293 [error] <0.7098.626> gen_server yz_cover terminated with reason: no match of right hand value error in mochiglobal:compile/2 line 51 2017-01-09

Re: Riak nodes constantly crashing

Oct 25, 2016 at 6:54 PM, Steven Joseph <ste...@streethawk.co> > wrote: > > Hi Ricardo, > > If you are using systemd might have to check LimitNOFILE for your units. > Active anti entropy runs periodically. > > Steven > > On Wed, 26 Oct 2016 04:36 Ricardo

Re: Riak nodes constantly crashing

Hi Ricardo, If you are using systemd might have to check LimitNOFILE for your units. Active anti entropy runs periodically. Steven On Wed, 26 Oct 2016 04:36 Ricardo Mayerhofer wrote: > What's weird is that the node crashes every minute at the same second. Is > there