Howdy all, this has been solved, and don't want to waste anyone's time. Just changed it in /usr/sbin/cassandra, and that fixed that problem.
Thank you for reading, and for everyone's continual contribution to this community! Kindest regards, Daniel On Wed, Apr 15, 2020 at 7:02 PM Daniel Kleviansky <dank...@gmail.com> wrote: > Hello everyone, > > I'm running Cassandra 2.2.15 on RHEL, and I've come across an interesting > issue when trying to get a certain Elasticsearch plugin to work. > > The plugin needs to know where the Cassandra data is stored, and gets this > parameter from the JVM option, -Dcassandra.storagedir > > While Cassandra is running fine, having set the data storage directory in > the cassandra.yaml, things are being written to and from perfectly, > however, when viewing my running JVM options, I have > "-Dcassandra.storagedir=", as in, its empty. > > This makes the ES plugin fail, as it can't detect where Cassandra data is > being stored. > Writing this parameter directly into the JVM with the cassandra-env.sh > file "works", but I then end up with two entries... One that has the > correct directory, and one without, still causing it to fail. > > This occurs with just a normal Cassandra installation, before anything > "extra or fancy" is added. > > Might anyone have any ideas? > > Kindest regards, > Daniel >
