that's why disabling gossip + flush is better than drain. we should
probably remove it.
drain could be good if there is way to undrain node - to switch it back
into r/w.
Implement nodetool shutdown which will work like we are trying. First
stop gossip then wait for other nodes to see it dow
: Radim Kolar [mailto:h...@sendmail.cz]
> Sent: November-08-11 6:29
> To: user@cassandra.apache.org
> Subject: Re: shutdown by KILL
>
>> Ooops, sorry about that. I overlooked the drain. Sorry for the
>> misinformation!
>>
> cassandra still replays log file even on clean
that's why disabling gossip + flush is better than drain. we should
probably remove it.
On Tue, Nov 8, 2011 at 6:38 PM, Radim Kolar wrote:
> drain switches node into read only, which is undesirable because other nodes
> still see it up.
>
--
Jonathan Ellis
Project Chair, Apache Cassandra
co-
drain switches node into read only, which is undesirable because other
nodes still see it up.
cassandra.apache.org
Subject: Re: shutdown by KILL
> Ooops, sorry about that. I overlooked the drain. Sorry for the misinformation!
>
cassandra still replays log file even on clean shutdown via nodetool
drain. It usually takes a while. I don't think it has concept of
clean-shutdown lik
Ooops, sorry about that. I overlooked the drain. Sorry for the misinformation!
cassandra still replays log file even on clean shutdown via nodetool
drain. It usually takes a while. I don't think it has concept of
clean-shutdown like SQL databases.
> nodetool drain flushes memtables before returning. its probably safe to kill
> it after drain without waiting for commit log flush.
Ooops, sorry about that. I overlooked the drain. Sorry for the misinformation!
--
/ Peter Schuller (@scode, http://worldmodscode.wordpress.com)
THEN, after that point, you have to wait for the 10 seconds to be
reasonably sure the commit log has been flushed.
nodetool drain flushes memtables before returning. its probably safe to
kill it after drain without waiting for commit log flush.
> sleep 10 seconds
If you are trying to prevent writes being lost in the typical case,
you need to wait *first* for all nodes to understand that the node is
down (as Chris mentioned). At that point, no node should be sending it
new writes. Assuming you also disabled the thrift interface, no writes
> If i kill Java process and log flush time is set to 10 seconds, will be last
> 10 seconds lost?
Up to, plus whatever delay resulting from scheduling jitter/overload/etc.
--
/ Peter Schuller (@scode, http://worldmodscode.wordpress.com)
For things like rolling restarts, we do:
disablethrift
disablegossip
(...wait for all nodes to see this node go down..)
drain
i implemented this in our batch scripts for cassandra
disablegossip
sleep 10 seconds
dissablethrift
drain
KILL -TERM
similar thing should be added to bin/stop-server
For things like rolling restarts, we do:
disablethrift
disablegossip
(...wait for all nodes to see this node go down..)
drain
2011/9/10 Radim Kolar
> what is recommended node stop method. drain or kill Java process? i haven't
> seen anybody using drain in stop scripts yet
>
> If i kill Java pro
12 matches
Mail list logo
