Based on lots of good feedback from this list, I moved to a date-based set of tables, which a unique per day. However, I am manually compacting previous days' tables to keep the amount of files required to be opened to a minimum.
I ran into an interesting issue--when I run compaction on a table that is already compacted, it still, well... compacts. The table's TTL is set to 0, there are no deletes or other writes to these tables, and I confirmed (on disk) that there was only a single set of files. There are no changes pending in memory for this table, either. Why is compaction being performed on a table that has no changes? Are there other reasons for compaction to be re-run, or does the compact command to nodetool just blindly do what it's told? Andrew
