Managing rapid data growth in MySQL Cluster

[Daniel Nita]

I am trying to use MySQL Cluster in a high-availability solution where there's a constant influx of data into one table. Only a couple days worth of this data needs to be retained at any time, the rest can be safely pruned from the table.

A typical solution would be to partition the table by date range and then simply drop partitions whose data has become too old. Unfortunately this doesn't seem to be possible with the NDB storage engine as it uses partitioning for data sharding and DROP PARTITION is not even available (see http://dev.mysql.com/doc/refman/5.6/en/mysql-cluster-limitations-syntax.html)

Has anyone faced this issue of pruning old data while maintaining high-availability and come up with a creative solution that they'd like to share?

Thanks in advance