On Mon, Mar 29, 2010 at 6:42 PM, Tatu Saloranta <tsalora...@gmail.com> wrote:
> Perhaps it would be good to have convenience workflow for replacing
> broken host ("squashing lemons")? I would assume that most common use
> case is to effectively replace host that can't be repaired (or perhaps
> it might sometimes be best way to do it anyway), by combination of
> removing failed host, bringing in new one. Handling this is as
> high-level logical operation could be more efficient than doing it
> step by step.Does anyone have numbers on how badly "nodetool repair" sucks vs bootstrap + removetoken? If it's within a reasonable factor of performance, then I'd say that's the easiest solution.
