> # 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://
p://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/commitlog-replay-missing-data-tp6573659p6580886.html
Sent from the cassandra-u...@incubator.apache.org mailing list archive at
Nabble.com.
> 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,
Hey all,
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
pertaining to the commitlog replay and no errors, but some of the
