[root#PPWFMD509 bin]# ./cassandra -f
Unrecognized VM option 'StringTableSize=1000003'
Could not create the Java virtual machine.
running on jdk1.6_11 version.
If it is Cassandra 2 then it needs JDK 1.7.
Related
When I try to start up Cassandra DB under windows 10, It complains about the Java version:
Cassandra 3.0 and later require Java 8u40 or later.
I believe I have the latest Java installed:
java --version
java 13.0.2 2020-01-14
Java(TM) SE Runtime Environment (build 13.0.2+8)
Java HotSpot(TM) 64-Bit Server VM (build 13.0.2+8, mixed mode, sharing)
I've installed Apache Cassandra 3.11.9 (the open source version not the Datastax version).
Why doesn't Cassandra recognize this version of Java? Do I need to install a different version of Java to get this working?
Yes, you need to install Java 8 to run Cassandra 3.11 - it will not work with Java 13 (yes, I understand that error message isn't clear). Support for Java > 8 was added only to Cassandra 4.0, that is currently in beta.
Also, on Windows it would be easier to use Docker to run Cassandra - there are different difficulties with running Cassandra on Windows.
I am trying to install Cassandra 3.11.6 in Windows 10. I have set the environment variables and my current java version is 1.8.0_241. When I run the command "cassandra -f" in command prompt I'm getting the below message.
WARNING! Powershell script execution unavailable.
Please use 'powershell Set-ExecutionPolicy Unrestricted'
on this user-account to run cassandra with fully featured
functionality on this platform.
Starting with legacy startup options
Starting Cassandra Server
Unrecognized VM option 'UseParNewGC'
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.
How can I get Cassandra to work ? Am I missing something ?
I am trying to get Cassandra to work on Linux Mint and I follow these instructions on Youtube (https://www.youtube.com/watch?v=pGhkX5z_vW8&list=PLalrWAGybpB-L1PGA-NfFu2uiWHEsdscD&index=4). They are the same like in the documentation:
JRE is openjdk version 1.8.0_242.
Cassandra is version 3.11.
My system is Linux Mint 19.3.
After starting Cassandra, I get this in my console:
There seems to be two problems, although I think if I fix one, I fix both:
(1) after "sudo service cassandra status" --> active (exited) should be active (running)
(2) after "nodetool status" --> Conncetion refused
Any idea? Thanks
I don't know, if this is a common problem or because of my ignorance. I could not make Cassandra work via Debian packages, but the INSTALLATION VIA BINARY TARBALL FILES worked fine on my machine. Here is the link to the official homepage:
https://cassandra.apache.org/doc/latest/getting_started/installing.html
You should check listen_address and rpc_address whether it is default or server IP if not you have to update the IP address then try nodetool status with host. It should work.
I am running Cassandra 2.2.14 on a virtual machine (CentOS). The issue is that I cannot run the command "cqlsh" to create tables and keyspaces.
when I was tipping at the terminal:
cqlsh localhost ks-schema-local.cql
bash shell :
bash: cqlsh: command not found
cf) java version:
openjdk version "1.8.0_201"
OpenJDK Runtime Environment (build 1.8.0_201-b09)
OpenJDK 64-Bit Server VM (build 25.201-b09, mixed mode)
How can I solve this issue?
is cassandra installation directory is in your classpath?, add cassandra bin directory to your classpath, or execute from bin location.
First install Cassandra to your computer, then go to bin directory and type:
./cqlsh
It should work if Cassandra is running in the default port (9160).
I have a brand new Windows 10 Home installation, with a brand-new installation of JDK 10.0.1 (which is what Oracle recommended when I went to the JDK download site.) I just now downloaded Cassandra 3.11.2, un-tar'd it, and put the bin directory on my classpath.
When I attempt to start Cassandra using the cassandra -f command, I get this error:
PS C:\javatools> cassandra -f
*---------------------------------------------------------------------*
*---------------------------------------------------------------------*
WARNING! Automatic page file configuration detected.
It is recommended that you disable swap when running Cassandra
for performance and stability reasons.
*---------------------------------------------------------------------*
*---------------------------------------------------------------------*
Failed 64-bit check. Re-running to get version from 32-bit
*---------------------------------------------------------------------*
*---------------------------------------------------------------------*
Cassandra 3.0 and later require Java 8u40 or later.
Java 10 is clearly "Java 8 rel 40 or later". I verified that I was, in fact, running the version of Java I thought I was:
PS C:\javatools> java -version
java version "10.0.1" 2018-04-17
Java(TM) SE Runtime Environment 18.3 (build 10.0.1+10)
Java HotSpot(TM) 64-Bit Server VM 18.3 (build 10.0.1+10, mixed mode)
How can I get Cassandra to recognize that I do, in fact, have "Java 8u40 or later"?
Cassandra does not support any Java release newer than Java 8.
References are as follows:
declined bug report against Java 9: CASSANDRA-9608
declined bug report against Java 10: CASSANDRA-14446
Furthermore, even though the documentation does indicate it's a "work in progress", it does indicate the following on the Getting Started page:
Prerequisites
The latest version of Java 8, either the Oracle Java Standard Edition
8 or OpenJDK 8. To verify that you have the correct version of java
installed, type java -version.
While it doesn't explicitly say "Java 9 and newer are not supported", this is apparently supposed to be inferred from this indicator.
Finally, the misleading error message appears to be a wontfix item.
I've managed to run cassandra 3.11.3 on java-11-openjdk-amd64 on localhost (ubuntu 18.04).
(Strangely, java -version shows openjdk version "10.0.1" 2018-04-17)
I tweaked a lot in jvm.options, because many gc options are not supported anymore, and ThreadPriorityPolicy could not be set to 42. (last thing is most annoying: it was really good compaction threads were low priority).
Also, to run nodetool I have to specify jvm 1.8 by JAVA_HOME.