Subscribe to Posts by Email

Subscriber Count

    701

Disclaimer

All information is offered in good faith and in the hope that it may be of use for educational purpose and for Database community purpose, but is not guaranteed to be correct, up to date or suitable for any particular purpose. db.geeksinsight.com accepts no liability in respect of this information or its use. This site is independent of and does not represent Oracle Corporation in any way. Oracle does not officially sponsor, approve, or endorse this site or its content and if notify any such I am happy to remove. Product and company names mentioned in this website may be the trademarks of their respective owners and published here for informational purpose only. This is my personal blog. The views expressed on these pages are mine and learnt from other blogs and bloggers and to enhance and support the DBA community and this web blog does not represent the thoughts, intentions, plans or strategies of my current employer nor the Oracle and its affiliates or any other companies. And this website does not offer or take profit for providing these content and this is purely non-profit and for educational purpose only. If you see any issues with Content and copy write issues, I am happy to remove if you notify me. Contact Geek DBA Team, via geeksinsights@gmail.com

Pages

Cassandra for Oracle DBA’s Part 16 : Shutting Down Best Practices

Shutdown Best Practice While Cassandra is crash-safe, you can make a cleanershutdown and save some time during startup thus:

- Make other nodes think this one is down. 

- nodetool -h $(hostname) -p 8080 disablegossip

- Wait a few secs, cut off anyone from writing to this node. 

- nodetool -h $(hostname) -p 8080 dissablethrift

- Flush all memtables to disk. 

- nodetool -h $(hostname) -p 8080 drain

- Shut it down.

- /etc/init.d/cassandra stop

 

Comments are closed.