Skip to content
DataMiner DoJo

More results...

Generic selectors
Exact matches only
Search in title
Search in content
Post Type Selectors
Search in posts
Search in pages
Search in posts
Search in pages
Log in
Menu
  • Updates & Insights
  • Questions
  • Learning
    • E-learning Courses
    • Empower Replay: Limited Edition
    • Tutorials
    • Open Classroom Training
    • Certification
      • DataMiner Fundamentals
      • DataMiner Configurator
      • DataMiner Automation
      • Scripts & Connectors Developer: HTTP Basics
      • Scripts & Connectors Developer: SNMP Basics
      • Visual Overview – Level 1
      • Verify a certificate
    • Video Library
    • Books We Like
    • >> Go to DataMiner Docs
  • Expert Center
    • Solutions & Use Cases
      • Solutions
      • Use Case Library
    • Markets & Industries
      • Media production
      • Government & defense
      • Content distribution
      • Service providers
      • Partners
      • OSS/BSS
    • Agile
      • Agile Webspace
      • Everything Agile
        • The Agile Manifesto
        • Best Practices
        • Retro Recipes
      • Methodologies
        • The Scrum Framework
        • Kanban
        • Extreme Programming
      • Roles
        • The Product Owner
        • The Agile Coach
        • The Quality & UX Coach (QX)
    • DataMiner DevOps Professional Program
      • About the DevOps Program
      • DataMiner DevOps Support
  • Downloads
  • More
    • DataMiner Releases & Updates
    • Feature Suggestions
    • Climb the leaderboard!
    • Swag Shop
    • Contact
    • Global Feedback Survey
  • PARTNERS
    • All Partners
    • Technology Partners
    • Strategic Partner Program
    • Deal Registration
  • >> Go to dataminer.services

Can I execute the compaction in only 1 DB Table? Advantages and dissadvantages?

Solved1.29K views23rd November 2021Cassandra compaction database
3
Arturo Lizcano [SLC] [DevOps Member]385 16th September 2020 0 Comments

Following  the line of this question:

https://community.dataminer.services/question/how-necessary-is-cassandra-compaction-as-it-requires-a-lot-of-resources/answer/21921/

In case a table is too big in the Cassandra database, can I execute the compaction only on that table? If so:

  • Will the system use the same amount of resources for one table? (Compaction will take all available RAM even for a short period of time.)
  • Will it be efficient to do this? (If in the end, we have to do a big DB compaction once a week, this doesn't seem to be a good use of resources.)

Any other advantages/disadvantages that you can point out?

Arturo Lizcano [SLC] [DevOps Member] Selected answer as best 23rd November 2021

1 Answer

  • Active
  • Voted
  • Newest
  • Oldest
5
Brent [SLC]1.57K Posted 16th September 2020 1 Comment

Is it possible? yes. Will it be more efficient? Probably not.

Cassandra will still take all the resources it needs to process the SSTables for a certain table, for a smaller table it might be possible that the system will use less resources but the larger tables will definitely use the same amount as with the full keyspace-compaction. So instead of having 1 big time window of high-resource usage, you will have a lot of short but equally resource intensive moments.

Efficiency wise, it will be a tad less efficient. During a full compaction cassandra can process multiple tables at the same time (if resources permit it), single table compaction will do one at a time, so the total time spent is expected to be bigger.

A big disadvantage here will be the administrative overhead. Dataminer can create/remove database tables on the fly (loggertables), which you will need to add/remove manually to the schedule. If there is a new table added in a software update, you will need to schedule this as well. Making the whole process error prone.

In the end, by doing compaction per table you would end up with more resource intensive moments, more time spent per complete compaction cycle and a more error prone process due to the administrative overhead.

Arturo Lizcano [SLC] [DevOps Member] Selected answer as best 23rd November 2021
Robin Devos [SLC] [DevOps Advocate] commented 18th September 2020

In addition to Brent’s answer, for a couple of customers, we had to execute compactions per table because there was insufficient disk space.

SizeTieredCompactionStrategy is used, which requires you to have at least 50% of the Cassandra data to be available as free disk space.
The ‘Cassandra data’ being the entire keyspace size in case of a regular “full” compaction or being a single table in case of compacting a single table.

You are viewing 1 out of 1 answers, click here to view all answers.
Please login to be able to comment or post an answer.

My DevOps rank

DevOps Members get more insights on their profile page.

My user earnings

0 Dojo credits

Spend your credits in our swag shop.

0 Reputation points

Boost your reputation, climb the leaderboard.

Promo banner DataMiner DevOps Professiona Program
DataMiner Integration Studio (DIS)
Empower Katas
Privacy Policy • Terms & Conditions • Contact

© 2025 Skyline Communications. All rights reserved.

DOJO Q&A widget

Can't find what you need?

? Explore the Q&A DataMiner Docs

[ Placeholder content for popup link ] WordPress Download Manager - Best Download Management Plugin