PLANNED MAINTENANCE

Hello, DataStax Community!

We want to make you aware of a few operational updates which will be carried out on the site. We are working hard to streamline the login process to integrate with other DataStax resources. As such, you will soon be prompted to update your password. Please note that your username will remain the same.

As we work to improve your user experience, please be aware that login to the DataStax Community will be unavailable for a few hours on:

  • Wednesday, July 15 16:00 PDT | 19:00 EDT | 20:00 BRT
  • Thursday, July 16 00:00 BST | 01:00 CEST | 04:30 IST | 07:00 CST | 09:00 AEST

For more info, check out the FAQ page. Thank you for being a valued member of our community.


question

cache_drive avatar image
cache_drive asked ·

How To Automate Cleanups & Repairs?

I have just been learning Cassandra from using my home lab w/ v3.x however the reason is I've been handed a very old v1.2 ring which is live in production (yes, I know!). From time to time, we (DBA team) have to do cleanups and repairs on the keySpaces. My questions is, how do you automate or simplify this process? It's a nightmare for the DBA. We have to SSH to each server, fire up a screen session because it takes so long, SSH will time out and finally run the command and wait until the prompt is returned to the bash shell and move on to the next node in the ring. Each node can take over 1hr time and we are scaling so as time goes on, this process becomes more unmanageable. Appreciate any and all suggestions on how to perform DBA maintenance that is smarter, not harder.

repaircleanupmaintenancedbanotdevops
10 |1000 characters needed characters left characters exceeded

Up to 8 attachments (including images) can be used with a maximum of 1.0 MiB each and 10.0 MiB total.

1 Answer

Erick Ramirez avatar image
Erick Ramirez answered ·

@cache_drive as you know, Apache Cassandra 1.2 is no longer supported so your options are limited. Not sure what you mean by "cleanups". If you're running nodetool cleanup, could you provide some background info? It isn't normal for a DBA to perform that on a regular basis -- it's usually only done when you have changed the cluster topology (added a node for example).

As far as repairs are concerned, we generally recommend using the OpsCenter Repair Service. But since C* 1.2 is no longer supported, I would suggest running nodetool repair -pr one node a time (not parallel) and schedule it via cron once a week. For more details on the -pr flag, see the blog post Repair in Cassandra. Cheers!

Share
10 |1000 characters needed characters left characters exceeded

Up to 8 attachments (including images) can be used with a maximum of 1.0 MiB each and 10.0 MiB total.