Re: [ANN] Riak 2.9.0 - Release Candidate 1 Available

2019-02-04 Thread Bryan Hunt
under the assumption that he had no additional >> resources to play with. >> >> Nicholas >> >> From: riak-users >> <mailto:riak-users-boun...@lists.basho.com> On Behalf Of Fred Dushin >> Sent: 01 February 2019 22:47 >> To: riak-users@lists.basho.com &l

Re: [ANN] Riak 2.9.0 - Release Candidate 1 Available

2019-02-01 Thread Guido Medina
ption that he had no additional resources to play with. Nicholas *From:* riak-users *On Behalf Of *Fred Dushin *Sent:* 01 February 2019 22:47 *To:* riak-users@lists.basho.com *Subject:* Re: [ANN] Riak 2.9.0 - Release Candidate 1 Available Wouldn't it be better to do a `riak-admin

Re: [ANN] Riak 2.9.0 - Release Candidate 1 Available

2019-02-01 Thread Fred Dushin
o additional > resources to play with. > > Nicholas > > From: riak-users On Behalf Of Fred Dushin > Sent: 01 February 2019 22:47 > To: riak-users@lists.basho.com > Subject: Re: [ANN] Riak 2.9.0 - Release Candidate 1 Available > > Wouldn't it be better to do a `riak

RE: [ANN] Riak 2.9.0 - Release Candidate 1 Available

2019-02-01 Thread Nicholas Adams
: [ANN] Riak 2.9.0 - Release Candidate 1 Available Wouldn't it be better to do a `riak-admin replace`? Leave could be problematic if there are other nodes in the cluster that are under-provisioned (disk space, for example). Plus a leave and add would move the data around the cluster twice

Re: [ANN] Riak 2.9.0 - Release Candidate 1 Available

2019-02-01 Thread Fred Dushin
Hunt > Sent: 01 February 2019 19:22 > To: Guido Medina > Cc: riak-users@lists.basho.com > Subject: Re: [ANN] Riak 2.9.0 - Release Candidate 1 Available > > Replication would be the optimum solution - in theory anything can be > implemented - but it would be enormously painful in

RE: [ANN] Riak 2.9.0 - Release Candidate 1 Available

2019-02-01 Thread Nicholas Adams
process. Best regards, Nicholas From: riak-users On Behalf Of Bryan Hunt Sent: 01 February 2019 19:22 To: Guido Medina Cc: riak-users@lists.basho.com Subject: Re: [ANN] Riak 2.9.0 - Release Candidate 1 Available Replication would be the optimum solution - in theory anything can be implemented

Re: [ANN] Riak 2.9.0 - Release Candidate 1 Available

2019-02-01 Thread Bryan Hunt
> <mailto:riak-users-boun...@lists.basho.com> On Behalf Of Martin Sumner >> Sent: 30 January 2019 21:07 >> To: riak-users@lists.basho.com <mailto:riak-users@lists.basho.com> >> Subject: [ANN] Riak 2.9.0 - Release Candidate 1 Available >> >> All, >>

Re: [ANN] Riak 2.9.0 - Release Candidate 1 Available

2019-02-01 Thread Guido Medina
that they can be fixed before the final release. Best regards, Nicholas *From:* riak-users *On Behalf Of *Martin Sumner *Sent:* 30 January 2019 21:07 *To:* riak-users@lists.basho.com *Subject:* [ANN] Riak 2.9.0 - Release Candidate 1 Available All, There is now a publicly available release

RE: [ANN] Riak 2.9.0 - Release Candidate 1 Available

2019-01-30 Thread Nicholas Adams
, Nicholas From: riak-users On Behalf Of Martin Sumner Sent: 30 January 2019 21:07 To: riak-users@lists.basho.com Subject: [ANN] Riak 2.9.0 - Release Candidate 1 Available All, There is now a publicly available release candidate for Riak 2.9.0 for users to test in their own environment. The release

[ANN] Riak 2.9.0 - Release Candidate 1 Available

2019-01-30 Thread Martin Sumner
All, There is now a publicly available release candidate for Riak 2.9.0 for users to test in their own environment. The release candidate is available to build from source here - https://github.com/basho/riak/tree/riak-2.9.0rc1 There is only one significant change to Riak 2.2.6 for users maintai