Including myself, I count 8 +1 votes and no -1 votes for this release.
I'll get the release published!
--
Kind regards,
Michael
On 10/05/2016 06:09 PM, Michael Shuler wrote:
> I propose the following artifacts for release as 2.1.16.
>
> sha1: 87034cd05964e64c6c925597279865a40a8c152f
> Git:
> ht
trunk:
===
testall: 2 failures
org.apache.cassandra.service.RemoveTest
.testLocalHostId
CASSANDRA-9541.
org.apache.cassandra.db.KeyspaceTest
.testLimitSSTables
New failure. Needs a jira ticket.
===
Hi Romain,
I appreciate you speaking up about this, but I stuck with my +1 in
order to get 2.1.16 with the NTR fix out since I have seen
CASSANDRA-11363 with every recent client installation. Also, running
the patch in production produced results satisfactory enough to me to
preclude the need for e
Nate, do think CASSANDRA-12758 should go to 2.1.x?
--
Michael
On 10/10/2016 02:26 PM, Nate McCall wrote:
> Hi Romain,
> I appreciate you speaking up about this, but I stuck with my +1 in
> order to get 2.1.16 with the NTR fix out since I have seen
> CASSANDRA-11363 with every recent client insta
It's too minor for a re-roll, and safe enough to just apply yourself if you
want it.
On Mon, Oct 10, 2016 at 2:44 PM, Michael Shuler
wrote:
> Nate, do think CASSANDRA-12758 should go to 2.1.x?
>
> --
> Michael
>
> On 10/10/2016 02:26 PM, Nate McCall wrote:
> > Hi Romain,
> > I appreciate you spe
> It's too minor for a re-roll, and safe enough to just apply yourself if you
> want it.
Agreed.
>
> On Mon, Oct 10, 2016 at 2:44 PM, Michael Shuler
> wrote:
>
>> Nate, do think CASSANDRA-12758 should go to 2.1.x?
>>
>> --
>> Michael
>>
>> On 10/10/2016 02:26 PM, Nate McCall wrote:
>> > Hi Romai
I also agree this is minor and did not intend to re-roll.
My question is whether CASSANDRA-12758 should go to to the
'cassandra-2.1' branch and be tagged with fixver of '2.1.x' in JIRA? Is
this minor improvement satisfactory for a the critical-only nature of
the 2.1 branch and go into the next 2.1
It's simple and very low risk, I wouldn't be adverse to it since 11363 is
in 2.1.
On Mon, Oct 10, 2016 at 3:55 PM, Michael Shuler
wrote:
> I also agree this is minor and did not intend to re-roll.
>
> My question is whether CASSANDRA-12758 should go to to the
> 'cassandra-2.1' branch and be tagg
The Cassandra team is pleased to announce the release of Apache
Cassandra version 2.1.16.
Apache Cassandra is a fully distributed database. It is the right choice
when you need scalability and high availability without compromising
performance.
http://cassandra.apache.org/
Downloads of source a
Hi Cassandra users,
We are trying to upgrade our Cassandra version from 2.2.5 to 3.0.8 (running
on Mesos, but that's besides the point). We have two datacenters, so in
order to preserve our data, we are trying to upgrade one datacenter at a
time.
Initially both DCs (dc1 and dc2) are running 2.2.5
You can't stream between major versions. Don't tear down your first data
center, upgrade it instead.
On Mon, Oct 10, 2016 at 4:35 PM Abhishek Verma wrote:
> Hi Cassandra users,
>
> We are trying to upgrade our Cassandra version from 2.2.5 to 3.0.8
> (running on Mesos, but that's besides the point
FYI there is an everywhere strategy waiting to be accepted:
https://issues.apache.org/jira/browse/CASSANDRA-12629
On Sat, 8 Oct 2016 at 10:56 Vladimir Yudovin wrote:
Well, it can be useful in some scenarios - e.g. temporary tables on nearest
or the same node.
Best regards, Vladimir Yudovin,
12 matches
Mail list logo
