cassandra-server/bin$ ./nodetool help
./nodetool: 333: [: Oracle: unexpected operator
usage: nodetool [(-u | --username )]
...
Why might I get the above "unexpected error"?
Thx.
Lou.
looking for: 'nodetool clearsnapshot
> -t nameOfMySnapshot'.
>
> From the documentation here:
> http://cassandra.apache.org/doc/latest/tools/nodetool/clearsnapshot.html?highlight=clearsnapshot
>
> Le lun. 5 nov. 2018 à 13:38, Lou DeGenaro a
> écrit :
>
>> The issue rea
:28 PM Oleksandr Shulgin <
oleksandr.shul...@zalando.de> wrote:
> On Fri, Nov 2, 2018 at 5:15 PM Lou DeGenaro
> wrote:
>
>> I'm looking to hear how others are coping with snapshots.
>>
>> According to the doc:
>> https://docs.datast
I'm looking to hear how others are coping with snapshots.
According to the doc:
https://docs.datastax.com/en/cassandra/3.0/cassandra/operations/opsBackupDeleteSnapshot.html
*When taking a snapshot, previous snapshot files are not automatically
deleted. You should remove old snapshots that are no
Is more information needed, for example from logs or verbose running? Is
anyone else seeing this behaviour?
Thanks.
Lou.
On 2018/10/30 15:36:38, Lou DeGenaro wrote:
> It seems that "nodetool listsnapshots" is unreliable?>
>
> 1. when issued, nodetool listsnapshot
It seems that "nodetool listsnapshots" is unreliable?
1. when issued, nodetool listsnapshots reports there are no snapshops.
2. when navigating through the filesystem, one can see clearly that there
are snapshots
3. when issued, nodetool clearsnapshot removes them!
Some sanitized evidence bel
Hello,
I issue the subject command running Cassandra 2.2.12 and get this response:
Requested clearing snapshot(s) for [all keyspaces] with snapshot name
[1537185517560-rmsharesducc]
But the snapshot does not go away.
degenaro@myhost1:~>
/users1/degenaro/svn/apache/ducc/workspace-trunk/cassandra
Good call! Java client was using Cassandra 2.11 lib jars in classpath.
Switching to Cassandra 3.11 jars in Java client classpath works!
Thx!
Lou.
On Thu, Apr 26, 2018 at 10:30 AM, Michael Shuler
wrote:
> On 04/26/2018 09:17 AM, Lou DeGenaro wrote:
> >
> > I started fresh and
r 26, 2018 at 10:03 AM, Michael Shuler
wrote:
> OK, thanks for the extra info.
>
> Hmm.. `unconfigured table schema_keyspaces`
>
> Seems like an incomplete upgrade to 3.0.9 (and now 3.11.2) from some
> earlier version, which used schema_columnfamilies, I think?
>
> --
> Mich
net $host $port`
> locally and remotely. Were the results expected?
>
> Basically, if using DNS, it has to be right everywhere and a lot of
> people get DNS wrong.
>
> --
> Kind regards,
> Michael
>
> On 04/26/2018 08:17 AM, Lou DeGenaro wrote:
> >
version: cassandra-3.0.9
conf/cassnadra.yaml changes:
>
> - seeds: "host421"
> listen_address: host421
> rpc_address: host421
>
Java client:
package database.tools;
>
> import java.net.InetSocketAddress;
> import java.util.Map;
> import java.util.Map.Entry;
>
> import com.datastax.driv
n searching for
> > Oracle Java options.
> > You will need to consult the IBM documentation in this case.
> >
> > Marcus Haarmann
> >
> >
> > *Von: *"Lou DeGenaro"
> > *An: *"
her suites e.g. to TLS_ECDHE_ECDSA_WITH_AES_
> 256_CBC_SHA384
> (which is a TLS1.2-only cipher suite).
>
> You can check the offered protocols for your server with an open source
> tool like sslyze (https://github.com/nabla-c0d3/sslyze)
>
> Marcus Haarmann
>
> -
Can someone please can tell me how to prevent Cassandra 3.0.9 from
using SSLv2?
Happy to use a newer version of Cassandra if that's what's required.
On Sat, Apr 21, 2018 at 8:30 AM, Lou DeGenaro
wrote:
> 3.0.9
>
> On Fri, Apr 20, 2018 at 10:26 PM, Michael Shuler
> wrote:
3.0.9
On Fri, Apr 20, 2018 at 10:26 PM, Michael Shuler
wrote:
> On 04/20/2018 08:46 AM, Lou DeGenaro wrote:
> > Could you be more specific? What does one specify exactly to assure
> > SSLv2 is not used for both client-server and server-server
> > communications? Example
, Michael Shuler
wrote:
> On 04/20/2018 07:41 AM, Lou DeGenaro wrote:
> > Running Cassandra produces the following error message:
> >
> > "SSLv2Hello is not a recognized protocol"
> >
> > because the JVM being used does not support SSLv2. The JVM does not
>
Running Cassandra produces the following error message:
"SSLv2Hello is not a recognized protocol"
because the JVM being used does not support SSLv2. The JVM does not support
SSLv2 because "it's a HUGE security risk."
How does one configure Cassandra to *not* use SSLv2?
Thanks.
Lou.
Yes, change rpc_address to node B.
Immutability aside, if Node A Cassandra and Node B Cassandra are using the
same directory on the same shared filesystem, let's call it
/cassandra/state/database,
would that not be a problem? Or said differently, does not Node A need its
own writable place /cassa
We use a single instance of Cassandra on Node A that employs a shared file
system to keep its data and logs.
Let's say we want to fail-over to Node B, by editing the yaml file by
changing Node A to Node B. If we now (mistakenly) bring up Cassandra on
Node B whilst the Cassandra on Node A is still
19 matches
Mail list logo
