Are there really no entries after those INFO messages? That indicates that
a person/script/daemon/tool/process killed Cassandra. Perhaps check the OS
logs to see if oom-killer kicked in to see if the C* process was
terminated. Cheers!
>
Thanks Aaron! Appreciate it.
Sushanta
On Wed, Feb 9, 2022 at 11:13 AM Aaron Ploetz wrote:
> > I am starting Cassandra with $CASSANDRA_HOME/bin/cassandra
>
> When starting Cassandra, it accepts a PID file location with the -p flag:
>
> $CASSANDRA_HOME/bin/cassandra -p
> I am starting Cassandra with $CASSANDRA_HOME/bin/cassandra
When starting Cassandra, it accepts a PID file location with the -p flag:
$CASSANDRA_HOME/bin/cassandra -p /var/run/cassandra/cassandra.pid
Start Cassandra with that, and then the PID file will be there. Assuming
of course, that the
Isn't the /etc/init.d/cassandra script supposed to create the PID file
if it doesn't exist? See:
https://github.com/apache/cassandra/blob/cb1c8f9d34edfa639096d2d122dfd0ee6d23b479/debian/init#L83
On 09/02/2022 15:17, Saha, Sushanta K wrote:
I picked up the script */etc/init.d/cassandra* from
I picked up the script */etc/init.d/cassandra* from the net. Not sure if
tarball installation includes such a script. It should.
This script is using the following line:
*pid_file=/var/run/cassandra/cassandra.pid*
But, there is no such *.pid* file that I can find. I am starting Cassandra
with
Nothing in the cassandra logs (system/debug) last lines are
INFO [RMI TCP Connection(10)-127.0.0.1] 2022-02-06 08:41:50,334
BinLog.java:420 - Attempting to configure bin log: Path: /mnt/fql_data Roll
cycle: HOURLY Blocking: true Max queue weight: 268435456 Max log
size:34359738368 Archive
Dear Apache Cassandra community,
we plan to run a large case performance study for Apache Cassandra and
MongoDB where the focus is not to compare both systems directly but to
answer the question: /how much performance can you get out each DBMS
with an optimal configuration compared to the
