[CASSANDRA-14765] Evaluate Recovery Time on Single Token Cluster Test

• Type: Sub-task
• Status: Resolved
• Priority: Normal
• Resolution: Done
• Component/s: Legacy/Streaming and Messaging
• Assignee: Sumanth Pasupuleti
• Reporter: Joey Lynch

Authors

Sumanth Pasupuleti

• Created: 19/Sep/18 01:55
• Updated: 16/Apr/19 09:29
• Resolved: 10/Apr/19 21:18

Description

Setup:

• Cassandra: 6 (2*3 rack) node i3.8xlarge AWS instance (32 cpu cores, 240GB ram) running cassandra trunk with Jason's 14503 changes vs the same footprint running 3.0.17
• One datacenter, single tokens
• No compression, encryption, or coalescing turned on

Test #1:

ndbench loaded ~150GB of data per node into a LCS table. Then we killed a node and let a new node stream. With a single token this should be a worst case recovery scenario (only  a few peers to stream from).

Result:

As the table used LCS and we didn't not have encryption on, the zero copy transfer was used via CASSANDRA-14556. We recovered 150GB in 5 minutes, going at a consistent rate of about 3 gigabit per second. Theoretically we should be able to get 10 gigabit, but this is still something like an estimated 16x improvement over 3.0.x. We're still running the 3.0.x test for a hard comparison.

Follow Ups:
We need to get more rigorous measurements (over more terminations), as well as finishing the 3.0.x test. sumanth.pasupuleti and djoshi3 are driving this.