On Fri, Oct 8, 2010 at 2:12 AM, Peter Schuller
wrote:
>> If your C* process dies and/or is killed you should not lose data. It's
>> written to the commit log before the client is acked, however that entry may
>> not have made it to disk yet in the case of commitlogsync=periodic. So, if
>> you ki
> If your C* process dies and/or is killed you should not lose data. It's
> written to the commit log before the client is acked, however that entry may
> not have made it to disk yet in the case of commitlogsync=periodic. So, if
> you kill the C* process you're fine. If you nicely restart the O
dnesday, October 06, 2010 8:53 PM
> *To:* user@cassandra.apache.org
> *Subject:* Re: Newbie Question about restarting Cassandra
>
>
>
> Rob is correct.
>
> drain is really on there for when you need the commit log to be empty (some
> upgrades or a complete backup of a shutdown cluster).
&g
Are there any data loss concerns if you have the commit log sync set to
periodic and are writing with CL One or Any?
From: Matthew Dennis [mailto:mden...@riptano.com]
Sent: Wednesday, October 06, 2010 8:53 PM
To: user@cassandra.apache.org
Subject: Re: Newbie Question about restarting
Rob is correct.
drain is really on there for when you need the commit log to be empty (some
upgrades or a complete backup of a shutdown cluster).
There really is no point to using to shutdown C* normally, just kill it...
On Wed, Oct 6, 2010 at 4:18 PM, Rob Coli wrote:
> On 10/6/10 1:13 PM, Aar
On 10/6/10 1:13 PM, Aaron Morton wrote:
To shutdown cleanly, say in a production system, use nodetool drain
first. This will flush the memtables and put the node into a read only
mode, AFAIK this also gives the other nodes a faster way of detecting
the node is down via the drained node gossiping
To shutdown cleanly, say in a production system, use nodetool drain first. This will flush the memtables and put the node into a read only mode, AFAIK this also gives the other nodes a faster way of detecting the node is down via the drained node gossiping it's new status. Then kill. AaronOn 07 Oct
Some relevant reading if you're interested:
http://dslab.epfl.ch/pubs/crashonly/
http://web.archive.org/web/20060426230247/http://crash.stanford.edu/
On Wed, Oct 6, 2010 at 1:46 PM, Scott Mann wrote:
> Yes. ctrl-C if running in the foreground. Use kill , if running
> in the background (see the
Yes. ctrl-C if running in the foreground. Use kill , if running
in the background (see the man page for kill if you are unfamiliar
with it). Killing Cassandra is the only way to terminate it.
On Wed, Oct 6, 2010 at 11:03 AM, Alberto Velandia wrote:
> So, is ctrl + C how you stop cassandra? or I'm
So, is ctrl + C how you stop cassandra? or I'm i better doing it another way?
Thanks
On Oct 6, 2010, at 11:59 AM, Norman Maurer wrote:
> CTRL + Z does not stop a programm it just suspend it. You will need to
> resume it with "fg" and then hit CTRL + C to stop it.
>
> For some basic background:
CTRL + Z does not stop a programm it just suspend it. You will need to
resume it with "fg" and then hit CTRL + C to stop it.
For some basic background:
http://linuxreviews.org/beginner/jobs/
Bye,
Norman
2010/10/6 Alberto Velandia :
> Hi I've stopped cassandra hitting Ctrl + Z and tried to rest
Hi I've stopped cassandra hitting Ctrl + Z and tried to restart it and got this
message:
INFO 11:46:16,039 JNA not found. Native methods will be disabled.
INFO 11:46:16,159 DiskAccessMode 'auto' determined to be mmap, indexAccessMode
is mmap
ERROR 11:46:16,449 Fatal exception during initializa
12 matches
Mail list logo
