ompatibility.
In closing... I think there should exist open discussions regarding
riak_core,
that don't get buried in the riak list, therefore I humbly suggest a
riak_core mailing list be started...
Thank you...
DeadZen -
#erlang / #erlounge on freenode
#6 - Erlang R16 Compatibility in a tagged release...
Some people aren't comfortable using a develop branch in production..
It's an important thing for riak_core applications and irrelevant of riak,
speaking of that..
#7 - Riak Core should be treated as a standalone app, not as a riak app..
A lot o
w00t
On Sat, Jan 18, 2014 at 3:27 PM, Luc Perkins wrote:
> Dear Riak community,
>
> We're excited to bring you our first "public" release of a 2.0 preview since
> the tech preview that we unleashed at RICON West.
>
> The list of changes is too long to trivially enumerate, as effectively all
> of
I don't even use java and I'm excited about that!
On Thursday, September 25, 2014, Brian Roach wrote:
> As of now, the new Java client for Riak v2.0 is available via Maven
> Central.
>
> To use in your project:
>
>
>
> com.basho.riak
> riak-client
> 2.0.0
>
> ...
>
>
> Java
It could be the logs need to be repaired. Or inadvertently multiple keys
have been added under the same index.
It's unlikely your whole database is corrupt
On Tuesday, March 8, 2016, Alexander Popov wrote:
> Noticied that sometimes 2i query and all keys requesrs returns extra
> records ~2% of al
+1
On Fri, May 6, 2016 at 8:17 PM, Sargun Dhillon wrote:
> We're using riak_dt in anger in our product. We are already using it
> with rebar3, and Erlang 18.3 through some super messy patches.
>
> I would love to see a register that takes the logical clock, and
> timestamp for resolution, rather
e are also using Riak DT as a base. However, we are doing a greenfield
> implementation of the new delta work in Lasp and hope to have an
> open-source library of these implementations available soon.
> >
> > - Christopher
> >
> > On Saturday, May 7, 2016, DeadZen
Any reason for the FreeBSD support drop?
Run into issues?
On Friday, May 20, 2016, Alexander Sicular wrote:
> Hello All,
>
> Just in time for the weekend we bring you a rundown of announcements,
> jobs, some code and, of course, the mailing list review.
>
> As always, we want to hear from you. I
Not to jump to conclusions, but this sounds like a quorum issue.
Such as your writes are not going to all three servers, but only to one or two.
Handoffs would occur when nodes went down unexpectedly, it doesn't
ever attempt to fetch unwritten data, it fetches data from other
servers which were sti
whats the problem currently?
something not working on freebsd?
On Thursday, May 26, 2016, Seema Jethani > wrote:
> Hello All,
> Basho is no longer directly supporting FreeBSD due to low levels of
> adoption amongst our commercial customers, but we are looking for members
> of the community to he
reiterating my last email
> theres no guarantee vnodes are assigned to unique servers..
referencing the docs
> Nodes *attempt* to claim their partitions at intervals around the ring
such that there is an even distribution amongst the member nodes and that
no node is responsible for more than one
np, number of nodes and ring size play a lot into that.
as does your r,w settings.
might be fun to create a visualization one day ;)
On Friday, May 27, 2016, Vikram Lalit wrote:
> Ok got it thanks.
> On May 27, 2016 4:02 PM, "DeadZen" > wrote:
>
>> reiterating my
this might be helpful, an Omniti article.
https://omniti.com/seeds/migrating-riak-do-it-live
As to fixing this specific error. That iirc can be done doing a name change
in the ring to match your new node name. renaming the node will make that
orddict lookup succeed.
Theres a supplied admin utilit
I wasn't referring to a cluster replace. node name/reip change can be
done on all offline nodes before starting them.
They still have a cluster if you dont delete the ring data.
Having done that you actually deleted the cluster, (but not the data) when
all that occurred was an ip address change suc
Definitely an excellent response from Alexander, describing the overall state
My suggestion would be to try at least two approaches and develop a
way to compare them.
Do you want to do statistics? are the entries for those statistics
fairly immutable? it seems TS would be a good choice.
User v
w00t
On Friday, July 8, 2016, Luke Bakken wrote:
> Hi everyone -
>
> I just released version 2.4.0 of the Erlang client. The main feature
> is support for both Riak KV and Riak TS.
>
> https://github.com/basho/riak-erlang-client/releases/tag/2.4.0
>
> https://github.com/basho/riak-erlang-client/
Hinted handoff from adding a node, removing a node or failing a node? Could
probably get some idea from a ring handler, hinted handoff could likely
very well trigger its own event as well without a large modification to
riak_core
On Sunday, July 24, 2016, Sargun Dhillon wrote:
> It might also m
hen Sargun’s “roll your own” idea is the
> better answer at the moment.
>
> On 25 Jul 2016, at 11:25, DeadZen >
> wrote:
>
> > Hinted handoff from adding a node, removing a node or failing a node?
> Could probably get some idea from a ring handler, hinted handoff could
>
Looks right, jmx not imx ;),
and yes provided the erlang kernel options are given to limit dist
comm range to 6000-7999
you can check this from the node (to make sure) with:
> [ application:get_env(kernel, X) || X <-
> [inet_dist_listen_min,inet_dist_listen_max] ].
[{ok,6000},{ok,7999}]
On Sun,
Nope, app.config is actually generated by riak.conf, through an
obscure process known as cuttlefishing ;p
On Mon, Sep 19, 2016 at 3:44 AM, Alex De la rosa
wrote:
> Ok, documentation was confusing, i thought i had to add the data in both
> riak.conf and app.config
>
> Thanks,
> Alex
>
> On Mon, Se
nice post, not a big fan of the proxy design.
On Monday, September 26, 2016, Andra Dinu
wrote:
> Hi,
>
> This post is a story about investigating a struggling Riak cluster,
> finding out why Riak's usual self-healing processes got stuck, and how our
> operations and maintenances tool WombatOAM c
there a backup tool that uses this yet? or is this meant more to be used
with snapshots provided through xfs/zfs?
On Monday, September 26, 2016, Matthew Von-Maszewski
wrote:
> Here are notes on the new hot backup:
>
> https://github.com/basho/leveldb/wiki/mv-hot-backup
>
> This sound like what y
ok I loled at this. then got worries trump could win a node election.
anyways. 24gigs per riak server is not a bad safe bet.
Erlang in general is ram heavy. It uses it more effectively then most
languages wrt concurrency, but ram is the fuel for concurrency and buffer
for operations, especially du
seems not actually a mochiglobal error so much as os_mon reported a system
limit. you can up some of your values in vm.args. max processes/ets table
limits/etc
On Mon,
Jan 9, 2017 at 5:14 AM Steven Joseph wrote:
> Hi Folks,
>
> I've started getting this error in my riak cluster almost periodic
Why are they public?
On Thu, Feb 9, 2017 at 3:11 PM, Alexander Sicular wrote:
> Speaking of timings:
>
> ring_members : ['riak-node1@64.137.190.244','riak-node2@64.137.247.82',
> 'riak-node3@64.137.162.64','riak-node4@64.137.161.229',
> 'riak-node5@64.137.217.73']
>
> Are these nodes in the same
Cheers indeed!
You added HEAD requests so a full GET wouldn't always be required?
Did I read that right? *dives into code*
%% GET requests first follow the path of a HEAD request, and if an object is
%% found, then fetch the value from the Journal via the Inker.
... WHAT?
Very nice work, will be m
not be helpful. Perhaps one of the
> drawbacks of working in isolation on this.
>
> Thanks
>
> Martin
>
>
>
>
> On 28 February 2017 at 16:51, DeadZen wrote:
>
> Cheers indeed!
> You added HEAD requests so a full GET wouldn't always be required?
> Did I read th
I don't see that being alluded to.. An erlang vm, which occupies an os
process runs an instance of the riak application, with a configurable
number of asynchronous threads for io and schedulers for processes
which are internal to erlang, this can be any number of hundreds of
thousands of "light pro
I'd like to keep the core project going, just depends on how much interest
there is.
There are a lot of separate issues and stalled initiatives, if anyone likes
to discuss them. Some have to do simply with scaling Distributed Erlang.
Theres a riak core mailing list as well that probably could use s
1. Yes, A lot of people use haproxy for this.
2. Would be a simple reimplementation of the get/put coordinators from riak
On Sun, Jul 9, 2017 at 5:24 PM, Russell Brown wrote:
>
> On 9 Jul 2017, at 21:54, Lloyd R. Prentice wrote:
>
>> Hello,
>>
>> Just finished viewing Mark Allen's excellent 2015
I am willing to start this asap
On Thu, Jul 13, 2017 at 12:59 PM Russell Brown
wrote:
> Agree.
>
> But at the moment they’re also not dead. Somewhat of a zombie, rumoured to
> be litigious. Circumspection is required.
>
> It’ll happen. Don’t worry.
>
> On 13 Jul 2017, at 17:51, Outback Dingo wr
Awesome! Ill forward details to here for a new fork, mailing list and
academy.
On Thu, Jul 13, 2017 at 1:41 PM Outback Dingo
wrote:
> as I am also ready to pitch in
>
> On Thu, Jul 13, 2017 at 1:38 PM, DeadZen wrote:
> > I am willing to start this asap
> >
> > On Th
Rackspace has provided some resources, love all the feedback.
On Thu, Jul 13, 2017 at 6:01 PM Outback Dingo
wrote:
> I know it was, i saw the smile :) and VMS doesnt run only on alphas
> anymore :) I have both Alpha and Itaniums with OpenVMS on it live
> now.
>
> On Thu, Jul 13, 2017 at 5:57
Riak was and still is a good platform, with the potential to be a
great platform.
I am fairly sure I am not the only one whose staked their reputation
on it.. The name is unimportant.
The question now is where is the focus going to be put next?
To ferret away whatever existing possibly panicking
Lloyd, I too have a great distaste for the cost of those things.
I don't believe that's how developers should be forced to climb the
ladder for knowledge.
Nor do I believe developers should be pushed to create most of the
content for those conferences just to be able to afford attending.
I defini
Hi I setup a sync of the basho repos in github.com/bashosync and the docs
should be in there. I copied labs as well on which I should still have some
access. Let's talk some more on setting up stuff.
On Wed, Aug 16, 2017 at 2:07 PM Gokhan Boranalp wrote:
> Source is in github[1] but i am not sur
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, Russell Brown
> wrote:
> > Hi,
> > I wrote up a blog post about two fixes to riak_core_claim made by/with
> > NHS-Digital.
> >
> >
> https
I'm down for a chat on how to finally get our collective stuff together.
Maybe a google hangout?
On Thu, Aug 17, 2017 at 2:14 PM Gokhan Boranalp wrote:
> Hi all,
>
> I have created a Slack channel. Here is the invitation link[1]
> I think it is better to have a quick talk beforehand in Slack to
yay we won!
now we can improve the closed source stuff too!
Three cheers for bet365
On Thu, Aug 24, 2017 at 2:12 PM David Bloom wrote:
> Thank you for saving this awesome technology. The open source community
> is rejoicing.
>
> On Aug 24, 2017 11:18 AM, wrote:
>
>> Hi
>>
>> I have been aske
Sept 16 is software freedom day, a release that day might be a nice idea.
On Wed, Sep 6, 2017 at 8:37 AM, Christopher Meiklejohn
wrote:
> Given that all of the code except for MDC (and maybe JMX) is under
> Apache 2, I would assume that those components would follow the
> already existing license
gt;>
> >> >>>> +1 Apache 2
> >> >>>>
> >> >>>>
> >> >>>> On Wed, 6 Sep 2017, 18:09 Tom Santero wrote:
> >> >>>>>
> >> >>>>> +1 Apache 2
> >> >>>>
This looks cool, and might give some indication that back pressure
should be aware of available file system space..
Any plans on LevelDB testing? A newer option Leveled might be cool to
compare with as well.
On Tue, Oct 3, 2017 at 6:58 AM, Grigory Fateyev wrote:
> Yury, thank you for sharing your
Great news dude, Ill see if i can run it and report back.
On Thu, Nov 9, 2017 at 10:53 AM Russell Brown wrote:
> Hi,
> I’ve spent a little time lately getting Riak’s `make test` command to
> work. I wrote about it here
>
>
> https://github.com/russelldb/russelldb.github.io/blob/master/make_test.
deadzen on skype, dead...@deadzen.com
On Mon, Feb 5, 2018 at 10:10 AM wrote:
> Just sorting out the logistics of this meeting with Russell - it's going
> to be done over Skype. We need to grab an email address from those who are
> wanting to join in, so we can send out the
w00t! You guys rock
On Fri, May 17, 2019 at 12:27 PM Russell Brown via riak-users <
riak-users@lists.basho.com> wrote:
> Congratulations all! Great news!
>
> On 17/05/2019 16:04, Nicholas Adams wrote:
> >
> > Dear All,
> >
> > I am extremely pleased to announce with Martin Sumner at Code BEAM STO
We all appreciate it, and erring on the side of caution. Thank you.
On Thu, Aug 22, 2019 at 12:22 PM Martin Sumner
wrote:
> Follow-up on this announcement. After further work today, it looks like
> the initial diagnosis of the Issue 1707 was incorrect, and that the defect
> does not obviously
46 matches
Mail list logo
