> That is correct. In 0.6, an anticompaction was performed and a temporary > SSTable was written out to disk, then streamed to the recipient. The way > this is now done in 0.7 requires no extra disk space on the source node.
Great. So that should at least mean that running out of diskspace should always be solvable in terms of the cluster by adding news in between other pre-existing nodes. That is provided that the internal node issues (allowing compaction to take place to space can actually be freed) are solved in some way. And assuming the compaction redesign happens at some point, that should be a minor issue because it should be easy to avoid the possibility of getting to the point of not fitting a single (size limited) sstable. -- / Peter Schuller
