Sure thing Abdul,
That's great to hear! Unfortunately, the JMX authentication needs to be in
the config file currently. And even if the JMX authentication was stored
within Cassandra, we would still need to store connection details within
the yaml and storing the JMX authentication credentials
Thanks Joaquin,
Yes i used the same and worked fine ..only thing is i had to add userid
password ..which is somewhat annoyoing to keep in comfig file ..can i get
reed of it and still store on reaper_db keyspace?
Also how to clean reaper_db by deleting completed reaper information from
gui? Or any
Hello Abdul,
Depending on what you want your backend to be stored on, you'll want to use
a different file.
So if you want your Reaper state to be stored within a Cassandra cluster,
which I would recommend, use this file as your base file:
Thanks
But the differnce here is cassandra-reaper-caasandra has more paramters
than the cassandra-reaper.yaml
Can i just use the 1 file with all details or it looks for one specific
file?
On Tuesday, April 24, 2018, Joaquin Casares
wrote:
> Hello Abdul,
>
> You'll
Hello Abdul,
You'll only want one:
The yaml file used by the service is located at
/etc/cassandra-reaper/cassandra-reaper.yaml and alternate config templates
can be found under /etc/cassandra-reaper/configs. It is recommended to
create a new file with your specific configuration and symlink it
Hi All,
For reaper do we need both file or only one?
Cassandra.reaper.yaml
Cassandra-reaper-cassandra.yaml
Thank you, Rahul!
From: Rahul Singh
Sent: Saturday, April 21, 2018 3:02:11 PM
To: user@cassandra.apache.org
Subject: Re: copy from one table to another
That’s correct.
On Apr 21, 2018, 5:05 AM -0400, Kyrylo Lebediev
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
Here's is what I was told by IBM JVM Support:
...the string "SSLv2Hello" is not supported in IBM JVM but
> more importantly, the protocol SSLv2 is no longer a valid protocol in
> our JVM.
> We don't even have SSLv3 enabled by default due to the HIGH severity
> vulnerabilities this protocol has.
>
Correct!
Thanks for the trace, Lou.
SSLFactory.java:67 specifies a list of protocols, including SSLv2Hello.
"It [IBM JSSE] does not support specifying SSLv2Hello."
OK, this is IBM JDK. The options might differ. I have been searching for Oracle
Java options.
You will need to consult the IBM documentation in this case.
Marcus Haarmann
Von: "Lou DeGenaro"
An: "user"
Gesendet: Dienstag, 24. April 2018
Hi Ahmed,
The java driver docs do a good job explaining how the driver uses paging,
including providing a sequence diagram that describes the flow of the
process:
https://docs.datastax.com/en/developer/java-driver/3.5/manual/paging/
The driver requests X rows (5000 by default, controlled via
I think I would start with the JVM. Sometimes, for export purposes, the
cryptography extensions (JCE), are in a separate jar or package from the
standard JRE or JVM. I haven’t used the IBM JDK, so I don’t know specifically
about that one.
Also, perhaps the error is correct – SSLv2Hello is not
Hello,
Can someone explain me how paging is implemented ?
according to the doc of datastax, the goal being to avoid loading much
results in memory.
Does it mean that the whole partition is not upload to heap memory?
C* version: 2.1
Java Driver version: 3.0
Best regards
Thanks for your suggestions. I tried using the -D shown below:
degenaro@bluej421:/users/degenaro/cassandra/bluej421> ./bin/cassandra
> degenaro@bluej421:/users/degenaro/cassandra/bluej421> numactl
> --interleave=all /share/ibm-jdk1.8/bin/java
> -Dhttps.protocols=TLSv1.2,TLSv1.1,SSLv2Hello
Hi,
I did take a look into the source code of 3.11, but I believe the code is more
or less the same.
The SSL code makes use of Java SSL Sockets so you can limit the protocols in
the "Java way".
The java way (at least for a recent Java 8) is to setup the protocols in the
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
I'm trying to integrate Apache Ignite with Apache Cassandra(3.11.2) as I want
to use Ignite to cache the data present in my already existing Cassandra
database.
After going through the online resources, I've done the following till now:
1. Downloaded Apache
18 matches
Mail list logo