Hi Ajay, honestly I would try to fix the main issue:
Sometimes, the cassandra-process gets killed (reason unknown as of now).
As focusing on how to restart Apache Cassandra every minute sounds like a
wrong approach to me:
Adding this in cron would at least ensure that the maximum downtime is 5
Yes, but it is legitimate to supervise and monitor nodes. I only doubt that
cron is the best tool for it.
2017-01-12 7:42 GMT+01:00 Martin Schröder :
> 2017-01-12 6:12 GMT+01:00 Ajay Garg :
> > Sometimes, the cassandra-process gets killed (reason unknown as of now).
>
> That's why you have a clus
2017-01-12 6:12 GMT+01:00 Ajay Garg :
> Sometimes, the cassandra-process gets killed (reason unknown as of now).
That's why you have a cluster of them.
Best
Martin
I think you should take a look at supervisord or sth similar. This is a
much more reliable solution than using crons.
Am 12.01.2017 06:12 schrieb "Ajay Garg" :
On Wed, Jan 11, 2017 at 8:29 PM, Martin Schröder wrote:
> 2017-01-11 15:42 GMT+01:00 Ajay Garg :
> > Tried everything.
>
> Then try
>
Hi Hannu.
On Wed, Jan 11, 2017 at 8:31 PM, Hannu Kröger wrote:
> One possible reason is that cassandra process gets different user when run
> differently. Check who owns the data files and check also what gets written
> into the /var/log/cassandra/system.log (or whatever that was).
>
Absolutely
On Wed, Jan 11, 2017 at 8:29 PM, Martin Schröder wrote:
> 2017-01-11 15:42 GMT+01:00 Ajay Garg :
> > Tried everything.
>
> Then try
>service cassandra start
> or
>systemctl start cassandra
>
> You still haven't explained to us why you want to start cassandra every
> minute.
>
Hi Martin.
One possible reason is that cassandra process gets different user when run
differently. Check who owns the data files and check also what gets written
into the /var/log/cassandra/system.log (or whatever that was).
Hannu
> On 11 Jan 2017, at 16.42, Ajay Garg wrote:
>
> Tried everything.
> Ever
2017-01-11 15:42 GMT+01:00 Ajay Garg :
> Tried everything.
Then try
service cassandra start
or
systemctl start cassandra
You still haven't explained to us why you want to start cassandra every minute.
Best
Martin
Tried everything.
Every other cron job/script I try works, just the cassandra-service does
not.
On Wed, Jan 11, 2017 at 8:51 AM, Edward Capriolo
wrote:
>
>
> On Tuesday, January 10, 2017, Jonathan Haddad wrote:
>
>> Last I checked, cron doesn't load the same, full environment you see when
>> yo
On Tuesday, January 10, 2017, Jonathan Haddad wrote:
> Last I checked, cron doesn't load the same, full environment you see when
> you log in. Also, why put Cassandra on a cron?
> On Mon, Jan 9, 2017 at 9:47 PM Bhuvan Rawal > wrote:
>
>> Hi Ajay,
>>
>> Have you had a look at cron logs? - mine is
Last I checked, cron doesn't load the same, full environment you see when
you log in. Also, why put Cassandra on a cron?
On Mon, Jan 9, 2017 at 9:47 PM Bhuvan Rawal wrote:
> Hi Ajay,
>
> Have you had a look at cron logs? - mine is in path /var/log/cron
>
> Thanks & Regards,
>
> On Tue, Jan 10, 20
Hi Ajay,
Have you had a look at cron logs? - mine is in path /var/log/cron
Thanks & Regards,
On Tue, Jan 10, 2017 at 9:45 AM, Ajay Garg wrote:
> Hi All.
>
> Facing a very weird issue, wherein the command
>
> */etc/init.d/cassandra start*
>
> causes cassandra to start when the command is run fr
12 matches
Mail list logo
