>
> Can you please provide dome JIRAs for superior fixes and performance
> improvements which are present in 3.11.1 but are missing in 3.0.15.
>
>
For the security conscious, CASSANDRA-11695 allows you to use Cassandra's
authentication and authorization to lock down JMX/nodetool access instead
of
Thanks a lot for the info!
Much appreciated.
On Tue, Jan 9, 2018 at 2:33 AM, Mick Semb Wever
wrote:
>
>
>> Can you please provide dome JIRAs for superior fixes and performance
>> improvements which are present in 3.11.1 but are missing in 3.0.15.
>>
>
>
> Some that come
>
> Can you please provide dome JIRAs for superior fixes and performance
> improvements which are present in 3.11.1 but are missing in 3.0.15.
>
Some that come to mind…
Cassandra Storage Engine: CASSANDRA-12269, CASSANDRA-12731
Streaming and Compaction: CASSANDRA-11206, CASSANDRA-9766,
Hi,
Can you please provide dome JIRAs for superior fixes and performance
improvements which are present in 3.11.1 but are missing in 3.0.15.
In addition,could you also provide the probable implications of the open
memory leak issue in Cassandra 3.11.
CASSANDRA-13929: BTree$Builder /
There’s a tweak to TWCS in 3.11.1 that lets data expire faster, but I wouldn’t
call it unstable in any version I’ve ever used it with. I’ve deployed it on
2.0, 2.1, 2.2 [1], and used it in every version of C* that we’ve shipped it,
and have never had an issue.
I would put 3.11.1 in prod
Thanks Guys!
Sorry for the late reply.
I'm interested in TWCS where I understand is more stable in 3.11.1 than in
3.0.15, tombstone compaction and slow logs.
I don't plan to use MVs and SASI in the near future, as I understand are
not Production ready.
Is it okay to use the above features?
>
> I want to upgrade from 2.x to 3.x.
>
> I can definitely use the features in 3.11.1 but it's not a must.
> So my question is, is 3.11.1 stable and suitable for Production compared
> to 3.0.15?
>
Use 3.11.1 and don't use any 3.0.x or 3.x features.
3.11.1 is effectively three sequential patch