mmm, my bad there.
First schema changes are always flushed to disk, so the commit log is not
really an issue.
Second when the commit log replays it just processes the mutations, the "Drop
keyspace” message comes from MigrationManager.announceKeyspaceDrop() and is not
called.
If you can rep
Do you have the logs from after the restart ?
Did it include a "Drop Keyspace…” INFO level message ?
Cheers
-
Aaron Morton
New Zealand
@aaronmorton
Co-Founder & Principal Consultant
Apache Cassandra Consulting
http://www.thelastpickle.com
On 4/12/2013, at 2:44 am, Desimpel, I
jstack shows that all the mutation stages are blocked on a synchronization:
"MutationStage:1" prio=10 tid=0x2aaabc01b000 nid=0x27b8 waiting
for monitor entry [0x42048000]
java.lang.Thread.State: BLOCKED (on object monitor)
at org.apache.cassandra.db.Table.apply(Table.java:4
> # wait for a bit until no one is sending it writes anymore
More accurately, until all other nodes have realized it's down
(nodetool ring on each respective host).
--
/ Peter Schuller (@scode on twitter)
> What are the other ways to stop Cassandra?
nodetool disablegossip
nodetool disablethrift
# wait for a bit until no one is sending it writes anymore
nodetool flush # only relevant if in periodic mode
# then kill it
> What's the difference between batch vs periodic?
Search for "batch" on http://
Peter Schuller wrote:
>
>> Recently upgraded to 0.8.1 and noticed what seems to be missing data
>> after a
>> commitlog replay on a single-node cluster. I start the node, insert a
>> bunch
>> of stuff (~600MB), stop it, and restart it. There are log messages
>
> If you stop by a kill, make sure
> Recently upgraded to 0.8.1 and noticed what seems to be missing data after a
> commitlog replay on a single-node cluster. I start the node, insert a bunch
> of stuff (~600MB), stop it, and restart it. There are log messages
If you stop by a kill, make sure you use batched commitlog synch mode
in
Have you verified that data you expect to see is not in the server after
shutdown?
WRT the differed in the difference between the Memtable data size and SSTable
live size, don't believe everything you read :)
Memtable live size is increased by the serialised byte size of every column
inserted,
how long the default flush expiry period is?
>
> Cheers,
> Steve
>
> -Original Message-
> From: sc...@scode.org [mailto:sc...@scode.org] On Behalf Of Peter Schuller
> Sent: Tuesday, June 21, 2011 9:13 AM
> To: user@cassandra.apache.org
> Subject: Re: CommitLog replay
&
nd how long the default flush expiry period is?
Cheers,
Steve
-Original Message-
From: sc...@scode.org [mailto:sc...@scode.org] On Behalf Of Peter Schuller
Sent: Tuesday, June 21, 2011 9:13 AM
To: user@cassandra.apache.org
Subject: Re: CommitLog replay
> I’ve got a single node deploy
> I’ve got a single node deployment of 0.8 set up on my windows box. When I
> insert a bunch of data into it, the commitlogs directory doesn’t clear upon
> completion (should it?).
It is expected that commit logs are retained for a while, and that
there is reply going on when restarting a node. Th
11 matches
Mail list logo
