Re: supervisord and cassandra

FWIW, if you are using something like supervisor to ensure that cassandra auto-starts if it crashes, you should be aware that there are good reasons to not do that. https://issues.apache.org/jira/browse/CASSANDRA-2356 Discusses some of the cases, but it basically sums to "starting a distributed s

Re: supervisord and cassandra

e: >> >>> Hi, >>> >>> Using now oracle 7. commented out the line StringTableSize=103 >>> same issue. but nothing in the log file now. >>> >>> but I start from, the command line the works. >>> >> >> What user are you ru

Re: supervisord and cassandra

So.. see the rest of my replies for a working configuration, but I wanted to reply to your initial post. What problem are you trying to solve, and why do you think using supervisord to restart a failed c* node will help? You really don't want a node to be bouncing up and down.. A de

Re: supervisord and cassandra

java -ea -javaagent:/opt/cassandra/bin/../lib/jamm-0.2.5.jar -XX:+UseThreadPriorities <...> and in the supervisor log: 2014-02-14 20:42:23,067 INFO daemonizing the supervisord process 2014-02-14 20:42:23,067 INFO supervisord started with pid 2777 2014-02-14 20:42:24,072 INFO spawned: '

Re: supervisord and cassandra

On 02/14/2014 08:27 PM, Michael Shuler wrote: On 02/14/2014 08:10 PM, Michael Shuler wrote: mshuler@debian:~$ sudo supervisorctl status cassandra_server:cassandra FATAL Exited too quickly (process log may have details) I imagine the problems all stem from the fact that the initializ

Re: supervisord and cassandra

On 02/14/2014 08:10 PM, Michael Shuler wrote: mshuler@debian:~$ sudo supervisorctl status cassandra_server:cassandra FATAL Exited too quickly (process log may have details) I imagine the problems all stem from the fact that the initializing script, in my case, /opt/cassandra/bin/ca

Re: supervisord and cassandra

d the attached conf - stopped/started supervisord to pick up the new conf - c* is running fine and nodetool confirms - supervisorctl status shows ignorance of c* running (wrong config, I assume) I missed a couple steps in here: - killed c* and supervisor never restarted it - restarted supervisor se

Re: supervisord and cassandra

, when running from the command line? What user is running c* via supervisord? So you peaked my interest and tried supervisord in a vm. I think you need to probably go hit up the supervisord community for some "how do I do this correctly" questions. Attached a console log and the c

Re: supervisord and cassandra

user is running c* via supervisord? -- Michael

Re: supervisord and cassandra

Hi, Using now oracle 7. commented out the line StringTableSize=103 same issue. but nothing in the log file now. but I start from, the command line the works. Thanks On Fri, Feb 14, 2014 at 9:48 AM, Michael Shuler wrote: > On 02/13/2014 07:03 PM, David Montgomery wrote: > >> I only

Re: supervisord and cassandra

On 14 February 2014 03:03, David Montgomery wrote: > I only added the -f flag after the first time it did not work. If I dont > use the -f flag. > > cassandra_server:cassandra FATAL Exited too quickly (process log > may have details) Whoops, I got mixed up; the -f param to Cassand

Re: supervisord and cassandra

On 02/13/2014 07:03 PM, David Montgomery wrote: I only added the -f flag after the first time it did not work. If I dont use the -f flag. cassandra_server:cassandra FATAL Exited too quickly (process log may have details) From your original message: > Unrecognized VM option 'St

Re: supervisord and cassandra

Hi, I only added the -f flag after the first time it did not work. If I dont use the -f flag. cassandra_server:cassandra FATAL Exited too quickly (process log may have details) On Thu, Feb 13, 2014 at 11:25 PM, Tristan Seligmann wrote: > On 13 February 2014 11:39, David Montg

Re: supervisord and cassandra

On 13 February 2014 11:39, David Montgomery wrote: > [program:cassandra] > command = /var/apache-cassandra-<%=@version%>/bin/cassandra -f I'm not familiar with supervisor specifically, but most process supervisors want the supervised process not to fork; that is, remove the -f from the command he

Re: supervisord and cassandra

Thanks, do you have a sample of the defaults? I just dont understand why from the command line it works but not from supervisor thanks [include] files = *.supervisor [supervisord] pidfile = /var/run/supervisord.pid nodaemon=false [supervisorctl] serverurl=unix:///var/run/supervisord.sock

Re: supervisord and cassandra

Hi David, We've had no problems running C* with supervisor, and your conf.d file is broadly similar to ours. I don't think those errors are anything to do with supervisor. We did however have issues starting C* with the recommended resource limits

supervisord and cassandra

omg..wow...can cassandra run under supervisor? this works from the command line as root /var/apache-cassandra-<%=@version%>/bin/cassandra -f this does not work. why? [program:cassandra] command = /var/apache-cassandra-<%=@version%>/bin/cassandra -f #environment=JVM_EXTRA_OPTS="-Dcom.sun.manage

Supervisord

Hi there, Is anyone using Supervisord to manage starting/stopping Cassandra? I was wondering what command and stopsignal instructions you might be using. Cheers, mark