Hi
Are there any plans to support Java 8 for Cassandra 2.0, now that Java 7 is EOL?
Currently Java 7 is also recommended for 2.1. Are there any reasons not to
recommend Java 8 for 2.1?
Thanks,
Stefan
Multiple inserts for the same partition key within a batch will be consolidated
into a single row update operation (since 2.0.6,
#6737https://issues.apache.org/jira/browse/CASSANDRA-6737). Ie. you get the
same row level isolationhttp://www.datastax.com/dev/blog/row-level-isolation
guarantees
This seems to be a good opportunity to dig a bit deeper into certain
operational aspects of NTP. Some things to be aware of:
How NTP Operates [1]
It can take several minutes before ntpd will update the system time for the
first time, while all processes are already started. This can be
We are also extending our backwards compatibility policy to cover all 3.x
releases: you will be able to upgrade seamlessly from 3.1 to 3.7, for
instance, including cross-version repair.
What will be the EOL policy for releases after 3.0? Given your example, will
3.1 still see bugfixes at
Hi Hannu
It should be as simple as copying the archived commit logs to the recovery
directory, specifying the point in time you like to restore from the logs
by using the 'restore_point_in_time' setting and afterwards starting the
node.
On Tue, Jan 10, 2017 at 7:45 PM, Hannu Kröger
If someone would create a benchmark showing that Cassandra is 10x faster
than Aerospike, would that mean Cassandra is 100x faster than ScyllaDB?
Joking aside, I personally don't pay a lot of attention to any published
benchmarks and look at them as pure marketing material. What I'm
interested in
I've been thinking about this for a while, but haven't found a practical
solution yet, although the term "fire drill" leaves a lot of room for
interpretation. The most basic requirements I'd have for these kind of
trainings would start with automated cluster provisioning for each
scenario (either
the steps how you can get a cluster into the situation which has
> been described
> in the scenario.
>
> Hope it’s a bit clearer now what I mean.
>
> Is there some kind of community space where we could start a
> document for this purpose?
>
> Best,
I think what this error indicates is that a client is trying to connect
using a SSLv2Hello handshake, while this protocol has been disabled on
the server side. Starting with the mentioned ticket, we use the JVM
default list of enabled protocols. What makes this issue a bit
confusing, is that
I'd not recommend using any consistency level but serial for reading
tables updated by LWT operations. Otherwise you might end up reading
inconsistent results.
On 09.02.18 08:06, Mahdi Ben Hamida wrote:
>
> Hello,
>
> I'm running a 2.0.17 cluster (I know, I know, need to upgrade) with 46
> nodes
Deleting data "without undue delay" in Cassandra can be implemented by
using crypto shredding and pseudonymization strategies in your data
model. All you have to do is to make sure that throwing away a person's
data encryption key will make it impossible to restore personal data and
impossible to
You may want to keep an eye on the following ticket:
https://issues.apache.org/jira/browse/CASSANDRA-13404
On 09.07.2018 17:12, Vitali Dyachuk wrote:
> Hi,
> There is a certificate validation based on the mutual CA this is a 1st
> factor, the 2nd factor could be checking the common name of the
The hard-coded protocol selection has been remove in one of the 3.x
releases. You may want to consider updating to the latest 3.11 release.
On 24.04.18 19:21, Lou DeGenaro wrote:
> Here's is what I was told by IBM JVM Support:
>
> ...the string "SSLv2Hello" is not supported in IBM JVM but
13 matches
Mail list logo
