[CASSANDRA-8986] Major cassandra-stress refactor

• Type: Improvement
• Status: Resolved
• Priority: Normal
• Resolution: Later
• Component/s: Feature/Lightweight Transactions, Legacy/Tools
• Labels: LWT stress
• Assignee: Unassigned
• Reporter: Benedict Elliott Smith
• Created: 18/Mar/15 11:50
• Updated: 25/Oct/19 13:11
• Resolved: 21/Dec/16 13:30

Description

We need a tool for both stressing and validating more complex workloads than stress currently supports. Stress needs a raft of changes, and I think it would be easier to deliver many of these as a single major endeavour which I think is justifiable given its audience. The rough behaviours I want stress to support are:

• Ability to know exactly how many rows it will produce, for any clustering prefix, without generating those prefixes
• Ability to generate an amount of data proportional to the amount it will produce to the server (or consume from the server), rather than proportional to the variation in clustering columns
• Ability to reliably produce near identical behaviour each run
• Ability to understand complex overlays of operation types (LWT, Delete, Expiry, although perhaps not all implemented immediately, the framework for supporting them easily)
• Ability to (with minimal internal state) understand the complete cluster state through overlays of multiple procedural generations
• Ability to understand the in-flight state of in-progress operations (i.e. if we're applying a delete, understand that the delete may have been applied, and may not have been, for potentially multiple conflicting in flight operations)

I think the necessary changes to support this would give us the functional base to support all the functionality I can currently envisage stress needing. Before embarking on this (which I may attempt very soon), it would be helpful to get input from others as to features missing from stress that I haven't covered here that we will certainly want in the future, so that they can be factored in to the overall design and hopefully avoid another refactor one year from now, as its complexity is scaling each time, and each time it is a higher sunk cost. jbellis iamaleksey slebresne tjake enigmacurry aweisberg blambov jshook ... and @everyone else

Issue Links

• is duplicated by: CASSANDRA-9091 Cassandra-stress should support map column type
• is related to: CASSANDRA-8780 cassandra-stress should support multiple table operations
• relates to: CASSANDRA-8500 Improve cassandra-stress help pages
• relates to: CASSANDRA-8601 cassandra-stress yaml profiles should support all -pop and -insert options
• relates to: CASSANDRA-8987 cassandra-stress should support a more complex client model
• relates to: CASSANDRA-8600 Refactor stress options to reduce prominence of legacy modes (counter_read, etc.)