>> It is a serious issue if you really need to repair one CF at the time. > > Why is it serious to do repair one CF at a time, if I cannot do that it at a > CF level, then does it mean that I cannot use more than 50% disk space? Is > this specific to this problem or is that a general statement? I ask because > I am planning on doing this so I can limit the max disk overhead to be a CF > (+ some factor) worth. I am going to be testing this in the next couple of > weeks or so.
The bug in 0.7 is causes data to be streamed for all CF:s when doing a repair on one. So, if you specifically need to repair a specific CF at a time, such as because you're trying to repair a small CF quite often while leaving a huge CF with less frequent repairs, you have an issue. If you're just wanting to repair the entire keyspace, it doesn't affect you. I'm not sure how this relates to the 50% disk space bit though. -- / Peter Schuller (@scode on twitter)
