Subscribe to Posts by Email

Subscriber Count

    699

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 10: Commit Logs (Managing Archivelogs & Redlogs)

Archive Logs & Redologs (commit logs)  Parameters that need to effect.

commitlog_directory: /root/.ccm/geek_cluster/node1/commitlogs

commitlog_directory: /root/.ccm/geek_cluster/node1/commitlogs

commitlog_segment_size_in_mb: 32

commitlog_sync: periodic

commitlog_sync_period_in_ms: 10000

/.ccm/geek_cluster/node1/resources/cassandra/conf/commitlog_archiving.properties file to keep archive_command

Argument 1 will give you the path to the files you'd want to copy, while 

Argument 2 will give uou the name if it. You can then create a command:

archive_command=/bin/bash /home/cassandra/scripts/cassandra-archive.sh %path %name

The above would be an example for me. As the commands by default only  execute 1 command, I have them point to a custom script that does what I  desire.

My script then looks something like this:

#! /bin/bash

# use bzip to compress the file

bzip2 --best -k $1

# move to commit log archive

mv $1.bz2 $HOME/commitlog_restore/$2.bz2

I compress my commitlog and then move it somewhere else. Cassandra will call this operation first, and then delete the commitlog. You can apply similar behaviours to all of those commands.

Comments are closed.