bin/cassandra is hardwired to run CassandraDaemon and in some instances it is
necessary to run a custom "main" for a particular installation
--------------------------------------------------------------------------------------------------------------------------------------------
Key: CASSANDRA-1819
URL: https://issues.apache.org/jira/browse/CASSANDRA-1819
Project: Cassandra
Issue Type: Improvement
Affects Versions: 0.7.0 rc 1
Reporter: B. Todd Burruss
In my particular case we use Zabbix as a monitoring tool and it requires an
agent to run in the JVM. so the solution is to start the agent, then call
CassandraDaemon.main.
my solution for a more generic "bin/cassandra" script is to check if a
CLASSNAME is provided in the environment. if so use it, if not use the default
CassandraDaemon.
patch attached.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
