in the commit directory.
-Original Message-
From: Bowen Song via user
Sent: Friday, September 23, 2022 3:47 PM
To: user@cassandra.apache.org
Subject: Re: Restart Cassandra
EXTERNAL
Did the node finish starting when you checked the "nodetool status"
output? Try "nodetool netstats"
org
Subject: Re: Restart Cassandra
EXTERNAL
Did the node finish starting when you checked the "nodetool status"
output? Try "nodetool netstats" on the starting node, the output will show
"Mode: NORMAL" if it has finished starting. It's also worth checking the
Did the node finish starting when you checked the "nodetool status"
output? Try "nodetool netstats" on the starting node, the output will
show "Mode: NORMAL" if it has finished starting. It's also worth
checking the "nodetool info" output, and make sure "Gossip active" and
"Native Transport act
Hi all,
Restarting the service on a node. Checking status from a remote node, I see:
(prod) marc.hoppins.ipa@ba-cassandra01:~ $ /opt/cassandra/bin/nodetool status
-r|grep 03
UN ba-cassandra09 779.03 GiB 16 ?
1fc8061d-2dd4-4b2c-97fa-e492063da495 SSW09
UN ba-cassandra20 796.94
What anti-pattern are you mocking me for exactly?
Sean Durity
From: daemeon reiydelle [mailto:daeme...@gmail.com]
Sent: Tuesday, February 23, 2016 11:21 AM
To: user@cassandra.apache.org
Subject: RE: Restart Cassandra automatically
Cassandra nodes do not go down "for no reason". Th
Hi Subharaj,
Cassandra is built to be a Fault tolerant distributed db and suitable for
building HA systems. As Cassandra provides multiple replicas for the same data,
if a single nide goes down in Production, it wont bring down the cluster.
In my opinion, if you target to start one or more failed
uesday, February 09, 2016 4:41 PM
> *To:* user@cassandra.apache.org
> *Subject:* Re: Restart Cassandra automatically
>
>
>
> On Tue, Feb 9, 2016 at 6:20 AM, wrote:
>
> Call me naïve, but we do use an in-house built program for keeping nodes
> started (based on a
: Restart Cassandra automatically
On Tue, Feb 9, 2016 at 6:20 AM,
mailto:sean_r_dur...@homedepot.com>> wrote:
Call me naïve, but we do use an in-house built program for keeping nodes
started (based on a flag-check). The program is something that was written for
all kinds of daemon processe
On Tue, Feb 9, 2016 at 6:20 AM, wrote:
> Call me naïve, but we do use an in-house built program for keeping nodes
> started (based on a flag-check). The program is something that was written
> for all kinds of daemon processes here, not Cassandra specifically. The
> basic idea is that is runs a s
: Restart Cassandra automatically
On Thu, Feb 4, 2016 at 8:26 PM, Debraj Manna
mailto:subharaj.ma...@gmail.com>> wrote:
What is the best way to keep cassandra running? My requirement is if for some
reason cassandra stops then it should get started automatically.
I recommend against this m
On Thu, Feb 4, 2016 at 8:26 PM, Debraj Manna
wrote:
> What is the best way to keep cassandra running? My requirement is if for
> some reason cassandra stops then it should get started automatically.
>
I recommend against this mode of operation. When automatically restarting,
you have no idea how
Hi,
What is the best way to keep cassandra running? My requirement is if for
some reason cassandra stops then it should get started automatically.
I tried to achieve this by adding cassandra to supervisord. My supervisor
conf for cassandra looks like below:-
[program:cassandra]
command=/bin/bash
There have been some commitlog-related fixes in later versions of 1.1, so
it's worth trying an upgrade. If that doesn't resolve the issue, open a
JIRA ticket with these details.
On Thu, Aug 9, 2012 at 9:15 AM, Kasun Weranga wrote:
> Any idea on how to fix this?
>
> Thanks,
> Kasun
>
>
> On Wed,
Any idea on how to fix this?
Thanks,
Kasun
On Wed, Aug 8, 2012 at 11:56 AM, Kasun Weranga wrote:
> Hi all,
>
> I am facing the above issue in Cassandra 1.1.0, it will add 134.2MB
> commitlog file in every restart, but it never delete it. We can't control
> the commitlog dir size even
> by expli
Hi all,
I am facing the above issue in Cassandra 1.1.0, it will add 134.2MB
commitlog file in every restart, but it never delete it. We can't control
the commitlog dir size even
by explicitly setting commitlog_total_space_in_mb in cassandra.yaml.
I set commitlog_total_space_in_mb as 512 in cassan
aiting for the
>>>>>> > JVM do decide to GC all remaining references. If there is not enough
>>>>>> > space (to store the total size of the files it is about to write or
>>>>>> > compact) on disk GC is forced and the files are
or
>>>>> compact) on disk GC is forced and the files are deleted. Otherwise they
>>>>> will get deleted at some point in the future.
>>>>> > In 1.0 files are reference counted and space is freed much sooner.
>>>>> > With regard to regula
ed at some point in the future.
>>>>> > In 1.0 files are reference counted and space is freed much sooner.
>>>>> > With regard to regular maintenance, node tool cleanup remvos data from
>>>>> > a node that it is no longer a replica for. This is
;>>> you have done a token move.
>>>> > I would not recommend a daily restart of the cassandra process. You
>>>> will lose all the run time optimizations the JVM has made (i think the
>>>> mapped files pages will stay resident). As well as adding additional
>>>> e
assandra process. You will
>>>> > lose all the run time optimizations the JVM has made (i think the mapped
>>>> > files pages will stay resident). As well as adding additional entropy to
>>>> > the system which must be repaired via HH, RR or nodetool r
the best approach
>>> would be to upgrade to 1.0.
>>> > Hope that helps.
>>> > -----
>>> > Aaron Morton
>>> > Freelance Developer
>>> > @aaronmorton
>>> > http://www.thelastpickle.com
>>> > On 26/01
tional entropy to
>>> > the system which must be repaired via
>>> > HH, RR or nodetool repair.
>>> > If you want to see compacted files purged faster the best approach would
>>> > be to upgrade to 1.0.
>>>
> Can you give a little more details on these 2 lines, what
do they do?
>
> java -jar cmdline-jmxclient-0.10.3.jar - localhost:8080
> java.lang:type=Memory gc
>
> Thank you,
> Mike
>
> -Original Me
;
>> > In his message he explains that it's for " Forcing a GC ". GC stands
>> for garbage collection. For some more background see:
>> http://en.wikipedia.org/wiki/Garbage_collection_(computer_science)
>> > Cheers!
>> >
>> >
helastpickle.com
> > On 26/01/2012, at 9:51 AM, R. Verlangen wrote:
> >
> > In his message he explains that it's for " Forcing a GC ". GC stands for
> > garbage collection. For some more background see:
> > http://en.wikipedia.org/wiki/Garbage_collection_(c
gt; > In his message he explains that it's for " Forcing a GC ". GC stands for
> garbage collection. For some more background see:
> http://en.wikipedia.org/wiki/Garbage_collection_(computer_science)
> > Cheers!
> >
> > 2012/1/25
> >
> > Karl,
> &
omputer_science)
> Cheers!
>
> 2012/1/25
>
> Karl,
>
> Can you give a little more details on these 2 lines, what do they do?
>
> java -jar cmdline-jmxclient-0.10.3.jar - localhost:8080
> java.lang:type=Memory gc
>
> Thank you,
> Mike
>
> -Original Message---
a.org/wiki/Garbage_collection_(computer_science)
>
> Cheers!
>
> 2012/1/25
>
>> Karl,
>>
>> Can you give a little more details on these 2 lines, what do they do?
>>
>> java -jar cmdline-jmxclient-0.10.3.jar - localhost:8080
>> java.lang:t
type=Memory gc
>
> Thank you,
> Mike
>
> -Original Message-
> From: Karl Hiramoto [mailto:k...@hiramoto.org]
> Sent: Wednesday, January 25, 2012 12:26 PM
> To: user@cassandra.apache.org
> Subject: Re: Restart cassandra every X days?
>
>
> On 01/25
2 lines, what do they do?
>
> java -jar cmdline-jmxclient-0.10.3.jar - localhost:8080
> java.lang:type=Memory gc
>
> Thank you,
> Mike
>
> -Original Message-
> From: Karl Hiramoto [mailto:k...@hiramoto.org]
> Sent: Wednesday, January 25, 2012 12:26 PM
> To: user@ca
To: user@cassandra.apache.org
Subject: Re: Restart cassandra every X days?
On 01/25/12 19:18, R. Verlangen wrote:
> Ok thank you for your feedback. I'll add these tasks to our daily
> cassandra maintenance cronjob. Hopefully this will keep things under
> controll.
I forgot to m
Thanks for reminding. I'm going to start with adding the cleanup & compact
to the chain of maintenance tasks. In my opinion java should determine
itselfs when to start a GC: doesn't feel natural to do this manually.
2012/1/25 Karl Hiramoto
>
> On 01/25/12 19:18, R. Verlangen wrote:
>
>> Ok thank
On 01/25/12 19:18, R. Verlangen wrote:
Ok thank you for your feedback. I'll add these tasks to our daily
cassandra maintenance cronjob. Hopefully this will keep things under
controll.
I forgot to mention that we found that Forcing a GC also cleans up some
space.
in a cronjob you can do th
Ok thank you for your feedback. I'll add these tasks to our daily cassandra
maintenance cronjob. Hopefully this will keep things under controll.
2012/1/25 Karl Hiramoto
> On 01/25/12 16:09, R. Verlangen wrote:
>
>> Hi there,
>>
>> I'm currently running a 2-node cluster for some small projects th
I also do repair, compact and cleanup every couple of days, and also
have daily restarts on
crontab. It doesn't hurt and I avoid having a node becoming unresponsive
after many days
of operation, that has happened before. Older files get cleaned up on
restart.
It doesn't take long to shut down
On 01/25/12 16:09, R. Verlangen wrote:
Hi there,
I'm currently running a 2-node cluster for some small projects that
might need to scale-up in the future: that's why we chose Cassandra.
The actual problem is that one of the node's harddrive usage keeps
growing.
For example:
- after a fresh
Hi there,
I'm currently running a 2-node cluster for some small projects that might
need to scale-up in the future: that's why we chose Cassandra. The actual
problem is that one of the node's harddrive usage keeps growing.
For example:
- after a fresh restart ~ 10GB
- after a couple of days runni
37 matches
Mail list logo
